OK I'll get tom and jerry. BTW, I was trying this in Visual Pinball 5 I think. Not Visual Pinball X
What version of Visual Pinball are you running exactly?
Edited by Tesla, 21 November 2023 - 10:21 PM.
Posted 21 November 2023 - 11:41 PM
I've got Visual PinballX, Visual Pinball 10, And the Physmod one as well as FuturePin I think.
Good. You previously posted something about Visual Pinball 5 ? I do not know anything useful about vp5-vp9.
As long as it's a VPX-Table running under Visual Pinball X v7.2 (or higher) I can continue to try helping you.
Edited by Tesla, 21 November 2023 - 11:51 PM.
Posted 22 November 2023 - 12:47 AM
I told you I would try once more, so here you go. This one fits the format of your original 12-number one (but with what I think to be the proper numbers plugged in). If you take a look, you can see it is actually pretty simple and easy to decipher.
Edited by Tesla, 22 November 2023 - 05:39 AM.
Posted 22 November 2023 - 05:02 AM
OK I think I found one big facet of the problem. I have B2S 1.0 not the later. I need to obviously update or get this working with the v1 config
Tom and Jerry works for me with B2S-Server v1.4 and VPX v7.2
That final ScreenRes.txt file will work with that version (or newer) also.
Just change to:
# Y-flip, flips the LED display upside down. Use 0 or 1.
Edited by Tesla, 22 November 2023 - 05:36 AM.
Posted 22 November 2023 - 05:31 AM
I'm going to try T&J. I ran another one and it is working but the backglass and DMD are offset and the wrong size:
This is the config that the generator created:
# V2.0.3-a1b7e6d # This is a ScreenRes file for the B2SBackglassServer. # From release 1.3.1.1 comment lines like this starting with a '#' are supported. # Playfield Screen resolution width/height 1920 1080 # Backglass width/height 476 356 # Define Backglass screen using Display Devicename screen number (\\.\DISPLAY)x or screen coordinates (@x) or screen index (=x) 2 # Backglass x/y position relative to the upper left corner of the screen selected 792 420 # width/height of the B2S (or Full) DMD area 1357 504 # x/y position of the B2S (or Full) DMD area - relative to the upper left corner of the backglass window 2800 -200 # Y-flip, flips the LED display upside down 0 # Background x/y position - relative to the backglass screen - has to be activated in the settings 1920 0 # Background width/height 1366 768 # path to the background image (C:\path\Frame) or black if none selected # This line would turn off B2SWindowPunch if activated #B2SWindowPunch=off
Posted 22 November 2023 - 05:48 AM
OK, went back and realized it was using the screenres in the tables directory, and replaced it with this:
# V2.0.3-a1b7e6d # This is a ScreenRes file for the B2SBackglassServer. # From release 1.3.1.1 comment lines like this starting with a '#' are supported. # Playfield Screen resolution width/height 1920 1080 # Backglass width/height 1366 761 # Define Backglass screen using Display Devicename screen number (\\.\DISPLAY)x or screen coordinates (@x) or screen index (=x) 1 # Backglass x/y position relative to the upper left corner of the screen selected 2 7 # width/height of the B2S (or Full) DMD area 1357 510 # x/y position of the B2S (or Full) DMD area - relative to the upper left corner of the backglass window 1372 208 # Y-flip, flips the LED display upside down 0 # Background x/y position - relative to the backglass screen - has to be activated in the settings 1920 0 # Background width/height 1366 768 # path to the background image (C:\path\Frame) or black if none selected # This line would turn off B2SWindowPunch if activated #B2SWindowPunch=off
When I do that, the backglass is in the right position but the DMD is nowhere to be seen.
Posted 22 November 2023 - 06:25 AM
So far messing with the numbers really doesn't move the DMD, no matter what I do. If I set the backglass position to 100,100 then I can start to see the DMD in the 3rd screen but it's off to the left and no matter what numbers I put in the the x/y pos of the DMD area it doesn't seem to change
Posted 27 May 2024 - 07:36 PM
Ok, finally bit the bullet and started messing with this. Solution? Kill the configs inside of regedit, and then manually "fix" the default resolution settings to match the correct size/position then once each one starts up then it starts working correctly again and make the changes to the needed tables stored in the registry.