24 replies to this topic

[Tesla]

Everything works fine on my 3-screen cabinet when I run my 11 tables from normal VPinballX.exe v8.0 (32bit Direct-X) on my Windows-11 Pro (64 bit) v24H2. 

 

I'm now trying to run a table from VPinballX64.exe (64bit Direct-X) for the FIRST TIME. I get this error as the table tries to load.

 

I think this is what I have installed:

VPX v10.8.0 (32/64 bit)

vPinMame v3.6 

DMDextensions v2.3.0.0

FlexDMD v1.9.1.0

B2S-Server v2.1.4

DOF [MJR 7-2025] (32/64 bit)

 

It's really just Toxie's install, and MJR's for the DOF-stuff. 

 

[Tesla]

As I read the error-message closer, looks like a rom-set problem maybe?

 

If I run \VPinMAME\Setup.exe (I suppose the x86/32-bit version)

- At the top is says it is currently installed

 

But if I run \VPinMAME\Setup64.exe

- It says it is NOT currently installed

 

I'm thinking maybe this is the problem.

Do I just click the button to install it?

Can I have them both "installed and registered" concurrently?

Edited by Tesla, 06 May 2026 - 06:49 PM.

[Tesla]

Nevermind. 

 

That was the problem after all. 

 

DOF and everything else seems to be working (no far) with Pinball-Y set to use vPinballX64.exe instead.

 

I'll leave it this way and run-through playing my tables and testing.

Edited by Tesla, 22 July 2026 - 02:47 PM.

[fhjui]

As I read the error-message closer, looks like a rom-set problem maybe?

 

If I run \VPinMAME\Setup.exe (I suppose the x86/32-bit version)

- At the top is says it is currently installed

 

But if I run \VPinMAME\Setup64.exe

- It says it is NOT currently installed

 

I'm thinking maybe this is the problem.

Do I just click the button to install it?

Can I have them both "installed and registered" concurrently?

yes, you have to install both versions, if you intend to use vpx32 and vpx64.

background: a 32bit program cannot communicate with 64bit modules /progams and vice versa. 
 

[Tesla]

 

yes, you have to install both versions, if you intend to use vpx32 and vpx64.

 

 

Thanks. I seem to have missed that memo.   I mean, I saw it there in the folder there, but I didn't know it wasn't actually installed/registered.

 

F14-Tomcat plays fine now. Of course, Pinscape buttons and nudge works ... and the DOF knocker sounded. The Backglass is there (so B2S-Server seems fine) and the Pinball-Y "Pause Menu" hook-thing works good enough.

 

I think I have at least one Table setup to use Flex-DMD. I think if the DMD "is a little prettier" and you right click on it ... options look different, that means it is that kind. That should test-out/verify Flex-DMD/DMD-Ext is also working in 64bit.

 

That should be about it ... Oh, and I want to verify Multi-Ball on some complex tables is still working smooth.

Not sure how you truly test SSF-7.1 inside a table, but it sounds about right.

This computer is Intel-i7/GTX-1070/RealTek-7.1 with 16gb-ram (so can hopefully utilize more of it now).

Edited by Tesla, 07 May 2026 - 03:11 AM.

[Tesla]

 

 

I think I have at least one Table setup to use Flex-DMD. I think if the DMD "is a little prettier" and you right click on it ... options look different, that means it is that kind. That should test-out/verify Flex-DMD/DMD-Ext is also working in 64bit.

 

 

 

Indiana Jones checks good for 64-bit VPX (Direct-X) operation ... with DMD-Ext (which also happens to be Alt-Color colorized).

 

So, yeah ... all these seem to check good for 64-bit:

Toxie's VPX_v10.8.0 installer (and all it contains)

B2S-Server v2.1.4

DOF (MJR 7-2025) 

Pinball-Y x64 v1.1.0

on Windows-11 Pro (64 bit) v.24H2

 

So, with bringing that table into my VPX-8.0 install ... I now have 12 tables adjusted & validated. Nice.

Since Pinball-Y is now set to use VPinballX64.exe instead, I plan to play a couple of full games on each to re-validate on 64bit before moving onto installing others.

If all that passes, might be a good time for a full backup Image.

[Tesla]

My 12 (main favorite) VPX Tables seem to be working fine with this software load-out.

So that my notes of "currently install software" for this Full Backup Image is accurate... would yall say this list is accurate?

 

I'm wondering if DMDextensions, FlexDMD, B2S-Server should also be declared as 32/64 bit, or are they just somehow 64-bit compatible?

 

My Virtual-Pinball VPX 3-screen Cabinet (software as of 5-2026):

VPX v10.8.0 (32/64 bit)

- Using VPinballX64.exe (Visual Pinball 64-Bit Direct-X)

vPinMame v3.6 (32/64 bit) SC "Stern Color patched roms"

- Both 32bit and 64bit versions installed and setup

DMDextensions v2.3.0.0

FlexDMD v1.9.1.0

B2S-Server v2.1.4

DOF [MJR 7-2025] (32/64 bit)

-

Pinball-Y x64 v1.1.0

on Windows-11 Pro (64 bit) v.24H2

Edited by Tesla, 26 May 2026 - 03:40 PM.

[Tiki]

 

I'm wondering if DMDextensions, FlexDMD, B2S-Server should also be declared as 32/64 bit, or are they just somehow 64-bit compatible?

 

• DMDextensions (freezy / dmdext)
  This is the one that is explicitly split into 32-bit and 64-bit binaries.
  The DLL loaded by the host process must match the host bitness:
  • VPX/VPinMAME 32-bit → DmdDevice.dll 32-bit
  • VPX/VPinMAME 64-bit → DmdDevice64.dll / 64-bit package
    The project itself documents installing both versions when mixing 32/64 apps.
• FlexDMD
  FlexDMD is mostly a COM/.NET component and is generally treated as “compatible with both” rather than something users manually think about as x86/x64.
  In practice:
  • newer FlexDMD releases work fine with VPX 64-bit
  • you usually install one package and it registers appropriately
  • table authors normally don’t specify “32-bit FlexDMD” vs “64-bit FlexDMD”
• B2S-Server
  Similar story to FlexDMD.
  B2S Server is largely a .NET-based COM server, so users typically don’t manage separate x86/x64 installs manually. Current releases work with VPX 64-bit without needing a distinct “B2S 64” workflow.

[Tesla]

Imaging only takes 9 minutes (with Verify pass) so not sure why I don't do it more often. My last one was before VPX v10.7.2 to v10.8.0 upgrade and of course before later reconfig for full 64bit.

OK, it is done and I feel better about saving all that work. This below is the Text file I saved along with the Image file:

 

My Virtual-Pinball VPX 3-screen Cabinet (software as of 5-2026)

 

VPX v10.8.0 (Both 32/64-bit installed)

- Using VPinballX64.exe [Visual Pinball 64-Bit Direct-X]

vPinMame v3.6 SC (Both 32/64-bit installed and setup) 

- Supports "Stern-Color patched roms"

DMDextensions v2.3.0.0 Freezy/DMDext (Both 32/64-bit DLL installed) 

- Supports Alt-Color files

FlexDMD v1.9.1.0 (32/64 compatible)

B2S-Server v2.1.4 (32/64 compatible)

DOF [MJR 7-2025] (Both 32/64-bit installers used)

*

Pinball-Y x64 v1.1.0 (64 bit)

- With some custom Javascript Addon Script-Files

- 50-second auto-start delay

PinVol v2.3 & EQ-APO for audio-balancing and SSF-7.1

Pinscaped KL25z (with headers & analog-nudge)

- Replay-Knocker with Night-Mode Switch

Windows-11 Pro (64 bit) v.24H2

*

12 VPX Tables adjusted & validated

- Only those shown in current Pinball-Y Selector Wheel

- Parallel install of old 32bit VPX-7.2 still in-place but dormant and un-used

*

Macrium Reflect v8.1.7401 Full-Image with Verify-pass

- Bootable Win-11/VPX C-Drive only (5-2026)

Edited by Tesla, 28 May 2026 - 06:20 PM.

[Tesla]

I am running VPX v10.8.0 (64bit Direct-X) everywhere and everything seems to be working pretty good. Through Pinball-Y ... some older (migrated over) v10.7.x tables are working, as well as some newer ones rated for v10.8.x.

I only have the one DOF device (a Replay Knocker).

 

DOF 64-bit Evaluation Test:

- In VPX-Editor (Global Options, no Table loaded) I have the Replay-Knocker set to DOF

- I load the VPU DOF Tester Table

- I press the Key to test the Replay-Knocker solenoid and it actuates and sounds every time.

 

Is this a 100% test that DOF 64-bit is installed and working 100% properly?

Or, was I suppose to do something additional to truly upgrade to DOF 64bit ... like maybe login to the VPU-Online-Tool and upgrade something?

 

What if I then see a VPX Table (like my old Elvira Scared Stiff) do something weird in relation to the Replay-Knocker? Since the above test of the DOF system passed with flying-colors, does that mean the glitch is with the Table itself?

Edited by Tesla, 14 June 2026 - 03:52 AM.

[digitalarts]

If you have "weird" effects with your Knocker in a table, I would do this:
Check what "Rom" a.k.a. DOFname is used in Script. (the "cgamename")
Check the DOF online config for this table/romname.
Check the Triggernumber(s) at the Knocker Line.In a "vpinmame-rom-less" table they are always "E..." numbers; in "vpinmame-rom" tables there could be S... or W... numbers - 'S' are Solenoids, 'W' are sWitches.
Search for these numbers in the table Script. So you can see when/where in the Script the Knocker will be triggered.
Then you have two options... Modify the DOF config settings OR modify the table script

Edited by digitalarts, 14 June 2026 - 01:05 PM.

[Tesla]

If you have "weird" effects with your Knocker in a table, I would do this:
 

 

OK, I will work on that.

BTW, this is what happened: https://www.vpforums...=36320&p=553471

 

But just to clarify ... you are happy with my testing of DOF 64-bit? You would call it "done"?

There is nothing extra to do inside VPU DOF Online Tool when switching over to a more pure 64-bit VPX install?

Edited by Tesla, 14 June 2026 - 07:07 PM.

[digitalarts]

DOF online Tool and it's created configs are completely independent. Doesn't matter if 32 or 64 is in use.

[Tesla]

DOF online Tool and it's created configs are completely independent. Doesn't matter if 32 or 64 is in use.

 

So, good to know.

 

However, there does seem to be something going on with my DOF (and I only have the one toy, the Replay Knocker). Like maybe something changed with DOF-codes on either v10.8.0 or moving to 64-bit.

 

Several Tables lately (usually newer ones that have been upgraded to be compatible with v10.8.0) ... the knocker now incorrectly sounds when:

- I just load-up Table

- or I just insert coins/add-credits

I've also heard the physical one sound when I have VPX-Prefs/DOF set to "Sound-FX only" for Knocker device. 

 

One Table had to be Script-hacked, another I had to stick with the older v10.7.x version.

As I find another and start to figure out how to fix it ... I'm beginning to wonder if the problem is more deeply-rooted. If not something particular to my config, maybe something with the DOF-control pipeline in general? 

 

One thing that still seems to work is that when Pinscape Night-Mode switch is ON, it never sounds (so that's good ... good that seems to still work).

Recall my Test here (also works)

https://www.vpforums...=56900&p=553353

 

Since this thread was about VPX 64-bit (and that seems to be working fine) I can will start a new thread about this new issue if you want.

[digitalarts]

Can you Name the Tables, where you have These "knocker-problems"?
So i can Test them in my cab, and Dive into Script/dof-config comparing...
But can Take some days... a new additional Hobby is awaiting - a full packed sim racing rig besides my vpin cab IS waiting to Install 😁

[Tesla]

But can Take some days... a new additional Hobby is awaiting - a full packed sim racing rig besides my vpin cab IS waiting to Install

 

Oh really? That is cool. Yeah, no problem.

[Tesla]

Can you Name the Tables, where you have These "knocker-problems"?
So i can Test them in my cab, and Dive into Script/dof-config comparing...
 

 

That would be great, thanks.

Yes, that is a good plan. I do not think any of this would exhibit a problem on a cabinet without a physical DOF Knocker. With the software abstraction layer, I don't think it has anything to do with me using a KL25z (but it might).

 

So the strange event where Scared Stiff with Elvira ignored the XPS-Prefs/DOF/Sound-FX-ONLY setting and fired the physical knocker anyway on Score Matching .

https://www.vpforums...e=7#entry553471

 

It's not that big of a problem but I feel it again points to DOF not working properly on v10.8.0

 

--------------------------------- 

 

With Teisen's Aladdin's Castle:

https://www.vpforums...&showfile=19407

Matched with HauntFreak's B2S.

 

When I insert a Coin, the Knocker sounds:

https://www.vpforums...=56221&p=553251

 

Both the one hosted here and the slightly-newer one on VPU do the same thing.

I moved back to Dozer/MJR's v1.01 and it works fine on v10.8.0 64bit-DX ... and no weird Knocker stuff.

https://www.vpforums...&showfile=13502

Actually, I still like it fine (since it has cool High-Score Sticky on Screen-3) so not looking to try to get back to Teisen's 

https://www.vpforums...0#commentsStart

 

---------------------------

 

I'll post the others later.

Thanks again for your help.

Edited by Tesla, 08 July 2026 - 12:34 AM.

[Tesla]

I had Replay Knocker issues with @Wiesshund's Heavy Metal (v4.0 Fantasy version) but he successfully helped me to just edit-away those DOF calls from the script completely, so we'll give that one a pass.

Just know that it was doing the "Physical Replay Knocker sounds often for no reason" thing ... both at Table load-up and as the game ends.

 

https://www.vpforums...=45009&p=553845

 

----------------------------------

 

So, Number-4 came up a few days ago and I started to get worried about my DOF again ...

 

X-Files VPX Table by TastyWasps v1.29

HauntFreaks' B2S-file

rom sets: xfiles2 (v2.x) and xfiles (v3.03)

X-Files Enhanced Alt-Sound file-set by iDigStuff

 

On my 3-Screen cabinet with SSF-7.1 & DOF, running VPX v10.8.0 64bit-DX.

 

After you add a Coin/Credit, the Replay Knocker sounds (at least once, maybe twice).

I keeps doing that for each coin/Credit

I had to turn-On Night-Mode switch temporarily to get some credit loaded in peace.

It's not when you load table or start a game ... just when adding credits.

 

Oh, and I think it might even do the "ignore XPS-Prefs/DOF/Sound-FX-ONLY setting" thing and always fire the physical knocker (regardless of setting) .

 

Everything else with the Table, it's graphics, and it's Sound seem fine.

 

Thanks again for the help.

I just want the Replay Knocker to ONLY sound at the correct times... like popping-a-game (while playing or entering initials) or score matching at the end.

In the arcades, that is the only time I ever heard it.

Edited by Tesla, 08 July 2026 - 12:35 AM.

[Tesla]

1. Can you Name the Tables, where you have These "knocker-problems"?

2. So i can Test them in my cab, and Dive into Script/dof-config comparing...
3. But can Take some days... a new additional Hobby is awaiting - a full packed sim racing rig besides my vpin cab IS waiting to Install

 

3. Well, did you get it setup? If so, how do you like it?

 

1. Done.

 

2. Have you had a chance to look at my issue? I could help if you tell me what to look for.

 

My DOF (and buttons and analog-nudge) is running from my little Pinscaped KL-25z (with soldered-in headers). 

Edited by Tesla, 28 July 2026 - 05:48 PM.

[digitalarts]

Hi Tesla,

 

first to my new additional Hobby:

Rig: Oplite GTR8 Infinity

Base: MOZA R3 with ESX Wheel and SRP Lite Pedals (Brake pedal modded with loadcell)

Screen: curved 21:9 34"

PC: intel ultra 250kf plus, NVidia 5070, 32 GB Ram

Games: all kind of racing games, like MAME (Outrunners,...), Model3 (Scud Race, ...), PC (Forza Horizons 5, ...) 

Fun: unbelievable

 

Now to your Knocker problems:

 

at Aladdins Castle (the version by Teisen), it's clearly seen in the table script:

 

If  Keycode = AddCreditKey Then 

Credits=credits + 1             'Add a credit.

MaxCredits                      'Call the max credits sub to check for maximum credits. 

PlaySound "credit"              'Play the sound.

PlaySound SoundFXDOF("",127,DOFPulse,DOFKnocker)        'Play the sound.

 

 

If you take a look into dof online config, search for "Aladdin Castle", you find "E127" at Knocker.

So in script, the used "Dof number" for knocker triggering is "127"

 

If you don't want the knocker at coin-insert, simply out-comment this line, like:

'PlaySound SoundFXDOF("",127,DOFPulse,DOFKnocker)        'Play the sound.

 

 

Scared Stiff: 

I use the table by VPW v1.1.1, no strange Knocker triggering at match points (if you mean the matching after last ball)

 

 

 

X-Files:

yes, this IS strange...

same behaviour at other Sega tables: The lost World Jurassic Park, Space Jam, Independance Day, Lost in Space, Harley Davidson, Godzilla.

in Dof Online config, for all of these tables there is "S24" set at Knocker

 

 

in other sega dof configs, where Knocker is assigned to "S8", no false knocker at coin-in.

Examples: Star Wars Trilogy, Starship Troopers, Mary Shelleys Frankenstein, Goldeneye, Baywatch, Batman Forever, Apollo 13

 

I found no reason for this behaviour.

But i did a test: in X-Files dof online config, I changed S24 to S8; saved this config as "user configuration", used this instead... 

boom, no more "false" knocker at coin-in within X-Files.

 

So you could do this at your side, too.

Edited by digitalarts, 02 August 2026 - 03:40 PM.