161 replies to this topic

[wiesshund]

 

Maybe you should start posting your PBY specific problems in the PBY thread. You would probably get a better chance of someone who uses it helping you there.

Well, this is more of a future dmd question though. PBY is just doing what it is being told. I doubt there would be a way to put a command in fp setup in pby that would know to turn off the future dmd only for certain tables. It would have to be programmed somehow within the futuredmd.ini file I would think? My batch file that pby runs from the run before field runs future dmd. But the table specific settings come from the ini.

 

 

If for the table in question you do not want to see the DMD
maybe try putting a size in the ini of 0x 0y

or putting the location off screen?

 

As i gather it shows the DMD regardless
It could be that the table in question has several DMD type screens in it and futureDMD is just picking up on one of them, whether it does something or not

[TerryRed]

The easiest solution for PBY and PBX is to create a FP-NoDMD emulator / system that doesn't launch FutureDMD. That's what I did with PBX way back.

 

I also recommend to cabinet users (who use PBY and PBX) who play my PinEvent FP table updates to do the same, as PinEvent doesn't use FutureDMD or the FP backglass (since those tables use PuP and PUPDMD). So they can have a separate PinEvent system that doesn't launch FutureDMD, and also edits the registry to not enable the FP Backglass only for those tables. The regular FP system launches FutureDMD and reenables the FP Backglass in the registry.

 

If using Popper... you can do anything you want with the launch script and the many data fields in Games Manager for "per table setings" using only one FP system.