ValveSoftware
STAR WARS: The Old Republic (1286830)
Compatibility Report
- Name of the game with compatibility issues: Star Wars The Old Republic (SWTOR)
- Steam AppID of the game: 1286830
System Information
- GPU: RX550
- Driver/LLVM version:
- Kernel version:
- Link to full system information report as Gist:
https://gist.github.com/okegima/6c5ff507e68d0701147d3c306afcea6c#file-gistfile1-txt
- Proton version:5.13-1
I confirm:
- [*] that I haven't found an existing compatibility report for this game.
- [ ] that I have checked whether there are updates for my system available.
Symptoms
Can't use ctrl c for copy and ctrl v to past in game chat or mail. ctrl a not working too. Not able to copy a word and past inside game and from outside (text editor) to inside game. It work's well on outside game (runing ubuntu 20.04.1 LTS
No issue when launching game one win 7.
Reproduction
Yes, did change keyboard, but nothing happen.
I have the same problem with cut and paste in swtor chat. Using Proton 5.0-9 or 5.13-1 on Steam .Didn't have the problem using Lutris.
I'm encountering a weird behaviour on the game part, some things straight out don't appear, for example the characters' portraits:
What is weird is that sometimes rarely, they do appear. This ain't exclusive to the portraits only, other times, though less often, the character models themselves don't appear, my companion goes invisible, and even scenery vanishing in a few cutscenes, just to appear again in the next one. I didn't have that jankiness when I installed the standalone client through Lutris.
Hello @ptkato, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.
For a few days now, I have the problem of the FPS of SWTOR often times dropping to single digits. It happens much more when moving. I've seen it on planets (wide open areas) as well as my personal starship (tiny closed off area). When using a full DXVK_HUD, I can see that the running equalizer goes into the red at that point. It almost looks like loading, but the assets of SWTOR are basically tiny and low resolution. I've also checked if it is shader compilation, but it doesn't seem to be, at least there's no message bottom left about compiling shaders when it happens.
As I am on a rolling release distribution, I could not specifically state if it started with any version of the proprietary NVidia driver, as it gets updated frequently. I was watching the issue to see if anybody else had the problem, but maybe the Linux population of that game is low.
A month ago I did not have that problem, everything in the game was silky smooth 200+ FPS.
Updated proton to proton-6.3-5 today, and i have severe stutters when turning around. This is due to dxvk being updated to 1.9 with proton-6.3-5.
Downgrading dxvk (replacing the d3d dlls in ~/.steam/steam/steamapps/common/Proton 6.3/dist/lib64/wine/dxvk and the 32-bit folder) with dxvk compiled from https://github.com/ValveSoftware/dxvk/tree/f8a4ca555a6e5d89f5162a042bbae550902f4e49 - dxvk-1.8.1 fixes the problem.
I did bisect this around april, but have since forgotten the commit ID. (But have an approximate if interested)
Hello @SveSop, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.
It might be worthwhile to also mention the regression to upstream DXVK with what bisect info you have left.
@SveSop, in the options, try disabling nameplate scaling. For some reason nameplate scaling destroys my FPS when moving the camera around.
@ptkato
@SveSop, in the options, try disabling nameplate scaling. For some reason nameplate scaling destroys my FPS when moving the camera around.
Interesting! That did indeed help a lot with DXVK-1.9. I guess this "scaling function" is what bugs out then, cos i did not really have any issues with fps < DXVK-1.9. Thanks :)
I might be mistaken, but I think it has to do with the shader cache, every time something new appears, the thingy needs to compile the shaders, when the name renders, the game stutters, but then when you turn the camera, the name changes its size, then it needs to compile the shaders again, thus stuttering once more. I used to have a similar problem in Path of Exile, when dynamic resolution was enabled.
@ptkato No problem seeing that being the case... Its just that this is not such an issue with DXVK-1.8.1, so atleast something did change there when it comes to this dynamic thing. Working with upstream DXVK atm, so will see if they can figure something out :)
@kisak-valve This has now been closed upstream by: https://github.com/doitsujin/dxvk/pull/2126
And in the meantime, it is a viable fix to disable Scale Nameplates with Distance in the settings, as this seems to help a lot.
I have noticed that anything newer than 6.3-6 the game will crash to desktop after playing for several hours. This includes Proton Experimental and Proton 6.16-GE-1. I can happily play for hours on end using 6.3-6.
I got an update to Mesa 21.2.1 two days ago and since then I have had no crashes on Proton 6.16-GE-1. It appears the issue was a driver issue for my 6900xt. I have not tried Proton Experimental.
I did test Proton Experimental shortly after my last post and it was working flawlessly but now it looks like things have broken again. I am now getting the following error message on Proton Experimental and Proton-6.18-GE-2 immediately after the recent updates. All other games I have tried are still working.
I continue to have a stable experience on Proton 6.3-7 playing SWTOR.
Edit: ...and as soon as I report the issue it is resolved. This was a XanMod Kernel bug. I just got an update to 5.14.9-xanmod2. It seems kernel 5.14 was released the same day I updated to 6.18 GE and a Proton Experimental update released. It is odd that this kernel bug affected SWTOR specifically on Experimental and GE specifically.
Here were the changes in this kernel update for thoroughness.
- 1d25d6095fa0 Linux 5.14.9-xanmod2
- f164cc43ea1a zstd: fix fall-through warnings
- 90383d79db7c futex2: Add sysfs entry for syscall numbers
- 442d05a80b7e kernel: Enable waitpid() for futex2
- e5a1578d65ce docs: locking: futex2: Add documentation
- fa85b67049cc futex2: Add compatibility entry point for x86_x32 ABI
- 5f5c48319897 futex2: Implement requeue operation
- 9970c3df4edb futex2: Implement vectorized wait
- 1ee81ce10706 futex2: Add support for shared futexes
- ea14247af977 futex2: Implement wait and wake functions
- 6afbd4f8cd3c futex: Implement mechanism to wait on any of several futexes
- 12aea22c5b44 futex*: remove FUTEX_WAIT_MULTIPLE operation and futex2 patchset
STAR WARS: The Old Republic (1286830)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/5392. @vasiliyaltunin posted on 2021-12-08T21:06:41:
Compatibility Report
- Name of the game with compatibility issues: Star Wars The Old Republic (SWTOR)
- Steam AppID of the game: 1286830
System Information
- GPU: GTX 1050 Ti
- Driver/LLVM version: 470.57.02
- Kernel version: 5.10
- Link to full system information report as Gist: https://gist.github.com/vasiliyaltunin/c631b87ea1108ab89f62c04d1fe90e7b
- Proton version: Experemental, 6.3-8
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
Colors depth seems to low, in Experemental and 6.3-8 in 5.13-6 all looks just fine
Reproduction
here i make screenshot to show color problems:
steam-1286830.log
As you can see in experimental colors looks like in old pc games you can clearly see it in places in shadows in torso
Hello @vasiliyaltunin, your log hints that you're using PROTON_USE_WINED3D=1 in the game's launch options. Can you double check if this is the case and remove it? This runtime option is not supported and could be directly related to the issue you're seeing.
Yes! Thank you this is solved problem! On experementall all works just fine!
My system information Proton version: 6.3 My launcher has a warning at the top "An error has ocurred. Please exit and restart the SWTOR Laucher." If I try to login, it hangs forever. launcher log has "ERROR Steam DLL failed to load" It used to work before. Played with no issues around the beginning of December. launcher_20220106.log steam-1286830.log
Hello @juliovco, these look like the lines of interest from your log:
err:module:import_dll Library api-ms-win-crt-runtime-l1-1-0.dll (which is needed by L"C:\\windows\\system32\\VCRUNTIME140.dll") not found
err:module:import_dll Library api-ms-win-crt-heap-l1-1-0.dll (which is needed by L"C:\\windows\\system32\\VCRUNTIME140.dll") not found
err:module:import_dll Library api-ms-win-crt-string-l1-1-0.dll (which is needed by L"C:\\windows\\system32\\VCRUNTIME140.dll") not found
err:module:import_dll Library api-ms-win-crt-stdio-l1-1-0.dll (which is needed by L"C:\\windows\\system32\\VCRUNTIME140.dll") not found
err:module:import_dll Library api-ms-win-crt-convert-l1-1-0.dll (which is needed by L"C:\\windows\\system32\\VCRUNTIME140.dll") not found
err:module:import_dll Library VCRUNTIME140.dll (which is needed by L"Z:\\home\\fnord\\.steam\\steamapps\\common\\Star Wars - The Old Republic\\steam.dll") not found
err:module:import_dll Library api-ms-win-crt-stdio-l1-1-0.dll (which is needed by L"Z:\\home\\fnord\\.steam\\steamapps\\common\\Star Wars - The Old Republic\\steam.dll") not found
err:module:import_dll Library api-ms-win-crt-string-l1-1-0.dll (which is needed by L"Z:\\home\\fnord\\.steam\\steamapps\\common\\Star Wars - The Old Republic\\steam.dll") not found
err:module:import_dll Library api-ms-win-crt-heap-l1-1-0.dll (which is needed by L"Z:\\home\\fnord\\.steam\\steamapps\\common\\Star Wars - The Old Republic\\steam.dll") not found
err:module:import_dll Library api-ms-win-crt-convert-l1-1-0.dll (which is needed by L"Z:\\home\\fnord\\.steam\\steamapps\\common\\Star Wars - The Old Republic\\steam.dll") not found
err:module:import_dll Library api-ms-win-crt-runtime-l1-1-0.dll (which is needed by L"Z:\\home\\fnord\\.steam\\steamapps\\common\\Star Wars - The Old Republic\\steam.dll") not found
err:module:import_dll Library api-ms-win-crt-environment-l1-1-0.dll (which is needed by L"Z:\\home\\fnord\\.steam\\steamapps\\common\\Star Wars - The Old Republic\\steam.dll") not found
I read this as either Proton 6.3 on your system or the game's wineprefix is damaged or incomplete. I would first try to verify the integrity of Proton's files in Steam, and if that doesn't help, then move the game's wineprefix (/home/fnord/.steam/steamapps/compatdata/1286830) somewhere out of the way. It should be noted that removing the wineprefix might cause saves and settings to be lost, which is why I suggested moving instead of deleting the folder.
Launcher works for me on 6.3 and Experimental Bleeding Edge. Checked just now.
Thank you both for the responses. I had already tried to verify integrity of both Swtor and Proton 6.3, but nothing changed. Also had tried uninstalling Swtor and installing again (I made a backup of the settings), nothing changed as well. Now I tried playing another game (Aragami) which I also installed with Proton 6.3, and it played normally. But maybe this one doesn't use those ms-win-crt stuff, I don't know. And now I tried changing Swtor to Proton 5.13 and it worked - so I'm happy, I can live with that. But then it seems there is something wrong with my Proton 6.3 installation. I tried uninstalling it through steam, but it failed with unexpected error. Is it because I have other games installed with this version? Do I have to change the proton version of those games to be able to uninstall it?
As you expected, Proton is treated as a game dependency by Steam when games are configured to use it. (https://github.com/ValveSoftware/steam-for-linux/issues/7407)
Maybe give https://github.com/ValveSoftware/Proton/issues/4269#issuecomment-794164206 a try?
I tried the solution from the other thread you linked (removing the dist folder of 6.3), then changed Swtor back to 6.3 to try again. Then the launcher worked, but when I logged in, the game became a black screen. I verified integrity of both Swtor and 6.3 files but nothing changed. So I changed the games that were using 6.3, and also my Steam Play default setting (it was set to 6.3 as well), and managed to uninstall 6.3. Started the game again to reinstall 6.3. This time the launcher didn't open anymore (tried multiple times). So I tried uninstalling both 6.3 and Swtor, deleted what remained of the 6.3 folder, and reinstalled Swtor (and 6.3 automatically). Same result, the launcher doesn't open. I click Play, nothing happens and after a long time the button turns green again. steam-1286830.log
It's working. I uninstalled Proton 6.3, deleted the folder, installed it again clicking on the Install button, changed Swtor back to 6.3 and clicked play. I don't know what difference it would make, or if it's just random, but now it's working.
System Information
- GPU: RTX 2070
- Driver/LLVM version: 510.47.03
- Kernel version: 5.16.9
- Link to full system information report as Gist: https://gist.github.com/ProjectSynchro/f0d4e4f102ca29c71a683ea49dd4df7e
- Proton version: 7.0-1
Symptoms
Publisher video only plays on first run of game in fresh prefix.
Reproduction
- Ensure there are no prior prefixes, and launch the game
- Observe Bioware video
- Relaunch game, observe no intro video
See below log for first run of game: steam-1286830-first-run.log
Log from second run of game in same prefix: steam-1286830-no-bioware-video.log
System Information
- GPU: RTX 2070
- Driver/LLVM version: 510.47.03
- Kernel version: 5.16.9
- Link to full system information report as Gist: https://gist.github.com/ProjectSynchro/f0d4e4f102ca29c71a683ea49dd4df7e
- Proton version: 7.0-1
Symptoms
New cinematic 'Disorder' does not play in game. This occurs during gameplay when the mission to begin the expansion is triggered for the first time, and in the main menu
Reproduction
- Launch the game
- Select 'Play Cinematic' on the main menu, select 'Disorder'
- Observe no video playback
See below log: steam-1286830-play-new-cinematic.log
System Information
- GPU: RTX 2070
- Driver/LLVM version: 510.54
- Kernel version: 5.16.11
- Link to full system information report as Gist: https://gist.github.com/ProjectSynchro/f0d4e4f102ca29c71a683ea49dd4df7e
- Proton version: Proton Experimental (experimental-7.0-20220228)
Symptoms
Shadows appear to be corrupted in various places, this behaviour is not seen in Proton 7.0-1 so I see this as a regression.
Reproduction
- Launch the game
- Start a new Sith Character, observe broken shadows outside the Sith Academy
Example:
Changing various graphics settings appears to fix certain areas, but breaks others.
What it looks like in Proton 7.0-1:
See below log: steam-1286830-experimental.log
This appears to be a DXVK issue (I'm assuming) should an issue be opened upstream?
i am getting some very rare crashes with Proton 7.0-1 and Experimental (also with Proton-GE), the log file is very large because these crashes can happen at various times and this time i captured it after about one or two hours so i uploaded the full log to my dropbox account https://www.dropbox.com/s/snlsbemykiqbpp8/steam-1286830.log?dl=0 and i attached a log file with only the first 100 lines and last 100 lines
@ProjectSynchro What are your graphical settings for reproducing the issue in your screenshot? I will do some quick testing here later.
@Culted It's possible it could be memory related crashes since this appears to be a 32bit game? There's a PR open in the dxvk repo that could possibly help. I will try to do a quick test if it appears to do anything for this game.
