Hello,

I'm having issues with running AC Valhalla through my Steam Link. The weird thing is, that there are only issues when I try to launch with the steam link, even though the first launch worked...
Everything stated here below is only for Valhalla, as Black Flag does not have this issue (Black Flag was the only other one still installed on which I could try to replicate the issues).
The game starts when:

• using ubisoft connect as starting point
• Steam as starting point with Steam in normal mode with AC Valhalla imported "non-Steam game"
• Steam big picture as starting point with AC Valhalla imported as "non-Steam game"

The game does not start however when I use the Steam Link and try to start if from the steam link with a controller in big picture mode.
This was not the case when I first tried the game, only after playing the start of the game for a few hours and afterwards trying to continue in the evening.
There was an update of the game (or Ubisoft Connect, I don't recall exactly) done in between those 2 playing sessions irc.

I already read the launcher.txt and other files and also took the following steps:

• Give the Steam Link a fixed IP (my PC already has a fixed IP)
• delete the crashlogs by hand (as the error code in the launcher log was saying it was unable to errase the crash reports under C:\user\"user"\AppData\Local\Temp\Ubisoft
• after deleting the crashlogs starting in normal mode (again Ubisoft and Steam launcher works, Steam Link does not work)
• after deleting the crashlogs starting in offline mode for Ubisoft Connect (again Ubisoft and Steam launcher works, Steam Link does not work)
• try to uncheck the Read-only option for the crashlog folder under C:\user\"user"\AppData\Local\Temp\Ubisoft, but to no avail as it keeps putting itself into read-only mode
• verifying installation folder and game files
• uninstalling and reinstalling the game on the C drive in the default ubisoft folder instead of in my own library under D-drive
• uninstalling Ubisoft Connect and reinstalling everything from zero (also having deleted all ubisoft related folders/files and registry entries etc)

When I go into the launcher after a succesfull launch through Steam or Ubisoft Connect, and compare it to the logs after a failed attempt with the Steam Link, the first difference I see in the logs appear on line 2 and line 5 (afterwards its just all disconnect info).

Succesfull launch:
[ 2872] 2021-03-20 17:37:34     [ 848]     INFO      GameStartPipe.cpp (81)                          Accepted connection.           
[ 2872] 2021-03-20 17:37:34     [ 848]     INFO      GameStartPipe.cpp (82)                          Starting game session.         
[ 2872] 2021-03-20 17:37:35     [ 848]     INFO      ApiProcessConnection.cpp (121)                  Game with process id 19396 connected.
[ 2872] 2021-03-20 17:37:35     [ 848]     INFO      ApiProcessConnection.cpp (132)                  Game with process id 19396 has been started with product id 13504 (branch: '').
[ 2872] 2021-03-20 17:37:36     [ 848]     INFO      UplayGameConnectionHandler.cpp (364)            Game with process id 19396 connected (API version: 2.3.0).
[ 2872] 2021-03-20 17:37:36     [ 848]     INFO      UplayGameConnectionHandler.cpp (364)            Game with process id 19396 connected (API version: 2.3.0).
[ 2872] 2021-03-20 17:37:36     [ 848]     INFO      UplayGameConnectionHandler.cpp (364)            Game with process id 19396 connected (API version: 2.3.0).
[ 2872] 2021-03-20 17:37:36     [ 848]     INFO      UplayGameConnectionHandler.cpp (364)            Game with process id 19396 connected (API version: 2.3.0).
[ 2872] 2021-03-20 17:38:00     [ 848]     ERROR     WSConnection.cpp (483)                          Received Http status code 403 for url wss://public-ws-ubiservices.ubi.com/v2/websocket?SpaceIds=e17be87d-2996-4f3b-97c4-19bb2dae2933&NotificationTypes=upc_free_games_updated,wallet-balance-update.
[ 2872] 2021-03-20 17:38:36     [ 848]     ERROR     WSConnection.cpp (483)                          Received Http status code 403 for url wss://public-ws-ubiservices.ubi.com/v2/websocket?SpaceIds=e17be87d-2996-4f3b-97c4-19bb2dae2933&NotificationTypes=upc_free_games_updated,wallet-balance-update.

Unsuccesful launch, where the first lines are identical, but then the first error line is different:
[ 2872] 2021-03-20 17:52:06     [ 848]     INFO      GameStartPipe.cpp (81)                          Accepted connection.           
[ 2872] 2021-03-20 17:52:06     [ 848]     INFO      GameStartPipe.cpp (82)                          Starting game session.         
[ 2872] 2021-03-20 17:52:06     [ 848]     ERROR     PlayCheckEdisonGamePatch.cpp (71)               Manifest not set for game with product ID 13504.
[ 2872] 2021-03-20 17:52:08     [ 848]     INFO      ApiProcessConnection.cpp (121)                  Game with process id 1740 connected.
[ 2872] 2021-03-20 17:52:08     [ 848]     INFO      ApiProcessConnection.cpp (132)                  Game with process id 1740 has been started with product id 13504 (branch: '').
[ 2872] 2021-03-20 17:52:09     [ 848]     INFO      UplayGameConnectionHandler.cpp (364)            Game with process id 1740 connected (API version: 2.3.0).
[ 2872] 2021-03-20 17:52:09     [ 848]     INFO      UplayGameConnectionHandler.cpp (364)            Game with process id 1740 connected (API version: 2.3.0).
[ 2872] 2021-03-20 17:52:09     [ 848]     INFO      UplayGameConnectionHandler.cpp (364)            Game with process id 1740 connected (API version: 2.3.0).
[ 2872] 2021-03-20 17:52:09     [ 848]     INFO      UplayGameConnectionHandler.cpp (364)            Game with process id 1740 connected (API version: 2.3.0).
[ 2872] 2021-03-20 17:52:11     [ 848]     ERROR     CrashReporter.cpp (219)                         Failed to delete a crash report: C:\Users\"User"\AppData\Local\Temp\Ubisoft\Exception_2021_03_20_17h52m10s.breport.
[ 2872] 2021-03-20 17:52:12     [ 848]     INFO      ApiProcessConnection.cpp (289)                  Game with process id 1740 disconnected.
[ 2872] 2021-03-20 17:52:12     [ 848]     INFO      UplayGameConnectionHandler.cpp (317)            Game with process id 1740 disconnected.
[ 2872] 2021-03-20 17:52:12     [ 848]     INFO      UplayGameConnectionHandler.cpp (317)            Game with process id 1740 disconnected.
[ 2872] 2021-03-20 17:52:12     [ 848]     INFO      UplayGameConnectionHandler.cpp (317)            Game with process id 1740 disconnected.
[ 2872] 2021-03-20 17:52:12     [ 848]     INFO      UplayGameConnectionHandler.cpp (317)            Game with process id 1740 disconnected.

This is driving me crazy, and you cannot post a support case at ubisoft itself, nor is anyone reacting on the chat for support...
Hopefully somebody here has some genious epifanie where the hell the problem would be situated.
Thanks!

@wookapotomas
I also opened a support case, and on there they are answering.
Firstly they completely ignored the statements that I made on what I had already done, concerning connection issues, reinstalling everything, etc... but now they seem to be digging deeper into it.
We are now at the point that I had to make an MSInfo report and a DXDiagnostics report.
I will update here if I have more info or a solution.

@ubi-mark
As mentioned by @Celestrike also, I feel more and more it is related to the fact that the game is trying to be launched by a controller or not.
If someone who plays with an XBox (or any other bluetooth) controller directly connected to a PC has the same issues, please reply!!

@wookapotomas Thanks!

Further:
Up until this moment no reply or solution has been issued.

I'll keep you guys updated on this case

@curranius I'm using a Nintendo Switch Pro controller, so it is not only to the steam controller. It is every interface with any bleutooth controller as far as I know.
If anyone can try with a Steamlink and and XBox controller then we can be sure it is for every bleutooth connected controller. I also want to know if you connect an XBox controller directly to a PC (with bleutooth) if it would generate the same issues, or that it is only when using a Steam Link

@tbr77 Thanks, will try this in the next days.

In the mean time:

@wookapotomas Thanks for the info!

Thing is that I never had to use GLOSC before as everything just worked with either my Switch Pro Controller or my PS4 Controller, and I would prefer to keep it that way.
The method described on reddit also gives issues that it appears to be without the Steam Link, as they start with mouse and keyboard and then turn on their controller, but for that to work for me I'd need to start up the steamlink, go to big picture mode and then connect to the game, which is not possible. The Steam Link will just stream the images, but will not let the controller take over the controls of the game in my case...

@wookapotomas @sherifdimples Thanks for the replies and clarification guys!

Further "update" (if you can call the same answer again an update):

@curranius I'm using a Nintendo Switch Pro controller, so it is not only to the steam controller. It is every interface with any bleutooth controller as far as I know.
If anyone can try with a Steamlink and and XBox controller then we can be sure it is for every bleutooth connected controller. I also want to know if you connect an XBox controller directly to a PC (with bleutooth) if it would generate the same issues, or that it is only when using a Steam Link

Small update from my side, no response from Ubisoft yet:

Further update:

@dalmomendonca92 This is really recognisable. Like said, I've found the same issues when starting the game in big picture with a keyboard and when then switching to the controller the game doesn't recognise it.
When starting big picture with the controller, I can try to launch the game but it immediatly fails when the loading screen with the green AC Valhalla logo is displayed.
The CPU usage is normally very high for several seconds (like 10s) when loading the game with Ubisoft Connect or with Steam (with AC Valhalla added as non-steam game to my library), but when launching in big picture with the controller the CPU usage drops to 0% after just 5s or so.

@ubi-mark
As mentioned by @Celestrike also, I feel more and more it is related to the fact that the game is trying to be launched by a controller or not.
If someone who plays with an XBox (or any other bluetooth) controller directly connected to a PC has the same issues, please reply!!

@wookapotomas Thanks!

Further:
Up until this moment no reply or solution has been issued.

I'll keep you guys updated on this case

Further update: