192 replies to this topic

[wiesshund]

Not all directb2s's have a DMD

 

Try this one

 

https://drive.google...?usp=drive_link

 

rename it to match the table of course

it's for bugs bunny, but you can rename it to whatever to test i guess

 

Purposely have everything all apart to show the backglass and b2s server work

dont know what b2s server version you have presently

 

[Tesla]

1. Not all directb2s's have a DMD

 

2. Try this one

 

https://drive.google...?usp=drive_link

 

3. Purposely have everything all apart to show the backglass and b2s server work

 

4. dont know what b2s server version you have presently

 

 

 

1. Correct. I'm only running one of my 39 VPX tables (that are all setup and config/working from before). Yes, I have a few without DMDs, but I'm leaving those for later.

 

2. Yes, I have this one. Bugs-Bunny is cool in my book. I also DL-ed yours in case a file from your file-set archive is newer/better than mine.

 

3. Right. You are better at this part than me. I had to step-away for a while but I'm back at it now. 

 

4. It says: B2S Backglass Server - Server v1.4.1 - Backglass file v1.2

 

IIRC, it was a good-stable release, back before 2.x came-out. Worked fine with my ALP in it's old hardware config.

Edited by Tesla, 06 November 2023 - 06:54 PM.

[wiesshund]

 

1. Not all directb2s's have a DMD

 

2. Try this one

 

https://drive.google...?usp=drive_link

 

3. Purposely have everything all apart to show the backglass and b2s server work

 

4. dont know what b2s server version you have presently

 

 

 

1. Correct. I'm only running one of my 39 VPX tables (that are all setup and config/working from before). Yes, I have a few without DMDs, but I'm leaving those for later.

 

2. Yes, I have this one. Bugs-Bunny is cool in my book. I also DL-ed yours in case a file from your file-set archive is newer/better than mine.

 

3. Right. You are better at this part than me. I had to step-away for a while but I'm back at it now. 

 

4. It says: B2S Backglass Server - Server v1.4.1 - Backglass file v1.2

 

IIRC, it was a good-stable release, back before 2.x came-out. Worked fine with my ALP in it's old hardware config.

 

Update B2S Server to 2.04 or latest build

If you dont, you are sort of in for a lot of headaches

 

Most recent build
​

 

Which has a new screen res setup tool which is visual

 

​

[Tesla]

 

1. Update B2S Server to 2.04 or latest build

If you don't, you are sort of in for a lot of headaches

 

 

2. Which has a new screen res setup tool which is visual

 

 

 

1. I'll work on it.

 

2. This used to be so easy. If they designed a whole new tool ... sounds like I'm not the only one having trouble targeting VPX display windows.

 

So what I noticed is that Tom & Jerry (the only 100% working one with all 3 screens) ... in the Alt-Tab list the 3rd screen content is called "B2S DMD". 

 

On the other tables I tried (like Beavis-Butthead and StarTrek-TNG ) ... they seem to be called "Virtual DMD". 

[wiesshund]

 

 

1. Update B2S Server to 2.04 or latest build

If you don't, you are sort of in for a lot of headaches

 

 

2. Which has a new screen res setup tool which is visual

 

 

 

1. I'll work on it.

 

2. This used to be so easy. If they designed a whole new tool ... sounds like I'm not the only one having trouble targeting VPX display windows.

 

So what I noticed is that Tom & Jerry (the only 100% working one with all 3 screens) ... in the Alt-Tab list the 3rd screen content is called "B2S DMD". 

 

On the other tables I tried (like Beavis-Butthead and StarTrek-TNG ) ... they seem to be called "Virtual DMD". 

 

 

Virtual DMD is not B2S, that is Freezys

and that does not care what screenres.txt is since it isnt part of B2S

 

It is most likely behind the playfield

 

1) edit dmddevice.ini in vpinmame folder

set virtual stay on top to true

 

2) turn off exclusive fullscreen in vpx video prefs temporarily

launch beavis table

 

3) grab the now visable DMD and drag it off to screen 3

size as needed
right click, pick save position GLOBALLY

 

4) Profit

[Tesla]

0a. Virtual DMD is not B2S, that is Freezys

 

0b. and that does not care what screenres.txt is since it isn't part of B2S

 

0c. It is most likely behind the playfield

 

1) edit dmddevice.ini in vpinmame folder

set virtual stay on top to true

 

2) turn off exclusive fullscreen in vpx video prefs temporarily

launch beavis table

 

3) grab the now visable DMD and drag it off to screen 3

size as needed
right click, pick save position GLOBALLY

 

4) Profit

 

 

0a. Yes, I was hoping I could mention that and then you say something helpful. 

 

0b. Now THAT ... I understand.

 

0c. Not sure. But I feel we are close to a solution.

 

1. OK, I did this.

 

2. Yes, that stays off for me during any table setup like this.

 

3. Still don't see DMD on any screen. Also (strangely) the whole playfield screen is moved to Display #3. Only Windows desktop on Screen #1. If I go into VPX/Prefs/Video I find my screen resolutions have been shifted around.

 

If I force them right, all the VPX screens disappear (but I can still hear the Table in Attract-Mode).

 

Let me try more tables.

[wiesshund]

 

3. Still don't see DMD on any screen. Also (strangely) the whole playfield screen is moved to Display #3. Only Windows desktop on Screen #1. If I go into VPX/Prefs/Video I find my screen resolutions have been shifted around.

 

 

DOnt try more tables, go back and undo what ever you did, vpx does not just make that change because it feels like it

 

Once you get that rectified, with nothing else running, go in the vpinmame folder

run flexdmdui.exe

 

click on either ultraDMD or flexDMD test tabs

 

See where the dmd appears

drag it to where it belongs, right click, save global

[Tesla]

1. Don't try more tables, go back and undo what ever you did, vpx does not just make that change because it feels like it

 

2. Once you get that rectified, with nothing else running, go in the vpinmame folder

run flexdmdui.exe

 

click on either ultraDMD or flexDMD test tabs

 

See where the dmd appears

drag it to where it belongs, right click, save global

 

 

1. I had to set virtual stay on top back to false to keep that from happening. 

 

2. I did this and it seemed to work. I had high-hopes, but it did NOT help my problem.

 

I even noticed that when I exit flexdmdui.exe and then run it again, it properly remembers the position of the DMD ... where I previously placed it on Screen #3 (and saved its position globally).

 

Additionally, I noticed it wrote this to DmdDevice.ini :

 

; x-axis of the window position

left = 3513

 

; y-axis of the window position

top = 454

 

; width of the dmd in monitor pixels

width = 1024

 

; height of the dmd in monitor pixels

height = 256

 

The 1024x256 size is fine if it would just appear, but notice the x/y coordinates.

But we already know the coordinates of that window because my screenres.txt works with Tom & Jerry. It's almost as if different parts of the VPX Ecosystem use different coordinate systems (like, now where exactly is 0,0 for THIS part of the setup).  

Edited by Tesla, 07 November 2023 - 04:55 AM.

[Tesla]

Can we please try to get Terminator-2 (Williams 1992) working?

 

It used to work on 3 screens, but now only displays on two of them (no DMD displays like the others).

 

I see NO Virtual-DMD for this table in the Alt-Tab list. Somehow, it had the normal (monochrome) PinMame-DMD running before and it worked fine.

[wiesshund]

so check dll and uncheck vpn in ROM settings?

something wrong if virtual stay on top messes up screens

 

make sure you have no scaling on any monitor

all must be 100%

start at your basics, doesnt help skipping around tables

[Tesla]

 

start at your basics, doesn't help skipping around tables

 

Since Tom & Jerry works, I thought I should try another kind of basic table. Not many, just ONE more.

 

Terminator-2 worked on 3 screens before. Somehow, it had the normal (monochrome) PinMame-DMD running before and it worked fine. AFAIK, it's DMD was simply generated by PinMame.

 

Since I see NO Virtual-DMD for this table in the Alt-Tab list, can I assume the FlexDMD is NOT used on this table ? (ie, can't be interfering with of the rendering or window-targeting of the desired DMD image).

[Tesla]

Wiesshund,

 

Thanks again for all your help. 

 

Seems like this “Feasibility Study” is not going so good. I’m starting to think I should have just left the ALP in it’s original (kludgy) hardware-config ... at least I could play it. Too bad, because this new LG-32 looks so-sweet laying down in there as the new Playfield (the DPI/PPI is high). But I really-need my Screen-3_DMD working or this project kinda-stops. 

 

I’m not sure why I’m stuck on this initial step (with screens and target-windows) but I’m thinking this might be what happens (on some systems) when you swap Windows hardware (especially monitors and controllers) out from underneath a working VPX-install. Seems that adjusting the settings (scattered around in various places) is challenging. 

Edited by Tesla, 07 November 2023 - 08:16 PM.

[Tesla]

 

something wrong if virtual stay on top messes up screens

 

 

 

Oh really?

 

OK then. I will temporarily turn it back on again and try to get the system to be happy with it ... long enough for me to do what I need to do (hopefully, I think ... find a drag-able DMD screen). 

[wiesshund]

 

Wiesshund,

 

Thanks again for all your help. 

 

Seems like this “Feasibility Study” is not going so good. I’m starting to think I should have just left the ALP in it’s original (kludgy) hardware-config ... at least I could play it. Too bad, because this new LG-32 looks so-sweet laying down in there as the new Playfield (the DPI/PPI is high). But I really-need my Screen-3_DMD working or this project kinda-stops. 

 

I’m not sure why I’m stuck on this initial step (with screens and target-windows) but I’m thinking this might be what happens (on some systems) when you swap Windows hardware (especially monitors and controllers) out from underneath a working VPX-install. Seems that adjusting the settings (scattered around in various places) is challenging. 

 

 

If you are swapping montors about
just run the monitor purge bat i gave you, reboot and then resituate the screens

and make sure windows does not auto apply scaling to any of them, cause by default it usually does on 1080p or higher

[Tesla]

1. If you are swapping monitors about

just run the monitor purge bat i gave you, reboot and then resituate the screens

 

2. and make sure windows does not auto apply scaling to any of them, cause by default it usually does on 1080p or higher

 

 

1. No, nothing like that. Just swapped out the Playfield screen, and moved it to the Nvidia's main DisplayPort like you said to.

 

Remember, Tom & Jerry works fine. Seems like all 3 monitors are setup properly in Windows if it can do that.

 

2. Yes, I always do.

 

I was able to set virtual stay on top to True. Retrying stuff now with that engaged. Sorry, this works fine now. My error for thinking it could not be switched-on temporarily for troubleshooting. 

Edited by Tesla, 20 November 2023 - 06:52 PM.

[wiesshund]

Mind you the stay on top = true wont have much meaning, once you get the DMD onto the correct screen and save position globally.

because there won't be anything for it to go underneath of, but one needs it to atl least find the DMD if it has gone under a table or backglass

 

Mind you you can do this with no table running

As i mentioned, you can run flexdmdui.exe and use one of the test tabs to get a dmd display to drag around

 

Or one could also boot up a DMD ROM in vpinmame's setup exe, with use external DLL enabled for that ROM

and drag it around, and then save position globally

 

If one has values in dmddevice.ini pertaining to location, that are off screen, one could simply edit the defaults back to this

; x-axis of the window position

left = 0

 

; y-axis of the window position

top = 0

 

; width of the dmd in monitor pixels

width = 1024

 

; height of the dmd in monitor pixels

height = 256

[Tesla]

 

1. Mind you the stay on top = true wont have much meaning, once you get the DMD onto the correct screen and save position globally.

because there won't be anything for it to go underneath of, but one needs it to atl least find the DMD if it has gone under a table or backglass

 

2. Mind you you can do this with no table running

As i mentioned, you can run flexdmdui.exe and use one of the test tabs to get a dmd display to drag around

 

Or one could also boot up a DMD ROM in vpinmame's setup exe, with use external DLL enabled for that ROM

and drag it around, and then save position globally

 

3. If one has values in dmddevice.ini pertaining to location, that are off screen, one could simply edit the defaults back to this

; x-axis of the window position

left = 0

 

; y-axis of the window position

top = 0

 

; width of the dmd in monitor pixels

width = 1024

 

; height of the dmd in monitor pixels

height = 256

 

 

1. Understood.

 

2. I tried. It seemed to work but not really.

 

3. Hmm. OK, I'll try.

[Tesla]

Well, good news ... I found another 100% working as 3-screens.

 

F14-Tomcat 

 

It's another B2S-DMD one, but pretty sure this table is also PinMame-rom based ... so good to see that tested and apparently working. 

[wiesshund]

you already know b2s works

 

go open vpinmame's setup.exe

find a DMD equipped ROM that you have.

 

ACDC? Apollo 13? Pirates of the Carribean? 

Something with a DMD

 

Click the button to set the options for that game

check use external DLL, uncheck use vpm display

 

start ROM

Look for the DMD to go someplace

[Tesla]

you already know b2s works

 

go open vpinmame's setup.exe

find a DMD equipped ROM that you have.

 

ACDC? Apollo 13? Pirates of the Carribean? 

Something with a DMD

 

Click the button to set the options for that game

check use external DLL, uncheck use vpm display

 

start ROM

Look for the DMD to go someplace

 

OK, now another table is working on 3-screens:

 

Batman (Data-East 1991)

 

I did the above on it. The position of the DMD window came up where I told it in FlexDMDui . I saved it's position for table AND ALSO GLOBAL. 

I did notice that the window is named Virtual-DMD (in Alt-Tab listing), so IIRC ... that is the first one of those to get working.

However, it didn't seem to help the problem tables.

 

It seems that FlexDMD has commandeered control of the DMD on many of my favorite tables.  Maybe I should just remove it and go back to vanilla-DMD? At least I'll be able to play Star Trek - TNG again (and be able to see the scoring).

Edited by Tesla, 08 November 2023 - 02:34 AM.