1st crash
only opened new table
and moved a GI lamp
Crash report VPX rev202 (9adbae3) ============ Process: VPinballX.exe Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:0042817B Attempt to write to 0x15278554 Thread ID: 0xF74 [3956] Call stack ========== 0042817B VPinballX.exe (0x00000010 0x00000000 0x00000000 0x00090700) 004E9BB4 VPinballX.exe (0x00000010 0x00000000 0x00000000 0x00000010) 00427C77 VPinballX.exe (0x00427C20 0x00090700 0x00000010 0x00000000) 74F15E7A USER32.dll GetClassLongW + 0x7AA (0x00427C20 0x00000000 0x00000010 0x00000000) 74F15259 USER32.dll GetSystemMetricsForDpi + 0x1449 (0x03834E50 0x00000000 0x00000000 0x00000001) 74F021D9 USER32.dll SendMessageA + 0x49 (0x00090700 0x00000010 0x00000000 0x00000000) 0056A525 VPinballX.exe (0x00000111 0x000080ED 0x00000000 0x00020784) 00557FE5 VPinballX.exe (0x00000111 0x000080ED 0x00000000 0x00000111) 00427C77 VPinballX.exe (0x00427C20 0x00020784 0x00000111 0x000080ed) 74F15E7A USER32.dll GetClassLongW + 0x7AA (0x00427C20 0x00000000 0x00000111 0x000080ed) 74F15259 USER32.dll GetSystemMetricsForDpi + 0x1449 (0x03826AB0 0x00000000 0x00000000 0x00000001) 74F021D9 USER32.dll SendMessageA + 0x49 (0x00020784 0x00000111 0x000080ED 0x00000000) 004E6D3A VPinballX.exe (0x00000000 0x00000001 0x0019F248 0x002fb000) 005C8F10 VPinballX.exe (0x00000000 0x00000001 0x002FB000 0x007528f0) 005B5520 VPinballX.exe (0x00400000 0x00000000 0x032D2859 0x00000001) 005E2261 VPinballX.exe (0x002FB000 0x7574FA10 0x0019FFDC 0x76fb7a9e) 7574FA29 KERNEL32.DLL BaseThreadInitThunk + 0x19 (0x002FB000 0x4EA51B27 0x00000000 0x00000000) 76FB7A9E ntdll.dll RtlGetAppContainerNamedObjectPath + 0x11E (0xFFFFFFFFFFFFFFFF 0x76FD8A45 0x00000000 0x00000000) 76FB7A6E ntdll.dll RtlGetAppContainerNamedObjectPath + 0xEE (0x02F882A0 0x002FB000 0x00000000 0x78746341) Environment =========== Date/time: 11/6/2021, 17:02:35:735 Number of CPUs: 4 Processor type: 586 System: Windows 10 (10.0 19043) Memory status ============= Total Reserved: 133616K (130M) bytes Total Commited: 405276K (395M) bytes Total Free: 3655348K (3569M) bytes Largest Free: 2095424K (2046M) bytes Registers ========= EAX=00000000 EBX=00000000 ECX=FFFFFFFF EDX=03372400 ESI=15278550 EDI=00000010 EBP=0019FFEC ESP=0019FFE4 EIP=76FB7A6E FLG=00010216 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B Failed to save minidump.
Is this deterministic for you? Cause i cannot repro.
when i launch vpinmame the version is 3.4 and if i open up vpx it says the version is 10.7. All of the tables seem to work except when i try a new one. It says im running ver 10.6 and the table is 10.7 and of course the playfield is just white.
This confuses me. 'It says im running ver 10.6': Who is 'it'? Cause two sentences before you say VPX says 10.7.
Lazy question of the day:
If I am updating from the last release candidate can I just update the executive? Or at least skip the scripts folder. I like to avoid having to update the scripts for my configuration after I update. Thanks.
You should also update the scripts.. And i guess the only thing you changed is in VPMKeys.vbs? These changes you would have to copy over from the old one.




Top












are all trademarks of VPFORUMS.