Permissions: of course, make sure *.dll are unblocked and that *.exe is set to run as admin.
Well, not 100% sure about the permissions on Win10 I should add.
Edited by Thalamus, 19 September 2017 - 06:00 PM.
Posted 19 September 2017 - 05:58 PM
Edited by Thalamus, 19 September 2017 - 06:00 PM.
From now on. I won't help anyone here at VPF. Please ask Noah why that is.
Posted 19 September 2017 - 06:05 PM
I had the same problem, but it went away when I tried the XDMD folder from Thalamus. But before I got this to work by using the XDMD folder from Thalamus, I did have a semi work around. If all else fails, you may want to try it as a last resort. But the work around is only for the case when you are using the PinballX front end.
The PinballX Game Manager allows for multiple pinball emulators (e.g., Visual Pinball 10, Visual Pinball 9.9, Future Pinball, etc.). So I created a new group specifically for the Visual Pinball 10 tables that use Ultra DMD (Champion's League, America's Most Haunted, and Minions). For this group, I set it up to use the normal VIsual Pinball 10 executable command line to run them, but I also used the feature in PinballX that allowed me to run a command before launching a table from this group. So I had PinballX start UltraDMD for me this way, before it launched the table. If I remember correctly, I also had a batch file to kill UltraDMD and I had PinballX run it when I exited the table and returned to PinballX.
Edited by CyclonePF, 19 September 2017 - 06:09 PM.
Posted 19 September 2017 - 06:21 PM
@Thalamus, I have 2 different versions of dmddevice.dll. The one within vpinmame is 4.5MB, while the one in XDMD and PinballX is 68k.
Posted 19 September 2017 - 06:22 PM
@psmiraglia - I just saw your post from earlier today. Yes, it is still working for me (with the XDMD folder from Thalamus). It is a very frustrating problem - had me pulling my hair out for months. I don't know what was in Thalamus's XDMD folder that made it work for me, and not sure why it isn't working for you. I wish I had some more suggestions for you, but if you run PinballX you may want to try the approach I suggested in my posting just above this one.
Posted 19 September 2017 - 07:08 PM
Unfortunately I can't see anything wrong in your setup psmiraglia. It is ok to have those extra in Future Pinball and Tools folder. I just wanted to make sure that you didn't have any in typical windows system folders. You've listed the dmddevice.dll - but, what about xdmd.dll and xdmd-native.dll ? Only in pinballx and xdmd is adviced.
From now on. I won't help anyone here at VPF. Please ask Noah why that is.
Posted 19 September 2017 - 07:17 PM
I'm sure you've tried this already - but, after you've verified that xdmd.dll and xdmdnative.dll isn't anywhere else. You've tried what I said in the #4 post ?
You need to open the 'cmd-prompt' as administrator. And then run those re-registert parameters.
Edited by Thalamus, 19 September 2017 - 07:19 PM.
From now on. I won't help anyone here at VPF. Please ask Noah why that is.
Posted 19 September 2017 - 07:36 PM
yes, xdmd and xdmdnative dlls in those two folders only (plus my ultradmd backup folder):
Edited by psmiraglia, 19 September 2017 - 07:38 PM.
Posted 19 September 2017 - 08:12 PM
Yes. I can understand why. Because I don't see anything that isn't how I wanted you to set this up.
I can't come to think of anything other that it being something registry related. But, what ? Maybe look around for any older articles that says something about registry and ultradmd.
Curious. Have you tried to reinstall Visual Pinball via the latest "all-in-one installer" ?
From now on. I won't help anyone here at VPF. Please ask Noah why that is.
Posted 19 September 2017 - 08:15 PM
as I'm re-enabling CyclonePF's workaround I noticed a consistent mis-behavior:
in PBX,m If I launch UltraDMD as a "launch before" application, everything works well. On the other hand, if I launch a BAT that, in turn, launched UltraDMD, I get the same error as when VPX launched UltraDMD from the table script.
there is something about launching ultradmd "indirectly" that makes ultradnmd.exe not be able to find/use the right dlls, or for the dlls not to function correctly. Adding my XDMD folder to %PATH% did not help either.
frustrating
Posted 19 September 2017 - 08:51 PM
I would not suggest this normally. But, what you are saying just makes sense so - try copying xdmd.dll and xdmdnative.dll to a system location.
eg. \windows\syswow64 - I believe these DLL to be 32 bit so that is the correct location ( I know it sounds wrong, that it should be the other way around - but it isn't )
if it was 64bit it should be put in \windows\system
Then run
regsrv32 xdmd.device
regsrv32 xdmdnative.dll
Make sure you have an elevated cmd prompt ( run as admin )
Oh crap - there is one thing I just remembered. There is this Microsoft patch that might help. Gimme a sec.
Install this Microsft patch https://www.microsof...s.aspx?id=26767
KB2533623
... try the M$ patch first and foremost ... the other is last resort.
Edited by Thalamus, 19 September 2017 - 09:18 PM.
From now on. I won't help anyone here at VPF. Please ask Noah why that is.
Posted 21 September 2017 - 06:29 AM
Posted 22 September 2017 - 07:00 AM
Me I play for all. But my issues are no more at this point.You are playing tables from only this site aren't you ?
Me I play for all. But my issues are no more at this point.You are playing tables from only this site aren't you ?
Posted 22 September 2017 - 08:01 AM
Ok. A bit confused. Are you running colored roms ? Do you have the new nicer looking virtual dmd ? You said you copied pindmd to pinballx and xdmd.
That would work, but, not giving you the improvements.
From now on. I won't help anyone here at VPF. Please ask Noah why that is.
Posted 24 September 2017 - 04:57 AM
No colored roms anymore. I can't get the roms to compile and not crash my vpinmame. But the dmc colors are all working. And my issue was ultradmd would not come up on me pindmd3 at all. Nor wpuld the pinballx video when in menu. This is all working nwo.Ok. A bit confused. Are you running colored roms ? Do you have the new nicer looking virtual dmd ? You said you copied pindmd to pinballx and xdmd.
That would work, but, not giving you the improvements.
Posted 24 September 2017 - 07:54 AM
Yeah. Ok. I just wanted to clarify so that people coming behind you don't get confused and believe they will be running VP with dmd-ext by following your advice. Using the one-in-all installer and answering what dmd you have ( even saying you want dmddevice ) during the installation is still not giving a dmddevice.dll that can run colored roms or other improvements.
Happy to see you resolved your issue.
From now on. I won't help anyone here at VPF. Please ask Noah why that is.
Posted 13 November 2017 - 07:39 PM
@Thalamus I come back to this every month
your note frrm 9/17 (the crossed out section) made me think... placing dmddevice.dll as well as dmddevice.ini and pindmd.ini in the SYSWOW64 folder did the trick vp9 and vpx launch ultradmd and pindmdv3 without errors. i guess vpx sets its tables folder as the working dir before calling ultradmd and the dll could noot be found... time to disable the additional ultradmd system in PBX. thanks to everyone that shahred ideas here.
Posted 13 November 2017 - 08:47 PM
Happy to hear that you resolved the problem. Even though it isn't the way I was hoping. Any time you need to update these you need to remember that you've put these into system folders and are in a way now protected by windows.
From now on. I won't help anyone here at VPF. Please ask Noah why that is.
Posted 11 July 2019 - 05:05 AM
Awesome. This did the trick for me too. After installing a Teensy 3.2 with octo board, my ultraDMD didn't work on my pinDMDv3
Could launch the ultradmd.exe manually before and than 1 table would launch.
Copy the pindmd.ini in the SYSWOW64 folder did the trick
Edited by Mike DA Spike, 11 July 2019 - 05:08 AM.
Try PinballX Database manager as a replacement of PinballX's game list manager
With special thanks to Scutters