373 replies to this topic

[Drybonz]

Oh, no idea... can't help you there.  I don't use Hyperpin.

[TNT2]

I have one more thing to offer on this.  I now see the issue you guys have with it losing focus inconsistently with different B2S files.   I was completely unable to launch Scared Stiff no matter what I tried.  

 

The current alt-tab hack doesn't work on Windows 8 or above.  They added some restrictions unless the binary is signed and set to be an accessibility app.    So I looked for other alternatives.     I found a MUCH simpler, better fix is to prevent B2S / VPM from stealing focus in the first place:

 

In Player::InitWindow add:

 

if (m_fFullScreen)

  ::LockSetForegroundWindow(LSFW_LOCK);

 

Right after the CreateWindow.    This function blocks processes from taking focus away from our exclusive fullscreen app.   Seems to work great. 

 

Could you explain this a bit more? I am running Windows 8.1 and 10.3 VPX.

 

So after reading this thread I have been able to get force exclusive fullscreen working. There is definitely an improvement to table visuals and I can enable brute force without lag. However DMDs are always disappearing when the table runs. The Alt+ tab workaround doesn't seem to work for me like it did whenever I had this issue playing in windowed mode. I am playing in desktop mode not in a cabinet. Some tables where the DMD screen has been enlarged by the table author still display just fine. It's where the DMD is in a much smaller window at the far upper left of the screen that it disappears. An example would be Sliderpoint's The Addams Family table.

 

Hopefully that makes sense. Any suggestions? 

Edited by TNT2, 17 July 2017 - 02:42 AM.

[DJRobX]

That post you quoted is quite old, the code change I mentioned has been integrated into the main VP release for some time now.

 

If you are using Desktop you *MUST* play a table with a built-in DMD to use exclusive fullscreen mode.    This is because VPM is unable to bring up a window (since VP has the screen exclusively locked to it).

 

The good news is that it's fairly easy to add the built-in DMD to VP tables.    For example the WCS one that was released this week just needed this at the top of the script:

 

Dim DesktopMode: DesktopMode = tablewpc94.ShowDT

Scoretext.visible = DesktopMode

 

dim UseVPMDMD:UseVPMDMD = DesktopMode

 

The black bolded part changes from table to table.  You may also need to copy the "Scoretext" table object into the table (on the backdrop) from another working table.   This object was already there in WCS.

Edited by DJRobX, 17 July 2017 - 02:42 AM.

[TNT2]

Thanks DJRob. That must be why some of the tables are working correctly. Built-in DMD on some tables. 

 

Dang. Wondering if this is worth all of the effort. 

[TNT2]

Ok ok. It's probably worth the effort. 

[DJRobX]

Yeah when I play on my laptop the difference is staggering.   It only takes a couple minutes to get the DMD working once you know how to do it.  

[TNT2]

Cool. Thanks again for the info.

[TNT2]

I guess this is the part that confuses me:  You may also need to copy the "Scoretext" table object into the table (on the backdrop) from another working table.

 

Not sure how you do that. Also some tables don't appear to have a scoretext box like UncleWilly's Bad Cats table.

Edited by TNT2, 18 July 2017 - 02:10 AM.

[TNT2]

I have been pretty amazed at how much of an effect this has on tables. For those of us who have been using directdraw = 1 by default, after converting tables it's almost like what VP11 could look like with the changes.

 

So once you have changed the registry entries it's a permanent change even if you upgrade to a newer VP10 (such as 10.3 or 10.4) version? I am assuming the only time you would need to go back in and change them again is if you get a new computer as the registry changes aren't saved to Visual Pinball itself?

Edited by TNT2, 19 July 2017 - 06:07 PM.

[hauntfreaks]

I have been pretty amazed at how much of an effect this has on tables. For those of us who have been using directdraw = 1 by default, after converting tables it's almost like what VP11 could look like with the changes.

 

So once you have changed the registry entries it's a permanent change even if you upgrade to a newer VP10 (such as 10.3 or 10.4) version? I am assuming the only time you would need to go back in and change them again is if you get a new computer as the registry changes aren't saved to Visual Pinball itself?

 

exactly.... once and done.... 

[Rajo Joey]

I have been pretty amazed at how much of an effect this has on tables. For those of us who have been using directdraw = 1 by default, after converting tables it's almost like what VP11 could look like with the changes.
 
So once you have changed the registry entries it's a permanent change even if you upgrade to a newer VP10 (such as 10.3 or 10.4) version? I am assuming the only time you would need to go back in and change them again is if you get a new computer as the registry changes aren't saved to Visual Pinball itself?

If you change the PC, you make a backup of the part of the registry and import it in your new one.

Gesendet von meinem SGP511 mit Tapatalk

[lacsusz]

Hello guys,

 

May I ask for your kind help regarding a 'True Full Screen' issue that I just can't solve by myself.

I went through all this forum topic and also looked on other forums (PBX, VPinball, etc) but no luck.

My only guess is that it's hardware-related and/or my config is too old but maybe there's a solution and you guys are my last hope.

 

I use a 3-screens VP cabinet. Here is the issue described through 3 scenarios:

 

1) I leave ddraw at 1 (intentionally, for the sake of explanation) in the rom registry, with "Force exclusive Fullscreen Mode" "ON" in VPX:

 

I get the VBS script error ("Machine (rom) terminated before initialized, check the rom path or rom file!") - that's normal, I know, as ddraw is set to 1...

...HOWEVER, and this is where my heart hurts the most, once I close down VPinMame and switch to the VPX table with ALT+TAB, I can SEE how truly BEAUTIFUL the VPX tables actually are, when the 'focus' is on the playfield (full) screen monitor. Unfortunately, I cannot play with the tables in this scenario.

 

2) Regardless to ddraw setting (0 or 1) in the rom registry, I turn "Force exclusive Fullscreen Mode" "OFF" in VPX:

 

I can play most of the PBX tables with "Post-Processed Anti-Aliasing" set to "Quality SMAA" and "Anti-Aliasing Brute-force 4x SSAA" disabled (if latter is ticked, it slows down the tables considerably, with a huge lag - approx 42 fps). Yes, I can play and have fun, but I am miles away from the seeing the TRUE BEAUTY in the vpx tables.

 

3) I set ddraw to 0 in the rom registry, with "Force exclusive Fullscreen Mode" "ON" in VPX:

 

Here is where things get an unexpected turn: I get a worse "gaming experience" than described in scenario 2) because even though I am SUPPOSED to have "Force exclusive Fullscreen Mode" turned "ON" in VPX, my feeling is that the 'focus' is not on the playfield monitor, i.e. that actually, the "Fullscreen Mode" is not "operating". The tables look just the same as in scenario 2), i.e. miles away from the beauty I can only "see" and not "feel" in scenario 1).

What am I doing wrong? TerryRed's post #355 gave me a little hope as he mentioned there is a chance that the 'focus' "switches" elsewhere...where? To the B2S monitor? How can I check that?

 

I have the latest VPX (10.3), DB2S Server (1.3.0.2.) and VPinMame (2.9) versions.

 

My configuration:

Win 8.1 64bit

4 GB RAM

AMD FX 6300 6-core CPU 3,50 GHz

AMD Radeon R7 200

3 monitors

 

Many thanks for your help.

[rickh]

I solved a similar problem with my setup and after finding all these unsolved threads I figured I had to come up with my own solution for the focus problem.  Allow me to summarize this issue before I go to the solution.  There appears to be a bug in PinMAME that when a DMD overlay is placed over the backscreen, the focus is stolen from the playfield.  This requires a mouse or Ctrl/Tab to place focus on the playfield so that the game is playable.  People with actual DMDs are not affected with this anomaly.  This problem seems to affect VP9.x and VPX. 

 

How to fix it for Pinballx  

 

1- invoke notepad (notepad++) 

2- Place the text in parenthesis ("")  into this file:

"

Option Explicit

 

Dim ObjShell :Set ObjShell = CreateObject("Wscript.Shell")

 

Wscript.Sleep (12000)

 

ObjShell.AppActivate("Visual Pinball Player")

"

3- Save this file as "VP_Focus.vbs" and place it into your pinballx folder

4- in the pinballX setup wizard select the visual pinball tab

5- on the 'Launch Before' section:

•      Enable Launch before option:YES
•      Launch Before working path: C:\PINBALLX
•      Launch Before Executable: VP_focus.vbs
•      Launch Before Parameters: 
•      Launch Before Wait for Exit: NO
•      Launch Before Hide Windows: YES

I suspect this will work with other front ends too.   On slower machines or long loading playfields, the sleep time might need to be increased.

 

Please enjoy and give me some feedback.  I am new to the .NET stuff and this is my first hack outside of LabVIEW. 

 

Regards,

 

Rick 

[knightrdrx]

With a real dmd should I go ahead and use full screen then?