search

ValveSoftware / Proton

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

Star Trek Online (9900) #1198

Open josephcocoa opened 6 years ago

josephcocoa commented 6 years ago

The game seems to run perfectly outside of some crackling audio. The crackling seems to come and go, but is there most of the time. My systems specs are:

https://gist.github.com/binarycocoa/8136601c67e54d720f43bd9c51d540c0

setsunati commented 6 years ago

Try this https://www.youtube.com/watch?v=UQ-Ml78kiEE

josephcocoa commented 6 years ago

It looks like the instructions referenced in the video (found at https://ludwig.im/en/projects/steam-pulseaudio-sound-latency-lagging-problem-noise#optimize-pulseaudio-settings-for-steam-games) corrected it for me. Specifically, editing the number of fragments and the size in my pusleaudio config to be default-fragments = 5 default-fragment-size-msec = 2

seems to have eliminated most if not all of the crackle. I'm recommending making this config a default for my distribution (Solus). I believe this can be closed now, but I'll leave that for someone else, since I'm not sure about the procedures here around closing out issues.

ryanmusante commented 6 years ago

Low latency ALSA patch: https://blog.thepoon.fr/osuLinuxAudioLatency/

ananace commented 6 years ago

I can't even get the launcher to work, how are you managing to get in game? For me the launcher just freezes almost instantly after logging in to it, and then has to be sigkilled.

Log output;

Setting default pigset mode...
done (0x00000000)                                                       (0.00)

[0908/130359:ERROR:network_change_notifier_win.cc(143)] WSALookupServiceBegin failed with: 0
[0908/130405:INFO:CONSOLE(0)] "Select shard: 0," source: http://launcher.startrekonline.com/static/all/js/api.js(157)

 -affiliate appid=9900
 -launchedfrom steam
Connecting to patchserver.crypticstudios.com:7255
PatchClientLib: connecting to patchserver.crypticstudios.com:7255
PatchClientLib: redirecting to 208.95.184.31:7255
PatchClientLib: skipping unneeded autoupdate CrypticLauncher3ST
PatchClientLib: successfully connected
AutopatchDialog thread shutting down
GamePrefsInit: giGamePrefSet now 0
Displaying status message: Connecting to Account Server
While finding unique IPs, converted controllertracker.crypticstudios.com to 208.95.186.113
While finding unique IPs, converted controllertracker0.crypticstudios.com to 208.95.186.141
While finding unique IPs, converted controllertracker1.crypticstudios.com to 208.95.186.113
While finding unique IPs, converted controllertracker2.crypticstudios.com to 208.95.186.141
While finding unique IPs, converted controllertracker3.crypticstudios.com to 208.95.186.113
While finding unique IPs, converted controllertracker4.crypticstudios.com to 208.95.186.141
While finding unique IPs, converted controllertracker5.crypticstudios.com to 208.95.186.113
While finding unique IPs, converted controllertracker6.crypticstudios.com to 208.95.186.141
While finding unique IPs, converted controllertracker7.crypticstudios.com to 208.95.186.113
While finding unique IPs, converted controllertracker8.crypticstudios.com to 208.95.186.141
While finding unique IPs, converted controllertracker9.crypticstudios.com to 208.95.186.113
Displaying status message: Attempting to connect to controller tracker.
Displaying status message: Loading launcher
2018-09-08 14:04:05 PROGRAM ASSERT OCCURRED! pNode

Hardware info; https://gist.github.com/ananace/fec7a290582e7d7070af19b675ac074d

Edit: Found why the launcher kept breaking, Steam was generating a broken game install path in the registry. Apparently any print statement left in the user settings end up appended to the game path.

ensonic commented 5 years ago

For me the launcher works, it downloads the game content and when I press engage I get this error: image The graphics card is for sure not the fastest, but above the minimal requirements.

kisak-valve commented 5 years ago

Hello @ensonic, 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. Also, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

ensonic commented 5 years ago

@kisak-valve was just about to add those. Edited my post with the asked details.

kisak-valve commented 5 years ago

Can you verify you have the libvulkan_radeon and libvulkan_radeon-32bit packages installed?

ensonic commented 5 years ago 
$ rpm -qf /usr/lib64/libvulkan_radeon.so
libvulkan_radeon-18.3.2-211.1.x86_64

after installing the 32bit package it starts! Thanks for the super quick help!

ensonic commented 5 years ago

That was too quick. It now goes to the loading screen for a few minutes then shows a graphical screen with the title and in the log I get an endless sequence of:

27991.354:005f:008b:fixme:rawinput:GetRawInputBuffer data (nil), data_size 0x112ffe14, header_size 16 stub!
27991.354:005f:008b:fixme:rawinput:GetRawInputBuffer data 0x21a2730, data_size 0x112ffe10, header_size 16 stub!
27991.356:005f:008b:fixme:rawinput:GetRawInputBuffer data (nil), data_size 0x112ffe14, header_size 16 stub!
27991.356:005f:008b:fixme:rawinput:GetRawInputBuffer data 0x21a2730, data_size 0x112ffe10, header_size 16 stub!

If I search for this error, it looks like those should have been fixed in wine several years ago.

kisak-valve commented 3 years ago

Star Trek Online chat issue, Proton 5.0.9

Issue transferred from https://github.com/ValveSoftware/Proton/issues/4264. @fbenedett posted on 2020-10-15T15:30:41:

People... I am not sure if this is the right place to put this issue. Apologies if I am mistaken.

Compatibility Report

System Information

Distro:Ubuntu 18.04.5 LTS Kernel:5.4.0-48-generic RAM:32 GB GPU Driver:NVIDIA 450.66 GPU:NVIDIA GeForce 930MX CPU:Intel Core i5-8250U @ 1.60GHz

I confirm:

steam-9900.log

Symptoms

The game runs smoothly using also: SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS=0; %command% BUT the chat does not work anymore if a person switch to another character.

Reproduction

Log in Star Trek Online with a character. Press esc and use the Switch character option. It is impossible to write or read anything in the chat. The chat result to be completely empty all the time.

fbenedett commented 3 years ago

Hello. The game does not run on Proton 5.13-2. After the launcher, I get a black screen. I also tried to leave it there for an hour but there was no change. I put in the attachment the log. steam-9900.log

kisak-valve commented 2 years ago

Steam Proton and Star Trek Online

Issue transferred from https://github.com/ValveSoftware/Proton/issues/5525. @Zabrat01 posted on 2022-01-29T19:07:47:

Compatibility Report

System Information

I confirm:

Symptoms

This is my first entry for issues due to being new.

STO had a recent update as of the 25th Jan 2022. Since then, the screen to enter my credentials suddenly ends to desktop. I have tried various other Proton drivers (ones seen on ProtonDb and random via Steam) and the same screen drop occurs every time. Now I can launch the game with the .exe but control in-game is not as good as it is via Steam/Proton. I have been using Proton Experimental since October 2021 and I did try the other 2 to see any effect. The same issue occurs. I have updated Proton DB with my entry. Thank you.

Reproduction

kisak-valve commented 2 years ago

Hello @Zabrat01, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, 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.

Zabrat01 commented 2 years ago

Hey Kisak,

Here is the gist: https://gist.github.com/Zabrat01/7c927a23744be81fca1b33f90b308bdb

As for the Proton log, I assume you mean putting the PROTON_LOG=1 %command% in the "General" area of Properties? I did try that but cannot find the file. I am new to Zorin OS to be honest. Thank you.

Zabrat01 commented 2 years ago

I think I may have found it..

steam-9900.log

kisak-valve commented 2 years ago

Possible lines of interest from the log:

PW_SDK::Init
calling SHGetKnownFolderPath
PW Launcher installation not found
CC_ERR_CLIENT_NOT_LAUNCHED: installed: false, running: false
Failure of some kind
Zabrat01 commented 2 years ago

Interesting. Last year ARC had forced an "Account Linking" between Steam and ARC. Afterward, I would log into Steam but it would pull up a new character creation screen as if am a new player. I have over 1,200 hours on STO. I did ask them to fix it at first but they were not sure how to. If I selected back to the login area I could then log in. I was still on Windows at that time. So, a couple days ago I asked them to unlink my account between Steam and ARC. They did just last night and when I used Steam to launch, it asked me to Link again, I did but this time it went to my character screen directly. So it is fixed in this sense. I wonder if it had anything to do with that? So basically I can access it now via Steam/Proton using Experimental again. Thanks all.

kisak-valve commented 2 years ago

Star Trek Online banned Windows 7... - This also affects proton.

Issue transferred from https://github.com/ValveSoftware/Proton/issues/5581. @Kepsz posted on 2022-02-16T18:59:44:

Compatibility Report

Symptoms

STO dev's decided to ban Windows 7 pc's from it's gamer base. Sadly it affects proton too, the game thinks it is running on a Windows 7 pc and throws a notification message...

Reproduction

Just try to launch the game. It's free.

The game worked fine with proton so far.

kisak-valve commented 2 years ago

Hello @Kepsz, it should be noted that Proton uses a Windows 10 wineprefix since Proton 5.0-1, unless the game has been run with Proton 4.11 or older.

Kepsz commented 2 years ago

@kisak-valve Thanks for the quick reply!

I have to correct myself. At this moment, the game is not running on Proton 7.0-1, and ProtonGE 6.21-1 (just for reference), but it is running with Proton-Experimental!

aeikum commented 2 years ago

@Kepsz What does the failure look like for you?

For me (never played before), the launcher went through its patching process, and I am able to launch the game client. The servers are down for maintenance right at the moment, so I can't proceed further. But it appears to be working up to that point.

Kepsz commented 2 years ago

@aeikum I think they patched the launcher today, because it is now working fine with both Proton 7.0 and Proton-Experimental. Yesterady, there was an error message about the unsupported OS, and no launcher at all.

Btw, there are one thing that newer worked with proton so far, that's the "on-demand patching". We all have to deactivate that feature in the launcher. - other than this, the game worked fine.

aeikum commented 2 years ago

Ah great. Just to confirm, it's working as well for you now in 7.0 as it was before in 6.3 and/or Experimental?

Kepsz commented 2 years ago

Yes. I played for an hour now with 7.0, it worked exactly as Experimental! I have never played the game with 6.3, I've been using the Experiment for as long as it exists.

aeikum commented 2 years ago

Great! Thanks for reporting and retesting. The game's launcher using an "Engage" button to start the game made me laugh :)

nstephenh commented 1 year ago

Recent reports on protondb and my own experience indicate that the game works fine on Proton 7.x but does not render properly on 8.x, I got a black screen and the game music.

kisak-valve commented 1 year ago

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

Natherul commented 1 year ago

steam-12456498923395088384.tar.gz

Using GE-proton 8-3 just tabbing a few times (sometimes the first time) and when tabbing back in its just straight black. I can with GE at least play without tabbing.

System info: https://gist.github.com/Natherul/1e30299733e7821ae63acb3559cca46a

kisak-valve commented 1 year ago

Thanks, besides using a third party build of Proton, you've configured Proton to run with PROTON_USE_WINED3D=1. This runtime option is not considered supported and any graphics issues with that need to be reproduced with vanilla wine and reported to the upstream wine project.

Please retest without that runtime option.

Natherul commented 1 year ago

Thanks kisak. I dont remember why I added it but I assume at some point I had issues and protondb comments pointed to it. But removing WINED3D does seems to solve the issues for me.

fbenedett commented 1 year ago

debug.txt

Hello,

the game stopped working on my system. I tried proton experimental, 8.0, 7.0, but none of them worked. The game doesn't start at all, ass soon as I click on the steam button "play" it immediately terminate.

Kepsz commented 1 year ago

debug.txt

Hello,

the game stopped working on my system. I tried proton experimental, 8.0, 7.0, but none of them worked. The game doesn't start at all, ass soon as I click on the steam button "play" it immediately terminate.

Works fine on my PC (EndeavourOS KDE) with proton Exp.

You can try: -check the game files for errors in steam, it will resets the launcher files too -launch steam from terminal and check the output for errors / missing things

Kepsz commented 1 year ago

Well, something is not right with this game or proton. I have 2 PC's, same OS, same software, exactly same hw except for memory, but that should not matter at all.

PC1: STO works fine with Proton Experimental

PC2: STO launcher instantly crashed with Proton Exp and Proton 8. At this time, I did a steam reset, but it solved nothing. Then I tried to reinstall the game. The launcher did only worked with Proton 7, but the game was unable to load. One day later, I was able to launch and play the game with Proton 8, but not with Proton Exp. Meanwhile, STO works fine on PC1 with proton Exp.

PC Specs: EndeavourOS KDE, always updated, kernel 6.4.1 Ryzen 5800X Amd RX6700XT with mesa 23.1.3

On PC2, I tried to get logs from running Steam from terminal, but did not seen any relevant output.

kisak-valve commented 1 year ago

Hello @Kepsz, on "PC2", please add PROTON_LOG=1 %command% to the game's launch options 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.

Kepsz commented 1 year ago

Hello @Kepsz, on "PC2", please add PROTON_LOG=1 %command% to the game's launch options 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!

Runtime Diag: [fc3ed4e971c2d0d5cd63f66c8b6ce529](https://gist.github.com/Kepsz/fc3ed4e971c2d0d5cd63f66c8b6ce529) Prot exp. log: steam-9900.log

"701.452:014c:0150:err:module:import_dll Loading library kernelbase.dll (which is needed by L"C:\windows\system32\kernel32.dll") failed (error c000012f)."

Btw, there was a launcher update today, and since then, it is now broken with Proton 8.0 too. The launcher loads, but the window content is completely black. The log for that: steam-9900_proton8.log

kisak-valve commented 1 year ago

"701.452:014c:0150:err:module:import_dll Loading library kernelbase.dll (which is needed by L"C:\windows\system32\kernel32.dll") failed (error c000012f)."

This reads like the Proton Experimental install on your system is damaged or incomplete.

Btw, there was a launcher update today, and since then, it is now broken with Proton 8.0 too. The launcher loads, but the window content is completely black. The log for that: steam-9900_proton8.log

These look like some lines of interest from your log: ``` [0706/084114.497:ERROR:shared_context_state.cc(77)] Skia shader compilation error ------------------------ // Vertex SKSL uniform float4 sk_RTAdjust;in float2 position;in half4 color;out half4 vcolor_S0;void main() {// Primitive Processor QuadPerEdgeAAGeometryProcessor vcolor_S0 = color;sk_Position = position.xy01;} // Fragment SKSL in half4 vcolor_S0;void main() {// Stage 0, QuadPerEdgeAAGeometryProcessor half4 outputColor_S0;outputColor_S0 = vcolor_S0;const half4 outputCoverage_S0 = half4(1);{ // Xfer Processor: Porter Duff sk_FragColor = outputColor_S0 * outputCoverage_S0;}} // Vertex GLSL #version 100 precision mediump float; precision mediump sampler2D; uniform highp vec4 sk_RTAdjust; attribute highp vec2 position; attribute mediump vec4 color; varying mediump vec4 vcolor_S0; void main() { vcolor_S0 = color; gl_Position = vec4(position, 0.0, 1.0); gl_Position = vec4(gl_Position.xy * sk_RTAdjust.xz + gl_Position.ww * sk_RTAdjust.yw, 0.0, gl_Position.w); } // Fragment GLSL #version 100 precision mediump float; precision mediump sampler2D; varying mediump vec4 vcolor_S0; void main() { mediump vec4 outputColor_S0; outputColor_S0 = vcolor_S0; { gl_FragColor = outputColor_S0; } } Errors: C:\fakepath:33:35: E5000: syntax error, unexpected '(', expecting ';' or ',' Warning: D3D shader compilation failed with default flags. (vs_5_0) Retrying with skip validation C:\fakepath:33:35: E5000: syntax error, unexpected '(', expecting ';' or ',' Warning: D3D shader compilation failed with skip validation flags. (vs_5_0) Retrying with skip optimization C:\fakepath:33:35: E5000: syntax error, unexpected '(', expecting ';' or ',' Warning: D3D shader compilation failed with skip optimization flags. (vs_5_0) Failed to create D3D Shaders 1078.274:01b8:0350:fixme:d3dcompiler:D3DCompile2 Ignoring flags 0xc000. 1078.274:01b8:036c:fixme:d3dcompiler:D3DCompile2 Ignoring flags 0xc000. vkd3d:fixme:hlsl_lexer_lex Unsupported preprocessor #pragma directive at line 8. vkd3d:fixme:hlsl_lexer_lex Unsupported preprocessor #pragma directive at line 7. 1078.274:01b8:0350:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 1078.274:01b8:0350:err:d3dcompiler:D3DCompile2 Shader log: 1078.274:01b8:0350:err:d3dcompiler:D3DCompile2 C:\fakepath:33:35: E5000: syntax error, unexpected '(', expecting ';' or ',' 1078.274:01b8:0350:err:d3dcompiler:D3DCompile2 ```
Kepsz commented 1 year ago

"701.452:014c:0150:err:module:import_dll Loading library kernelbase.dll (which is needed by L"C:\windows\system32\kernel32.dll") failed (error c000012f)."

This reads like the Proton Experimental install on your system is damaged or incomplete.

Oh yeas, it was. Now integrity check did fixed it. Thx for the note!

So in PC2, right now both Proton 7, 8, and 8 exp is able to run the STO launcher. But the launcher does only shows a black screen. It works otherwise, the buttons are there, just nothing is visible. There are many vkd3d errors in the log file. steam-9900.zip

Other games like Cyberpunk works fine with proton exp. I may be able to check STO in PC1 today. Maybe.

*update: the situation is the same on PC1 too. vkd3d errors.

Kepsz commented 1 year ago

The launcher atm is still showing a black picture. Some times the game is able to start after clicking the not visible start button, but in most cases it freez.

fbenedett commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/1198#issuecomment-1633682261

To fix that you can use the --disable-gpu launch option. Later the game will still work on the GPU.

fbenedett commented 1 year ago

In my case the game works well but it does not close. It always hang at the closure then I am able to close it with the "force quit" option proposed by Ubuntu.

Kepsz commented 1 year ago

With today's proton-exp update, there are some syntax error within ?skia? vkd3d shader compliation (most detailed from line 5749):

C:\fakepath:33:35: E5000: syntax error, unexpected '(', expecting ';' or ',' steam-9900.log

@fbenedett thx, --disable-gpu works with the launcher.

dsalt commented 1 year ago

The Iconian gateway symbol-matching game, as seen in ”Sphere of Influence” part “The Other Side”, does not display any symbols. This makes it effectively impossible to complete, with the only practical option being to skip the mission.

Tested with radv and lavapipe; Mesa 23.1.5, navi23.

kisak-valve commented 1 year ago

Hello @dsalt, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the misrendering, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)

Kepsz commented 1 year ago

With today's proton-exp update, there are some syntax error within ?skia? vkd3d shader compliation (most detailed from line 5749):

C:\fakepath:33:35: E5000: syntax error, unexpected '(', expecting ';' or ',' steam-9900.log

@fbenedett thx, --disable-gpu works with the launcher.

Since STO got an updated launcher, it is now working fine on both of my machines. The game works fine too.

dsalt commented 1 year ago

Re. the missing graphics in “Sphere of Influence” – looks like that's a known issue and is affecting Windows too. Other missions are affected in similar ways – I saw another which has a sometimes-electrified floor; it's just not possible to see when…

Anyway, I'm seeing random startup failure (main game) – works fine with Steam overlay switched off, falls over a lot while displaying “Cryptic” and the initial progress meter otherwise (but does start up sometimes).

[Edit] Discussion with @kisak-valve on IRC pointed me at ValveSoftware/steam-for-linux#9586. Tested with Big Picture a few times, no startup failures.

Steam build timestamp 1694301770.

CallMeTheArrow commented 5 months ago

When Star Trek Online is launched via Steam with either the latest proton experimental (as of 3/22/2024) and also Proton 9 Beta - the launcher is completely black and unusable. This appears to be a problem with Valve's official Proton software (Proton Experimental and Proton 9 Beta). Using --disable-gpu in the launch options does not fix it.

Steam Version: 1709846872

Side note: The launcher works completely normally (not a black screen) in GE-Proton 9-1 but the same black screen problem happens in GE-Proton 9-2.

Kepsz commented 5 months ago

I tested it with proton experimental, but STO launcher works fine on my 2 PC's. Both have AMD 6700XT, with mesa 23.2.4.

alasky17 commented 4 months ago

@CallMeTheArrow Thank you so much for the report! I finally got some time to investigate and it turns out that this game was impacted by the switch from defaulting to nvapi off -> nvapi on. I will look into this and report to the proper folks to fix this properly. In the meantime, if you want to use 9.0-x, you can just add "PROTON_DISABLE_NVAPI=1 %command%" to your launch options, and the launcher should work again :)

CallMeTheArrow commented 4 months ago

@alasky17 Thank you so much for getting back to me! I can confirm that the proposed workaround does work and fixes the issue with 9.x (currently 9.4 at the time I wrote this) for me! Sincere thanks! I really appreciate it.

Side note - I suspect Champions Online and Neverwinter may be similarly affected since the those games (I believe) use the same launcher (reskinned) and the game engines are basically the same.