Proton
Proton copied to clipboard
ValveSoftware
Assassin's Creed Syndicate (368500)
Compatibility Report
- Name of the game with compatibility issues: Assassin's Creed Syndicate
- Steam AppID of the game:368500
System Information
- GPU: GTX 980
- Driver/LLVM version: nvidia 4.18.56
- Kernel version: 4.18.0-16
- Link to full system information report as Gist:
- Proton version: 4.2-1
I confirm:
- [x ] that I haven't found an existing compatibility report for this game.
- [x ] that I have checked whether there are updates for my system available.
Symptoms
Game installs, updates uplay. Uplay logs in and runs ok.
Game launches. Game loads main menu, then crashes.
Reproduction
Run game, each time the menu is loaded it takes 1 to 3 seconds before the game closes.
@howels look here: https://github.com/doitsujin/dxvk/wiki/Common-issues#nvapi
@RiantAnda I've tried all this a while back- disabling NVAPI with PROTON_USE_NVAPI=0 and
Launch options: DXVK_CONFIG_FILE=/home/user/dxvk-acsyndicate.conf %command%
/home/user/dxvk-acsyndicate.conf:
dxgi.customDeviceId = E366
dxgi.customVendorId = 1002
Tried this last evening and it doesn't run under Proton 4.2-3. What options is everyone else using?
Mine launches in a window, I get the "press a key" prompt, main menu loads and then it closes.
Tested on Proton 4.2-5. Still crashes out even with nvapi and nvapi64 disabled via winecfg.
Tested on Proton 4.2-9. Still crashing as soon as "press A to continue" is shown after loading.
Issue located - online services cause the game to crash. If the user disables network connection after Uplay has loaded and started the game, but before the main menu loads, then the game will run.
However, when combining FXAA + MSAA there are graphical errors, with strips of inverted colour across the image. I will investigate if a hosts file block is sufficient to fix this issue, as the game is not really a multiplayer game and online services seem irrelevant.
UPDATE: Works without crashing at main menu when "Always start Uplay in offline mode" is selected in uplay settings/network.
Tested with Proton 4.2-9. Works very well after setting Uplay to start in offline mode. One minor thing: when resolution is lower than screens native, game does not scale and appear only on portion of the screen.
This game was working very well in Linux Mint 19.3. When I upgraded to 20.1, the game now freezes when I try to open the menu. I can get into the game but hitting escape instantly causes the freeze. I don't know if my drivers are installed incorrectly or what. I noticed some errors in the log about dxva_video_decode_accelerator and a couple other errors about gpu processes failing to initialize, which is why I suspect my gpu drivers have something to do with it. I tried a fresh prefix as well, but no luck.
EDIT: False alarm, I rebooted after turning off vkbasalt and mangohud in goverlay, it works fine now.
System Info: system_info.txt Proton Log: steam-368500.log.zip
Proton experimentstol useing. Ubisoft old luncher. Can’t play assassin creed syndicate
Issue transferred from https://github.com/ValveSoftware/Proton/issues/6957. @Brandonstone200 posted on 2023-07-23T17:10:04:
Compatibility Report
- Name of the game with compatibility issues:
- Steam AppID of the game: assassin creed syndicate
<Blank details skipped>
Symptoms
U play out dated
Reproduction
Need Ubisoft connect
/
Is there. A way to update. Uplay. To the new luncher. On steam deck
Is there. A way to update. Uplay. To the new luncher. On steam deck
install protontricks via flatpak
flatpak run com.github.Matoking.protontricks 368500 ubisoftconnect
Something is screwed up with the latest versions of Proton and this game.
The game crashes after a random interval from loading the game. You can get further if you delete the introduction movies.
Deleting the introduction movies, and selecting Proton 8.0-5 gives you the ability to actually get into the game. It instantly appears stable by comparison.
The "Valve Steam Deck certification" claims Proton v9.0-4, this is not true.
Hello @syberphunk, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.
@kisak-valve On my PC this game also crashes with both Proton 9.0-4(steam-368500.log) & Experimental ; OOTB it crashes when playing the nvidia logo, after renaming the videos it crashes after a few seconds in the menu. After switching back to Proton 8.0-5 seems to run perfectly again.
System Information:
- GPU: AMD Radeon RX 6800 XT (radeonsi, navi21, LLVM 18.1.8, DRM 3.59, 6.12.5-arch1-1)
- GPU DRIVER: 4.6 Mesa 24.3.1-arch1.3
- KERNEL: 6.12.5-arch1-1
PS: Other Assassin's Creed(Unity/Black Flag) run perfectly with 9.0-4. Also i noticed that UBI-Connect needs to be killed manually after the exiting the games, but that is probably intentional by ubisoft.
@cintoros Just to verify, could you change the game's launch parameter to this and see if it works? PROTON_DISABLE_NVAPI=1 %command%
Hello @syberphunk, please add
PROTON_LOG=1 %command%to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam->Help->Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.
Hi @kisak-valve , I appreciate the ongoing effort from the Proton team to make gaming on Linux such a great experience. However, I’d like to share my perspective on this issue.
As a consumer who has purchased both the game and the Steam Deck, I feel that debugging and providing logs for issues—while understandable in an open-source context—can sometimes feel like I'm doing work that might be more suited to Valve’s QA team. I understand that logs are helpful, but I’d expect that Valve’s resources could be directed toward reproducing and diagnosing such issues internally, especially for widely used setups like Proton on the Steam Deck.
That said, I also recognize the importance of community involvement in improving Proton. If there are no internal ways to replicate this issue on your end, please let me know, and I’ll consider gathering the logs as requested.
Thank you for understanding my perspective.
@syberphunk Does adding the launch option PROTON_DISABLE_NVAPI=1 %command% fix the issue you have reported? I am currently in the process of adding that to the default Proton script for future releases :)
Thank you for the respectful way of stating your perspective. This tracker is not solely used by Steam Deck owners - it is not obvious from your original post that you are using Steam Deck. Adding that piece of information would have mostly negated the request for the Steam Runtime Diagnostics output which we use to determine the hardware/software being used. There can be material differences in behavior between deck models, so specifying if you are using an OLED or LCD deck is also requested if you comment on other issues in the future.
You do not need to immediately respond with logs if that is too much trouble for you. Issues are not blanketly ignored until logs are provided. Obviously, logs can be useful for triaging issues more quickly.
@simifor I can confirm that PROTON_DISABLE_NVAPI=1 %command% works (tested with Proton 9.0-4)
My game looks like this:
My launching options:
PROTON_DISABLE_NVAPI=1 LD_PRELOAD="" DXVK_FRAME_RATE=144 PULSE_LATENCY_MSEC=60 mangohud gamemoderun %command% with Proton Experimental.
Game settings are all on Ultra high, at 2k resolution.
Anything I can do?
// edit It was the anti-aliasing. Any setting other than "Off" or "FXAA" resulted in the above.
