Launching tables from the table folder

[kron]

Hey guys,

 

Recently I added a 3rd monitor to my cab, got that working with extdmd enabled using freezy’s latest dmddevice files and things are great! If I open VPX, then select a table everything works. The problem now (which I didn’t have before) is I cannot launch tables directly from the table folder. Same problem when using PBX. What happens is VPX and the table launch, and show on the screens, but the dmd is full orange and it basically freezes there, or sometimes it quits out over a period of time. This happens on any table when launching directly from the tables folder/or using PBX.

I’m guessing there is some link missing with the extdmd? Again, things work when i launch VPX first, then browse to the table through the app.

Any help would be appreciated!

10.6/Win7/3 screens

 

Thanks!

 

You need to login in order to like this post: click here

[kron]

Bump.

 

Any suggestions with this one?

 

Thanks.

You need to login in order to like this post: click here

[randr]

Try turning off exclusive full screen in vp video preferences and see if you get farther or see an error pop up.

********************************************************
Messing with the VPinball app and push notifications.
So if you haven't downloaded app yet what are you waiting for!?
for IOS and Android

********************************************************

You need to login in order to like this post: click here

[Thalamus]

Where did you put your dmddevice.dll ? Do you have several versions of it maybe ?

You need to login in order to like this post: click here

[kron]

Hey there – thanks for the reply! Really appreciate it.

randr – exclusive full screen is already off.

Thalamus – I put the dmddevice.dll in the VPinMAME folder.  Did a search for that filename in the Visual Pinball folder and also found one in each of the PinDMD1,2,3 folders. Should they be removed?

A Question I did have is if I go into my tables folder and right click on a vpx table (say AC/DC Prem) and click properties, it shows ‘Open with: Visual Pinball 10.3.0? Is that normal? I tried clicking change and selecting my VpinballX.exe in the VP root (which is 10.6) but it doesn’t change what it says in the properties. Perhaps there is something in the registry that could fix that?

To be clear things work fine when opening VpinballX.exe and browsing to a table, but if just going to the tables folder and double clicking on a vpx table it crashes after show on the screen briefly. Same problem when using PBX.

 

DmdDevice.log: <in vp root>

[3] 2019/03/29 19:07:33.693 INFO | Successfully loaded config from D:\Visual Pinball\VPinMAME\DmdDevice.ini.
[3] 2019/03/29 19:07:33.717 INFO | No altcolor folder found, ignoring palettes.
[3] 2019/03/29 19:07:33.717 INFO | Starting VPinMAME API through VPinballX.exe.
[3] 2019/03/29 19:07:33.717 INFO | [vpm] Open()
[3] 2019/03/29 19:07:33.717 INFO | [vpm] PM_GameSettings(0)
[3] 2019/03/29 19:07:33.717 INFO | Disabling game colorization
[3] 2019/03/29 19:07:33.717 INFO | Setting game name: acd_168h
[3] 2019/03/29 19:07:33.717 INFO | Setting color: #FFFF5820
[3] 2019/03/29 19:07:33.733 INFO | Opening virtual DMD…
[8] 2019/03/29 19:07:33.787 INFO | Found B2S, moving behind DMD.
[8] 2019/03/29 19:07:33.792 INFO | Added VirtualDMD renderer.
[8] 2019/03/29 19:07:33.792 INFO | Transformation options: Resize=Fit, HFlip=False, VFlip=False
[8] 2019/03/29 19:07:33.792 INFO | Applying default color to render graphs (#FFFF5820).
[8] 2019/03/29 19:07:33.792 INFO | Resizing virtual DMD to 128×32
[8] 2019/03/29 19:07:33.807 INFO | Setting up 2-bit VPM Graph for 1 destination(s)
[8] 2019/03/29 19:07:33.807 INFO | Connecting VPM 2-bit Source to Dmd (Gray2 => Rgb24)
[8] 2019/03/29 19:07:33.852 INFO | Setting up 4-bit VPM Graph for 1 destination(s)
[8] 2019/03/29 19:07:33.852 INFO | Connecting VPM 4-bit Source to Dmd (Gray4 => Rgb24)
[8] 2019/03/29 19:07:33.852 INFO | Setting up RGB24-bit VPM Graph for 1 destination(s)
[8] 2019/03/29 19:07:33.852 INFO | Connecting VPM RGB24 Source to Dmd (Rgb24 => Rgb24)

 

 

Crash.txt <in tables folder>

Crash report VPX rev3653
============
Process: VPinballX.exe
Reason: 0xC0000005 – EXCEPTION_ACCESS_VIOLATION at 0023:44A90002
Attempt to read from 0x44A90002
Thread ID: 0xE4C [3660]

Call stack
==========
44A90002 (0x06868E10 0x00000000 0x000026FC 0x44a90002)
353D9AD3 vpinmame.dll (0x000026FC 0x00000000 0x00000000 0x35838998)
3530D8D9 vpinmame.dll (0x24FD78F8 0x3531FF90 0x00000001 0x3583f154)
3530BC82 vpinmame.dll (0x00000609 0x35818EA8 0x3463FF88 0x00000001)
3531FE72 vpinmame.dll (0x084EBB88 0x00000000 0x76B5281B 0x00000000)
3531FBAA vpinmame.dll (0x2542A108 0x00000000 0x00000030 0x00000030)
7717432F ntdll.dll RtlInitializeCriticalSection + 0x3F (0x00000030 0x00000008 0x3463FED8 0x2559dd60)
35497CB8 vpinmame.dll DllUnregisterServer + 0x1CB38 (0xFFFFFFFF9C2D128D 0x05FED058 0x7FFFFFFF 0x720e1f18)
7718BF19 ntdll.dll RtlUniform + 0x28 (0x7285BB14 0x399E2A32 0x7FFFFFFF 0x00000000)
7718BF19 ntdll.dll RtlUniform + 0x28 (0x72330E14 0x2559DC70 0x2559DC70 0x084ebb88)
720E9812 AcXtrnal.DLL (0x00000004 0x35814F70 0x35814ED0 0x3576ef84)
35485ADC vpinmame.dll DllUnregisterServer + 0xA95C (0x00000000 0x2533A930 0x2533A930 0x3576ef84)
35485ADC vpinmame.dll DllUnregisterServer + 0xA95C (0x356338CC 0x2533A930 0x3463FF88 0x00000000)
35485ADC vpinmame.dll DllUnregisterServer + 0xA95C (0x00000000 0x084EBB88 0x76B5281B 0x354747ab)

Environment
===========
Date/time: 29/3/2019, 19:07:36:802
Number of CPUs: 4
Processor type: 586
System: Windows XP

Memory status
=============
Total Reserved: 175548K (171M) bytes
Total Commited: 1449180K (1415M) bytes
Total Free: 2569512K (2509M) bytes
Largest Free: 2096384K (2047M) bytes

Registers
=========
EAX=44A90002 EBX=00000000 ECX=44A90002 EDX=000026FC
ESI=00000000 EDI=000026FC EBP=00000000 ESP=3463FF50 EIP=3547C543
FLG=00010206 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B

Failed to save minidump.

You need to login in order to like this post: click here

[outhere]

PinDMD1,2,3 folders. Should they be removed? <– NO

What happens if you right click the game, then click on open with

You need to login in order to like this post: click here

[kron]

Thanks Outhere!

 

open with gives the same problem. Steps, open with and browser to vpinballx.exe from vp root.

 

anything in the registry to check?

You need to login in order to like this post: click here

[outhere]

I’m sure there something in a registry but I’ve never had this problem

You need to login in order to like this post: click here

[Thalamus]

Yes. I agree. It is a registry problem. I’m sure I can find a way to fix it. But, now in front of my cab right now so my suggestion is as follows. Rename “c:\visual pinball” to “c:\visual pinball.bak” – run the one in all installer. Make sure to use the path that you had before the rename. Once done. Delete the “new” unneded install and rename the original back to what it was. Should work – shouldn’t it ?

If you don’t want to do this. I could have a second look. I know I have the same problem for VP9, but, I never play from double clicking so I haven’t bothered to fix it yet. Now, I just might want to find out just for the hell of it :)

You need to login in order to like this post: click here

[kron]

Thanks Thalamus!

I did try your suggestion but unfortunately it made no difference.

Any other suggestions?

Does anyone know the difference between opening a table directly from the table folder vs opening Visual Pinball.exe and browsing to the table to open it?

You need to login in order to like this post: click here

[kron]

Got it working!! 

After lots of researching around and troubleshooting I finally got the tables to launch directly from the table folder.

Fix:

Changed the registry line item at91jit under VPinMame from 1 to 0 under each rom.

If you recently added a virtual dmd and have this problem, try the fix above.

 

Thanks to all who helped or gave suggestions – greatly appreciated!

 

 

You need to login in order to like this post: click here

[Author]

Posts