4027 replies to this topic

[fripounet]

Crash report VPX rev368 (559a147)
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:0043AA4B
Attempt to write to 0x1B934D74
Thread ID: 0x2A5C [10844]

Call stack
==========
0043AA4B VPinballX.exe (0x00000010 0x00000000 0x00000000 0x002e04bc)
004F8D84 VPinballX.exe (0x00000010 0x00000000 0x00000000 0x00000010)
0043A537 VPinballX.exe (0x0043A4E0 0x002E04BC 0x00000010 0x00000000)
764984EA USER32.dll GetClassLongW + 0x7CA (0x0043A4E0 0x00000000 0x00000010 0x00000000)
764978A9 USER32.dll GetSystemMetricsForDpi + 0x1449 (0x03C02420 0x00000000 0x00000000 0x00000001)
764847F9 USER32.dll SendMessageA + 0x49 (0x002E04BC 0x00000010 0x00000000 0x00000000)
0057C0E5 VPinballX.exe (0x00000111 0x000080ED 0x00000000 0x000503c8)
00569A07 VPinballX.exe (0x00000111 0x000080ED 0x00000000 0x00000111)
0043A537 VPinballX.exe (0x0043A4E0 0x000503C8 0x00000111 0x000080ed)
764984EA USER32.dll GetClassLongW + 0x7CA (0x0043A4E0 0x00000000 0x00000111 0x000080ed)
764978A9 USER32.dll GetSystemMetricsForDpi + 0x1449 (0x03BF9260 0x00000000 0x00000000 0x00000001)
764847F9 USER32.dll SendMessageA + 0x49 (0x000503C8 0x00000111 0x000080ED 0x00000000)
004F5F11 VPinballX.exe (0x00000000 0x00400000 0x002C1000 0x002e04bc)
005DA99C VPinballX.exe (0x00000000 0x00000001 0x002C1000 0x007702c0)
005C7EEE VPinballX.exe (0x00400000 0x00000000 0x031B45F2 0x00000001)
005F479E VPinballX.exe (0x002C1000 0x76F3FA10 0x0019FFDC 0x770d7bbe)
76F3FA29 KERNEL32.DLL BaseThreadInitThunk + 0x19 (0x002C1000 0x6BAA7C44 0x00000000 0x00000000)
770D7BBE ntdll.dll RtlGetAppContainerNamedObjectPath + 0x11E (0xFFFFFFFFFFFFFFFF 0x770F8D36 0x00000000 0x00000000)
770D7B8E ntdll.dll RtlGetAppContainerNamedObjectPath + 0xEE (0x005F4822 0x002C1000 0x00000000 0x78746341)

Environment
===========
Date/time: 12/10/2022, 09:45:58:770
Number of CPUs: 6
Processor type: 586
System: Windows 10 (10.0 19044)

Memory status
=============
Total Reserved: 163372K (159M) bytes
Total Commited: 551752K (538M) bytes
Total Free: 3479116K (3397M) bytes
Largest Free: 2095436K (2046M) bytes

Registers
=========
EAX=00000000 EBX=00000010 ECX=FFFFFFFF EDX=03262440
ESI=1B934D70 EDI=1B934D70 EBP=0019FFEC ESP=0019FFE4 EIP=770D7B8E
FLG=00010216 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

[jpsalas]

@fripounet: we aren't supposed to test rev 368. We are supposed to test rev 364 from the link as toxie posted.

 

Rev 364 works very well on my two computers, no artifacts, and it loads tables quite fast. No crashes for now. I have done some editing today, just a few hours, and everything seems to be ok.

(main computer: Windows 11, I7 10th gen, RTX 3080. Laptop Windows 10, i7, Intel Iris Plus Graphics, this laptop can't load tables with huge graphics, works ok limiting the images to 2048)

Edited by jpsalas, 12 October 2022 - 08:45 AM.

[pablo99]

Rev 364 working perfectly for me in my pincab:

Intel Core i5-2500S

8GB DDR3 RAM

Radeon RX550 2GB

Windows 10 Pro 21H1

[toxie]

Thanks guys for the quick feedback!

 

Now i also need especially some feedback from people that experience the startup hangs with the 'normal builds'.

[lukpcn]

Thanks guys for the quick feedback!

 

Now i also need especially some feedback from people that experience the startup hangs with the 'normal builds'.

Will be checking in 6 hours, I had problems opening the builds on my cab.

[studlygoorite]

hmmm, not so lucky here with rev 364, my delays are back. What would I be missing by using v368 or v354 that play nice with my system? 

[wiesshund]

hmmm, not so lucky here with rev 364, my delays are back. What would I be missing by using v368 or v354 that play nice with my system? 

 

dont know

since i had none of the issues toxie is looking for in 364, i am running 368

jp's deadpool is 3 seconds to launch, on my laptop, after allowing vpx to get the file itself read in

which is not a byproduct of vpx, just the laptops energy miser hdd that does everything slow and battery friendly

it does that with everything

 

4 seconds to launch funhouse

 

4 seconds for theater of magic

 

dont have whirlwind on laptop

[Cliffy]

rev 364 running like a champ here. Looks good too! JP Avengers wireforms look fantastic and loads quick even with the puppack. Did some editing of skitsos twilight zone with a lot of tweak, save, run test, quit, edit, test more, must have been at least a dozen opens and closes in one session with NO crashing and fast as usual load times. Just did the same thing with balutitos Hellraiser (based off JP's Mago de Oz), same thing. no crashes and relatively fast loads

 

Windows 10 Home 21h2

Intel® Core™ i7-6700 CPU @ 3.40GHz 16GB

Nvidia GTX 1060 6GB

[lukpcn]

@Toxie

 

Wanted to let You know that I've just checked rev. 364 and it works like it should on my cabinet (finally) - works the same as Thalamus's special build - same loading speeds around 12-15secs to load a table (probably can go faster if I switch to m.2 drive, running SATA6 so far in my cab.)

 

the last non-problematic revision for my cab was rev. 133...

Edited by lukpcn, 12 October 2022 - 06:24 PM.

[fourbanks]

Sorry guys to be a pain but iv'e lost my way in this topic. 

Are we supposed to be updating these new builds, or do we just stick to the main update on the first page 

thanks 

 

VPinballX-10.7.2-277-30548e4-Release-win-x86.rar 

Edited by fourbanks, 12 October 2022 - 08:25 PM.

[Thalamus]

Go with this one fourbanks - pretty sure you won't be disappointed

 

https://www.vpforums...=44135&p=507899

Edited by Thalamus, 12 October 2022 - 08:27 PM.

[fourbanks]

Go with this one fourbanks - pretty sure you won't be disappointed

 

https://www.vpforums...=44135&p=507899

Thank you my friend  

[toxie]

hmmm, not so lucky here with rev 364, my delays are back. What would I be missing by using v368 or v354 that play nice with my system? 

The 'delays' are normal with that build. 10.7.2 will not feature the new faster-preprocessing improvements by vbousquet yet.

We will not include these yet, as we first want to have a stable 10.7.2 release, and his changes are still WIP.

Sorry guys to be a pain but iv'e lost my way in this topic.

I know.. Its a bit confusing this time. But i think we're nearing the 10.7.2 release now, and then enter a new 10.8.0 cycle after that.

[Outhere]

rev. 364
No delay in opening

[leeoneil]

@Everybody, please test this new 10.7.2RC, done using a more 'official' build setup by jsm:

https://github.com/v...ase-win-x86.zip

 

Hello, this rev 364 seems to work fine for me, no particular problem noticed !

Normal loading, perfect playing.
I tried it with about fifteen tables, everything is ok !

 

Thank's !

 

(Windows 10, SSD, Intel i7 4770K and GTX 1070)

Edited by leeoneil, 13 October 2022 - 04:44 PM.

[BrandonLaw]

This 364 is working great.  VERY Snappy!  (I'm particularly fond of these Images being loaded/visible now when I import them...not having to click backbox to refresh the menus first.)

[tmpc]

RC working great for me.

[Cliffy]

10.8.0 beta 372 weird crash while resizing alphanumeric displays using the handles in game mode. vpx just suddenly closed in the middle of the resize but b2s server kept running. vpx did not generate a crash.txt. table was Bigus modde DE time machine. using last Freezy dmddevice.dll 1.10.3.0 and lucky pin2color 1.1.0.0

I realize this is a beta vpx but wanted to toss it out there anyway

[wiesshund]

10.8.0 beta 372 weird crash while resizing alphanumeric displays using the handles in game mode. vpx just suddenly closed in the middle of the resize but b2s server kept running. vpx did not generate a crash.txt. table was Bigus modde DE time machine. using last Freezy dmddevice.dll 1.10.3.0 and lucky pin2color 1.1.0.0

I realize this is a beta vpx but wanted to toss it out there anyway

 

that is not a function of vpx but of freezys
you might check dmddevice log
freesyz may have crashed, knocked out vpinmame, which knocked out vpx

[Cliffy]

 

10.8.0 beta 372 weird crash while resizing alphanumeric displays using the handles in game mode. vpx just suddenly closed in the middle of the resize but b2s server kept running. vpx did not generate a crash.txt. table was Bigus modde DE time machine. using last Freezy dmddevice.dll 1.10.3.0 and lucky pin2color 1.1.0.0

I realize this is a beta vpx but wanted to toss it out there anyway

 

that is not a function of vpx but of freezys
you might check dmddevice log
freesyz may have crashed, knocked out vpinmame, which knocked out vpx

 

yeah unfortunately I didn't check the log before restarting again so it got wiped. I cant seem to force a crash again so could have been a fluke. Thanks Wiesshund