18 replies to this topic

[bpjacobsen]

been a while since I set my 3 screen cab up but I just hooked everything back up and of course my displays are screwed up. right now playfield is on the  BG monitor. BG is on dmd and dmd is on nothing at this point. Can someone please remind me what file needs to be edited to fix this and where? TIA

[Outhere]

been a while since I set my 3 screen cab up but I just hooked everything back up and of course my displays are screwed up. right now playfield is on the  BG monitor. BG is on dmd and dmd is on nothing at this point. Can someone please remind me what file needs to be edited to fix this and where? TIA

3 Screen set-up and more  --  https://www.vpforums...e=7#entry346276

[wiesshund]

Did you take the cab all apart or something?

 

1st thing i would do is delete the monitors from the registry, then reboot PC
Delete all 3 of these registry jey

• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Connectivity
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\ScaleFactors

 

After the reboot, you will only have 1 set of monitor entries in the registry

 

Then right click the desktop, click identify and see what monitor is what, then drag them in the following order left to right
with all tops exactly aligned
Playfield, Backglass, DMD (i am assuming LCD DMD?)

 

Once that is done
Open VPX, do not open any tables yet.
click on preferences and go to video

Pick the correct screen and resolution.
And uncheck exclusive full screen mode, until everything else is fixed.
now launch a table, does not matter which table, and does not matter is desktop or cab mode at the moment
all that matters is it comes up on the correct screen.

Make note of what screen number that is, in case it is something other than what windows calls it.

 

Ok, once that is happening on the correct screen, exit out of VPX

open the tables folder and run b2s setup

put in the correct resolution for both playfield and backglass monitors
To prevent monitor musical chairs etc, you may find it easier to do this.
Set backglass monitor number in the dropdown to be the same monitor as VPX says the playfield is on.

Then in the box marked backglass X pos, type in a number that is 1 pixel wider than your playfield resolution.

Like if it is 1920 x 1080, then type in 1921 for backglass X pos
dont put anything in Y position

 

The DMD part is for B2S DMD's but in case you have some of those
put in the width and height for your visible DMD LCD
The X Offset will be playfield width + Backglass width + at least 1 pixel if i remember right.

And that has no effect on anything except a B2S backglass with a separate DMD component, does not affect a VPM DMD or ultraDMD or flexDMD

For those, once you have the table and backglass where they belong, you should be able to alt tab to the DMD and then drag it to the right place.

 

If your VPM DMD's appear to be at a screen co-ordinate that no longer exists or something
you can hand edit a valid one in the registry, or remove the rom entries from the registry and they will land back on the playfield screen at default size again

[bpjacobsen]

still struggling with this. the BG is on the correct monitor but is too small so I need to edit the b2s setup I guess but the playfield is still on the dmd screen. how do I get that on the correct monitor? ugh!

Edited by bpjacobsen, 22 November 2020 - 09:45 PM.

[wiesshund]

still struggling with this. the BG is on the correct monitor but is too small so I need to edit the b2s setup I guess but the playfield is still on the dmd screen. how do I get that on the correct monitor? ugh!

well now that backglass is on correct seen, just make sure the resolution for that screen is correct in b2s setup

 

as far as the playfield
easy
Just open vpx, go to prefs, and video
pick a monitor, launch any old table
wrong one?

exit table pick another monitor

You only have 3 choices and you are already using one of the choices
so will only take 2 tries max LOL

[bpjacobsen]

OMG I'm such an idiot. I didn't realize that dropdown in vpx was just for selecting the monitor for playfield. duh! OK PF fixed! now, no dmd is coming up at all, and the bg is still not filling the screen. I matched up the nvidia resolution with b2s setup but it's not changing the size. I also confirmed the dmd (tried internal and the freezy option but it's completely missing. No idea why. and I confirmed it's not opening at all by hitting alt tab so it's not even running in the background. WTH?

Attached Files

•  nvidia.png   63.86KB   13 downloads
•  b2s setup.png   24.9KB   12 downloads

Edited by bpjacobsen, 22 November 2020 - 10:00 PM.

[wiesshund]

May i ask, what is with the odd resolution settings?

should be like
1366x768, 1440x900,1600x900, 1920x1080, 3840x2160, those are standard native resolutions

 

Your EM32TS tv does a resolution of
1366 x 768, it is a 720p LCD

 

Your DeLL 1503FP runs at
1024 x 768

 

And your Insignia NS-40D510NA15 LED HDTV runs
1920x1080

I do not think you should have those funky resolutions in place or your video drivers are going to start virtually scaling things

because you can not put 1842 pixels wide and 1048 pixels tall on a screen that has only 1366 pixels across and 768 pixels down

 

Do you know why you have such strange values set?

 

PS:
Worry about the DMD after correcting the screens entirely
but if you can not alt tab to the DMD then the DMD is not running, at least visually.

You sure that DMD is not set hidden in the table script?
 

Edited by wiesshund, 22 November 2020 - 10:26 PM.

[bpjacobsen]

May i ask, what is with the odd resolution settings?

should be like
1366x768, 1440x900,1600x900, 1920x1080, 3840x2160, those are standard native resolutions

 

Your EM32TS tv does a resolution of
1366 x 768, it is a 720p LCD

 

Your DeLL 1503FP runs at
1024 x 768

 

And your Insignia NS-40D510NA15 LED HDTV runs
1920x1080

I do not think you should have those funky resolutions in place or your video drivers are going to start virtually scaling things

because you can not put 1842 pixels wide and 1048 pixels tall on a screen that has only 1366 pixels across and 768 pixels down

 

Do you know why you have such strange values set?

 

PS:
Worry about the DMD after correcting the screens entirely
but if you can not alt tab to the DMD then the DMD is not running, at least visually.

You sure that DMD is not set hidden in the table script?
 

it was b/c I had to adjust screensize due to overscan but I reset to 1366x768 in both b2s and nvidia (no more overscan somehow) but the BG is still not filling the screen. I"m at a loss. it still sits upper left in my bg display and is not close to filling the screen. ?????????? I also tried no scaling, full screen, and aspect, but none of those make any difference. GRrrrr!

Attached Files

•  b2s setup.png   10.55KB   4 downloads
•  nvidia.png   29.58KB   4 downloads
•  nvidia2.png   22.48KB   4 downloads

Edited by bpjacobsen, 23 November 2020 - 01:41 AM.

[wiesshund]

Well, your issue does not appear to be B2S in this case, though you are still showing some funky resolution for your playfield

It looks like either the nvidia drivers, or the TV itself is monkeying with things

B2S will put out what ever you tell it, even if you lie to it.
If i tell it to do a 4k resolution on a 900p screen
it will do just that, and i will see the top left corner of the backglass, and the rest will go off the screen into no-man's land

And if i tell it that it is 800X600 then i will get a small backglass in the top left corner surrounded by a bunch of empty screen.

 

I dont know that it is going to help the backglass, but i would get your playfield out of that non existent resolution as well
 

What does windows itself look like on the backglass screen when nothing is running?
does it at least sit on the screen in the proper resolution and size?

 

Also, i think you would want to preform scaling on GPU as opposed to screen

Edited by wiesshund, 23 November 2020 - 02:40 AM.

[bpjacobsen]

Ugh, no idea why, but the only way I could get the BG to display properly was to trial and error the size and position in b2s setup per attached. I remember this from last time. For some stupid reason simply setting the resolution to the native does not allow the b2s to display correctly without having screwy settings in the b2s setup. If anyone else has any idea why this is the case, please chime in. I know the resolution should be the same as windows my system is possessed.

Attached Files

•  b2s setup.png   12.58KB   5 downloads

[wiesshund]

I dunno, you got very strange sizes there
and in windows from your earlier screen shots.

 

All monitors should be set to a real resolution in windows
and b2s should also be set using real resolutions

Playfield should be set as primary desktop
and screens should in in playfield, backglass, dmd order left to right, with all tops aligned
All screens should be set at 100% scale

And nothing in windows, the video drivers, nor the hardware settings on the screens themselves should be set to go about rescaling anything.
And then it should work.
If it does not, the answer is not to bastardize vpx and b2s because nothing ever comes out right going that route and usually at some point gets worse, but to figure out the external cause

 

You may also find it easier to set the backglass on the playfield screen
WITH the real resolution of the BACKGLASS screen 1366x768 and WITH the playfield set at the proper resolution of 1920 x 1080
then set the backglass X pos to 1921

And if that does not put the right things in the right places at the right sizes, you need to correct the thing that is wrong
which wont be B2S or VPX, but someplace between windows, nvidia, and the display panels themselves, which you are kind of already showing here

You got some kind of rescaling or underscan hocus pocus going on
 

[bpjacobsen]

lol, that about sums it up. so I should have nvidia set to 'no scaling"

[bpjacobsen]

OMG WTH? so I just set the proper resolutions as suggested again and now it's perfect, no overscan, no whacky numbers. so how's that for hokus pokus? lol. No clue why it decided to cooperate but I'll take it! Thanks for all your help. sheesh!!

 

OK, now to fix my dmd issue. I loaded a table that I know uses freezy dmd. (batman Dark Knight) and it shows virtual dmd is running but it does not show the actual dmd. even if I hit alt tab.

 

I tried both the internal dmd and virtual dmd (ext) and same issue with both. Ugh!

Edited by bpjacobsen, 23 November 2020 - 03:45 PM.

[wiesshund]

OMG WTH? so I just set the proper resolutions as suggested again and now it's perfect, no overscan, no whacky numbers. so how's that for hokus pokus? lol. No clue why it decided to cooperate but I'll take it! Thanks for all your help. sheesh!!

 

OK, now to fix my dmd issue. I loaded a table that I know uses freezy dmd. (batman Dark Knight) and it shows virtual dmd is running but it does not show the actual dmd. even if I hit alt tab.

 

I tried both the internal dmd and virtual dmd (ext) and same issue with both. Ugh!

Hmm ok that is odd
open pinmame32 and launch the batman ROM
can you see any part of it show on screen?

 

[wiesshund]

So i tested batman dark knight
which uses bkd_294.zip for the ROM

 

it does not use freezys anything
I mean you could choose to do so, but the table script itself does not force anything
It loads a straight VPM DMD

 

so i would launch the table, and hit F1 and make sure that show DMD is checked
and if it is and you still can not see it, then i would open regedit
and delete the reg key for bdk_294, as it may be at some screen coordinates that dont exist hence you cant see it

 

Computer\HKEY_CURRENT_USER\SOFTWARE\Freeware\Visual PinMame\bdk_294

Which should get you your VPM DMD back, sitting on top of your table
(or under if you enable exclusive full screen mode, which i would not do until you are done adjusting things)

 

If you want it to use freezy's that is fine, but if that goes off screen, you have to fix that in the dmddevice.ini

[bpjacobsen]

Well, I had spent a lot of time setting up my freezy dmds and colorizing them. but whether I enable external or vpm dmd, the same issue prevails. It's like the virtual dmd app window shows in alt tab but no dmd display. I did run batman via pinmame32 and it does display but is it supposed to display in the BG monitor or should it show in the correct monitor when run from pinmame? perhaps it is hiding behind my BG? But normally I can see it in alt tab and get it to come forward then move it but it's not even showing at all. I really hope this is not some screwed up Windows 10 thing b/c this was working perfectly on windows 7. I just updated to windows 10 b/c it was giving me some problems. By the way this is all tables, not just Batman. there is clearly an issue with vpinmame or dmd. I tried zeroing out the positions in b2s.setup and setting to internal dmd but no dice. nothing is allowing any dmd to display at all. I really am at a loss and don't get it. It's insane and driving me nucking futs.

[wiesshund]

If you see it in alt tab but not on any screen, it most likely means it IS on screen
but at a screen co-ordinate that does not exist in your screen space

So what you do is

 

VPM DMD
go into the registry, and either delete the key for that ROM

or edit the horizontal and vertical positions to 0 both
and then it will appear at the top left of the playfield so you can then grab it, drag it off resize it etc

 

Software DMD

Open the DmdDevice.ini file in notepad
Which should be in the VpinMAME folder (which is also where freezy's stuff should have went)

Search it for the ROM name
 

It should look kinda like this for example

[apollo13]

virtualdmd left = 4279

virtualdmd top = 2795

virtualdmd width = 379

virtualdmd height = 110

 

Now edit that so it looks like this

[apollo13]

virtualdmd left = 0

virtualdmd top = 0

virtualdmd width = 379

virtualdmd height = 110

 

Or you can remove the entry all together
either should put it into viewable space so you can then move and resize it

 

And no, Pinmame32 will just display the rom running on your primary screen, and possibly sideways as well
but it proves that the ROM does work and is visible

 

Edited by wiesshund, 24 November 2020 - 03:48 AM.

[bpjacobsen]

Something else is jacked up here. I can't see the dmd display at all even in alt tab. All I see is a virtual DMD window. See attached screenshot. (had to take a photo with phone then screenshot a portion to keep size down) I went in and set the coordinates to zero in the main section of the dmdext.ini file since Fire! is set to use the universal setting and not it's own settings. It dn matter what I do with the position or size. The dmd simply will not display at all. I have never in several years of doing this seen this issue before. I'm totally at a loss. And the same thing happens if I run the vpinmame dmd where it will just show the pinmame window but no display. Usually I can at least see the dmd in alt tab but I"m not even getting that far. I thought about re-loading the latest pinmame but why would this be happening with both freezy and pinmame dmd? 

Attached Files

•  dmd.png   165.02KB   3 downloads

Edited by bpjacobsen, 24 November 2020 - 12:23 PM.

[bpjacobsen]

Finally solved my dmd nightmare! Whew!!! So I installed the latest beta 3.3 vpinmame and just replaced the dmdext.ini with mine that had the saved settings, then whamo! the dmd is magically working. Must have been on an older version of vpinmame or it was jacked up somehow.  but I"m back in business! Thanks for the help. Always much appreciated. Now I can sleep again. lol

Edited by bpjacobsen, 24 November 2020 - 03:58 PM.