Closed Brakelmann closed 7 years ago
Hmm I've never heard about that controller. Looks like an input controller though. What are you using for the DMD? And can you post a log of the crash?
Hi freezy,
I am using an LCD Monitor as DMD. Try to get a log file an get back.
BR, Brakelmann.
Trying to create the log file without success. Get the following DEBUG Lines when running in console mode. Good Case: (DMD Test Grafics appears on screen)
C:\Users\vpin\Downloads\dmdext-v1.5.2>dmdext.exe test
[1] 2017/09/17 23:57:03.751 INFO | Launching console tool.
[1] 2017/09/17 23:57:03.782 DEBUG | PinDMDv1 device not found.
[1] 2017/09/17 23:57:03.798 DEBUG | PinDMDv2 device not found.
[1] 2017/09/17 23:57:03.798 DEBUG | Checking port COM1 for PinDMDv3...
[1] 2017/09/17 23:57:03.892 DEBUG | Error: Falscher Parameter.
[1] 2017/09/17 23:57:03.892 DEBUG | PinDMDv3 device not found.
[1] 2017/09/17 23:57:03.907 DEBUG | PIN2DMD device not found.
[1] 2017/09/17 23:57:03.970 INFO | Added VirtualDMD renderer.
[1] 2017/09/17 23:57:03.985 DEBUG | Resizing virtual DMD to 128x32
[1] 2017/09/17 23:57:04.001 INFO | Setting up Render Graph for 1 destination(s)
[1] 2017/09/17 23:57:04.001 INFO | Connecting Image Source to Dmd (Bitmap => Bitmap)
[1] 2017/09/17 23:57:04.032 INFO | Press CTRL+C to close.
[9] 2017/09/17 23:57:16.187 INFO | Source for 1 renderer(s) stopped.
[9] 2017/09/17 23:57:16.187 DEBUG | Disposing render graph.
Bad Case: (DMD Test Grafics not opening up)
[1] 2017/09/18 00:00:23.977 INFO | Launching console tool.
[1] 2017/09/18 00:00:24.024 DEBUG | PinDMDv1 device not found.
[1] 2017/09/18 00:00:24.040 DEBUG | PinDMDv2 device not found.
[1] 2017/09/18 00:00:24.040 DEBUG | Checking port COM1 for PinDMDv3...
[1] 2017/09/18 00:00:24.134 DEBUG | Error: Falscher Parameter.
[1] 2017/09/18 00:00:24.134 DEBUG | Checking port COM3 for PinDMDv3...
Stuck here...
And I guess checking on COM3 might be the issue, as the PinIn is registered on COM3. Any Idea how to get that solved?
Thanks, Brakelmann.
Yeah, specify the output device with --destination=virtual
or set enabled=false
for all devices but the virtual dmd in DmdDevice.ini.
Setting the output device with --destination=virtual
works, but changing the sttings in the DmdDevice.ini does not have any effect. It still tries to load the DMDv1 to V3.
Attache there is my DmDDevice.ini:
I do not see any misconfiguration in it. Maybe the DLL loads default values on doe not take care about the ini parameters.
I needed to txt to file otherwise I could not attach the file here. DmdDevice.ini.txt
On my computer it has the correct extension .ini.
Any idea? Thanks, Brakelmann.
What's the host application? Where are you running it from? Where's DmdDevice.dll and DmdDevice.ini located?
It in my test directory C:\Users\vpin\Downloads\dmdext-v1.5.2. Just using the test mode with "dmdext.exe test" not using the host application at the moment.
It would be VPinMame located under: C:\Pinball\Visual Pinball\VPinMAME
I will give it a try using VPinMame...
Well, have a look at the documentation how it works. DmdDevice.ini is only used by DmdDevice.dll, which needs a host application through VPM. For the command line tool, use the command line parameters.
Thats it, its working within VPinMame! Thanks a lot freezy, Brakelmann.
Hi,
I am running a VPIN on Winows10 64Bit with PinIn1 as Input controller (Arduino based). http://www.vpin-shop.de/epages/64158583.sf/de_DE/?ObjectPath=/Shops/64158583/Products/50021
I am using the latest dmdext V1.5.2 an copied the DmdDevice.dll to the VPInMame folder. As long as I am just using the keyboard, everything is workin as expected. I use the VPinMame Setup to test the ACD LE (rom: acd_168h) and changed the DMD to use external. As soon as I connect the PinIn1 controller and redo the test VPinMame does not show the DMD and crashes on exiting.
Any idea how to solve this issue?
Thanks in advance, Brakelmann.