search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.67k stars 1.07k forks source link

STAR WARS: The Old Republic (1286830) #4326

Open okegima opened 4 years ago

okegima commented 4 years ago

Compatibility Report

System Information

https://gist.github.com/okegima/6c5ff507e68d0701147d3c306afcea6c#file-gistfile1-txt

I confirm:

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.

droidoz commented 4 years ago

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.

ptkato commented 3 years ago

I'm encountering a weird behaviour on the game part, some things straight out don't appear, for example the characters' portraits:

image

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.

kisak-valve commented 3 years ago

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.

ptkato commented 3 years ago

Here you go.

TheDromundKaas commented 3 years ago

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.

My system information

SveSop commented 3 years ago

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)

kisak-valve commented 3 years ago

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.

ptkato commented 3 years ago

@SveSop, in the options, try disabling nameplate scaling. For some reason nameplate scaling destroys my FPS when moving the camera around.

SveSop commented 3 years ago

@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 :)

ptkato commented 3 years ago

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.

SveSop commented 3 years ago

@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 :)

SveSop commented 3 years ago

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

ChaosBlades commented 3 years ago

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.

ChaosBlades commented 3 years ago

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.

ChaosBlades commented 3 years ago

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.

Screenshot from 2021-10-03 19-17-03

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.

kisak-valve commented 2 years ago

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

System Information

I confirm:

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: experemental 5136 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

kisak-valve commented 2 years ago

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.

vasiliyaltunin commented 2 years ago

Yes! Thank you this is solved problem! On experementall all works just fine!

juliovco commented 2 years ago

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

kisak-valve commented 2 years ago

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.

ChaosBlades commented 2 years ago

Launcher works for me on 6.3 and Experimental Bleeding Edge. Checked just now.

juliovco commented 2 years ago

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?

kisak-valve commented 2 years ago

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?

juliovco commented 2 years ago

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

juliovco commented 2 years ago

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.

ProjectSynchro commented 2 years ago

System Information

Symptoms

Publisher video only plays on first run of game in fresh prefix.

Reproduction

  1. Ensure there are no prior prefixes, and launch the game
  2. Observe Bioware video
  3. 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

ProjectSynchro commented 2 years ago

System Information

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

  1. Launch the game
  2. Select 'Play Cinematic' on the main menu, select 'Disorder'
  3. Observe no video playback

See below log: steam-1286830-play-new-cinematic.log

ProjectSynchro commented 2 years ago

System Information

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

  1. Launch the game
  2. Start a new Sith Character, observe broken shadows outside the Sith Academy Example: Screenshot_20220303_212600

Changing various graphics settings appears to fix certain areas, but breaks others.

What it looks like in Proton 7.0-1: image

See below log: steam-1286830-experimental.log

This appears to be a DXVK issue (I'm assuming) should an issue be opened upstream?

Culted commented 2 years ago

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

swtor.log

Blisto91 commented 2 years ago

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

ProjectSynchro commented 2 years ago

@ProjectSynchro What are your graphical settings for reproducing the issue in your screenshot? I will do some quick testing here later.

It's been a while since I last logged in and I have gotten new hardware since then.. However I was able to get that regardless of the settings I was using (at the time). I don't have NVIDIA hardware anymore so I can't get a 1:1 reproduction of the issue.

EDIT: I have relogged into the game and travelled to some areas that I used to see the issues with shadows, I cannot see any issues anymore (with Proton Experimental). This could be related to my changing to AMD hardware, or due to updates to dxvk.

Blisto91 commented 2 years ago

@ProjectSynchro Roger. I have access to both a AMD and Nvidia setup. AMD is my main so if you know of anything specific with that just say so. A PR just got opened at the dxvk repo with a configuration option that fixes some stuff in this game, so I'm interested if that also helps here or if something else is required for this.

elinmyr commented 2 years ago

EDIT: I have relogged into the game and travelled to some areas that I used to see the issues with shadows, I cannot see any issues anymore (with Proton Experimental). This could be related to my changing to AMD hardware, or due to updates to dxvk.

I had this issue awhile back, too. Windows 8.1, NVIDIA gpu. I was also using ReShade at the time. DXVK 1.10.1 resolved the issue for me. I just tested this a few minutes ago, because I've also done some software/driver updates since then.

DXVK 1.10 dxvk before

DXVK 1.10.1 dxvk after

Blisto91 commented 2 years ago

@ProjectSynchro @elinmyr 👍 Thanks for testing.

kisak-valve commented 2 years ago

Star Wars - The Old Republic Game Launcher stopped working

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6360. @schwigi posted on 2022-12-03T09:28:58:

Symptoms

With the latest release of Proton Experimental (2022-12-01) the Game Launcher does not show up on screen. The process is running though and not crashing.

Reproduce

Run the game with Proton Experimental (2022-12-01) on the Steam Deck. This happens on my Desktop PC as well.

Used Hardware

1) Steam Deck, running Steam Beta channel 2) AMD Ryzen 3600, RX 580 running a Manjaro Linux

steam-1286830.log

Additional Note

The reasons for running Proton Experimental at all, are graphic error on the Steam Deck when using Proton 7.0-4 or Proton Next 7.0-5 during the cut scenes.

alasky17 commented 1 year ago

@schwigi Thank you for reporting this! We looked into this one and turns out it was an incorrect early version of a patch in experimental. The upstream version in Wine should not have the same issue, and is already pushed to the bleeding-edge branch. This will be fixed in the next official experimental update as well.

schwigi commented 1 year ago

Just checked on my end as well and the launcher is starting again with Proton Experimental on my Desktop. Also tested it on the Steam Deck (updated to Preview channel) and the launcher does not show yet.

Thanks for you work.

Edit: Tested again and it is working again on Steam Deck as well.

Newbytee commented 1 year ago

The launcher no longer starts up with Proton Experimental for me as of today. I was able to play it two days ago (18 jan 2023). Reverting to Proton 7.0-5 works around the issue and both the launcher and the game start up fine.

Blisto91 commented 1 year ago

@Newbytee Hello and thanks for the report. I can reproduce the issue and will try to bisect it.

Blisto91 commented 1 year ago

@Newbytee The Proton devs have fixed the regression and it should work now on bleeding edge. Will probably get pulled into next regular experimental update.

ahjolinna commented 1 year ago

swtor still wont launch for me (7.0-6, experimental-bleeding or GE-Proton7-49)

here is the log steam-1286830.log

my system spec:


             .;ldkO0000Okdl;.                
         .;d00xl:^''''''^:ok00d;.            OS: openSUSE MicroOS
       .d00l'                'o00d.          Kernel: x86_64 Linux 6.1.12-1-default
     .d0K^'  Okxoc;:,.          ^O0d.        Uptime: 3h 21m
    .OVVAK0kOKKKKKKKKKKOxo:,      lKO.       Packages: Unknown
   ,0VVAKKKKKKKKKKKKK0P^,,,^dx:    ;00,      Shell: bash 5.2.15
  .OVVAKKKKKKKKKKKKKk'.oOPPb.'0k.   cKO.     Resolution: 3072x1728
  :KVAKKKKKKKKKKKKKK: kKx..dd lKd   'OK:     DE: KDE 5.103.0 / Plasma 5.27.0
  lKlKKKKKKKKKOx0KKKd ^0KKKO' kKKc   lKl     WM: KWin_wayland
  lKlKKKKKKKKKK;.;oOKx,..^..;kKKK0.  lKl     GTK Theme: Breeze [GTK2],  [GTK3]
  :KAlKKKKKKKKK0o;...^cdxxOK0O/^^'  .0K:     Icon Theme: Papirus-Dark
   kKAVKKKKKKKKKKKK0x;,,......,;od  lKP      Disk: 16T / 21T (75%)
   '0KAVKKKKKKKKKKKKKKKKKK00KKOo^  c00'      CPU: AMD Ryzen 7 5700G with Radeon Graphics @ 16x 4.3GHz
    'kKAVOxddxkOO00000Okxoc;''   .dKV'       GPU: NVIDIA GeForce RTX 3060 Ti
      l0Ko.                    .c00l'        RAM: 5594MiB / 15779MiB
       'l0Kk:.              .;xK0l'         
          'lkK0xc;:,,,,:;odO0kl'            
              '^:ldxkkkkxdl:^'
Blisto91 commented 1 year ago

@ahjolinna have you tried deleting the prefix and then verifying the game again afterwards? Looking at your log paths i believe it should be located at ~/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/compatdata/1286830

ahjolinna commented 1 year ago

@ahjolinna have you tried deleting the prefix and then verifying the game again afterwards? Looking at your log paths i believe it should be located at ~/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/compatdata/1286830

yeah I did, and I also tried it again ....did not help and I had the same error at the end of the log again

ahjolinna commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/4326#issuecomment-1439510055

okay I found the solution for my MicroOS issue or more exact SELinux issue

apparently I need to run this command: sudo setsebool selinuxuser_execmod 1 to get the game run and other (mmo) games that had the same issue

more about it here: https://en.opensuse.org/Portal:MicroOS/Desktop#Steam_Proton,_Bottles,_WINE,_Lutris,_Android_Studio_emulator_not_working_from_flatpaks

marcelomendes commented 1 year ago

Star Wars - The Old Republic Rendering issues with Proton 8

Symptoms

With the latest release of Proton 8-x the game presents some rendering/lighting issues.

Reproduce

Run the game with Proton 8-x (7-x works just fine) Tested on a fresh prefix with the same results.

Used Hardware

Operating System Version: Debian GNU/Linux 12 (bookworm) (64 bit) Kernel Name: Linux Kernel Version: 6.1.0-8-amd64 X Server Vendor: The X.Org Foundation X Server Release: 12101007 X Window Manager: GNOME Shell Steam Runtime Version: steam-runtime_0.20230118.0

Video Card: Driver: NVIDIA Corporation NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 Driver Version: 4.6.0 NVIDIA 525.105.17 OpenGL Version: 4.6

Workaround:

Fallback to Proton 7-x

Using Proton 8-x

Screenshot from 2023-05-04 17-15-35

Using Proton 7-x

Screenshot from 2023-05-04 17-27-57

Log generated with PROTON_LOG

steam-1286830.log.gz

kisak-valve commented 1 year ago

Hello @marcelomendes, 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.)

marcelomendes commented 1 year ago

@kisak-valve Added the compressed log as requested.

Blisto91 commented 1 year ago

@marcelomendes Hi there and thank you for the report.

This is a Nvidia driver bug that got unveiled in a dxvk commit included in Proton 8. It has already been fixed in the beta drivers but have yet to arrive in the stable ones. A way to work around it besides playing with Proton 7 is to set the ingame AA to below high if i remember corectly. High and Very High include MSAA which triggers the issue.

marcelomendes commented 1 year ago

Setting AA to Medium solved it for now. Thank you @kisak-valve for the quick response!

schwigi commented 1 year ago

With the latest proton experimental build (2023-07-19) the camera jumps around crazy after the the right click. Camera movement without releasing the RMB is.

This happens on only my desktop (Manjaro Linux) running plasma-wayland.

It is working fine on the steam deck and on my desktop when using X11. So there might be some issue how the newer wine handles wayland input.