Continue your odyssey

Welcome to discussion

Welcome to discussion

Quick Suggestions

Hello! These new forums are an open beta and we welcome your feedback in this section.
  • Asyncroon
    Original poster 17 posts

    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!

  • Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old. Richard McClintock, a Latin professor at Hampden-Sydney College in Virginia, looked up one of the more obscure Latin words, consectetur, from a Lorem Ipsum passage, and going through the cites of the word in classical literature, discovered the undoubtable source. Lorem Ipsum comes from sections 1.10.32 and 1.10.33 of "de Finibus Bonorum et Malorum" (The Extremes of Good and Evil) by Cicero, written in 45 BC. This book is a treatise on the theory of ethics, very popular during the Renaissance. The first line of Lorem Ipsum, "Lorem ipsum dolor sit amet..", comes from a line in section 1.10.32.

    Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old. Richard McClintock, a Latin professor at Hampden-Sydney College in Virginia, looked up one of the more obscure Latin words, consectetur, from a Lorem Ipsum passage, and going through the cites of the word in classical literature, discovered the undoubtable source. Lorem Ipsum comes from sections 1.10.32 and 1.10.33 of "de Finibus Bonorum et Malorum" (The Extremes of Good and Evil) by Cicero, written in 45 BC. This book is a treatise on the theory of ethics, very popular during the Renaissance. The first line of Lorem Ipsum, "Lorem ipsum dolor sit amet..", comes from a line in section 1.10.32.

    Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old. Richard McClintock, a Latin professor at Hampden-Sydney College in Virginia, looked up one of the more obscure Latin words, consectetur, from a Lorem Ipsum passage, and going through the cites of the word in classical literature, discovered the undoubtable source. Lorem Ipsum comes from sections 1.10.32 and 1.10.33 of "de Finibus Bonorum et Malorum" (The Extremes of Good and Evil) by Cicero, written in 45 BC. This book is a treatise on the theory of ethics, very popular during the Renaissance. The first line of Lorem Ipsum, "Lorem ipsum dolor sit amet..", comes from a line in section 1.10.32.

  • wOOKaPotomas
    5 posts

    @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.

  • Asyncroon
    Original poster 17 posts

    @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.

  • Blauhung
    1 posts

    I have the same issue and am interested in any progress

  • Asyncroon
    Original poster 17 posts
    This post is deleted!
  • Celestrike
    1 posts

    Same issue for me. I can launch the game from my pc in the same cases that you described but if I try to launch the game by using a controller the game will crash.

    Secondly, launching the game from the PC using a mouse and then booting up the steam link and connecting to the game does not work as the game will fail to recognize any input from the controller at that point. This was all introduced in v1.2.

  • Asyncroon
    Original poster 17 posts

    @celestrike I also tried that and that also failed with me. You can start in big picture mode on PC without issues (and play using mkb), but if you then switch to the steam link and want to use the controller the game will not recognise the controller or any input you generate on the steam link (forcing you to close the game using mkb). As said in my first post, it all worked fine when first trying, but after an update things all went to hell...

  • Asyncroon
    Original poster 17 posts
    This post is deleted!
  • wOOKaPotomas
    5 posts

    Doing god's work

  • Ubi-Mark.
    Ubisoft Support Staff 669 posts

    Hello @Asyncroon,

    Sorry to hear that your game keeps crashing while using Steam Link.

    I just double-checked your case and I can see that this issue has been reported to the game team and as soon as we have an update, we are going to let you know through your case.

    Apologies for any inconvenience caused by this and thank you for your patience while our team is investigating this issue. If you have any additional questions, please let us know.

    Official Response
  • ReisenHotpot
    1 posts
    This post is deleted!
  • Asyncroon
    Original poster 17 posts

    @wookapotomas Thanks!

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

    I'll keep you guys updated on this case

  • Asyncroon
    Original poster 17 posts

    @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!!

  • Ubi-Mark.
    Ubisoft Support Staff 669 posts

    Hello @Asyncroon,

    Thank you for your update! I'm not sure if it's related to the controller itself, but as soon as the team has an update on this, you will receive reply 🙂

    If it's controller related, our team will also investigate it further 🙂

    Official Response
  • dalmomendonca92
    2 posts

    @asyncroon I'm having the same issue.

    AC Valhalla works fine if I launch it from UPlay, but it doesn't recognize my PS5 or Xbox controller. This is an issue for me because I can't play the game very well using the mouse and keyboard (i.e., I'm not good at it).

    For the past several months, the one workaround I've found was to add the game to Steam as a non-Steam game. Then I entered big picture mode with the PS5 controller connected. Then I launched AC Valhalla from Steam and the game recognized the controller as an input. This is the way I've been playing for several months. But it broke with the March update.

    Now, when I follow the same steps, the game's logo appears in the center of the screen for a few seconds, and then it crashes.

    If I follow the same steps with the Xbox controller, I get the same results. I always send the crash report, but I'm imagining nobody actually looks at these.

    undefined

    Note that if I'm in big picture mode in steam, and then I disconnect the controller (PS5 or Xbox), I can launch the game from Steam just fine. But at that point the game doesn't recognize my controller, even if I plug it in after it's launched successfully.

    So I agree that there's something about having an external controller connected in big picture mode that causes the game to crash, and this was introduced with the v1.2 update. Until the game team/developers find a fix, is there a way to uninstall this latest update and just play the game on the previous version that used to work fine?

    I see that Ubisoft is aware of this issue and has not yet prioritized it highly enough to get it fixed. I imagine it's because they believe (perhaps rightly so) that there aren't many people in my situation: really invested in playing this game on the PC but in need of a controller instead of using the keyboard and mouse.

    On a personal note, this is particularly frustrating for me because I bought at $4k computer with the one and only purpose to play this game. Then I spent 177 hours on the game, and, in March, this broke and I can't finish it. So now I have an expensive machine collecting dust, and I feel disappointed that my experience doesn't seem important enough to merit a speedy fix (or workaround) to the bug introduced with the update.

    @Ubi-Mark Thank you for following up on this issue. In addition to what you've already done, what can you do today to find alignment between our needs and Ubisoft's commitment to honoring the gaming experience for users like us?

  • dalmomendonca92
    2 posts

    Here's the launcher log errors for when I try to launch the game through steam in big picture mode with each controller.

    launcher_log.txt                           

    NB: this post was "flagged as spam by Akismet.com" incorrectly. This is making it more difficult to post more info here to troubleshoot.

  • Asyncroon
    Original poster 17 posts

    @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.

  • Semajaral_II
    4 posts

    Please address this issue Ubisoft. This poster went through painstaking detail to outline the issue to you. This was working perfectly fine before the latest update. I am also experiencing this issue and have played the game fine for 20+ hours via steam link/controller prior to this update. I cannot even launch it now.

    My issue manifests exactly as the original poster describes. I've added AC Valhalla to my Steam account as a non-steam game. I launch via controller in Big Picture mode, otherwise using a controller (e.g. using mouse mode via steam link) and the game will not launch. Ubisoft launcher appears briefly, followed by AC Valhalla launcher, then disappears. If I run the game directly via Ubisoft or if I click on the.exe directly in the folder it will launch properly. However, the controller input will NOT be recognized.

  • Semajaral_II
    4 posts

    @asyncroon Thank you for this post. You did a great job summing up the issues and even included excellent logs for them. I'm following the thread now as well as I am seeing the issue exactly as you described, and this is AFTER having played w/ a controller via Stream Link for easily 20+hours. Checked a few other Ubisoft titles I had installed as well and NONE have this issue. Clearly something broke w/ most recent update. Thanks again.

  • Asyncroon
    Original poster 17 posts
    This post is deleted!

Suggested Topics

Community Details

17
Online
129.1k
Users
22.2k
Topics
115.1k
Posts