33 replies to this topic

[hlr53]

[Snip]

Sorry, double post from my tablet.

Edited by hlr53, 05 October 2017 - 12:51 AM.

[hlr53]

Not sure what you mean by enabling the log file? It has full privileges. I think I may have a .Net problem and/or something in the registry. I even had a VPX table shutdown due to a .Net error tonight. I'll run some scans on the framework and Windows. If worse comes to worst, I can do a full Windows reset this weekend. My cab does not have many programs installed and my PinballX media is backed up.

Tomorrow I may plug the DMD into my Alienware laptop and see if dmdext runs a test.

[Thalamus]

http://www.vpforums....=38769&p=389788

 

Enable log is explained in my previous post.

It might be a good idea to report problems. This is bleeding edge software - there will be bugs.

Edited by Thalamus, 05 October 2017 - 05:38 AM.

[hlr53]

Before I bother GitHub I want to check some things. It may be as simple as the PATH. Not sure exactly what a PATH and environment variables do? I never had to worry about it before?

Edited by hlr53, 05 October 2017 - 12:06 PM.

[Thalamus]

Again ... enable logging and you don't really need to

 

windows + r

cmd <enter>

cd <somewhere where dmdext is located>

dmd-ext <with your prefered params>

 

Sounds about right.

Edited by Thalamus, 05 October 2017 - 11:16 AM.

[hlr53]

I have tried that - it doesn't work. Thanks for the help though :-)

[freezy]

Maybe a few basics.

• You don't need to run dmdext.exe as admin except for Pinball Arcade.
• "Not unblocked" is as obvious as Windows explicitly asking you if you want to execute that file. If it doesn't ask, it's unblocked.
• DmdDevice.ini has nothing to do with dmdext.exe, which takes all parameters from the command line. The .ini is for DmdDevice.dll where you don't have a command line, and is only relevant when using VPM.
• "The log" is what dmdext outputs. When you run it in the command prompt, what's printed, that's the log. You can select it by right-clicking on the command line window and copy it. You can also just take a screenshot, which is fine too if it's not a long log. 
• The file "dmdext.log.config" it not the log. It's a file that tells dmdext.exe how to log. It just needs to be there but usually you don't need to modify it. If it's not there, dmdext.exe doesn't log anything.
• dmdext.exe doesn't need an AHK script to run. While you can do it, I don't recommend it when identifying problems because it's another factor where things can go wrong.
• When you run dmdext.exe, you either need to be in the same directory as dmdext.exe, or that directory must be in the system's PATH environment variable.

For your problem, @hlr53, I still don't know what's going on without a log. What you've pasted was the log config. To be honest, until now all problem reports I've received about FX3 were configuration problems, so maybe just try to double-check the install instructions. If you think it's a problem with dmdext: Logs please!

[hlr53]

[RESOLVED]

 

Thanks Freezy, making sense now and thanks for the help. Log terminology was throwing me for a loop. I know we can be a PITA at times. I figured it was always a config problem. First thing I did after work was install dmdext on my gaming laptop in the documents folder and plugged in the DMDv3 (which thankfully had a 6' cable attached to reach from the cab) and ran test. Ran perfectly and got the test image. 

 

On my cab I moved dmdext to my documents folder (which I know is my path) and it tested fine. Launched it from Powershell and all it would do is tell me program usage?

 

Then I realized I was a dumbf**k and had:

 

dmdext.exe dmdext mirror --source=pinballfx3 --no-virtual

 

because of all my copying and pasting I accidentally added an extra dmdext.

 

MANY THANKS TO EVERYONE!

 

And just now realized you can put static backglass images on FX3 without using PinballX.

[Slydog43]

I'm having trouble with DMDext again.  I have Win10x64, unblocked exe and dll.  Device manager has no errors, clean Win10 install.  After reading above messages I see that the config file is not read, makes sense as it checks for PinDMD1, 2, etc.  Now this make sense

 

here is what I see

 

C:\DMDExt>dmdext test

 [1] 2017/10/10 19:25:53.829  INFO | Launching console tool.

 [1] 2017/10/10 19:25:53.852 DEBUG | PinDMDv1 device not found.

 [1] 2017/10/10 19:25:53.868 DEBUG | PinDMDv2 device not found.

 [1] 2017/10/10 19:25:53.876 DEBUG | Checking port COM1 for PinDMDv3...

 [1] 2017/10/10 19:25:53.960 DEBUG | Error: The parameter is incorrect.

 [1] 2017/10/10 19:25:53.960 DEBUG | Checking port COM3 for PinDMDv3...

 

 

PinDMD3 should be found on COM4, any ideas?  Thanks

 

Z270 motherboard with Intel Chipset

Edited by Slydog43, 10 October 2017 - 11:29 PM.

[freezy]

Did you read my previous post?

[vondes]

Is it work if we use the mobile-phone-tracker.org mobile recorder on Android?

[SM26101977]

J'ai utilisé le programme dmdext-69 de freezy (voir le lien plus haut) et ça fonctionne sur FX3
Merci à vous et à freezy

Edited by SM26101977, 22 March 2018 - 02:41 PM.

[bpjacobsen]

yeah when you upgrade, you have to unblock all again.

 

Open powershell and use this command where path is where the files are.  It will unblock all of the files in the folder

 

Not sure if anyone will see this but for some reason since I updated my playfield screen, I cannot get the dmd for FX3 to appear anymore. I updated the dmdext w/ the latest and made sure none of the files are blocked but it will not display the dmd anymore. it's not like I changed the monitor displaying the dmd, only the playfield so no clue why this stopped working??

[bpjacobsen]

posted to GH w/ files so NVM. hopefully I can get help there.