4027 replies to this topic

[toxie]

also, @all: please check the script editor carefully if there are any quirks, cause this is the first update of SciLexerVP in >5 years i think

[onemanproject]

 

Thank you for the update. But i think that the table loading times are still to long. Can you this accelerate ?

compared to 10.6, or in general?

 

VP 10.7 beta (Rev.: 4255)

[fourbanks]

also, @all: please check the script editor carefully if there are any quirks, cause this is the first update of SciLexerVP in >5 years i think

the script editor is fine as far as i can see ?

Edited by fourbanks, 24 July 2020 - 06:09 PM.

[jpsalas]

Save as is not working in 4255

Neither does the Export Mesh (single object export mesh)

Edited by jpsalas, 24 July 2020 - 06:18 PM.

[Robsoie]

 

If that's what it takes, why not? Do you have ideas/suggestions what we could do on the VPM or VPX side to make this more efficient to access?

Instead of dynamically calling a snippet of code 

SolCallback(10) = "setLamp 100,"

SolCallback(11) = "raiseRamp "

should instead be something like:

 

sub HandleSolCallback(num, value) 

    select case num

        case 10:  SetLamp 100, value

        case 11: RaiseRamp value

   end select

end sub

 

And then changing the solenoid handler to just call HandleSolCallback.

 

This avoids a dynamic script execution which will probably perform much better under security paranoia conditions because I strongly suspect that the AMSI is being invoked to check every dynamic call (for obvious reasons, it's ideal for obfuscating nefarious behavior).   But again, to do this will require changing all tables, it's not something you can just take care of in the core scripts.     Probably could do a proof of concept by disabling UseSolenoids and writing a sub that reads the solenoid states the way the core script does, on a table that's currently performing poorly with AV enabled.   

 

 

This would be very interesting to see if it could completely solve the stutters on some tables affected by it.

[fuzzel]

rev4257 is up:

 

- fix return value for sz2f() conversion function
- fix showing the export save dialog for a primitive mesh
 

 

Update: The previous build has a small error in a string to float conversion function. That creates really strange problems especially when you enter a value in the elements properties but the value is changed to 0 instead of the entered one. So better you don't use rev4255 at all

Edited by fuzzel, 24 July 2020 - 06:40 PM.

[onemanproject]

rev4257 is up:

 

- fix return value for sz2f() conversion function
- fix showing the export save dialog for a primitive mesh
 

 

Update: The previous build has a small error in a string to float conversion function. That creates really strange problems especially when you enter a value in the elements properties but the value is changed to 0 instead of the entered one. So better you don't use rev4255 at all

Okay thank you

[fourbanks]

rev4257 is up:

 

- fix return value for sz2f() conversion function
- fix showing the export save dialog for a primitive mesh
 

 

Update: The previous build has a small error in a string to float conversion function. That creates really strange problems especially when you enter a value in the elements properties but the value is changed to 0 instead of the entered one. So better you don't use rev4255 at all

it appears ok with save working on adjusting the minor scripts like ball light strength etc 

[trizoneGB]

on newest vpx beta build and clicking on import pov seems to crash vpx for me. thanks guys!!

[toxie]

 

 

Thank you for the update. But i think that the table loading times are still to long. Can you this accelerate ?

compared to 10.6, or in general?

 

VP 10.7 beta (Rev.: 4255)

 

Damn.. I already updated our threading lib for that rev (4255).. So too bad that this still happens for you with the latest revisions.. :/

[toxie]

on newest vpx beta build and clicking on import pov seems to crash vpx for me. thanks guys!!

Fixed, thanks!!

[toxie]

Save as is not working in 4255

Neither does the Export Mesh (single object export mesh)

"Save as" (and Export->Blueprint) also fixed, thanks!

[jpsalas]

Thanks toxie and here it is another crash with the latest version. The crash happened when I had changed a few flashers and pressed F5 to run the table:

 

Crash report VPX rev4257

============

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:3F3F3F3F

Attempt to read from 0x3F3F3F3F

Thread ID: 0x504 [1284]

 

Call stack

==========

3F3F3F3F  (0x32A8ECC0 0x0019D980 0x0074F568 0x0019d9ec)

004D0EC7 VPinballX.exe (0x123F47E0 0x00000000 0x123244E8 0x123244e8)

6B89896E vbscript.dll (0x00000000 0x0019DA38 0x6B89D86B 0x123244e8)

6B89880B vbscript.dll (0x123244E8 0x252F6160 0x0DA9A620 0x00425c80)

6B89D86B vbscript.dll (0x123244E8 0x00000002 0x252F6160 0x00361592)

00556E0F VPinballX.exe (0x0000C238 0x252F6160 0x00000000 0x00020818)

00553071 VPinballX.exe (0x0000C238 0x252F6160 0x00425C80 0xffffffffffffffbc)

00426483 VPinballX.exe (0x0000C238 0x00000000 0x00000000 0x00361592)

00565BB6 VPinballX.exe (0x0000C238 0x00000000 0x00000000 0x0000c238)

00425CCF VPinballX.exe (0x00425C80 0x00361592 0x0000C238 0x00000000)

751C67BC user32.dll CallWindowProcW + 0xB2C (0x00425C80 0x00000000 0x0000C238 0x00000000)

751C58FB user32.dll DispatchMessageW + 0x23B (0x751B69B0 0x005B0A16 0x0019E80C 0x0019ff24)

751BBC50 user32.dll DispatchMessageA + 0x10 (0x0019E80C 0x0019FF24 0x0025C000 0x00000000)

005B0A16 VPinballX.exe (0x00000000 0x00000001 0x0025C000 0x0075ab50)

005B0B9B VPinballX.exe (0x00000001 0x0025C000 0x0075AB50 0x00000000)

 

Environment

===========

Date/time: 26/7/2020, 15:46:04:240

Number of CPUs: 8

Processor type: 586

System: Windows 10 (10.0 17763)

 

Memory status

=============

Total Reserved: 249264K (243M) bytes

Total Commited: 1096560K (1070M) bytes

Total Free: 2848416K (2781M) bytes

Largest Free: 2095424K (2046M) bytes

 

Registers

=========

EAX=FFFE0300 EBX=00000001 ECX=32A8ECC0 EDX=0002020D

ESI=00000000 EDI=333C43A0 EBP=0000038D ESP=0019E82C EIP=005B0B9B

FLG=00210206 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B

 

 

Mini dump saved successfully.

[jpsalas]

Here it is another crash while pressing F5 to run a table. I guess it is very similar to the last one.

 

Crash report VPX rev4257

============

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:07D37C48

Attempt to read from 0x07D37C48

Thread ID: 0x15D4 [5588]

 

Call stack

==========

07D37C48  (0x07D37DD0 0x00000001 0x18841328 0x07d37c48)

 

Environment

===========

Date/time: 28/7/2020, 07:03:26:214

Number of CPUs: 8

Processor type: 586

System: Windows 10 (10.0 17763)

 

Memory status

=============

Total Reserved: 254060K (248M) bytes

Total Commited: 788436K (769M) bytes

Total Free: 3151744K (3077M) bytes

Largest Free: 2095468K (2046M) bytes

 

Registers

=========

EAX=00000000 EBX=0019D9EC ECX=0B4AC8E0 EDX=0002020E

ESI=0019D980 EDI=0B4AC8E0 EBP=00000000 ESP=0019D9B4 EIP=6C5C6583

FLG=00210246 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B

 

 

Failed to save minidump.

[toxie]

Are these 2 new issues (i.e. only happening with latest builds) or did such things occur already for longer?

[kiwi]

If you can have the option "Visible" for the lights, in the light properties panel,

in order not to break the compatibility, I think that by default it should be visible.

 

Thanks.

[fuzzel]

If you can have the option "Visible" for the lights, in the light properties panel,
in order not to break the compatibility, I think that by default it should be visible.
 
Thanks.

Why you need a visible option for a light? The intensity option can be used for that.

[jpsalas]

Are these 2 new issues (i.e. only happening with latest builds) or did such things occur already for longer?

 

They are new to me. They happen when I pressed F5 to run the table after editing some flashers.

[kiwi]

 

If you can have the option "Visible" for the lights, in the light properties panel,
in order not to break the compatibility, I think that by default it should be visible.
 
Thanks.

Why you need a visible option for a light? The intensity option can be used for that.

 

It is not really necessary, but in some cases it could simplify the control of lights via script, having more options does not hurt (if it is possible).

 
If it could be useful,
I saw that the Playmatic/Inder rollovers also have a short version, I modified the previous rollover to make the short one, so the z position is around -35.
In the zip I also put the rollovers for Zaccaria, one normal and one short, the z position for these is 0.
 Rollovers.zip   3.66KB   1 downloads

[Bushav]

Can there be added an option to set the font size in the F6 mode where we set the inclination and stuff ? on the 4k monitor it is really tiny to see.

 

 

I second this "wish list"