835 replies to this topic

[vbousquet]

@Quicksave : sorry for that. I have updated the 1.7.0 release, so please redownload, then run FlexDMDUI.exe. Let's hope we will be good this time !

[wiesshund]

fingers crossed

[QuickSave80]

@Quicksave : sorry for that. I have updated the 1.7.0 release, so please redownload, then run FlexDMDUI.exe. Let's hope we will be good this time !

 

 

fingers crossed

It's finally registered and working! No idea what caused it but thank you @vbousquet for fixing that. And @wiesshund for going over and beyond to help me figure this and out and get it fixed. I am new to the Vpin community but it's much better than the arcade community. I owe you guys a beer!

 

[wiesshund]

 No idea what caused it

 

 

Basically, somewhere at some time, it got ran and locked the DLL locations and saved the info some how somewhere

which appears to make it so that it can not find the stuff to run, or in your case register/unregister again.
It gets stuck and dies.

 

Vbousquet wrote in a contingency for that so that it could correct itself

I highly imagine that if one was to download, and open the zip, and accidentally run it from the zip

one might create a situation where one can no longer point things back at the original locations to attempt to fix on their own
because one does not know the temp folder name that was created on the fly, and then auto deleted.

And if you could not find either of the DLL's in the registry to find the path, you would have no hope of trying to recreate the folders.

 

just a guess anyways

And now the issue will not happen to anyone any more

Thanks @Vbousquet

[QuickSave80]

Makes sense. It's a new custom PC I replaced on my cocktail to make it double as a vpin set up and I installed and clicked a lot of things. I'm sure it would not be hard to run it from somewhere else and not remember

[freneticamnesic]

I don't seem to have any real options with the appearance of the DMD, color or size or anything. Trying out AMH and everything is overwritten with default settings, even if I change the DMD color in the script it defaults to orange.

Testing out another table I was working on in UltraDMD, when I tested yesterday with UltraDMD (prior to FlexDMD install) it gave a script error (one of the scene commands) but the same table in FlexDMD just crashes out completely (closes VP upon table load)

Nothing in the designer seems to work except registering the dlls (IE no preview of scenes or anything)

I'm not sure where dmddevice.dll is coming from, I installed mine with the 10.6 AIO installer, I noticed in your notes to grab the dll from Feezy but he only has dmddevice64.dll, so it's still showing a dmddevice.dll mismatch in the UI.

[vbousquet]

FlexDMD needs Freezy's DMD to work, so you need to install both. Most of the time, Freezy's DMD is laready installed with the all in one installer, in the Visual PinMame folder, which is fine. So in this situation, just downloading the zip for FlexDMD, unzipping it in your VPM folder, then running FlexDMDUI.exe should allow you to register it. FlexDMD search for both dmddevice.dll (for x86 applications like VPX) and dmddevice64.dll (for x64 applications like PinballY) but if you only have dmddevice.dll, it will be fine if you only use x86 applications like VPX.

 

Now, FlexDMDUI.exe is really here to ensure that everything is ok; if it's not working in it, it is very unlikely that it will work from other applications. The applications is designed to give the best feedback it can so what to solve; if the messages are unclear, a screenshot would help to see what is going wrong.

 

Finally, FlexDMD and Freezy's DMD create logs for situations where you end up in a crash. The files are named FlexDMD.log and DmdDevice.log. Posting them will alow to get some help from here.

 

Regards,

 

     Vincent

[Outhere]

Some more help it needed -- https://vpinball.com...all#post-194336

[wiesshund]

I don't seem to have any real options with the appearance of the DMD, color or size or anything. Trying out AMH and everything is overwritten with default settings, even if I change the DMD color in the script it defaults to orange.
Testing out another table I was working on in UltraDMD, when I tested yesterday with UltraDMD (prior to FlexDMD install) it gave a script error (one of the scene commands) but the same table in FlexDMD just crashes out completely (closes VP upon table load)
Nothing in the designer seems to work except registering the dlls (IE no preview of scenes or anything)
I'm not sure where dmddevice.dll is coming from, I installed mine with the 10.6 AIO installer, I noticed in your notes to grab the dll from Feezy but he only has dmddevice64.dll, so it's still showing a dmddevice.dll mismatch in the UI.

you are looking in the wrong place?
 
Freezy's DLL's
 
dmdext-v1.8.2-x64.zip
dmdext-v1.8.2-x86.zip
 
FlexDMD

FlexDMD -v1.7.1.zip

All of the above go unzipped into your VPinMAME folder

then you run FlexDMDUI and register it

and you can test both ultradmd and flexdmd functions by clicking on either tabs at the top of flexdmdUI

 

You do need your .NET framework up to date

Download .NET Framework | Free official downloads

And you need your VC++ runtimes up to date

Visual C++ Redistributable Runtimes All-in-One

 

 

 Freezy's DMD is laready installed with the all in one installer

 

What comes in that is a terribly old version, like 1.6 or 1.7 i think, also packs around an antiquated version of ultraDMD in the XDMD folder

it is also VPX 10.6.0 and has outdated scripts
We really need an updated installer i think?

Edited by wiesshund, 28 February 2021 - 08:00 PM.

[freneticamnesic]

Yea Freezy's 1.8.2 are split, x64 and x86, so you have to grab both to get both updated dlls. I don't know if it matters, but it only worked when I had dmddevice.dll from the x86 install. 

 

 Freezy's DMD is laready installed with the all in one installer

 

What comes in that is a terribly old version, like 1.6 or 1.7 i think, also packs around an antiquated version of ultraDMD in the XDMD folder

it is also VPX 10.6.0 and has outdated scripts
We really need an updated installer i think?

 

 

Looked like 1.4 lol

[wiesshund]

Yea Freezy's 1.8.2 are split, x64 and x86, so you have to grab both to get both updated dlls. I don't know if it matters, but it only worked when I had dmddevice.dll from the x86 install. 

 

 Freezy's DMD is laready installed with the all in one installer

 

What comes in that is a terribly old version, like 1.6 or 1.7 i think, also packs around an antiquated version of ultraDMD in the XDMD folder

it is also VPX 10.6.0 and has outdated scripts
We really need an updated installer i think?

 

 

Looked like 1.4 lol

 

Right this moment, unless you are compiling your own VPX, you do not technically need the 64bit

flexdmdUI will grumble about it, but it is a harmless grumble

32 bit VPX will not call up 64bit pinmame nor 64bit DMD extensions, though if there are any other pinball simulations that do or can use the DMD extensions in DLL
form, they may use the 64bit

 

I put it in there anyways, if i need it, maybe we get a 64bit beta or something, it's there, if not, it's only a few kb

I think if you run setup64 in the pinmame folder, and test/setup ROMs, it might actually use it but i am not actually sure, i never really bothered to look
but it would make sense if it did use it.

FlexDMD would not actually use it though, it is 32 bit, it just likes to grumble and tell you that the 32 and 64 bit DLL's dont match
it will still register as flex and ultra DMD's though

 

and provided the .NET and VC++ dependencies are up to date, should run

you should be able to run the demo screens right there in flexdmdUI

 

 

1.4?
oh my, that is terrible
when 10.7 comes out of beta, we really need a new fully updated all in one installer

Edited by wiesshund, 28 February 2021 - 08:33 PM.

[vbousquet]

In fact, FlexDMD is a "universal" app ; it is both x86 and x64, and depending on who is calling it, it adapts itself and dynamically loads the right version of dmddevice. That's why when installing it search for both x86 and x64.

For the moment, FlexDMD is used in the following contexts:

• VPX: x86
• VPinMame setup: x86 or x64, depending on the one you use between setup.exe and setup64.exe
• PinballY: x64 (may also be x86 if you use the x86 version of PinballY)

[freneticamnesic]

Finally, FlexDMD and Freezy's DMD create logs for situations where you end up in a crash. The files are named FlexDMD.log and DmdDevice.log. Posting them will alow to get some help from here.

 

 

No error in these logs, just a hard crash

[vbousquet]

For AMH, normally you should not need to modify anything to run it. FlexDMD replace UltraDMD silently. If you want to change, colors and such, you use FlexDMDUI.exe, there is a tab for that.

Regarding the crash, what are you using precisely ? Only the original table (could you post the table name, to get the version number) with its original script ? A modified script (which one ?) ?

[wiesshund]

For AMH, normally you should not need to modify anything to run it. FlexDMD replace UltraDMD silently. If you want to change, colors and such, you use FlexDMDUI.exe, there is a tab for that.

Regarding the crash, what are you using precisely ? Only the original table (could you post the table name, to get the version number) with its original script ? A modified script (which one ?) ?

 

AMH has a line in the script IIRC

that force sets the DMD colour to a pale ghostly green

have to comment out that line, if using that script version, or edit it to another colour

 

i think it was

 

 FlexDMD.Color = RGB(31, 255, 127)

a lot of people i think have an older AMH like 062718 or so

they should have 091315, that is the latest

Thalamus has it HERE

 

and they may want to make a small edit

UseFullColor = "True" '                           "True" / "False"
'DMDColorSelect = "Green"            ' Rightclick on UDMD window to get full list of colours

Well, if they want to use the color DMD anyways
(and if you cant find the coloured DMD, just ask, i can zip and upload it)

 

Finally, FlexDMD and Freezy's DMD create logs for situations where you end up in a crash. The files are named FlexDMD.log and DmdDevice.log. Posting them will alow to get some help from here.

 

 

No error in these logs, just a hard crash

 

 

If you have a vbs script for AMH i the table folder
remove the script
 

Go to thalamus's site at the link i gave above
replace the table's script in the table editor, with thalamus's table script

 

run table

flexDMD should simply run it with the table's native ultraDMD functions

and if you have the coloured DMD and do not want it green, then see my above edits for lines 44 and 45

[vbousquet]

That was my question ; the line you show is from a very old alpha release of FlexDMD. Now with the latest versions, you don't need anything ; FlexDMD is supposed to work out of the box with all UltraDMD tables. So this script should not be used anymore ; it has been removed from the distribution. Using the original script or Thalamus' one is the way to go. Therefore, colors should be the ones from the configuration (not the script, since you use the original script).

[wiesshund]

That was my question ; the line you show is from a very old alpha release of FlexDMD. Now with the latest versions, you don't need anything ; FlexDMD is supposed to work out of the box with all UltraDMD tables. So this script should not be used anymore ; it has been removed from the distribution. Using the original script or Thalamus' one is the way to go. Therefore, colors should be the ones from the configuration (not the script, since you use the original script).

 

Yea, problem is
1) some places have prepatched the table, and then never updated it
2) some places have old documentation, and again, never update it

 

So the guy playing it tries to do right, but ends up doing wrong due to old info

or at least info from a source that never updated.

 

That's why i directly point at your distributions rather than mirror them as you have updated and/or removed no longer valid scripts in your zip

 

I am presently using none of the flexDMD scripts from before UltraDMD takeover, with the exception of a few of JP's tables
that simply did not leverage an external display at all UltraDMD or otherwise, and those will go to the trashbin when JP finishes those updates and leverages FlexDMD directly.

 

Anything that directly leveraged UltraDMD, as you said, simply just works now, as is, in stock form.
And at much less CPU load to boot.

[freneticamnesic]

AMH works fine, with or without the script - the only fickle thing was installing Freezy's x64 version rather than x86, so we're all good now that you've sorted me out

And I don't think you need to worry about me having the latest version of AMH or not.... Unless someone has updated it since I last uploaded it, the script that came with the FlexDMD install is numbered 062718a so it's the most recent version. But as far as I can tell, the script isn't needed on this table with your latest build. I haven't tested thoroughly but it boots up and launches.

 

I have an unreleased table I was working on that I tried to get up and running, but like I said it's not been updated in 3 years, oddly enough though UltraDMD hasn't been updated in at least that long, and while it worked previously it wasn't working recently. It gave a script error on one of the UltraDMD.Scene lines and kicked back to the editor (this was when I was using UltraDMD). That was fine, at least it gave me a starting point, but with FlexDMD there's no such error, just a hard crash. I wouldn't worry too much about it in this case, it's not holding me back from doing anything, I'm just reporting a bug. 

 

Thanks guys for the help.

[wiesshund]

And I don't think you need to worry about me having the latest version of AMH or not.... Unless someone has updated it since I last uploaded it, the script that came with the FlexDMD install is numbered 062718a so it's the most recent version. But as far as I can tell, the script isn't needed on this table with your latest build. I haven't tested thoroughly but it boots up and launches.

 

 

Well, 062718a is actually an old version of the table script (regardless of flexDMD modified or not)

and the script has issues unrelated to flexDMD or ultraDMD.

 

The script i linked you above is the most recent for America's Most Haunted and fixes a number of things unrelated to ultraDMD or flexDMD

The table needs nothing special though to run as far as flexDMD is concerned though

 

You could drop the Thalamus script in the tables folder, but personally, i recommend copying the script
and pasting it into the script editor, replacing the existing script entirely, that way you dont have scripts floating around in places.

 

On this table, the script itself was the only way i ever saw it updated, never saw it updated in a full table package for what ever reason.

 

What you have will run fine as far as the DMD but if you want to correct some table oddities, what you need is up there a couple posts

 

 

 

On the table you are working on
Do you by chance remember the ultraDMD error?
Or can you show that the offending line was?

FlexDMD usually does show the error if you botch an ultraDMD line, but maybe you got something it is not sure how to report?
Might help Vbousquet to know what it is?

[freneticamnesic]

 

And I don't think you need to worry about me having the latest version of AMH or not.... Unless someone has updated it since I last uploaded it, the script that came with the FlexDMD install is numbered 062718a so it's the most recent version. But as far as I can tell, the script isn't needed on this table with your latest build. I haven't tested thoroughly but it boots up and launches.

 

 

Well, 062718a is actually an old version of the table script (regardless of flexDMD modified or not)

and the script has issues unrelated to flexDMD or ultraDMD.

 

The script i linked you above is the most recent for America's Most Haunted and fixes a number of things unrelated to ultraDMD or flexDMD

The table needs nothing special though to run as far as flexDMD is concerned though

 

You could drop the Thalamus script in the tables folder, but personally, i recommend copying the script
and pasting it into the script editor, replacing the existing script entirely, that way you dont have scripts floating around in places.

 

On this table, the script itself was the only way i ever saw it updated, never saw it updated in a full table package for what ever reason.

 

What you have will run fine as far as the DMD but if you want to correct some table oddities, what you need is up there a couple posts

 

 

 

On the table you are working on
Do you by chance remember the ultraDMD error?
Or can you show that the offending line was?

FlexDMD usually does show the error if you botch an ultraDMD line, but maybe you got something it is not sure how to report?
Might help Vbousquet to know what it is?

 

 

It sounds like whoever updated the script was updating a 2015 build of the table, because the date at the end is September 2015, even though the table was updated in June 2018. 

 

Here's the error I get when I run the other table with UltraDMD

Line: 1019

The remote server machine does not exist or is unavailable

'ultradmd.DisplayScene00'

 

Here's the table in question https://www.dropbox....1pCl_DGb1a?dl=0

 

Crashes at the same spot in FlexDMD and UltraDMD, only UltraDMD gives the error (and only crashes to editor) while Flex closes VP

Other games are working fine, AMH, Diablo, the fantastic Mad Scientist table

Edited by freneticamnesic, 01 March 2021 - 02:44 AM.