X360e on Pinball X

[halen]

I don't know what's wrong. If the problem is Windows 11, Pinscape or X360e. What's happening: When upgrading from Windows 10 to Windows 11 the X360e stops working and gives this error message:

Error calling Setup DiGetDevice RegistryPropertyW: 122..

I have a HD with Windows 10 with the last update and works without any problem. Now when I upgrade to windows 11 I get the above error message. I try all of X360E  versions and the problem persists.

My configuration is a Pinscape with X360e 3.2.10.82 and Windows 10. I dont have Ledwiz and my pinscape is setting with USB identification Pinscape ID 1209, Product EAEA.

If i change the usb identification to Ledwiz Unit 1 i have the same problem. 

if i use the new X360e i have problems with pinball x.

[Draco1962]

You note a problem with PinballX when you use the new X360ce - can you attach your pinballx.ini and log.txt file from that configuration on Windows 11 with the new X360ce?

Did you search by the error and see this on YouTube?

 

[Mike_da_Spike]

It is a known bug in x360ce.
See https://github.com/x360ce/x360ce/issues/830#issuecomment-1321113284
 

It started for me a couple of weeks ago when I added Pinball FX to my Cabinet (see post of Joyrider).
I have W11 running for a while and a pinscape controller.

It is just the config tool that has an issue to enumerate the devices.

Version 4.x is working as a charm, but no solution for a front end as it creates a new joydevice and the button numbering confuses the front end (mine ended up to starting slow)

Version 3.2 is still working fine, but the x360ce could launch which this error.

A game doesn't need the x360ce.exe. this is just the tool to configure the ini file.

A game uses the .dll file that it embedded in the exe file. A large list of games is added and shows which dll is used by which game.

Mostly it is xinput1_3.dll, but I thought Zacaria uses xinput1_4.dll

These dll's only differences in name. So, you can just use them.

The dll uses x360ce.ini as input file.

This ini file is created with x360ce.exe.

My issue was that the plunger (that was mounted as 'half inverted xas' on the right thump stick) was being pulled all the time and needed to set a dead zone.

After creating a correct x360ce.ini manually, all my games were working again.

There are some older versions like 2.0 of the exe file, that is working as well. And you can use the dll from 3.2 with this created ini file.

I hope this make sense. It took me more than a week to understand the complete process and get my complete cab up and running again, but all my Steam and Epic games are working again