1630 replies to this topic

[mjr]

I just would like to know what settings should be entered for FP in PBY to launch FP tables with future dmd and have the dmd close when exiting.

 

I'm not sure what's required for that, but if it doesn't close automatically on its own when FP exits, you'll probably want to add an "After" command that does a Windows TASKKILL command-line command to terminate the Future DMD process by name.  Hopefully someone here who runs FP knows what I'm talking about and can supply the command.

[wiesshund]

I just would like to know what settings should be entered for FP in PBY to launch FP tables with future dmd and have the dmd close when exiting.

 

Well, the FP commandline itself looks like this

 /STAYINRAM /open "[TABLEPATH]\[TABLEFILE]" /play /exit /arcaderender,,hide UseErrorLevel

 

and the EXE is fploader.exe

as for the futureDMD
First, make sure it is not running at windows start
Otherwise it wont exit, it will just try to run 2 of them, and the one that was running at startup wont exit

 

I do not know the pinballY syntax, but the commands i think are similar to pinballX

 

LaunchBeforeEnabled=True
LaunchBeforeWorkingPath=(path to your future pinball directory)
LaunchBeforeExecutable=FutureDMD.exe
LaunchBeforeParameters=table="[TABLEFILE]" close=1

[bpjacobsen]

 

I just would like to know what settings should be entered for FP in PBY to launch FP tables with future dmd and have the dmd close when exiting.

 

Well, the FP commandline itself looks like this

 /STAYINRAM /open "[TABLEPATH]\[TABLEFILE]" /play /exit /arcaderender,,hide UseErrorLevel

 

and the EXE is fploader.exe

as for the futureDMD
First, make sure it is not running at windows start
Otherwise it wont exit, it will just try to run 2 of them, and the one that was running at startup wont exit

 

I do not know the pinballY syntax, but the commands i think are similar to pinballX

 

LaunchBeforeEnabled=True
LaunchBeforeWorkingPath=(path to your future pinball directory)
LaunchBeforeExecutable=FutureDMD.exe
LaunchBeforeParameters=table="[TABLEFILE]" close=1

 

see attached fp settings in pby. I tried the command and fploader.exe but it will not launch a table. also see the other screenshot showing the instructions from the future dmd guide for pbx. The fields are not exactly the same and I am not sure where to put what. Surely somebody out there has pby working with  FP and future dmd???

Attached Files

•  fp settings in pby.png   23.36KB   2 downloads
•  future dmd guide.png   18.18KB   2 downloads

Edited by bpjacobsen, 08 December 2020 - 05:09 PM.

[bpjacobsen]

So for the most part I can load FP tables via pby but I just cannot figure out how to get the darn future dmd to run properly. The settings page is confusing to me and does not mimic pbx. I'm obviously not very savvy at this stuff. So por favor if someone please can help me out a bit more with where you think the commands should go in the pby fp settings per screenshot above, I would greatly appreciate it. I'm just really surprised that nobody has this setup and working that can supply screenshot of setup. Are there not a lot of folks using pby? Would love to get this working so I can get my recordings done and move on to fx3 setup. Will play more but it's a shot in the dark for me at this point.

[Thalamus]

Using PBY - sure, Future pinball - Hell no.

[wiesshund]

 

 

I just would like to know what settings should be entered for FP in PBY to launch FP tables with future dmd and have the dmd close when exiting.

 

Well, the FP commandline itself looks like this

 /STAYINRAM /open "[TABLEPATH]\[TABLEFILE]" /play /exit /arcaderender,,hide UseErrorLevel

 

and the EXE is fploader.exe

as for the futureDMD
First, make sure it is not running at windows start
Otherwise it wont exit, it will just try to run 2 of them, and the one that was running at startup wont exit

 

I do not know the pinballY syntax, but the commands i think are similar to pinballX

 

LaunchBeforeEnabled=True
LaunchBeforeWorkingPath=(path to your future pinball directory)
LaunchBeforeExecutable=FutureDMD.exe
LaunchBeforeParameters=table="[TABLEFILE]" close=1

 

see attached fp settings in pby. I tried the command and fploader.exe but it will not launch a table. also see the other screenshot showing the instructions from the future dmd guide for pbx. The fields are not exactly the same and I am not sure where to put what. Surely somebody out there has pby working with  FP and future dmd???

 

 

 

I see nothing listed in program EXE for your future pinball launcher

You are also missing your NVRAM folder

And you have nothing in the run before boxes, so you wont get any future DMD
 

 

FutureDMD.exe table="[TABLEFILE]" close=1

 

if it needs the path to work right then

FutureDMD.exe table="[TABLEPATH]\[TABLEFILE]" close=1

 

maybe lets see your pinballY config file?

Edited by wiesshund, 09 December 2020 - 07:58 PM.

[bpjacobsen]

update. So I was able to get what should be the correct setup via the pby facebook group per attached (1st pic) The dmd loads and closes as it should. However, I"m having the following issues;

 

1. When I attempt to run a table in pby, I get the message in the 2nd pic and if I select to option to allow admin, the table still won't run. There were a couple of times where a table ran but it's very inconsistent and most times I get the attached message (regardless of if I flag fploader.exe to run as admin or not)

2. The dmd will not hold the position when opened. I set it to screen 2 which is my dmd monitor according to FP editor and windows, but it will not stay put. I made sure the ini is not read only. HMM.

Attached Files

•  fp settings in pby.png   25.57KB   2 downloads
•  pby msg running fp table.png   41.08KB   1 downloads

[wiesshund]

update. So I was able to get what should be the correct setup via the pby facebook group per attached (1st pic) The dmd loads and closes as it should. However, I"m having the following issues;

 

1. When I attempt to run a table in pby, I get the message in the 2nd pic and if I select to option to allow admin, the table still won't run. There were a couple of times where a table ran but it's very inconsistent and most times I get the attached message (regardless of if I flag fploader.exe to run as admin or not)

2. The dmd will not hold the position when opened. I set it to screen 2 which is my dmd monitor according to FP editor and windows, but it will not stay put. I made sure the ini is not read only. HMM.

 

er huh?
If you right click future pinball.exe
does it have run as admin set in compatibility or something?
FP nor BAM should be running as admin

And even if you unflag BAM, if FP is still flagged it will still ask for admin

 

Nearly nothing pinball related should be run as Admin
 

[bpjacobsen]

I will double check but keep in mind, this only happens in PBY. I can run tables all day long via the editor. Wondered if a parameter is wrong or something in the settings I posted.

[bpjacobsen]

 

update. So I was able to get what should be the correct setup via the pby facebook group per attached (1st pic) The dmd loads and closes as it should. However, I"m having the following issues;

 

1. When I attempt to run a table in pby, I get the message in the 2nd pic and if I select to option to allow admin, the table still won't run. There were a couple of times where a table ran but it's very inconsistent and most times I get the attached message (regardless of if I flag fploader.exe to run as admin or not)

2. The dmd will not hold the position when opened. I set it to screen 2 which is my dmd monitor according to FP editor and windows, but it will not stay put. I made sure the ini is not read only. HMM.

 

er huh?
If you right click future pinball.exe
does it have run as admin set in compatibility or something?
FP nor BAM should be running as admin

And even if you unflag BAM, if FP is still flagged it will still ask for admin

 

Nearly nothing pinball related should be run as Admin
 

fixed the dmd position issue (had to change screen to 1 for some reason) but I confirmed that neither exe is set to run as admin. I am baffled as to why I"m getting this prompt. If I select the option to allow admin, that ends up checking the run as admin box for the fploader.exe. I'm at a stand still with this. I cannot run tables at all. I don't get it. 

[wiesshund]

dont know
Not sure if PBY has a run as admin option or something?

 

probably can tell better from your ini or xml or what ever config file format pby uses

Edited by wiesshund, 09 December 2020 - 11:37 PM.

[bpjacobsen]

I'll have to poke around for a file. I assume somewhere in there is an ini file. gotta be pulling the settings from somewhere. This is driving me insane. I need to turn the vpx system back on and make sure I'm not having the same issue there. But again, the message says "future Pinball requires administrative privileges". It's maddening.

[wiesshund]

I'll have to poke around for a file. I assume somewhere in there is an ini file. gotta be pulling the settings from somewhere. This is driving me insane. I need to turn the vpx system back on and make sure I'm not having the same issue there. But again, the message says "future Pinball requires administrative privileges". It's maddening.

http://mjrnet.org/pi.../AdminMode.html

 

You are not running that exe by mistake are you?

Edited by wiesshund, 10 December 2020 - 12:16 AM.

[mjr]

If you're getting that "Admin Mode Required" prompt, then you definitely have one of your executables (FP or BAM or one of the related ones) set to run in admin mode.  You should be able to clear this all up by removing the admin mode settings from whichever exe's you have set for admin mode.  You should probably go through ALL of your FP-related executables and make sure that their admin mode flags are all turned off.  Right click on each executable, select Properties, go to the Compatibility tab, and make sure Run this program as an administrator is un-checked.

[bpjacobsen]

apparently there is a separate admin mode exe for pby. beginning to wonder if my shortcut is pointing to that one. But then why would it not do the same thing when running vpx tables? so maybe not. I'll check when done work.

[bpjacobsen]

OMG, I figured it out! the fploader.exe and future pinball.exe both had the box checked to run in compatibility mode for xp. I unchecked it and now it's working perfectly! geez

[mjr]

OMG, I figured it out! the fploader.exe and future pinball.exe both had the box checked to run in compatibility mode for xp. I unchecked it and now it's working perfectly! geez

 

Glad you tracked it down.  That's a new one to me, but it makes sense given XP's relatively primitive security model that full admin mode would be needed for some old apps.  I'll have to add a note to the troubleshooting section about this in case anyone else runs into it.

[bpjacobsen]

 

OMG, I figured it out! the fploader.exe and future pinball.exe both had the box checked to run in compatibility mode for xp. I unchecked it and now it's working perfectly! geez

 

Glad you tracked it down.  That's a new one to me, but it makes sense given XP's relatively primitive security model that full admin mode would be needed for some old apps.  I'll have to add a note to the troubleshooting section about this in case anyone else runs into it.

 

Any idea why pby is loading the future dmd in the background? I have to hit alt-tab to get it to come forward. 

[wiesshund]

you try having it do the mouse click to set app in focus?

[bpjacobsen]

I got my dmd issue resolved I think. (had to update the table dmd in editor to 128x32. so it seems. 

 

When paging through the wheel, some tables are showing 2-3 times even though the db file only has it listed once.

where else might it be pulling a table name from?

 

I then tried copying a 'working' table's syntax in the db file and this seems to cause replication of table in the wheel even though I deleted the original one and saved. It seems like it is saving it somewhere inside pby or something? and this might be causing an issue with it freezing and not loading the tables. Hmm

 

So then I discovered that if I try to proceed with capturing video for one instance of the table showing on the wheel, I get the attached message. Almost like it's not seeing any of the info from the db file. but yet the table will run fine. So I'm guessing the db file is not used to actually run the table. it just runs it out of the tables folder based on the table name. Then if I try to setup capture parameters on the 2nd instance, it does not give me the error and acts like it will work, but then the table will not load and just freezes. So it's as if one instance sees the table FPT file and runs it but doesn't see the db file, and the other sees the db file but not the fpt file. really odd. It's like there is a jacked up link between the table and the xml file. Hope this makes sense. I will need to poke around more later but if anyone has insight, please due chime in.

Attached Files

•  capture msg.png   60.44KB   0 downloads

Edited by bpjacobsen, 10 December 2020 - 10:44 PM.