error and crash latest pinballx

[thechadisgr8_69]

Keep getting this whenever I try and change controller inputs. Any ideas? windows11 everythinbg up to date.

log.txt SetupWizard.log XDMDlog.txt

 

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'SlimDX4, Version=4.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
File name: 'SlimDX4, Version=4.0.0.0, Culture=neutral, PublicKeyToken=null'
   at Headsoft.Tools.DirectInput..ctor(Control control, Object tag)
   at Headsoft.FrontEnd.frmGetJoy.c(Object A_0, EventArgs A_1)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9325.0 built by: NET481REL1LAST_25H2_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
Settings
    Assembly Version: 1.0.9618.16700
    Win32 Version: 1.0.9618.16700
    CodeBase: file:///C:/PinballX/Settings.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9325.0 built by: NET481REL1LAST_25H2_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9333.0 built by: NET481REL1LAST_25H2_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9319.0 built by: NET481REL1LAST_25H2_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Management
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[Draco1962]

Your pinballx.ini please. Thanks!

 

[Tom Speirs]

i see this. it must be missing a visual c runtime. ill get to it shortly.

[thechadisgr8_69]

Thank you sir!

[Tom Speirs]

ill make sure the installer is right but i think it is this one x64.

https://www.microsoft.com/en-us/download/details.aspx?id=26999

[Tom Speirs]

iI needed a new pinballx version. It was not the runtime. 7.23 is now available.

[thechadisgr8_69]

Ty for your diligence! I will try when I get back home.

[Mike_da_Spike]

On 5/13/2026 at 1:23 AM, thechadisgr8_69 said:

Ty for your diligence! I will try when I get back home.

And ? Any results ?

[thechadisgr8_69]

Yessir works now, must have been a bug, though I think I'm going to give up on pinballx since I dont think it's capable of doing what I'm looking for

[Tom Speirs]

8 minutes ago, thechadisgr8_69 said:

Yessir works now, must have been a bug, though I think I'm going to give up on pinballx since I dont think it's capable of doing what I'm looking for

no worries. good luck.

ps: no harm in asking if you have a request.

[Mike_da_Spike]

1 hour ago, thechadisgr8_69 said:

I think I'm going to give up on pinballx since I dont think it's capable of doing what I'm looking for

What are you looking for?

[Tom Speirs]

5 minutes ago, Mike_da_Spike said:

What are you looking for?

He posted in the GameEx forum with what his is issue is. Thanks. Does not sound much.

[thechadisgr8_69]

Which do you think would be easier/better to use as a base for this? Gamees or pimballx?

[Draco1962]

Since you are asking in the PinballX side of the forums, most people here will have some bias. 😜 

Following is my opinion and very "high level" overview - It depends upon your experience/comfort level with command line-based emulators, controllers and goals, etc.

Both frontends are fine, but their menu and display options differ quite a bit.

GameEx is probably the best place to start, having greater flexibility in theming and initial emulator setup "baked in"  to the Setup Wizard.

That said, I recommend that you start with one emulator, confirm that you have it working first outside of the frontend BEFORE adding it to the frontend, troubleshooting any issues that may arise. 

Best of luck with your decision! We're here if you need help along the way.

 

[thechadisgr8_69]

So I've gotten pinballx set to launch to systems list so games and tables aren't grouped together,  I think my Achilles heal is going to be xml files, is there any way to automate that process ie generate xml's via rom directory? I've used pretty much every front end out there, starting with gamex 15 years ago, my current go to is launchbox but thatf doesn't handle pinball very well, using pinup popper for pinball but that doesn't handle emulators/pc games as well. Anyway, the reason I stopped using gameex years agao was the xml file thing. No way to just scan a directory and use those files based on file extension? 

[Draco1962]

17 hours ago, thechadisgr8_69 said:

Anyway, the reason I stopped using gameex years agao was the xml file thing. No way to just scan a directory and use those files based on file extension? 

Since that is a GameEx specific question, I will defer a direct answer, suggesting that you ask in the correct forum where you already have a post open.

Assuming you have a pincab from which you are attempting to run emulators as well as digital pinball systems, another suggestion would be to configure your pins to run exclusively on PinballX and your arcade and emulators via GameEx (probably Arcade Edition would be best as there is minimal theming and it just works!). I get the impression that you want an AIO solution but, given the complexity of what you are attempting and the use of Pinup Popper, it might be best in the long run to keep them separate. Again, my 2 centavos.