Doing god's work

@asyncroon I am using an xbox one controller with the wireless dongle attached to the steam link. I did try using the dongle directly on the PC and the same issue occurred. I tried without the dongle via bluetooth on BOTH PC and steam link and the same issue occurred.

@asyncroon

I was able to play the game the other night by disabling my controller completely, launching the game via steam, and turning it back on during the (insanely long) seizure message at the beginning. The steam button message as well as the configs loaded message pops up as soon as the controller connects to the dongle on my PC and everything works perfectly fine.

I found this post:

https://www.reddit.com/r/SteamController/comments/m8ax00/help_from_people_who_use_glosc_and_or_play_ac/

OP says this works but doesn't load his custom configs (he is disabled and needs a specific layout). I use the standard layout for xbox one controller so this is not an issue for me.

I should mention that I used SteamDB grid manager to re-add the shortcut to the game as a step before trying the controller method, but having the controller on before launching this new shortcut produced the same crash (so it's not an issue with the shortcut itself). Something on Ubisoft's side is conflicting with steam's controller connection on launch which as we all know manifested after the latest title update.

A pretty easy workaround, yet not ideal. I can finally play again, but Ubi should help this disabled dude out!

@asyncroon

I was able to play the game the other night by disabling my controller completely, launching the game via steam, and turning it back on during the (insanely long) seizure message at the beginning. The steam button message as well as the configs loaded message pops up as soon as the controller connects to the dongle on my PC and everything works perfectly fine.

I found this post:

https://www.reddit.com/r/SteamController/comments/m8ax00/help_from_people_who_use_glosc_and_or_play_ac/

OP says this works but doesn't load his custom configs (he is disabled and needs a specific layout). I use the standard layout for xbox one controller so this is not an issue for me.

I should mention that I used SteamDB grid manager to re-add the shortcut to the game as a step before trying the controller method, but having the controller on before launching this new shortcut produced the same crash (so it's not an issue with the shortcut itself). Something on Ubisoft's side is conflicting with steam's controller connection on launch which as we all know manifested after the latest title update.

A pretty easy workaround, yet not ideal. I can finally play again, but Ubi should help this disabled dude out!

@asyncroon I am using an xbox one controller with the wireless dongle attached to the steam link. I did try using the dongle directly on the PC and the same issue occurred. I tried without the dongle via bluetooth on BOTH PC and steam link and the same issue occurred.

bump bump bump

Doing god's work

@asyncroon Great job with the helpful information that Ubisoft seems to be completely ignoring. This used to work perfectly for me until the last update.