152 replies to this topic

[wiesshund]

 

I'm on PinballY, I believe it uses the [TABLEFILE] variable according to the help file. I don't need a specific DMD size for every table, so with a global size/dimension from the command line (actually from the batch file), I'm happy, and is enough for me right now.
 

@echo off

c:

cd "C:\Games\Visual Pinball\VPinMAME"

start /min ""  "dmdext.exe" mirror --source=futurepinball --FPS 60 --virtual-stay-on-top --virtual-position 4930 12 1490

 

But I'll try your suggestion anyway. Thanks!

 

 

You need the INI file working to use any styles as well
mind you i do not know what you have for a DMD, it could be a pinDMD for all i know
and you dont get styles with that.

[Cadorna]

 

 

I'm on PinballY, I believe it uses the [TABLEFILE] variable according to the help file. I don't need a specific DMD size for every table, so with a global size/dimension from the command line (actually from the batch file), I'm happy, and is enough for me right now.
 

@echo off

c:

cd "C:\Games\Visual Pinball\VPinMAME"

start /min ""  "dmdext.exe" mirror --source=futurepinball --FPS 60 --virtual-stay-on-top --virtual-position 4930 12 1490

 

But I'll try your suggestion anyway. Thanks!

 

 

You need the INI file working to use any styles as well
mind you i do not know what you have for a DMD, it could be a pinDMD for all i know
and you dont get styles with that.

 

 

I tried what you suggest me about using a fresh dmddevice.ini file in a different directory and the issue continue. The problem is the height of the DMD window, I mean, every time that the batch runs, the height change from the value on the .INI file to a different one.

 

For example, my desire DMD dimmensions and position after rezising the DMD manually are:

 

virtualdmd left = 4839

virtualdmd top = 8

virtualdmd width = 1671

virtualdmd height = 358

 

But when the table is re-launched, the DMD height is noticeable bigger and if I click on the DMD and save the new value, the resultant INI file is:

 

virtualdmd left = 4839

virtualdmd top = 8

virtualdmd width = 1671

virtualdmd height = 418

 

It seems a kind of issue with the "Ignore Aspect radio" option.

[wiesshund]

ignore aspect ratio should only have affect when grabbing and resizing.
For FP, due to the nature of it's DMD, it is probably best not to ignore the aspect ratio
as the DMD's tend to look kinda bad, not as forgiving as pinmame of flexDMD images, for some reason

 

make sure you dont use an INI and try specifying a dimensions value in the command line both
i think they will fight eachother

[Cadorna]

make sure you dont use an INI and try specifying a dimensions value in the command line both

i think they will fight eachother

 

Yes, that's what I was doing and will continue to do before this test. My cab has a wooden skin over an LCD monitor and I need specific dimensions for the DMD to fit properly.

[ManWorkingHere]

I checked on GitHub for support of DMDEXT and it appears this sizing problem is with the program.  Someone else in March '22 already commented on this issue in multiple GitHub posts.

 

So until a developer changes DMDEXT, the sizing issue will be with us.

 

I was wondering about going back to an earlier version, like 1.8 of DMDEXT to see if the sizing problem started there.

[wiesshund]

 

make sure you dont use an INI and try specifying a dimensions value in the command line both

i think they will fight eachother

 

Yes, that's what I was doing and will continue to do before this test. My cab has a wooden skin over an LCD monitor and I need specific dimensions for the DMD to fit properly.

 

 

 

Highly exaggerated obviously
but works perfectly fine here, 0 issues.
I can make it any distorted size and save it and thats how it runs, every time.

 

 

I checked on GitHub for support of DMDEXT and it appears this sizing problem is with the program.  Someone else in March '22 already commented on this issue in multiple GitHub posts.

 

So until a developer changes DMDEXT, the sizing issue will be with us.

 

I was wondering about going back to an earlier version, like 1.8 of DMDEXT to see if the sizing problem started there.

 

Respectfully, i would have to say this is some kind of user error rather than dmdext issue
as it works as expected here?

That or i am doing something weird?

Edited by wiesshund, 03 November 2022 - 07:18 PM.

[ManWorkingHere]

wiesshund

Posted 03 November 2022 - 07:07 PM

 

"Highly exaggerated obviously

but works perfectly fine here, 0 issues.
I can make it any distorted size and save it and that's how it runs, every time."
 

---

 

I am trying to make this work from the Pinup Popper menu on my home made cabinet.  I would like to get the DMDEXT to size to 1024 by 768.  Would you mind sharing the syntax of how you launch Future Pinball?  A copy of the command line with a resizing example would help this user. 

 

I would like to see how you change the sizing to any shape you like.

 

Thanks!

 

Edited by ManWorkingHere, 06 November 2022 - 10:45 PM.

[acem77]

trying to run this with just future pinball, using info from the bitpixel instructions.

that uses the 1st line in this list. but i get the same errors no mater what i try as there seems to be a syntax error "=" missing after -s

 

dmdext.exe mirror -s futurepinball --use-ini=DmdDevice.ini

dmdext.exe mirror -s=futurepinball --use-ini=DmdDevice.ini

dmdext.exe mirror -s=futurepinball --use-ini="C:\vPinball\VisualPinball\VPinMAME\DmdDevice.ini"

dmdext.exe mirror -s futurepinball --use-ini="C:\vPinball\VisualPinball\VPinMAME\DmdDevice.ini"

 

 

ERROR:

 

  -s/--source option violates format.

  -s/--source required option is missing.

[AceE012]

Hello, I was able to get this working with no issues when using VPX but I cannot get it to work with FP on my front end.  All of the scrips shown in the tutorial are for a a pinup popper system but I am not in a cabinet and am wanting to run this from big box.  I understood everything until I got to the script portion of the installation instructions.  Now I am completely lost!  I have tried copying the script shown below into launch box "running script" field in the edit emulator portion of the front end.  Being that I know NOTHING about these launch scrips, I don't even know if I am putting the script in the right place or if the script will even work with launchbox...  My FP and VPX installs are in the default locations and I confirmed I copied OpenGL32.dll to the Future Pinball directory.  I can launch FP tables from launchbox without issue using these parameters;

 

/open %romfile% /play /exit 

 

but have no idea what I would need to add to launch the dmd?

 

c:
cd "C:\vPinball\VisualPinball\VPinMAME"
start /min "" "dmdext.exe" mirror --source=futurepinball -q --virtual-stay-on-top --fps 60 -g "[GAMENAME]" --use-ini="C:\vPinball\VisualPinball\VPinMAME\DmdDevice.ini"

[AceE012]

deleted

Edited by AndrewL12, 30 March 2023 - 11:50 PM.

[mandermannen77]

How can i adjust the DMD style settings per table. I only can make settings per table if the table has a ROM. For future pinball tables i cannot set a style of settings per table in dmddevice.ini. I tried different gamenames (the fpt-filename and the game name in de info in FP) but it selects only the default style. Do is miss something? 

[TerryRed]

How can i adjust the DMD style settings per table. I only can make settings per table if the table has a ROM. For future pinball tables i cannot set a style of settings per table in dmddevice.ini. I tried different gamenames (the fpt-filename and the game name in de info in FP) but it selects only the default style. Do is miss something? 

 

 

Try updating to the latest version of dmdext.exe

 

I was just testing this, and it seems to work correctly now.

[mandermannen77]

Thank you for your fast response! I tríed the new and newest beta version of dmdext.exe but still it doesnt work. Maybe its because i also have a pixelcade. Therefore i have to check the external dll in the settings. In vpx i can create per tablesettings, but only for tables with a rom.

[mandermannen77]

Maybe i can set a an ini file per table and use the if function in the script from the emulator to recall to the specific ini file with different default settings? But i don't know if you can use an ini file with a different name as dmddevice. i'm new to all this

[mandermannen77]

That didn't work. It's only using the dmddevice.ini in C:\vPinball\VisualPinball\VPinMAME. 

[mandermannen77]

Making some process. I find out that pixelcade als have an exe with the commandline dmdext.exe mirror -s futurepinball --use-ini=DmdDevice.ini

I think it only accepts 1 ini-file for my 2 dmd's. I deleted this exe from the Future pinball script and now it accepts different named ini-files (1 ini for 2 dmd's). Now i have to make an if function per table in the emulator script from FP if i want to have a different style of DMD per table. Still strange that i only can save styles per table directly in the VirtualDMDscreen with vpx-tables with rom files en have to use this workaround for other tables. Maybe because i use 2 DMD's

[wiesshund]

dmdext.exe" mirror --source=futurepinball -g "tablename" --use-ini="D:\Pinball\FP\DMDext\DmdDevice.ini" 

 

"tablename" will be whatever what ever variablename your frontend uses

 

for example, PinballX would use [TABLEFILEWOEXT] so

 

dmdext.exe" mirror --source=futurepinball -g "[TABLEFILEWOEXT]" --use-ini="D:\Pinball\FP\DMDext\DmdDevice.ini" 

[mandermannen77]

It works, thank you so much!! I was referring to the wrong dmddevice.ini inside vpx. Indeed just use the tablename from pinup popper

[wiesshund]

It works, thank you so much!! I was referring to the wrong dmddevice.ini inside vpx. Indeed just use the tablename from pinup popper

you can share the ini but i do not
just in case a table name overlaps etc

 

so i keep the fp and the vpx totally separate

[mandermannen77]

Yes thank you! I also keep it this way, 2 ini files for vpx and fp. If i run into problems i will let it know. Its really nice to have a active community for this hobby, to share the knowledge, i just run into this hobby when i was planning to build an arcade but found out that vp has so much more challenges