4027 replies to this topic

[Thalamus]

Yes. You should report it. My intention was just to remind users that if you want a stable VP, then play the official.

[wiesshund]

No problem whatsoever, just wanted to report it., I have very good experience with the betas up until now. Just now it is giving me lots of problems. I have now gone back to version 4439 and it works perfectly with some more demanding tables. Will try the Lesscputhreads and report back, but I also use Pinaffinity so maybe that is the issue here.

 

Just to let you know, this beta is giving me lots of problems. Cannot start AC/DC it gives me OUTOFVIDEOMEMORY errors. I did try to change to the enhanced 7.1 and also tried not to change the sound settings but whatever I do I cannot get AC/DC to run. Reverted back to previous beta rev 4442 and works again.

 fired up acdc luci, ran fine
i do not know your specs though

what do you have selected for max texture size?

will it run if you pick something other than unlimited?

 

 

I have a 3060 ti in the machine so it is very unlikely that there is a problem with going out of video memory. I did a test last week and that showed me that VPX is only using 2,1 Gigabytres of video memory ever with any machine. I found out that Cirques Voltaire was the most demanding.

 

Well, i dont think that is it either, as i set my laptop tp unlimited
and it has no dedicated vram or gpu
and it still opened.

 

Which ACDC table do you have?
If you have more than 1 do they all do it?

[ronaldvg]

Did some more testing, but the AC/DC Luci gives me the error that 10.7.0 has stopped working. Tried it with Pinaffinity on, with and without -LESSCPUTHREADS and also with Pinaffinity off with and without -LESSCPUTHREADS

 

Again after going back to a previous beta the table starts perfectly. In this test I did not change the sound settings at all.

@wieshund I tried 4 different versions of the AC/DC table, but they all use the same Rom obviously (Colored). Also tried lowring the texture size, bit it sttill gives me the error. Also when the error appears, the machine gets very slow and I can barely close the window. All is ok with previous beta.

 

Let's just wait to see what others are experiencing, maybe it is something in my cab,. There are so many progrmas working together...

Edited by ronaldvg, 18 March 2021 - 11:20 PM.

[Thalamus]

Out of curiosity. It has often on my end, with loading - been related to having external dmd enabled. I would call that a known problem. Using extenal dmd and you will crash more often. If that is a timing thing or something else ? It's not that. Using external is something I do have enable for almost all tables. But, if I turn it off, it before this release at least. it seems to be rock solid. But, then again, the truth is, since using external is my default. It doesn't run through as many tests as having it enabled does.

 

I mentioend pin-bot crashing, that I haven't seen before. So, I expect there is still something not 100% right with this release. But, to early to say. Was the only table that crashed on loading in the few tables I tried tonight. But, then again - has never crashed before.

Edited by Thalamus, 18 March 2021 - 11:25 PM.

[wiesshund]

Out of curiosity. It has often on my end, with loading - been related to having external dmd enabled. I would call that a known problem. Using extenal dmd and you will crash more often. If that is a timing thing or something else ? It's not that. Using external is something I do have enable for almost all tables. But, if I turn it off, it before this release at last. Something I haven't been able to re-produce. But, then again, the truth is, since using external is my default. It doesn't run through as many tests as having it enabled does.

DING DING DING

External DLL, PinMAME 3.3b official Stock ROM

Can not load, CRASH

Crash report VPX rev98 (f9a3765)
============
Process: VPinballX.exe
Reason: 0xE0434352 - UNKNOWN at 0023:7639A8B2
Thread ID: 0x2EE8 [12008]

Call stack
==========
7639A8B2 KERNELBASE.dll RaiseException + 0x62 (0xFFFFFFFFE0434352 0x00000001 0x00000005 0x0d58f1ec)
6DC628F1 clr.dll GetMetaDataPublicInterfaceFromInternal + 0x9741 (0x00000000 0x3AA7F350 0x0D58F240 0x0d58f25c)
6DD3071E clr.dll CorDllMainForThunk + 0x40AE (0x00000002 0x0D58F768 0x6DC623D0 0x0d58f26c)
6DD30790 clr.dll CorDllMainForThunk + 0x4120 (0x00000002 0xFFFFFFFFB09E9C6E 0x6DB701A0 0x0d58f790)
6DD307CE clr.dll CorDllMainForThunk + 0x415E (0x00000002 0x3AA7F350 0x6DC93D40 0xffffffffbdff46ea)
6DD307D6 clr.dll CorDllMainForThunk + 0x4166 (0xFFFFFFFFBDFF4662 0x3EE86AE0 0x00000002 0x12a7e850)
6DC75136 clr.dll GetMetaDataPublicInterfaceFromInternal + 0x1BF86 (0x00001000 0x0D58F848 0x12A7E850 0x0c1d3485)
6DC751A0 clr.dll GetMetaDataPublicInterfaceFromInternal + 0x1BFF0 (0x3D123A30 0x3D0B1B08 0x0D58FAB8 0x3d069a88)

Environment
===========
Date/time: 18/3/2021, 19:25:08:789
Number of CPUs: 4
Processor type: 586
System: Windows 10 (10.0 19042)

Memory status
=============
Total Reserved: 172784K (168M) bytes
Total Commited: 1777096K (1735M) bytes
Total Free: 147208K (143M) bytes
Largest Free: 24448K (23M) bytes

Registers
=========
EAX=0D58F128 EBX=00000005 ECX=00000005 EDX=00000000
ESI=0D58F1EC EDI=00000001 EBP=00000000 ESP=0D58F848 EIP=3CCA3374
FLG=00000216 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.

not sure how the vpx player changes factor into pinmame and dmddevice.dll doing their thing

but yep, can not load it with freezys enabled, only with vpm display

seems same crash each time

and yes before crashing things get sloooooooow

pinmame never inits either, DOA

Crash report VPX rev98 (f9a3765)
============
Process: VPinballX.exe
Reason: 0xE0434352 - UNKNOWN at 0023:7639A8B2
Thread ID: 0x3184 [12676]

Call stack
==========
7639A8B2 KERNELBASE.dll RaiseException + 0x62 (0xFFFFFFFFE0434352 0x00000001 0x00000005 0x23e9f3e4)
6DC628F1 clr.dll GetMetaDataPublicInterfaceFromInternal + 0x9741 (0x00000000 0x34367F24 0x23E9F438 0x23e9f454)
6DD3071E clr.dll CorDllMainForThunk + 0x40AE (0x00000002 0x23E9F960 0x6DC623D0 0x23e9f464)
6DD30790 clr.dll CorDllMainForThunk + 0x4120 (0x00000002 0x30DA39F3 0x6DB701A0 0x23e9f988)
6DD307CE clr.dll CorDllMainForThunk + 0x415E (0x00000002 0x34367F24 0x6DC93D40 0x130cf717)
6DD307D6 clr.dll CorDllMainForThunk + 0x4166 (0x130CF78F 0x384D6AE0 0x00000002 0x0d8db610)
6DC75136 clr.dll GetMetaDataPublicInterfaceFromInternal + 0x1BF86 (0x00001000 0x23E9FA40 0x0D8DB610 0x0c1c3485)
6DC751A0 clr.dll GetMetaDataPublicInterfaceFromInternal + 0x1BFF0 (0x36773A30 0x36701B08 0x23E9FCB0 0x366b9a88)

Environment
===========
Date/time: 18/3/2021, 19:31:02:337
Number of CPUs: 4
Processor type: 586
System: Windows 10 (10.0 19042)

Memory status
=============
Total Reserved: 247644K (241M) bytes
Total Commited: 1691964K (1652M) bytes
Total Free: 157480K (153M) bytes
Largest Free: 12636K (12M) bytes

Registers
=========
EAX=23E9F320 EBX=00000005 ECX=00000005 EDX=00000000
ESI=23E9F3E4 EDI=00000001 EBP=00000000 ESP=23E9FA40 EIP=362F3374
FLG=00000212 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.

Not even sure why it is only some ROMs
NON edited ROMs at that, as on laptop acdc is not color patched

and vpm is not sam build

[ronaldvg]

Out of curiosity. It has often on my end, with loading - been related to having external dmd enabled. I would call that a known problem. Using extenal dmd and you will crash more often. If that is a timing thing or something else ? It's not that. Using external is something I do have enable for almost all tables. But, if I turn it off, it before this release at least. it seems to be rock solid. But, then again, the truth is, since using external is my default. It doesn't run through as many tests as having it enabled does.

 

I mentioend pin-bot crashing, that I haven't seen before. So, I expect there is still something not 100% right with this release. But, to early to say. Was the only table that crashed on loading in the few tables I tried tonight. But, then again - has never crashed before.

 

Yes confirmed, Pinbot is crashing here too with trhe same error: Fatal error E_OUTOFMEMORY (0x80070000e: Ran out of memory) at D:\a\vpinball\vpinball\pin\player.cpp:1767

 

I do not know what the D:\a... stands for because I do not have a D disk in the cab. Probably it means something else.

[ronaldvg]

I tried this also but the Pinbot table does not have External DMD enabled (I checked in the F1 menu) as I do not want the scores and displays to be replicated on the DMD, only on the backglass. The new beta gives me the same error anyway. Again using the previous beta is fine (that is how I checked with the F1 menu).

 

I also just saw that the new VPX version is way smaller than the previous one. Previous was 17.550kB and new one is 10.236kB. That is also strange or not ??

Edited by ronaldvg, 18 March 2021 - 11:51 PM.

[Thalamus]

The filesize isn't something you should have to worry about or trust as being a sign of change. I expect that one is compressed, the other not. I should add. Pin-bot crashed only on first try to load, reloading worked. That is also why I said it probably  wasn't a good enough test. But, seeing others, makes me more suspicious. Wiesshund, maybe if you turn off at91jit in the registry, for the rom, you'll be able to get it to run ? at91jit and stern is explained before as a probably timing issue. freezy too. Both in combination can lead you down to desperation, especially on win7. Seems the new vpx may even make that happen more often ?!

Edited by Thalamus, 19 March 2021 - 12:11 AM.

[ronaldvg]

The filesize isn't something you should have to worry about or trust as being a sign of change. I expect that one is compressed, the other not. I should add. Pin-bot crashed only on first try to load, reloading worked. That is also why I said it probably  wasn't a good enough test. But, seeing others, makes me more suspicious. Wiesshund, maybe if you turn off at91jit in the registry, for the rom, you'll be able to get it to run ? at91jit and stern is explained before as a probably timing issue. freezy too. Both in combination can lead you down to desperation, especially on win7. Seems the new vpx may even make that happen more often ?!

 

Tried turning of the at91jit but still same problem for AC/DC. 

 

Regarding the filesize: it increased with every new version a little bit, but now it is only 60% of the previous executable. That is significant.

Edited by ronaldvg, 19 March 2021 - 12:40 AM.

[wiesshund]

 

 

 

Yes confirmed, Pinbot is crashing here too with trhe same error: Fatal error E_OUTOFMEMORY (0x80070000e: Ran out of memory) at D:\a\vpinball\vpinball\pin\player.cpp:1767

 

I do not know what the D:\a... stands for because I do not have a D disk in the cab. Probably it means something else.

 

Toxie or Fuzzel has the source code in d:\a\vpinball\vpinball\pin\

 

useless to you, but tells them what file and line to look at

The filesize isn't something you should have to worry about or trust as being a sign of change. I expect that one is compressed, the other not. I should add. Pin-bot crashed only on first try to load, reloading worked. That is also why I said it probably  wasn't a good enough test. But, seeing others, makes me more suspicious. Wiesshund, maybe if you turn off at91jit in the registry, for the rom, you'll be able to get it to run ? at91jit and stern is explained before as a probably timing issue. freezy too. Both in combination can lead you down to desperation, especially on win7. Seems the new vpx may even make that happen more often ?!

 

Nope, did not help, seemed to take it longer to finish crashing though, and nearly ties up entire system while it does it too

Crash report VPX rev98 (f9a3765)
============
Process: VPinballX.exe
Reason: 0xE0434352 - UNKNOWN at 0023:7639A8B2
Thread ID: 0x22F4 [8948]

Call stack
==========
7639A8B2 KERNELBASE.dll RaiseException + 0x62 (0xFFFFFFFFE0434352 0x00000001 0x00000005 0x0aa3ee5c)
6DC628F1 clr.dll GetMetaDataPublicInterfaceFromInternal + 0x9741 (0x00000000 0x316510E4 0x0AA3EEB0 0x0aa3eecc)
6DD3071E clr.dll CorDllMainForThunk + 0x40AE (0x00000002 0x0AA3F3D8 0x6DC623D0 0x0aa3eedc)
6DD30790 clr.dll CorDllMainForThunk + 0x4120 (0x00000002 0x535B9FEA 0x6DB701A0 0x0aa3f400)
6DD307CE clr.dll CorDllMainForThunk + 0x415E (0x00000002 0x316510E4 0x6DC93D40 0x59ba22d4)
6DD307D6 clr.dll CorDllMainForThunk + 0x4166 (0x59BA255C 0x382A6AE0 0x00000002 0x0dc3e850)
6DC75136 clr.dll GetMetaDataPublicInterfaceFromInternal + 0x1BF86 (0x00001000 0x0AA3F4B8 0x0DC3E850 0x0c1f3485)
6DC751A0 clr.dll GetMetaDataPublicInterfaceFromInternal + 0x1BFF0 (0x36543A30 0x364D1B08 0x0AA3F728 0x36489a88)

Environment
===========
Date/time: 18/3/2021, 20:48:02:452
Number of CPUs: 4
Processor type: 586
System: Windows 10 (10.0 19042)

Memory status
=============
Total Reserved: 193076K (188M) bytes
Total Commited: 1694516K (1654M) bytes
Total Free: 209496K (204M) bytes
Largest Free: 20376K (19M) bytes

Registers
=========
EAX=0AA3ED98 EBX=00000005 ECX=00000005 EDX=00000000
ESI=0AA3EE5C EDI=00000001 EBP=00000000 ESP=0AA3F4B8 EIP=360C3374
FLG=00000212 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.

incidentally, when i went back to the previous beta build or 10.6.1, it would not work right until i set at91jit e back on, but maybe that is normal

 

 

 

Regarding the filesize: it increased with every new version a little bit, but now it is only 60% of the previous executable. That is significant.

 

 

could be a few things, code cleanup
removal of no longer necessary debugging routines or other baggage that is doing nothing but coming along for the ride.

 

I mean it could mean something important, so mentioning it can not hurt

[njk70]

Re: .WAV file mono playback. A few extra tweaks and I think it is safe from causing any side effects. But I did put in a protection against a case that I can't trivially fix. The mono to dual-channel inline conversion will only work if the original .WAV file was in PCM format. alaw/mulaw encoded .WAV files will be unchanged (I don't know anything about those encodings). I think I will throw an error box up if it detects one of those and run through all my tables but I don't have that many tables on my machine yet so I don't know how representative it will be.

[wiesshund]

Re: .WAV file mono playback. A few extra tweaks and I think it is safe from causing any side effects. But I did put in a protection against a case that I can't trivially fix. The mono to dual-channel inline conversion will only work if the original .WAV file was in PCM format. alaw/mulaw encoded .WAV files will be unchanged (I don't know anything about those encodings). I think I will throw an error box up if it detects one of those and run through all my tables but I don't have that many tables on my machine yet so I don't know how representative it will be.

 

I do not think i have run across any non PCM wavs, yet

would kind of hope no alaw or ulaw sounds pop up, cause those generally tend to sound like cell phone recordings, for the obvious reasons

 

At least we are not using headerless raw  MSADPCM files

[njk70]

I see, sounds like we should be safe then.  I submitted first PR to fix moving .WAV samples to backglass (you may need a center channel, or EqualizerAPO redirecting center channel to left/right). Its all of two lines fixing a couple conditional checks.

 

I have a little more testing to do on the mono to 2-channel upscaling (for lack of a better word?) but I should have a PR for that submitted by the weekend. Code is kinda ugly and might be a bit slower than it needs to be so am going to ponder on that for a bit as well. Its only a dozen lines or so.

[davidcd13]

 

Hello,

Metallica Premium Monsters (Stern 2013) VPW Mod table (https://vpinball.com...vpw-mod/page/5/) gives error on launch: "line 302 cannot create active component x "

I know it works with vpx 10.6, it seems to me that it worked with an old version 10.7.

 

Thanks for all your hard work.

 

Back to version 10.7 rev4439, it works now.

I think the last version (10.7 rev98) was having problems with SAMbuild 3.3b because I had a problem loading the "mtl_180hc" rom.

[Outhere]

I'm testing on a  - Intel i7-3770 CPU @ 3.40GHz,  No video card, Desktop
With -- VPX_7_beta_rev98
Doesn't seem to be liking color roms
For this game Metallica Premium Monsters mtl_180hc" rom. it says it can not find the rom, works fine in 10.7 rev4439
For this game AC-DC Premium acd_170hc  This game with color rom crashes VP,  works fine in 10.7 rev4439

Also without color rom --> For this game AC-DC Premium acd_170h  It says it can not find the rom, works fine in 10.7 rev4439
 

Edited by Outhere, 20 March 2021 - 12:29 AM.

[wiesshund]

For this game AC-DC Premium acd_170hc  This game with color rom crashes VP,  works fine in 10.7 rev4439

 

Crashes with unmodified ROM and official vpinmame and dmddevice.dll as well, regardless of if jit is on or off
(and vpinmame 3.2 also)

[Segovia11]

 

Out of curiosity. It has often on my end, with loading - been related to having external dmd enabled. I would call that a known problem. Using extenal dmd and you will crash more often. If that is a timing thing or something else ? It's not that. Using external is something I do have enable for almost all tables. But, if I turn it off, it before this release at least. it seems to be rock solid. But, then again, the truth is, since using external is my default. It doesn't run through as many tests as having it enabled does.

 

I mentioend pin-bot crashing, that I haven't seen before. So, I expect there is still something not 100% right with this release. But, to early to say. Was the only table that crashed on loading in the few tables I tried tonight. But, then again - has never crashed before.

 

Yes confirmed, Pinbot is crashing here too with trhe same error: Fatal error E_OUTOFMEMORY (0x80070000e: Ran out of memory) at D:\a\vpinball\vpinball\pin\player.cpp:1767

 

I do not know what the D:\a... stands for because I do not have a D disk in the cab. Probably it means something else.

 

 

Bug Report

 

I do not use Roms or an external DMD system & my tables are standalone desktop tables which work very well with the 4406 & 98 rev. The Desktop configuration in use is an : Intel® Core™ i7-9700 CPU : @ 3.00GHz x 8 and 16 GB of Ram plus a NVIDIA Geforce RTX 2070 using Windows 10 with the latest updates.

 

However, I tested one of my tables with the Intel® Core™ i5-7400  : CPU @ 3.00GHz x 4 which has 8 GB of Ram & + NVIDIA Geforce RTX 1050 again using Windows 10 with the latest updates &, with this set up I got a Fatal error E_OUTOFMEMORY (0x80070000e: Ran out of memory) at D:\a\vpinball\vpinball\pin\player.cpp:1767 report with Visual Pinball Rev 98. Although rev 4406 was error free.

I also tested Abra Ca Dabra (1975) which has a file size of 31,940 kb which is larger than my 79,220 kb file size & the the table loaded without problems.

 

It looks as though I got away with it thanks to my i7 setup. (Maybe somebody is promoting desktop upgrades!)

 

   

Edited by Segovia11, 19 March 2021 - 07:29 PM.

[bmheyob]

Unfortunately I have a couple revision 98 problems to report:

• America's Most Haunted won't load
• Pizza Time loads but the playfield is all white

Edited by bmheyob, 19 March 2021 - 11:07 PM.

[jpsalas]

Yes, this revision 98 has some problems running some tables. It may be a compiler error or we may have the wrong C++ libraries, as the error involves the C++ runtime.

 

One table that gives this error is City Slicker  : City Slicker Desktop - VPForums.org

 

And the error is this

Crash report VPX rev98 (f9a3765)
============
Process: VPinballX.exe
Reason: 0xE06D7363 - UNKNOWN at 0023:75FAA8B2
Thread ID: 0xC3C [3132]

Call stack
==========
75FAA8B2 KERNELBASE.dll RaiseException + 0x62 (0xFFFFFFFFE06D7363 0x00000001 0x00000003 0x034fdc40)
67EA75B6 VCRUNTIME140.dll CxxThrowException + 0x66 (0x034FDC5C 0x008E1628 0x007AB0BC 0x008afb64)
0076E321 VPinballX.exe (0x00000000 0x005E80B2 0x00000000 0x25a00440)
005E80B2 VPinballX.exe (0x0000C21A 0x00000000 0x00000000 0x00070166)
006A3210 VPinballX.exe (0x034FE1E4 0xFFFFFFFF9F53DC44 0x00000000 0x00000000)
75D662FA MSCTF.dll TF_Notify + 0x2FA (0x005E7F30 0x00070166 0x0000C21A 0x00000000)
75585ECA user32.dll GetClassLongW + 0x7AA (0x755893C6 0x034FE1A0 0x00000018 0x00000000)
77322BCC ntdll.dll ZwCallbackReturn + 0xC (0x034FE1A0 0x00000018 0x00000000 0x00000001)
755893C6 user32.dll Ordinal2712 + 0x146 (0x00000000 0x00000000 0x00000000 0x035011c8)
75585CDE user32.dll GetClassLongW + 0x5BE (0x005E7F30 0x00000000 0x0000C21A 0x00000000)
75583C3A user32.dll DispatchMessageW + 0x24A (0x7558A000 0x007858C1 0x034FE2C0 0x00000000)
75575D80 user32.dll DispatchMessageA + 0x10 (0x034FE2C0 0x00000000 0x00000001 0x034ff760)
007858C1 VPinballX.exe (0x00000000 0x00000001 0x0335A000 0x008b25a4)
00777687 VPinballX.exe (0x00000001 0x0335A000 0x008B25A4 0x00000000)

Environment
===========
Date/time: 20/3/2021, 05:44:34:241
Number of CPUs: 16
Processor type: 586
System: Windows 10 (10.0 19042)

Memory status
=============
Total Reserved: 142808K (139M) bytes
Total Commited: 1512096K (1476M) bytes
Total Free: 442184K (431M) bytes
Largest Free: 102488K (100M) bytes

Registers
=========
EAX=034FDBC0 EBX=19930520 ECX=00000003 EDX=00000000
ESI=25A00468 EDI=008E1628 EBP=00000558 ESP=034FE2E0 EIP=00777687
FLG=00000216 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

[jpsalas]

Other tables gives this smaller error, like for example The Flintstones, The Flintstones – VPINBALL.COM

Mostly are tables with a lot of graphics.

 

Edit: This is using only VPX and vpinmame  3.3b (without front ends, db2s, or external dmd)

Crash report VPX rev98 (f9a3765)
============
Process: VPinballX.exe
Reason: 0xE06D7363 - UNKNOWN at 0023:75FAA8B2
Thread ID: 0xE80 [3712]

Call stack
==========
75FAA8B2 KERNELBASE.dll RaiseException + 0x62 (0xFFFFFFFFE06D7363 0x00000001 0x00000003 0x034fe150)
67EA75B6 VCRUNTIME140.dll CxxThrowException + 0x66 (0x034FE16C 0x008E1628 0x007AB0BC 0x008afb64)
0076E321 VPinballX.exe (0x000F423F 0x0000C21A 0x4F20D0E0 0x00000000)
005E80B2 VPinballX.exe (0x0000C21A 0x00000000 0x00000000 0x000e04e8)
006A3210 VPinballX.exe (0x034FE704 0x00000000 0x00000000 0x76194b70)
75D662FA MSCTF.dll TF_Notify + 0x2FA (0x005E7F30 0x000E04E8 0x0000C21A 0x00000000)

Environment
===========
Date/time: 20/3/2021, 06:20:02:157
Number of CPUs: 16
Processor type: 586
System: Windows 10 (10.0 19042)

Memory status
=============
Total Reserved: 148260K (144M) bytes
Total Commited: 1537276K (1501M) bytes
Total Free: 411552K (401M) bytes
Largest Free: 139700K (136M) bytes

Registers
=========
EAX=034FE0D0 EBX=19930520 ECX=00000003 EDX=00000000
ESI=4F20D108 EDI=008E1628 EBP=00000000 ESP=034FE664 EIP=75585ECA
FLG=00000212 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

Edited by jpsalas, 20 March 2021 - 07:18 AM.