Chaos Legion PC - Bugs and crashes when accessing control configuration menu about xidi HOT 5 CLOSED

There have been a lot of compatibility improvements since 4.1.1. Does a recent development build help at all?

Does the crash also occur without Xidi?

from xidi.

I tried the development build of Xidi and the crashes stopped happening with the newer build but the Gamepad 2 menu option still appears to be bugged unless I take Xidi out, change the in-game control configuration to Gamepad 2, then put Xidi back.

from xidi.

I was able to obtain access to this game for the purpose of testing with it, and I can't point to a specific issue with Xidi to fix to make this game work better. The game appears to do a lot of very strange things, but I was not able to reproduce the issues reported here with Xidi.

From what I understand there are two issues here:

1. The game (sometimes) hangs and crashes to the desktop when entering the controller configuration menu.

   • Ironically, I was not able to reproduce this issue with Xidi, but I was able to reproduce it semi-regularly without Xidi.
   • What I found is that the game is slow to enter the controller configuration menu with Xidi and less slow to enter without Xidi. This is because the game enumerates DirectInput devices a very high number of times in very quick succession, and Xidi inserts its own processing each time that happens.
   • There seems to be an implementation issue with the game itself. In the logs and also in the debugger I see the game making incorrect out-of-order DirectInput API calls which, not surprisingly, fail. This only happens sometimes, though. If I add a bit more concurrency control to Xidi that makes the frequency drop even further, which suggests a threading issue.

2. "Gamepad 2" cannot be selected.

   • I was not able to reproduce this issue at all. Assuming the game made it into the controller configuration menu, I never had any trouble selecting Gamepad 2 and then actually using the right analog stick to control camera in the game.
   • I wonder if this is an issue with how the custom mapper is set up?

For Issue 2, could you please try removing your Xidi.ini and replacing it with this:

[Workarounds]
ActiveVirtualControllerMask = 0x01

from xidi.

I tried the replacement Xidi config file and this did fix the inability to select Gamepad 2 settings in the Control options of the game. Sadly I cannot have both the above fix with custom control bindings since the latter cancels out the former when I want to configure so that it can be applied to the game for an out-of-the-box set-up with the original PlayStation 2 controls when set to Gamepad 2 in the settings.

from xidi.

Thank you for the update. What this tells me is that the issue is not a Xidi bug but rather a problem with the custom mapper configuration you are trying to create.

If you would like assistance getting your custom mapper to work correctly, please feel free to open a Q&A topic and share the Xidi.ini configuration file you were trying to use. To open a Q&A topic, navigate to this repo's Discussions tab, click "New discussion" and finally choose "Q&A" as the category.

We can also discuss how to submit game configurations to XidiGameConfigurations if you wish.

from xidi.