

Worked out of the box

Wont open launcher
Tried all protons back to 6, tried several protonGE. Opening the exe with just wine actually made the launcher start, but it was non-interactive.

PROTON_USE_WINED3D=1 %command%
using the windows / command button (or alt+tab) switching back to OS then back to game fixes the issue
Works great with minor mouse issue

switch to proton experimental, sto-launcher takes its time after pressing engage but nothing else. game runs perfectly fine.

gamemoderun %command%
the only probably not proton issue was a crash uppon opening shuttle-customisation-bridge-preview (worked after restart -> prob played to long w/o restart or smth)
If i select "Fullscreen" option, then the game slow down. But i reselect the "windowed" option the game works perfect!

Work well with proton experimental
Hit install, hit play, it just worked. Runs perfectly out of the box.
Runs perfect without any problems out of the box
gamemoderun
Installed d3dcompiler_47.dll

SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS=0 %command% --disable-gpu
protontricks 9900 d3dcompiler_47
Missing glyphs in a memory/symbol-match minigame, making it effectively impossible to complete that task. Missions containing this minigame have to be skipped.
Frequently crashes when starting up (initial progress bar still displayed). This appears to be related to the Steam overlay.

Installed d3dcompiler_47.dll through Protontricks (Star Trek Online prefix 9900) to fix blackened launcher. Launch option --disable-gpu isn't required as a resault.
Being a multiplayer-only game, STO runs and plays extremely well, even better in fact than natively on Windows without any crashes, lockups or hangs whatsoever when run on Kubuntu 20.04 and Proton 8.0-3.
This of course was after installing d3dcompiler_47.dll through Protontricks 1.10.4 from Flathub to resolve a blackened game launcher.
In order to fix STO's blacked-out launcher, Proton 8.0-3 must be under Steams Compbitability option and d3dcompiler_47.dll must be installed with Protontricks 1.10.4 from Flathub. Alternately, other players reported the launcher option "--disable-gpu" may be used as a viable fix.

Launcher is blackened out unless you install d3dcompiler_47.dll as noted. Game hangs on exit.
Install d3dcompiler_47.dll using CLI or Protontricks Winecfg using Star Trek Online prefix 9900.
Game hangs on exit. Shut down the game using Steam or kill the process afterwards.
Should mention that Vulkan runs great. Not sure why people are overriding to use WineD3D instead.

--disable-gpu
Pick either full screen, windowed, or windowed full screen and don't switch between them during gameplay unless you restart the game after changing the setting. Once set and restarted, game is very stable. I usually run it windowed (without any issues).
Performs just as well as it does on Windows 11, under Debian 12.1 with KDE.
Be sure to add the launch options --disable-gpu in Steam and in the game's launcher (command line field) as well. If you don't, you may have a full black screen window where the launcher is. You may want to cap FPS using in-game options at 30 (not required, but recommended if you have any heat or stability issues). Overall, the game peforms well and is very stable. Sound works well also.

Out of the Box the Game Launcher stays black but the buttons still work, can be fixed by using Proton Experimental and executing protontricks <APPID> d3dcompiler_47
.
Since the "On-demand patching" feature causes long delays when switching maps it should be turned off.
Exiting causes the Game to hang, has to be killed by Steam.

PROTON_USE_WINED3D=1 %command%
You can load a character that already exists but if you want to start a new then you get stuck on the loading screen since it doesn´t load like at all. Same goes if you want to start a mission.
as stated above
it did not work without the advice from previous posts since thee launcher remains black.

The game launcher screen is black after starting. This can be fixed by using protontricks. Ex protontricks 9880 d3dcompiler_47
protontricks 9880 d3dcompiler_47

PROTON_USE_WINED3D=1 %command%
Cursor desyncs sometimes, switch into fullscreen and back to fix.
Be aware there is a current issue with the game wherein the launcher is a black screen, but if you can find the "Engage" button that resides in the bottom right corner, (and if the button works, which it sometimes won't), the game will launch and play as normal.
PROTON_USE_WINED3D=1 %command%
When alt+tab out of the game and back to the game, the game would display only a black screen. This is fully resolved by changing: Options -> Display -> Display Mode -> Windowed Maximized. As far as I can tell theres no practical difference between this and fullscreen.
Apologies for the duplicate report (I can't edit the existing report).
Recommend DISABLING the On-demand Patching option in the game launcher Options (STO's game launcher, not the Steam options). If this option remains enabled, you may encounter random hangups and/or longer load-times during in-game on-the-fly patching.
Using AMD's proprietary graphics drivers:
amdgpu-install --usecase=dkms,graphics,multimedia,opencl,hip --opencl=legacy --opengl=mesa --vulkan=amdvlk --accept-eula
I encountered a defect when switching out of the game to my web browser and then back into the game... the screen was all black but sound was still playing and the game was still running (I could hear actions being performed even though the screen was black). I believe it may have something to do with graphics quality as when gaphics settings were low, this issue did not occur. This issue can be resolved by changing the in-game options from Fullscreen to Windowed Maximized and you can keep settings at high/max.
NOTE: I did NOT encounter this window-switching/black-screen issue on my nVidia (GeForce GTX 860M) computer (Alienware Steam Machine Alpha R1)... The Fullscreen setting worked fine on that one.
PROTON_USE_WINED3D=1 %command%
See notes
Recommend DISABLING the On-demand Patching option in the game launcher Options (STO's game launcher, not the Steam options)
Using AMD's proprietary drivers... I think? I ran amdgpu-install. This is a new system, I have not had time to extensively test the game on this system. I encountered a defect when switching out of the game to my web browser and back to the game; the game screen was all black but sound was still playing and the game was still running (I could hear actions being performed even though the screen was black). I will try to remember to update this note to advise whether this defect is or is not persistent and/or how to fix it.
STO barfs up an error saying video card is unsupported upon updating to Proton 8. Works fine on Proton 7.0-6. Under Proton 7, it sometimes gets stuck on load screen and also freezes when quitting game. Use Steam to force quit.
PROTON_USE_WINED3D=1 %command%
Has trouble with on-demand patching. Disable to fix. Disable full-screen on initial load, and switch to full-screen after game has loaded, if desired.
Works excellent. Make sure your flavor of Linux is up to date, as well as your graphics drivers. I believe if you have any NVIDIA 700 series GPU or newer, you can install driver version 525, otherwise install 470.
Perfect emulation, only a minor glitch as the in-game exit hangs. Workaround is simple: start and stop game session from Steam.
In-game exit command doesn't work, need to close the session from Steam
Little to no difference running this game on the OS that was tested (Regata) and Windows.
PROTON_USE_WINED3D=1 %command%
Has trouble with on-demand patching. Disable to fix. Disable full-screen on initial load, and switch to full-screen after game has loaded, if desired.
It works great. Remember to input this command in "properties>general>launch options
PROTON_USE_WINED3D=1 %command%
I don't know too much of the technical details of the command, its what i read from other reports. It does launch the game properly, as I have tested both with and without that launch command.
RESULTS WILL VARY. By some miracle I have successfully ran a game on an 11-year old laptop.
DirectX error when launching
PROTON_USE_WINED3D=1 %command%
A DirectX error will show when launching even tho the use of the right version is forced by the launch parameter. Tested with nvidia-open drivers and a RTX 3060 Ti.
Unsupported Operating System
The launcher display this message : "You will be unable to play using this Operating System." I used to be able to play before the last launcher update. I tried many proton version from 7.0.6 to any other experimental ones.
Turn off "On Demand Patching"
It sometimes causes game crashes on moving your character/ship between maps.
Had some lag after i tinkered with the settings. Can run at high/max settings for graphics and CPU. leave your field of view rendering to 100 and everything will load fine. if you see lowdown, make sure the in-game renderscale is set to 1. to do this, within the chatbar type /renderscale 1. this gives the smoothest experience possible. i also made layout i was comfortable with by customizing the sto hotbar layout. you can download my layout if you like. with it, it makes the game 100% playable
Plays well out of the box on Debian stable with LXQt.
If the patcher pauses or freezes up, shut down the game and try again. The patcher is smart enough to keep previous progress and successive attempts will have less to download. Eventually the entire patch will complete. Disable on-demand patching to avoid getting stuck downloading assets in loading screens.
Sometimes the game will freeze on exit. I just alt-tab over to Steam and shut down the game from there.
Sometimes the game will hang on the loading screen on CRYPTIC with a totally empty progress bar. Simply restart the game.
I had to install and run this manually by adding non-steam game to my library and choosing the launcher executable. Then running the launcher through that method patched/downloaded the game. After launching the game properly with this method, it worked fine using the normal steam library option with proton. On my particular setup it [b]refused[/b] to launch the launcher any other way. Everything is working fine now though.
Alt-tabbing works but sometimes is glitchy and will cause the screen to flicker and stutter.
I am unable to figure out if this is a game issue or a linux issue but ocassionally while loading a new sector/zone (with the loading screen) the game just sits there and never finishes loading. This may not be a proton issue though.
works OK
will hang and become unresponsive after a few hours of play.
occasional ping spikes. not sure if it was caused by proton or my connection.
has some crashes after a few hours
SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS=0 PROTON_USE_WINED3D11=1 %command%
The launch options I used are required, otherwise STO will exit with a message stating the video card is no longer supported. Everything worked perfectly. I am now completly free of Winows again! :) Thank you Valve! I will follow you into the gates of hell if necessary.
SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS=0 PROTON_USE_WINED3D11=1 %command%
I'm extremely pleased with the playability of this game, given my hardware (Acer Chromebook 15 CB3-532/Banon; 2GB RAM/16GB eMMC). Running PeppermintOS (Debian 11.3 (Bullseye)). [Note: I'm not sure if the Launcher Options are required. I only added them because there were several reports of it being beneficial to add them.]
Touch-Emulation
Locked to 30FPS
It is playable, after a lot of cusomization with the gamepad and touchscreen emulation.
The game installs and runs out of the box. I've only made some graphical changes (the same as I do on Windows – Bloom, ambient occlusion off) and have on par performance.
SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS=0 PROTON_USE_WINED3D11=1 %command%
MMORPG. Running Fine
Nice to have the game working again after a few weeks broken.
Changed default controller config
For starship/space controls, you need to manually set your camera to "Free Look"
30FPS limit, and Medium graphics
Set launcher to minimize and autolaunch
Its an MMO, everything works as expected.
Once the right control configs are put in place, the game controls well and is playable all around. Biggest inconvenience is initial setup and relearning controls.