1488 replies to this topic

[jpsalas]

I guess the number of frames will be limited to the intenger max value which is 2,147,483,647, but who is gone build a reel image with so many frames

[NailBuster]

The new video display settings with the display number does not work correctly on my cab.

 

It shows Display 3* which is my correct primary monitor, but does not list the correct display modes available for that display.    The correct modes are being shown under display 1.   But display 1 is my DMD so VPX tries to start in 4k there.   Not good.  

I know most people have their primary display as #1, but I can't set mine that way.   #1 is the DVI-I/VGA output that I need for my DMD display.

 

With latest files, i have exact same graphics issue.  My PF is windows display #1 but GPU display #3.  VPX lets me select #3 (4k display), but the available display modes don't allow 4K (showing display modes of another display).    

 

Needed to revert back to older vpx version.

[GInsonic]

 

With latest files, i have exact same graphics issue.  My PF is windows display #1 but GPU display #3.  VPX lets me select #3 (4k display), but the available display modes don't allow 4K (showing display modes of another display).    

 

Needed to revert back to older vpx version.

 

Same here, I had to go back to v3618!

[sliderpoint]

Would you still like crash.txt files?  I get many for various scenarios that have already been described here, but don't want to flood if you don't need them right now.

 

-Mike

[toxie]

what always helps is definetly which table, if you were in the editor (and doing what there) or playing (and when/how roughly it happened).

[toxie]

 

 

With latest files, i have exact same graphics issue.  My PF is windows display #1 but GPU display #3.  VPX lets me select #3 (4k display), but the available display modes don't allow 4K (showing display modes of another display).    

 

Needed to revert back to older vpx version.

 

Same here, I had to go back to v3618!

 

 

This should be fixed with the next build..

[fuzzel]

rev3639 is up:

 

- one more display selection patch by Caligula

- optimize some shaders

- fix hit event handling for primitives

- cleanups and fixing random crashes

[lukpcn]

Crash report VPX rev3639
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:00535C10
Attempt to read from 0x0911F000
Thread ID: 0x4298 [17048]

Call stack
==========
00535C10 VPinballX.exe (0xFFFFFFFF80019030 0x09044E0C 0x40ABD752 0x0019ef1c)
0048612B VPinballX.exe (0x08E10930 0xFFFFFFFF80019030 0x40ABD752 0x0019eefc)
00485C05 VPinballX.exe (0x22887CD0 0x0019EF70 0x00000424 0x0019ef80)
0049E394 VPinballX.exe (0x544E5044 0x0019EF70 0x00000003 0x08e60668)

Environment
===========
Date/time: 19/2/2019, 00:09:56:293
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 17134)

Memory status
=============
Total Reserved: 357144K (348M) bytes
Total Commited: 1874636K (1830M) bytes
Total Free: 1962460K (1916M) bytes
Largest Free: 1035744K (1011M) bytes

Registers
=========
EAX=8905DE3C EBX=80019030 ECX=10278D57 EDX=40ABD752
ESI=0911F000 EDI=800F3224 EBP=00000000 ESP=0019EF48 EIP=00485BC9
FLG=00010207 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.

[BrandonLaw]

New update installed...anyone cannot exit editor now?  Try to edit FOV/CAM settings and stays hard stuck on screen.  Can't anything out of it.

[STV]

I'm getting lotsa crashes like lukcpn posted.   Pretty much within a minute of starting play.   The gameplay just freezes.  Then hitches once.   Then the exe closes.  robo-war, guns n roses are the two I've tested the crash on.   If I put back a 3569, just the exe and nothing else, the crashing no longer occurs.

 

 

Crash report VPX rev3639

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

Process: vpinballx.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:0047A17C

Attempt to write to 0x0AF6F0D0

Thread ID: 0x1794 [6036]

 

Call stack

==========

0047A17C vpinballx.exe (0xFFFFFFFFC0BA55C8 0x1840AE80 0x0000000D 0x0019f750)

004D8EF0 vpinballx.exe (0x00240304 0x2073746E 0x0C213050 0x0d09bfe0)

74616572 SHELL32.dll Ordinal813 + 0x1ED62 (0x2073746E 0x0C213050 0x0D09BFE0 0x0ba4a980)

00240304  (0x0C213050 0x0D09BFE0 0x0BA4A980 0x0c4d7a00)

2073746E  (0x0D09BFE0 0x0BA4A980 0x0C4D7A00 0x64200001)

0C213050  (0x0BA4A980 0x0C4D7A00 0x64200001 0x00000000)

0D09BFE0  (0x0C4D7A00 0x64200001 0x00000000 0x02de46d0)

0BA4A980  (0x64200001 0x00000000 0x02DE46D0 0x2077654e)

0C4D7A00  (0x00000000 0x02DE46D0 0x2077654E 0x1840c1f0)

64200001  (0x02DE46D0 0x2077654E 0x1840C1F0 0x1840c1f0)

 

Environment

===========

Date/time: 18/2/2019, 17:32:34:706

Number of CPUs: 6

Processor type: 586

System: Windows 10 (10.0 17134)

 

Memory status

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

Total Reserved: 339472K (331M) bytes

Total Commited: 644092K (628M) bytes

Total Free: 3210676K (3135M) bytes

Largest Free: 2095360K (2046M) bytes

 

Registers

=========

EAX=0AF6ED7C EBX=00000000 ECX=0BC0F4C0 EDX=3FAE2B3D

ESI=0BC0F4C0 EDI=0B8EAAC0 EBP=0C4D7A00 ESP=1840AEA4 EIP=64200001

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

 

 

Failed to save minidump.

[loganchihuahua]

Reporting that 3639 is hanging on closing tables.  You hit esc and then end and it just hangs.  You have mouse control and can hit ctrl alt delete and end task, but it will not close on its own. At least for me.  Sounds like others too.

 

Thanks for all the hard work!!!

[NailBuster]

same here... Hanging on closing tables #3639.  Wont go back to editor after launch (no front end).

 

The GPU/Display selection works in this build now .  But pressing ESC and end just hangs.  Going back to prior builds works ok.

[twelvepsigt]

evening all.

been having same crashes been working my way back versions trying to resolve i have not tried the new rev. i notice it can vary on tables, did in on acdc, demolition man, family guy, sometimes with in a minute other when i kicking but lol hope this helps

Crash report VPX rev3628

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

Process: vpinballx.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:0047E40C

Attempt to write to 0x0E18F0F8

Thread ID: 0x1750 [5968]

 

Call stack

==========

0047E40C vpinballx.exe (0xFFFFFFFFBFDFA7BB 0x112F6960 0x00000015 0x74c8e9f0)

004E360E vpinballx.exe (0x3D0BE25F 0x0000000A 0x3DCCCCCD 0x3f8dfa30)

004E2E77 vpinballx.exe (0x0EA6A8C0 0x112F6960 0xFFFFFFFFFFFF2E26 0x003be335)

004E427F vpinballx.exe (0x02F85330 0x0019FA1C 0x74C8E9F0 0x00000001)

 

Environment

===========

Date/time: 14/2/2019, 18:10:33:717

Number of CPUs: 12

Processor type: 586

System: Windows 10 (10.0 17763)

 

Memory status

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

Total Reserved: 375940K (367M) bytes

Total Commited: 1589820K (1552M) bytes

Total Free: 2228480K (2176M) bytes

Largest Free: 2095296K (2046M) bytes

 

Registers

=========

EAX=0E18ED9C EBX=00000001 ECX=144BE6E0 EDX=00673C40

ESI=144BE6E0 EDI=4895FC60 EBP=00000000 ESP=0019F770 EIP=004EA4E9

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

 

 

Failed to save minidump.

[GInsonic]

 

 

 

With latest files, i have exact same graphics issue.  My PF is windows display #1 but GPU display #3.  VPX lets me select #3 (4k display), but the available display modes don't allow 4K (showing display modes of another display).    

 

Needed to revert back to older vpx version.

 

Same here, I had to go back to v3618!

 

 

This should be fixed with the next build..

 

 

Thanx Toxie, I can confirm, that the display bug is fixed, but VPX immediately crashes when terminating game play (after the first press of Esc) and when FullScreenExclusive is enabled, and since VPX stucks, there is no crash log! When FSE is disabled, it does not crash when ending gameplay!

[sliderpoint]

also crash on exit.  (newly released potc on vpinball).  I've noticed that if you only play for a short amount of time and exit it doesn't crash (for me) but if you play for a minute or so it does.

Crash report VPX rev3639
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:00535A0E
Attempt to read from 0x08FEF000
Thread ID: 0x490 [1168]

Call stack
==========
00535A0E VPinballX.exe (0x7FFF7030 0x08F0BF85 0x5845543D 0x0019ef1c)
0048612B VPinballX.exe (0x0AE78130 0x7FFF7030 0x5845543D 0x0019eefc)
00485C05 VPinballX.exe (0x5C1DA170 0x0019EF70 0x00000424 0x0019ef80)
00502504 VPinballX.exe (0x544E5044 0x0019EF70 0x000000F1 0x08f0b640)

Environment
===========
Date/time: 19/2/2019, 09:14:51:525
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 17134)

Memory status
=============
Total Reserved: 231064K (225M) bytes
Total Commited: 2491788K (2433M) bytes
Total Free: 1471388K (1436M) bytes
Largest Free: 649224K (634M) bytes

Registers
=========
EAX=613613C2 EBX=7FFF7030 ECX=583723C2 EDX=5845543D
ESI=08FEF000 EDI=800DA0AB EBP=00000000 ESP=0019EF48 EIP=00485BC9
FLG=00010207 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.

Edited by sliderpoint, 19 February 2019 - 05:38 PM.

[lukpcn]

last stable version on my side is rev, 3592

[jpsalas]

last stable version on my side is rev, 3592

I agree.

[BorgDog]

I'm also having issues on latest beta, rev3639, with wall objects not registering hit events. slingshots seem to work, but not just wall hits.  for example, my star wars redux table on vpinball.com, the 3 targets under the front of the death star do not register hits.  they do under rev3628 and older.

[Fendrix]

Hi.
Medieval Madness, castlegate does not detect hit from ball in rev. 3639.

Thanx

[toxie]

will look into the missing hits, that might be most likely my fault..  :/

 

 

as for the others: is rev 3592 also the last 'good' one for you if you test through the builds here: https://vpinball.com...s/vp-10-6-beta/ ?

(i.e. is 3608 already crashing for you while 3592 not?)

Edited by toxie, 19 February 2019 - 10:40 PM.