1790 replies to this topic

[LunatechFringe]

To the best of my knowledge - tilt bob is more or less hard coded to the letter 'T'. Once it hit, you should in notepad or any editor, see the 'T' being typed. The mjr plugin, once done correctly, you will get the same amount of tilt warnings as the rom is set to. Often 2 or 3. Without it - it will often tilt on first. I'm 99.5% sure that you should see the letter 'T' being typed. It's been ages since I did this last. Try mapping it to 'T' and see if that doesn't change anything.

 

Following Wiesshunds advice is valid, but, maybe a bit unnecessary brutal, what I would do is. Delete the registry for the rom only, then run it once. If that works, consider his solution. You should after you delete the registry for the rom, and start the rom once, see it come back. If you don't, then there is some reigstry issues going on and you should definately do what Wiesshund suggests.

 

What can happen is that you play a game with different settings first time around, and then add some hardware/software and want to change - vp / pinmame isn't bug free and this is windows too So, deleting the rom entry in question is a good thing to do when something isn't working as you expect it to. Cleaning nvram too, but, that is only game related and not useful in this particular case.

 

My VPX preferences are configured with T and Button 13 for Mech Tilt.  It was what was suggested in the Pinscape Build Guide.  The tilt bob is working as expected.  With a table open, I can manually move the tilt bob to close the circuit, and VPX will tilt after two to three attempts of doing that (it doesn't tilt automatically the first time).  I can also confirm renaming NudgePlugIn_mjrAccelAndTilt.vbs in the Scripts folder to NudgePlugIn.vbs produces the same results as before where analog nudging stops working if that file is present.  Without it, it seems to be working fine.  I just need to fine-tune my nudging experience.  I'll let Steve know about the experience with NudgePlugIn.vbs and see what he says.

 

Regarding the ROMs, I looked at the registry entries for the Theatre of Magic table (tom_14hb), but I couldn't find anything wrong.  It's baffling.  It matches with VPinMAME, where F1 shows the Show DMD setting unchecked.  Use External DMD and Colorize DMD is checked.  The showpindmd entry is enabled in the registry, while showwindmd is disabled.

Per DmdDevice.ini:

[tom_14hb]

virtualdmd left = 2271

virtualdmd top = 580

virtualdmd width = 666

virtualdmd height = 104

 

I've deleted nvram files when a table is showing a clear problem, but this seems like something else.

 

Software is ever-changing, so bugs are a fact of life.  After working in IT for over 25 years, it's been proven as the nature of it.  So, back to troubleshooting...I'll need to break down Wiesshund's suggestions and see what I come up with.

[Thalamus]

Did you delete the registry key for the rom ? You seem to know what you're doing so I expect so.

[wiesshund]

There is not in mine, but since he is only seeing it on certain tables

Is there any remote possibility that the tables happen to have a pinmame over-ride in the script?

You can force the vpm dmd on, just like we can force sound off (and then re-enable at table exit)

 

I sort of think the answer is no, but i guess i have to ask.

 

Not quite sure if he said it only happened when checking to use color or not?
TOM is an external color patch, VNI and PAL files

 but i am not sure how that would cause vpm to simply ignore the show DMD = false setting?

Since this is a thing that does not seem to be experienced by any of the rest of us, i wonder what the mitigating factor is

cause we all have the same color rom downloads, not like there is any variety there

[LunatechFringe]

I followed Wiesshund's suggestions and it reminded me of something I've been seeing.  If I unregister and clean the registry out, then reregister vpinmame and setup the defaults, everything seems to be normal during the setup process.  If I reset the defaults, quit vpinmame's setup, then open it again to setup defaults, the Default Options window will appear again once I click OK (the second window contains the settings I already made).  When this happens, I never see the success prompt after configuring it.  I ended up reimporting only my rom settings for the registry, leaving default and globals out of it.  The problem was still there.  I even backed up cfg, ini, and nvram folders and had the empty folders, and it still happened.  I then did it without importing any of my registry backups (unregister, clean registry, reregister, setup defaults), and it still happened when I loaded the table from VPX, albeit the built-in DMD showed up on top of the table.  As before, the ROMs by themselves are fine while testing in vpinmame.  It only happens when the table is loaded with VPX (10.7 build 270 rc).  It's as if vpinmame is running twice...really strange.

Edited by LunatechFringe, 21 July 2021 - 11:43 PM.

[Thalamus]

This is TOM 2.4 - right ? What happens when you change the script ? Controller.ShowDMDOnly = 0 ?

[LunatechFringe]

This is TOM 2.4 - right ? What happens when you change the script ? Controller.ShowDMDOnly = 0 ?

 

Yes, it is TOM 2.4.  I get a box with white text under the built-in DMD.

Trunk Pos : 0        0 0 0 29
Trunk Face:  Closed
Trunk Mag.:  Off
Trap Door : Closed
L.Post:  On T.Post:  On
L. Gate:  C| R. Gate:  C|
Coin Door :  Closed

[wiesshund]

I followed Wiesshund's suggestions and it reminded me of something I've been seeing.  If I unregister and clean the registry out, then reregister vpinmame and setup the defaults, everything seems to be normal during the setup process.  If I reset the defaults, quit vpinmame's setup, then open it again to setup defaults, the Default Options window will appear again once I click OK (the second window contains the settings I already made).  When this happens, I never see the success prompt after configuring it.  I ended up reimporting only my rom settings for the registry, leaving default and globals out of it.  The problem was still there.  I even backed up cfg, ini, and nvram folders and had the empty folders, and it still happened.  I then did it without importing any of my registry backups (unregister, clean registry, reregister, setup defaults), and it still happened when I loaded the table from VPX, albeit the built-in DMD showed up on top of the table.  As before, the ROMs by themselves are fine while testing in vpinmame.  It only happens when the table is loaded with VPX (10.7 build 270 rc).  It's as if vpinmame is running twice...really strange.

ok, testing the following combination

 

VPX 10.7 revision 285
VPM 3.4 revision 280
Freezy's 1.9.0.24
FlexDMD 1.8.1 (which doesnt come into play here at all)
ROM tom_14hb
Table Theatre of Magic (Bally 1995) 2.4 VPX (Fleep)
patchless pin 2 dmd ROM colorization from VPU

 

So definitely nothing in the stock script, and not in the bigus version either

 

[LunatechFringe]

 

I followed Wiesshund's suggestions and it reminded me of something I've been seeing.  If I unregister and clean the registry out, then reregister vpinmame and setup the defaults, everything seems to be normal during the setup process.  If I reset the defaults, quit vpinmame's setup, then open it again to setup defaults, the Default Options window will appear again once I click OK (the second window contains the settings I already made).  When this happens, I never see the success prompt after configuring it.  I ended up reimporting only my rom settings for the registry, leaving default and globals out of it.  The problem was still there.  I even backed up cfg, ini, and nvram folders and had the empty folders, and it still happened.  I then did it without importing any of my registry backups (unregister, clean registry, reregister, setup defaults), and it still happened when I loaded the table from VPX, albeit the built-in DMD showed up on top of the table.  As before, the ROMs by themselves are fine while testing in vpinmame.  It only happens when the table is loaded with VPX (10.7 build 270 rc).  It's as if vpinmame is running twice...really strange.

ok, testing the following combination

 

VPX 10.7 revision 285
VPM 3.4 revision 280
Freezy's 1.9.0.24
FlexDMD 1.8.1 (which doesnt come into play here at all)
ROM tom_14hb
Table Theatre of Magic (Bally 1995) 2.4 VPX (Fleep)
patchless pin 2 dmd ROM colorization from VPU

 

So definitely nothing in the stock script, and not in the bigus version either

 

Mine is the same except for the VPX 10.7 build and FlexDMD being 1.8.0.  I'm running a two-screen cabinet.

It seems to be loading the built-in DMD as 'bring to front'.  In Task Manager looking under Visual Pinball 10.7.0 (32-bit) (4), I can see Theatre of Magic (1.4H Coin Play).  If I right-click and minimize it, only the colorized DMD displays (until I close and reopen the table).

Edited by LunatechFringe, 22 July 2021 - 01:06 AM.

[wiesshund]

This doesnt fix anything, just hides it
but drag it to the playfield screen and resize it to make vpm save the position

Since the table is running in exclusive fullscreen it will vanish behind the playfield

 

But that does not fix the issue, just hides it.

 

I looked at all vpx settings, i cant find any that would seem to cause this

do not see anything in vpx registry that sounds like it could create the issue for you

[LunatechFringe]

This doesnt fix anything, just hides it
but drag it to the playfield screen and resize it to make vpm save the position

Since the table is running in exclusive fullscreen it will vanish behind the playfield

 

But that does not fix the issue, just hides it.

 

I looked at all vpx settings, i cant find any that would seem to cause this

do not see anything in vpx registry that sounds like it could create the issue for you

 

Agreed that it just hides it.  This is actually happening in "force exclusive fullscreen mode", and the DMD was already moved to the playfield.  I thought unchecking it, closing and reopening VPX, then checking it again would be worth a shot, but it didn't fix it.  I'm stumped.

[wiesshund]

I am kind of at a loss

And short of going scorched earth (after backing everything up) i am not sure at the moment what so suggest.

Obviously, somehow, pinmame is ignoring the show DMD part, but unsure how that is taking place.

 

You do not have any scripts in the tables folder at all?

 

Maybe @Toxie may have some idea

You might post a link to this thread in the 10.7 beta thread, as you said it wont happen in 10.6?

[LunatechFringe]

I am kind of at a loss

And short of going scorched earth (after backing everything up) i am not sure at the moment what so suggest.

Obviously, somehow, pinmame is ignoring the show DMD part, but unsure how that is taking place.

 

You do not have any scripts in the tables folder at all?

 

Maybe @Toxie may have some idea

You might post a link to this thread in the 10.7 beta thread, as you said it wont happen in 10.6?

I'm curious if any of these would affect anything:

* "The emulator that cannot be named."  However, it is not loaded when the problematic tables are running.
*  P-ROC
*  UltraDMD (I run it separately from FlexDMD).

 

Actually, it happened with 10.6, as well.
 

Edited by LunatechFringe, 22 July 2021 - 09:47 PM.

[LunatechFringe]

@Thalamus
@Toxie
@Wiesshund

I figured it out, and it appears to be my mistake.  I was enabling "Always run full-screen on this display" in Global Settings (Setup Paths...) from VPinMAME's setup.exe.  Once I unchecked it, the problem went away.

 

Sorry for the stress, guys, but I greatly appreciate the help and input.

[wiesshund]

@Thalamus
@Toxie
@Wiesshund

I figured it out, and it appears to be my mistake.  I was enabling "Always run full-screen on this display" in Global Settings (Setup Paths...) from VPinMAME's setup.exe.  Once I unchecked it, the problem went away.

 

Sorry for the stress, guys, but I greatly appreciate the help and input.

 

Well, that is an option i have never tried, as i have no suitable screen to do that on

might be useful with a marquee screen, though i do not know that pinmame would go to it by default

 

Maybe a legacy option from the parent MAME branch or something

[Thalamus]

Yepp. New to me too that one. Happy though that you figured it out and thanks for sharing this oddity.

[naeromagus]

So i know that I've mentioned this earlier, Having issues with The Addams Family Gold, (the game starting with the coin door interlock is engaged, what i didn't mention,

is when Buy an extra ball option comes on i cant buy in. (Normally assigned to Key 2)  I use a default keys for my cab. Also i notice now the Music speeds up when i open the coin Door, 

 

where with previous versions it did not latest SC variant used for Cheech and Chong compatibility 

 

Can anyone else confirms this 

Edited by naeromagus, 28 July 2021 - 02:48 PM.

[flipperkopf1976]

Thank you, but after this Update 3.4 no music sound at Dr Who table.
Danke für die Arbreit, aber beim Table Dr. Who gehen nur noch ball Geräusche der gesamte andere Sound Musik geht nicht mehr. Hat jemand eine Idee.
Danke

[Thalamus]

user error : https://www.vpforums...=47361&p=483999 - learn how to check the rom, it will tell you what is wrong.

[fourbanks]

all my tables working well on this beta build with no issues whatsoever 

[leeoneil]

Hello and thank you to the team involved in this project.

 

I'm just trying this 3.4 beta (lot's of problem with my Pin2 DMD, so i give it a try).

It's seems to work fine with the beta.

 

Except one thing thant i can't understand.

The "historic orange" is gone, all the text on the rom are showing in a colour very clear, almost white.

I tried to change the color in the defaut setup, but nothing happen.

 

What i am missing ?

Thank's if you have any idea.

Edited by leeoneil, 06 November 2021 - 12:27 PM.