51 replies to this topic

[wiesshund]

 

5. I also found that the dmd position is not holding so I'm guessing I need to change a line in the script? I feel like some shit has gotten reset. like the grills that I previously turned off on some b2s are not showing up again. Like, cmon man!

 

 

DMD position
Make sure cabinet mode is checked, when you hit F1
If it isnt in cabinet mode, it wont remember jack

 

Grills showing up or not would have been stored in the B2STableSettings.xml file
if that got recreated or the table file's name changed then the settings would have been lost
just a guess there?

 

And like Outthere said
Make sure this isnt on at all





 

Edited by wiesshund, 29 November 2020 - 07:31 PM.

[Thalamus]

Be very careful using freezy in combination with alphanumeric. There is a few of us that have had B2SServersetting.xml overwritten with just one game trying to write alphanum related info back to the file. It is already mentioned as a bug in the github repo. However, Freezy' focus has shifted. VPE is now the new thing, so I won't hold my breath waiting for it to be fixed. If you use alphanum, then take backups often.

 

Almost all your issues are a simple export of freeware registry hive - followed with a search and replace and reimport. No need to manually go through each rom.

[wiesshund]

You mean DMDDevice.ini dont you rather than B2STableSettings.xml?
If it eats that too, i have never had it happen yet (knock on wood) but dmddevice it eats every time

 

My method for doing alpha numeric setup is

 

copy DMDDevice.ini DMDDevice.real
copy DMD.Device.blank DMDDevice.ini

 

Run table i want to adjust the alpha numerics on

adjust everything Now, size position colour transparency etc
exit table when done

 

open DMDDevice.ini in notepad++

open DMDDevice.real in notepad++

 

Copy all the alphanumeric instructions from DMDDevice.ini
everything under

[Alphanumeric]

 

but not the header itself of course

 

now click on the DMDDevice.real

scroll down to the [game name] header for the game you are wanting to set up
paste what you copied into that section

 

save your file

 

then delete DMDDevice.ini
copy DMDDevice.real to DMDDevice.ini

 

 

So my real DMDDevice.ini reads

 

[alphanumeric]
enabled = false

Always
That is the only line at all in the alphanumerics header

 

Then for the specific ROM that i did want the alphanumerics for, it's entry, and only it's entry, would look like this
and yes, there is a reason that the virtual DMD size is set to 0, 0
 

[closeenc]
alphanumeric enabled = true
style..skewangle = 12
style..weight = Thin
style..backgroundcolor = #ff000000
style..foreground.enabled = true
style..foreground.color = #ff00bfff
style..foreground.blur.enabled = true
style..foreground.blur.x = 2
style..foreground.blur.y = 2
style..foreground.dilate.enabled = false
style..innerglow.enabled = true
style..innerglow.color = #1e00ffff
style..innerglow.blur.enabled = true
style..innerglow.blur.x = 15
style..innerglow.blur.y = 13
style..innerglow.dilate.enabled = true
style..innerglow.dilate.x = 15
style..innerglow.dilate.y = 10
style..outerglow.enabled = true
style..outerglow.color = #1487cefa
style..outerglow.blur.enabled = true
style..outerglow.blur.x = 15
style..outerglow.blur.y = 4
style..outerglow.dilate.enabled = true
style..outerglow.dilate.x = 78
style..outerglow.dilate.y = 5
style..background.enabled = true
style..background.color = #ff000000
style..background.blur.enabled = true
style..background.blur.x = 7
style..background.blur.y = 7
style..background.dilate.enabled = false
alphanumeric pos.0.left = 1624
alphanumeric pos.0.top = 327
alphanumeric pos.0.height = 67
alphanumeric pos.1.left = 954
alphanumeric pos.1.top = 280
alphanumeric pos.1.height = 75
alphanumeric pos.2.left = 979
alphanumeric pos.2.top = 185
alphanumeric pos.2.height = 67
alphanumeric pos.3.left = 964
alphanumeric pos.3.top = 233
alphanumeric pos.3.height = 73
alphanumeric pos.4.left = 1296
alphanumeric pos.4.top = 221
alphanumeric pos.4.height = 41
alphanumeric pos.5.left = 1180
alphanumeric pos.5.top = 227
alphanumeric pos.5.height = 41
alphanumeric style = 
virtualdmd enabled = false
virtualdmd left = 1729
virtualdmd top = 669
virtualdmd width = 0
virtualdmd height = 0

And you gotta do this for literally every table you go trying to set alpha numerics on.

I can not find a lot of call to use external alphanumerics, as B2S handles most any need i can think of for them
I suppose maybe if you are using PUP or like a PinballX backglass image/animation instead of a real B2S backglass?

 

Other than that, i have only found it useful for making nice LED digit images to use in table or on an FSS backbox or stuff like that.

Edited by wiesshund, 30 November 2020 - 12:06 AM.

[bpjacobsen]

I'm not sure what is meant by alphanumeric setup? Is that the built in dmd? Or what is that exactly?

Also, what is VPE?

and lastly, where are the direct draw settings? I opened dxdiag but per attached screenshot you can see that I have no option to disable this.

 

 

Attached Files

•  DirectX Diagnostic Tool.png   39.8KB   0 downloads

Edited by bpjacobsen, 30 November 2020 - 01:09 AM.

[wiesshund]

I'm not sure what is meant by alphanumeric setup? Is that the built in dmd? Or what is that exactly?

Also, what is VPE?

and lastly, where are the direct draw settings? I checked the nvidia settings  and vpx but not sure where that is?

 

Alphanumeric is a game display that is made of segmented LED's and is not a Dot Matrix Display(DMD)
It's the 50 boxes of numbers you posted about appearing on the screen when you picked to use external DLL on a ROM that does not have a DMD
A DMD is a board full of round LEDs, anything that does not consist of the is not a DMD

 

VPE has no bearing on your issues, it is a project of converting VPX to the Unreal Unity engine
and again, it has 0 bearing here.

 

I just showed you the direct draw settings, i gave you an exact screen shot from PinMAME32

You use MAME, so i assume pinmame32 will be familiar to you?

Or you can do it via the registry, as thalamus said, you can export the vpinmame registry, do a search and replace
save it, then re-import it.

Or you can do it by hand, no idea how many roms you would be dealing with
 

[bpjacobsen]

OK so that is ruled out. direct draw is turned off.

[wiesshund]

OK so that is ruled out. direct draw is turned off.

did you specifically check both per table and general?

 

You said that this SSD was working fine previously
Then you upgraded it from windows 7 to windows 10 ?

When you did this upgrade, did you do an inplace upgrade? (bad)
Or did you do a clean fresh install and just activate windows 10 with your existing windows 7 COA ? (good)

[bpjacobsen]

OK so I realized somelthing funky happened to my dmdext.ini file. the settings were all jacked up like they got overwritten. so I copied my backup I have with my original global settings and some table specific settings and now the freezy dmd is working again including GNR. Hmm

[Thalamus]

Uh. Yes. Of course, dmddevice.ini is what I was thinking about. And, I believe that alphanum might still be enabled by default for at least 1.8 release. I of course highly recommend turning that off.

[wiesshund]

I believe that alphanum might still be enabled by default for at least 1.8 release. I of course highly recommend turning that off.

 

It is unfortunately.
Least it was when i installed it last.

 

[alphanumeric]

enabled = false

 

got added real quick, but not quicker than it got me

 

[bpjacobsen]

For me, at least in my backup file it shows alphanumeric = false. But I noticed something else rather odd. after applying the size and position globally  using the right click option, this is what the size/postion shows in the ini file now:

 

; x-axis of the window position

left = 2245.33333333333

 

; y-axis of the window position

top = 245.333333333333

 

; width of the dmd in monitor pixels

width = 597.333333333333

 

; height of the dmd in monitor pixels

height = 149.333333333333

 

What on God's earth would cause this?

[wiesshund]

 

For me, at least in my backup file it shows alphanumeric = false. But I noticed something else rather odd. after applying the size and position globally  using the right click option, this is what the size/postion shows in the ini file now:

 

; x-axis of the window position

left = 2245.33333333333

 

; y-axis of the window position

top = 245.333333333333

 

; width of the dmd in monitor pixels

width = 597.333333333333

 

; height of the dmd in monitor pixels

height = 149.333333333333

 

What on God's earth would cause this?

 

Well
That sort of tells me that it believes that is is being displayed from display0 (screen 1) 2245 pixels to the right
and 245 pixels down
To the top left corner of the DMD window

and is 597 pixels wide by 149 pixels tall

Which, if you have 2+ screens, and the 1st screen is 1920 or less wide, would put that DMD on your 2nd screen someplace

 

So i do not exactly see an issue here?

Aside from that i hope you are not using a VPM display with the GnR table
It has no need of it as it is only a alphanumeric ROM and the backglass has a much nicer display

I mean, you can use it, but it is a bit funky, but at least you know globally, where they should appear from now on
then you can adjust on a game by game basis if needed