Turning off "bring to front" feature

[Drybonz]

The recently added "bring to front" feature appears to be also activated for "other systems" as my VP9 tables are being sent to the back, as there is no true fullscreen problem with VP9.  How do I disable this feature?

[Drybonz]

Just wondering how to turn off this feature, either for all tables, or just for the VP9 tables, which don't need it.  Can't find an option to turn this off.  Thanks.

[TerryRed]

Is your "other system" for vp9 set to system type "custom" or "Visual Pinball"? Try setting it to custom.

 

I myself would prefer for all of the "fixes" to have the option to be disabled, as its very frustrating to setup something in PBX, only to find that a workaround for another problem (that you don't need) is causing you issues.

Future Pinball, for me, is the only system that uses built-in support. All others are "other system" and set to "custom". This eliminated a lot of problems I had.

[Drybonz]

Thanks, Terry... it was, in fact, set to "visual pinball" so I just changed it to "custom" and hopefully that will fix it.  Good call.

I also would like to see things like this as options instead of hard coded fixes.

[Draco1962]

7 hours ago, Drybonz said:

Thanks, Terry... it was, in fact, set to "visual pinball" so I just changed it to "custom" and hopefully that will fix it.  Good call.

I also would like to see things like this as options instead of hard coded fixes.

Don't forget we have a Features and Enhancements Request thread just for making this type of request. 

[Tom Speirs]

Hi, the bring to front feature is for VPX only and only if you if have set it to fullscreen exclusivie. PinballX detects if VP 10 is running (via the process description) before doing anything. So this sounds like some other issue?

It is hard coded but in a very smart way.

[Drybonz]

Yeah, I had to change the system type to "custom" for VP9, as Terry suggested, above.

[Tom Speirs]

I still think its an unrelated issue.

[Drybonz]

Correct.

[Carny_Priest]

I can't say that I'm loving this feature either. I wound up having to move Visual Pinball to a custom system slot. Probably because I am having PinballX run a custom launcher that itself launches a bunch of helper apps. I recall there was mention of some dB2S backglasses not getting displayed in PinballX although everything runs fine outside of PinballX. In updating my launcher to run VPX in True Full Screen, I was running into the same issue. Weird bit, I mentioned in this post:

Weird thing - If a dB2S is really large and/or takes a long time to load, such as the one released with Fire! or the big fantasy one for Monster Bash, there winds up being some sort of a conflict with PinballX where B2SBackglassServerEXE.exe is shutdown or crashes. I don't know if it is a timing issue or resource conflict. But if Task Manager is running at the same time, then dB2S backglasses always load successfully. It's hacky, but without knowing what else to do at this point, I programmatically start Task Manager before launching Visual Pinball and then close it down when quitting the table.

This helped me with start up reliability not only with VPX but with VP9 tables that take a relatively long time to load such as Stern AC/DC PhysMod5.

 

[Tom Speirs]

Hey Carny, did you see what I said in that the feature does not affect vp9 and only kicks in under very specific circumstances? At least it is supposed to. I will check.

 

[Tom Speirs]

I had a look and yeah it should only affect VP 10 and when specificlally you have set it to full screen exclusive. So not sure how I can help right now unless you provide some better detail on the issue. Maybe I messed up something else, I dunno!

[Carny_Priest]

I would not say that there is anything that you can do for me. I'm satisfied with what I have at this point. After all, this version of VPX is still in beta. Who knows what else will change? I've made it work for me by moving over to a custom system.

I feel like the dB2S server crashing or not loading for very large files is a different issue, related to timing or order of focus. It's just weird to me that I can solve it by running in parallel with Task Manager. Again, this may be because I'm running a script instead of VP directly. I've linked to it if you want to look, and I mention it because I recall that someone else was having a similar issue at some point. Maybe it was TerryRed.