73 replies to this topic

[wiesshund]

 

 

2. Yeah, I saw that the other day, but that is already set to a very dark-shade of black.

Somehow, I think the light-gray is coming from somewhere else.

 

http://vpforums.org/...o13-margins.jpg

 

 

Look, no offense but i gave you an absolute specific answer, and you want to dispute it and argue it.
I gave you the answer, you can accept it and do that, or not and have grey

Edited by wiesshund, 20 February 2023 - 06:40 AM.

[Tesla]

 

 

 

2. Yeah, I saw that the other day, but that is already set to a very dark-shade of black.

Somehow, I think the light-gray is coming from somewhere else.

 

http://vpforums.org/...o13-margins.jpg

 

 

Look, no offense but i gave you an absolute specific answer, and you want to dispute it and argue it.
I gave you the answer, you can accept it and do that, or not and have grey

 

 

No, not really.

 

It's just that it's already set to almost pure Black (unless the color-picker is way-way off). The color Black it shows would be fine.

I didn't want to break/mess-up the table since it appears to be something else.

 

However, it just occurred to me that I can backup/save the table as it is now (99% working fine), and then make the change exactly as you said. If it doesn't work, I can just restore the backup. Sorry, I'm pretty new at this.

[wiesshund]

 

 

 

 

 

It's just that it's already set to almost pure Black 

 

 

There is no such thing as almost.
It is pure black or it is not

[Tesla]

 

1. To turn the grey to black
In editor, click the backglass icon
Set background color to pure black
Hue 160
Sat 0
Lum 0
Red 0
Blue 0
Green 0

 

2. Anything not pure black will look some shade of grey ... or if an actual color, will look like a color.

 

1. I backed-it-up first (I'm afraid of breaking something, since I don't really know what I am doing).

 

Yes, that worked, thanks.

 

2. Why was it even like that, and why did it work? Well, I suppose my answer is in this sentence somehow.

[wiesshund]

Default color is dark grey when you start making a table

[OpinballeyesO]

Are you running Freezy DMDExt?

[Tesla]

Are you running Freezy DMDExt?

 

Hard to say as I'm a total newbie and not sure where Flex-DMD ends and Freezy DMD-Ext starts. Why do you ask?

 

However, as of today, I definitely am as I just fully installed Heavy Metal Rowamet 1983 v1.5.2 VPX. 

[Tesla]

Mr. Wiesshund,

 

So, after I got your Heavy Metal VPX table installed (totally awesome by the way) , I lost the animated 13-MultiBall BLASTOFF letters on Apollo-13 for some reason.  

 

I also (all of a sudden) had a strange looking DMDExt Window appear ... not only on Heavy Metal (as I finally got Flex-DMD working) but also LAH and Apollo-13. I got rid of it on all three VPX tables, but Apollo-13's  BLASTOFF letters never came back.

Edited by Tesla, 22 February 2023 - 05:59 AM.

[wiesshund]

Mr. Wiesshund,

 

So, after I got your Heavy Metal VPX table installed (totally awesome by the way) , I lost the animated 13-MultiBall BLASTOFF letters on Apollo-13 for some reason.  

 

I also (all of a sudden) had a strange looking DMDExt Window appear ... not only on Heavy Metal (as I finally got Flex-DMD working) but also LAH and Apollo-13. I got rid of it on all three VPX tables, but Apollo-13's  BLASTOFF letters never came back.

need way more info on what all you changed, because the heavy metal table does not change anything

[Tesla]

 

need way more info on what all you changed, because the heavy metal table does not change anything

 

 

I installed FlexDMD and Freezy's DMD-Ext as suggested in the Heavy Metal setup notes to enable all of the table's functions. I think you are well-aware of what all that entails.

 

I changed some vPinMame F1 options trying to get stuff to work. I right-clicked on some backglass and DMD-windows to get to their options ( and some of those inevitably end-up being global ). I dragged some DMD-windows around. I deleted some nv files to try to reset my tables.

 

That's about it, AFAIK.

[wiesshund]

FlexDMD and Freezys DMD extensions have no bearing on B2S, nor does VpinMAME's F1 options

 

What B2S stuff did you change?

[Tesla]

1. FlexDMD and Freezys DMD extensions have no bearing on B2S, nor does VpinMAME's F1 options

 

2. What B2S stuff did you change?

 

1. Good to know.

 

2. None that I recall . I have B2S installed in it's own folder (as you suggested a while back). 

[wiesshund]

 

1. FlexDMD and Freezys DMD extensions have no bearing on B2S, nor does VpinMAME's F1 options

 

2. What B2S stuff did you change?

 

 

 

2. None that I recall . I have B2S installed in it's own folder (as you suggested a while back). 

 

 

??
You said above you were right clicking on backglasses changing stuff?

 

try renaming your b2stablesettings.xml to .bak and relaunching vpx

[Tesla]

 

1. You said above you were right clicking on backglasses changing stuff?

 

2. try renaming your b2stablesettings.xml to .bak and relaunching vpx

 

 

2. I did that, but it did not help unfortunately. I found it in my \Tables folder.

 

I noticed:

- The file did have Apollo-13 stuff in it

- It did NOT get re-written after running the table a few times (so whatever it does is apparently non-existent now).

 

1. Right, that's all I know to do. I thought I was in the right area. Is that not allowed? I was trying to fix it myself because my only other option is to post a message here and wait 24 hours for an answer (and that is just when you are checking on me and kind-enough to post).

 

Maybe if I knew what the F1 and B2S options were even suppose to be for this Table. Is it documented somewhere? I asked in the Apollo-13 support thread, but have received no answer as of yet.

[wiesshund]

F1 options pertain to ROMS and nothing else
the ROM has no effect on how B2S displays anything

 

It is a DMD ROM, so youd most likely want show VPN display off and use external DLL on

 

None of that has any bearing on the B2S backglass though

 

This is an Arcade Legends cab?
So you only have 1 LCD screen in the backglass?
The DMD is dotmatrix is it not?

[Tesla]

1. F1 options pertain to ROMS and nothing else
the ROM has no effect on how B2S displays anything

 

2. It is a DMD ROM, so youd most likely want show VPN display off and use external DLL on

 

3. None of that has any bearing on the B2S backglass though

 

4. This is an Arcade Legends cab?
So you only have 1 LCD screen in the backglass?
The DMD is dotmatrix is it not?

 

1. ROMS and vPinMame, right? So, even if you drag the animated ROM-DMD to the backglass, it has nothing to do with B2S, huh. OK, if you say so.

 

2. IIRC, Apollo-13 and LAH both had F1 options set to "Show DMD/Display window". Only table that has "Use external DLL" checked is Heavy-Metal (I thought because it was using Flex-DMD now).

 

3. Hmm. Then what are those BLASTOFF letters? Some kind of specially formatted and defined auxiliary DMD ?

 

4. It's an AtGames Legends Pinball (ALP) cabinet in OTG-Mode. I have added a 3rd small LCD for DMDs, etc.

 

https://www.vpforums...=50679&p=513291

[wiesshund]

Heavy metal doesnt need use DLL or show vpm checked
as the score is both in the backglass and via flexDMD

so you dont want the VPM display nor freezys DLL display

VPM will get you a score box you simply dont want
and enabling external DLL will result in freezys and flexDMD fighting over control of the same display window
which will result it it either flashing back and forth, or might possibly result in 2 windows, one of which you didnt want.

 

The Blastoff letters are a subsection of the B2S Backglass
Some, not all, backglasses have a floating section designated as DMD, which will display on the DMD screen
But ONLY if said DMD screen is LCD, B2S can not render to a real DMD screen, B2S doesnt do dot matrix

 

Some things you can try (they require table restart between changes)

 

Run apollo
right click backglass
change it to send form to back

it may presently be form to front or standard
change to send to back
If DMD is under the backglass, you wont see it

 

Save that change, then restart table
see if it appears anyplace

 

You can also check in those same options that B2S DMD is not set to hidden.

 

If you still cant find it anyplace

Backup your screenres.txt (you should only have one)

then change it to the last lines pertaining to the LCD panel are all 0
that is the last 5 lines

Then relaunch the table and see if the blastoff does not at least re-appear on the backglass itself.

[Tesla]

1. VPM will get you a score box you simply dont want

and enabling external DLL will result in freezys and flexDMD fighting over control of the same display window
which will result it it either flashing back and forth, or might possibly result in 2 windows, one of which you didnt want.

 

2. Heavy metal doesnt need use DLL or show vpm checked

as the score is both in the backglass and via flexDMD

 

so you dont want the VPM display nor freezys DLL display

 

 

 

1. Correct. I saw how that worked the other day. It's all documented in the Table-Script. No problems there.

 

2. So, I brought-up Heavy-Metal to check those F1 options. They were incorrect, but it is working. I turn them both off and restart table. I now notice a small red-mark below my DMD/video box. It's a squished DMD ... I think it said "Virtual DMD" . I right-click to Properties and it's DMDExt. I end the Table, VPX Editor and everything. It's still running and there is no exit.

 

When running VPX in Windowed-Mode (so I can drag stuff around or right-click) this Virtual-DMD has top focus over any other program or Window. This is what was running the other night on top of all my tables (all of a sudden). I thought it was the tables and started to try to fix them. It was just this all along. Now, I just don't know why it sometimes starts itself (usually when running Heavy Metal). Notice, no table is even loaded. When you right-click-to-Properties, that is what it shows.

 

http://vpforums.org/...xt-takeover.jpg

Edited by Tesla, 23 February 2023 - 04:19 AM.

[wiesshund]

 

1. VPM will get you a score box you simply dont want

and enabling external DLL will result in freezys and flexDMD fighting over control of the same display window
which will result it it either flashing back and forth, or might possibly result in 2 windows, one of which you didnt want.

 

2. Heavy metal doesnt need use DLL or show vpm checked

as the score is both in the backglass and via flexDMD

 

so you dont want the VPM display nor freezys DLL display

 

 

 

1. Correct. I saw how that worked the other day. It's all documented in the Table-Script. No problems there.

 

2. So, I brought-up Heavy-Metal to check those F1 options. They were incorrect, but it is working. I turn them both off and restart table. I now notice a small red-mark below my DMD/video box. It's a squished DMD ... I think it said "Virtual DMD" . I right-click to Properties and it's DMDExt. I end the Table, VPX Editor and everything. It's still running and there is no exit.

 

When running VPX in Windowed-Mode (so I can drag stuff around or right-click) this Virtual-DMD has top focus over any other program or Window. This is what was running the other night on top of all my tables (all of a sudden). I thought it was the tables and started to try to fix them. It was just this all along. Now, I just don't know why it sometimes starts itself (usually when running Heavy Metal). Notice, no table is even loaded. When you right-click-to-Properties, that is what it shows.

 

http://vpforums.org/...xt-takeover.jpg

 

 

That is freezys display with heavymetal ROM translated to it
This happens if use external DLL is enabled, which you dont need since the table has a flexDMD

 

If for some reason you cant seem to turn it off
in regedit go to
Computer\HKEY_CURRENT_USER\Software\Freeware

 

look for any entries for heavymetal or heavymtl
delete them which will reset that rom

PS, it will be in your taskbar
you can close it from your taskbar, the orphaned window

[Tesla]

 

 

1. VPM will get you a score box you simply dont want

and enabling external DLL will result in freezys and flexDMD fighting over control of the same display window
which will result it it either flashing back and forth, or might possibly result in 2 windows, one of which you didnt want.

 

2. Heavy metal doesnt need use DLL or show vpm checked

as the score is both in the backglass and via flexDMD

 

so you dont want the VPM display nor freezys DLL display

 

 

 

1. Correct. I saw how that worked the other day. It's all documented in the Table-Script. No problems there.

 

2. So, I brought-up Heavy-Metal to check those F1 options. They were incorrect, but it is working. I turn them both off and restart table. I now notice a small red-mark below my DMD/video box. It's a squished DMD ... I think it said "Virtual DMD" . I right-click to Properties and it's DMDExt. I end the Table, VPX Editor and everything. It's still running and there is no exit.

 

When running VPX in Windowed-Mode (so I can drag stuff around or right-click) this Virtual-DMD has top focus over any other program or Window. This is what was running the other night on top of all my tables (all of a sudden). I thought it was the tables and started to try to fix them. It was just this all along. Now, I just don't know why it sometimes starts itself (usually when running Heavy Metal). Notice, no table is even loaded. When you right-click-to-Properties, that is what it shows.

 

http://vpforums.org/...xt-takeover.jpg

 

 

That is freezys display with heavymetal ROM translated to it
This happens if use external DLL is enabled, which you dont need since the table has a flexDMD

 

If for some reason you cant seem to turn it off
in regedit go to
Computer\HKEY_CURRENT_USER\Software\Freeware

 

look for any entries for heavymetal or heavymtl
delete them which will reset that rom

PS, it will be in your taskbar
you can close it from your taskbar, the orphaned window

 

 

Thank you for the details about how the F1 options work, how to set them properly for Heavy-Metal Table, and why it happens.

 

The way it "takes over" was worrying to me. I mistakenly thought Freezys DMDExt was instead all my tables being messed-up. At least now I know that maybe my core-install of VPX is likely fine after all. 

 

I'll keep an eye-out for further issues with it. If it continues to be a problem, I'll dig-into the Registry to attempt to resolve it.

Edited by Tesla, 24 February 2023 - 12:26 AM.