32 replies to this topic

[Mrtr32]

Unregister FLEXDMD from FlexDMDUI

Delete all the FLEXDMD entry in the registry

Restart computer

Register FlexDMD again

 

You must have only 1.8.0 in the registry

[Andy McDandy]

Unregister FLEXDMD from FlexDMDUI

Delete all the FLEXDMD entry in the registry

Restart computer

Register FlexDMD again

 

You must have only 1.8.0 in the registry

 

Already did that but I'm going to do it again just in case I missed an entry.  There are two entries that Windows would not allow me to delete.

[Andy McDandy]

@Mrtr32 - Just completed that process again and still no luck.

[wiesshund]

Are you sure the DMD is not possibly appearing under the table?

If you are using exclusive fullscreen mode (which you should)
disable it temporarily so you can see any things that might go under the table
you should be able to see the flexDMD in the task bar or by alt tabbing, if it is running.

 

The table already enables flexDMD if table orientation is FS

You say the test tabs in flexDMDUI work, so flexDMD itself works then

[Andy McDandy]

Nothing comes up in the taskbar for FlexDMD when loading any tables using it.  I am now considering maybe redoing the system from scratch in case there are other issues I have not yet noticed.

[wiesshund]

Do the demo tabs in FlexDMDUI work?

 

the ultraDMD and FlexDMD tabs?

if the demo tabs work
run a table, then exit it
then look for the flexDMD log file
and try to paste the log here

[Andy McDandy]

I can go to the tabs but nothing happens when I click on start or stop.

[wiesshund]

I can go to the tabs but nothing happens when I click on start or stop.

Ok

Then we have flexDMD prolem

 

Did you try unregistering flexDMD

 

and then reregistering it?

 

Also, are you sure Freezy's is working?
Are you able to set ROM DMD's to use external DLL and have the freezy's display show up?
FlexDMD requires Freezy's installed and working

You should have a flexdmd log and a dmddevice log

Maybe you can show those to us?

[Andy McDandy]

Here is FlexDMD.log

 

 [1] 2022/05/11 19:47:47.162  INFO | FlexDMD version 1.8.0.0
 [1] 2022/05/11 19:47:47.201  INFO | Table File defined to JP's Ghostbusters Slimer 3.0.1.vpx
 [1] 2022/05/11 19:47:47.201  INFO | Render mode set to DMD_RGB
 [1] 2022/05/11 19:47:47.201  INFO | Game name set to jp_ghostbusters
 [1] 2022/05/11 19:47:47.218  INFO | Show DMD
 [1] 2022/05/11 19:47:47.218  INFO | Loaded dmddevice.dll from C:\vPinball\Visual Pinball\VPinMAME\dmddevice.dll to create a virtual DMD
 [1] 2022/05/11 19:47:48.862 ERROR | Failed to load dmdscreen.dll in C:\vPinball\Visual Pinball\VPinMAME\dmdscreen.dll
 [1] 2022/05/11 19:47:48.862  INFO | Starting render thread for game 'jp_ghostbusters' using render mode DMD_RGB
[11] 2022/05/11 19:47:48.867  INFO | RenderThread start
 [1] 2022/05/11 19:47:49.032  INFO | New bitmap added to asset manager: VPX.bkempty
 [1] 2022/05/11 19:47:49.041  INFO | New bitmap added to asset manager: VPX.dempty&dmd=2
[11] 2022/05/11 19:47:49.174  INFO | Attaching to Visual Pinball Player window lifecycle
[11] 2022/05/11 19:47:49.174  WARN | Abnormally long elapsed time between frames of 0.085239s (rendering lasted 85.2386ms, sleeping was 0ms), limiting to 66ms
 [1] 2022/05/11 19:47:49.583  INFO | New bitmap added to asset manager: VPX.dempty&dmd=2&add
 [1] 2022/05/11 19:47:49.589  INFO | New bitmap added to asset manager: VPX.dg&dmd=2&add
 [1] 2022/05/11 19:47:49.589  INFO | New bitmap added to asset manager: VPX.da&dmd=2&add
 [1] 2022/05/11 19:47:49.589  INFO | New bitmap added to asset manager: VPX.dm&dmd=2&add
 [1] 2022/05/11 19:47:49.601  INFO | New bitmap added to asset manager: VPX.de&dmd=2&add
 [1] 2022/05/11 19:47:49.601  INFO | New bitmap added to asset manager: VPX.do&dmd=2&add
 [1] 2022/05/11 19:47:49.601  INFO | New bitmap added to asset manager: VPX.dv&dmd=2&add
 [1] 2022/05/11 19:47:49.601  INFO | New bitmap added to asset manager: VPX.dr&dmd=2&add
 [1] 2022/05/11 19:47:49.617  INFO | New bitmap added to asset manager: VPX.bkempty&dmd=2
 [1] 2022/05/11 19:47:51.688  INFO | New bitmap added to asset manager: VPX.dc&dmd=2&add
 [1] 2022/05/11 19:47:51.693  INFO | New bitmap added to asset manager: VPX.dd&dmd=2&add
 [1] 2022/05/11 19:47:51.693  INFO | New bitmap added to asset manager: VPX.di&dmd=2&add
 [1] 2022/05/11 19:47:51.693  INFO | New bitmap added to asset manager: VPX.dt&dmd=2&add
 [1] 2022/05/11 19:47:51.693  INFO | New bitmap added to asset manager: VPX.ds&dmd=2&add
 [1] 2022/05/11 19:47:51.709  INFO | New bitmap added to asset manager: VPX.d0&dmd=2&add
 [1] 2022/05/11 19:47:51.709  INFO | New bitmap added to asset manager: VPX.dn&dmd=2&add
 [1] 2022/05/11 19:47:53.758  INFO | New bitmap added to asset manager: VPX.jppresents&dmd=2
 [1] 2022/05/11 19:47:56.777  INFO | New bitmap added to asset manager: VPX.title&dmd=2
 [1] 2022/05/11 19:48:00.897  INFO | New bitmap added to asset manager: VPX.dh&dmd=2&add
 [1] 2022/05/11 19:48:02.217  INFO | New bitmap added to asset manager: VPX.d1&dmd=2&add
 [1] 2022/05/11 19:48:02.233  INFO | New bitmap added to asset manager: VPX.dmore&dmd=2&add
 [1] 2022/05/11 19:48:02.400  INFO | New bitmap added to asset manager: VPX.d0a&dmd=2&add
 [1] 2022/05/11 19:48:04.618  INFO | New bitmap added to asset manager: VPX.d2&dmd=2&add
 [1] 2022/05/11 19:48:04.684  INFO | New bitmap added to asset manager: VPX.db&dmd=2&add
 [1] 2022/05/11 19:48:07.020  INFO | New bitmap added to asset manager: VPX.d3&dmd=2&add
 [1] 2022/05/11 19:48:09.424  INFO | New bitmap added to asset manager: VPX.d4&dmd=2&add
 [1] 2022/05/11 20:35:28.371  INFO | Stopping render thread
[11] 2022/05/11 20:35:28.388  INFO | RenderThread end
 [1] 2022/05/11 20:35:28.388  INFO | Hide DMD
 [1] 2022/05/11 20:35:28.388  INFO | Disposing DMD dynamic link library

 

And here is DmdDevice.log

 

 [1] 2022/05/11 19:47:48.543  INFO | Successfully loaded config from C:\vPinball\Visual Pinball\VPinMAME\DmdDevice.ini.
 [1] 2022/05/11 19:47:48.554  INFO | Starting VPinMAME API 1.9.0 through VPinballX.exe.
 [1] 2022/05/11 19:47:48.554  INFO | Assembly located at C:\vPinball\Visual Pinball\VPinMAME\dmddevice.dll
 [1] 2022/05/11 19:47:48.554  INFO | [vpm] Create(): New output id is 1
 [1] 2022/05/11 19:47:48.554  INFO | [vpm] Open(1)
 [1] 2022/05/11 19:47:48.554  INFO | [vpm] PM_GameSettings(1, jp_ghostbusters, 0)
 [1] 2022/05/11 19:47:48.554  INFO | Disabling game colorization
 [1] 2022/05/11 19:47:48.554  INFO | Setting game name: jp_ghostbusters
 [1] 2022/05/11 19:47:48.554  INFO | Setting color: #FFFF5820
 [1] 2022/05/11 19:47:48.694  INFO | PinDMDv1 device not found.
 [1] 2022/05/11 19:47:48.769  INFO | PinDMDv2 device not found.
 [1] 2022/05/11 19:47:48.774  INFO | Checking port COM1 for PinDMDv3...
 [1] 2022/05/11 19:47:48.851 ERROR | Error: The parameter is incorrect.
 [1] 2022/05/11 19:47:48.851  INFO | PinDMDv3 device not found.
 [1] 2022/05/11 19:47:48.851 ERROR | No renderers found, exiting.
 [1] 2022/05/11 20:35:28.390  INFO | [vpm] Close(1)
 [1] 2022/05/11 20:35:28.390  INFO | Closing up.

 

[wiesshund]

Umm well, FlexDMD is actually running

 

Freezy's though seems to be exiting?
it also looks like it is looking for PinDMD devices

 

You may want to look at your dmddevice.ini and set all the pinDMD type device entries to FALSE

 

a few things to check

 

[virtualdmd]
enabled = true


; virtual dmd stays on top of all other windows
stayontop = True

[pindmd1]

; if false, doesn't bother looking for a pinDMD1
enabled = false

[pindmd2]

; if false, doesn't bother looking for a pinDMD2
enabled = false

[pindmd3]

; if false, doesn't bother looking for a pinDMD3
enabled = false

; COM port, e.g. COM3
port = 

[pin2dmd]

; if false, doesn't bother looking for a PIN2DMD
enabled = false

; how long to wait in milliseconds after sending a palette
delay = 25

[pixelcade]

; if false, doesn't bother looking for a Pixelcade
enabled = false

; COM port, e.g. COM3
port = 

; color matrix to use, either "rgb" or "rbg"
matrix = rgb

[Andy McDandy]

Wow, that worked.  Thank you so much.  It does raise a question though, why are those settings not set by default?

[wiesshund]

Wow, that worked.  Thank you so much.  It does raise a question though, why are those settings not set by default?

 

In all honesty? I think that...
 

Freezy's was primarily invented to create a video stream that could be sent to a real DMD device
VPM DMD's already displayed just fine on a LCD
A real DMD device needs the image sent to it in a way it can read and display, which is 128 dots long and 32 dots tall

And so that was the default way to be

 

Then it was determined that freezy's could also make a nicer LCD display

 

And Later (recently) Freezy and Vbousquet(FlexDMD) worked together and greatly enhanced freezy's dmd extensions
which is what makes the image, to have a lot of LCD based enhancements to get an LCD to look damned near like a real DMD display

But its reason for existing in the 1st place, was to allow the use of a real DMD and so makes sense it would carry default settings
towards that end.

[Andy McDandy]

That makes sense.  Thanks again for your help.