PlayableShow Details
Unknown
Worked great out of the box
Edit/create options.ini in game folder with "Driver = DirectX" under [Graphics] section
Game runs great, including multiplayer but requires display driver/renderer switch which can only be done via editing the options.ini file since default results in a blank screen
Limit to 45 FPS
Deactivate "Wind Effects", and the game runs at 60 FPS on low/medium settings. With wind effects, ~35 FPS
Works out of the box after activating "Steam Play for all titles" and "Proton Experimental"
Work 100% out of the box.
I did not try with DirectX API tho as I had already excellent performance with everything maxed out under opengl. No tinkering required
Also had to do the same as Siosm suggested for the overall Linux report:
- Launch the game once, you'll get a black screen
- Force close it / it might crash
- Get into Desktop mode and navigate to your Steam library
- Select the game and choose: Manage > Browes local files
- Edit the "options.ini" file under Graphics and set: ''Driver = DirectX"
- Go back into Gaming mode and launch the game
- Initial tutorial load was <1FPS
- Waited long enough to hit ESC for menu
- Changed Quality options and click Apply (any Low-Med-High option will do)
- Return to game and no slowdown
Need to update options.ini
I was trying to run the game after installing it on my older hdd used for windows. After closing steam and reopening it from the terminal I could see the log, which retuned an error regarding some "drive_c". This github page https://github.com/ValveSoftware/Proton/issues/5168 showed that there are some issues with NTFS partitions and reused windows partitions.
It worked perfecly without any tinkering* after I uninstalled it from the NTFS partition and installed it on an ext4 partition mounted on /home from my linux Mint. ( I umounted the NTFS partition before to be sure nothing on it was being used).
I used Proton version 8.0-5, didn't try it with experimental on the ext4 partition. (while on ntfs partition, no version available worked)
Running slow on an Atari VCS 16GB RAM 2GB Video Allocated. I expect it's fine on Higher End AMD Radeon / Ryzen Hardware.
Also had to do the same as Siosm suggested for the overall Linux report:
- Launch the game once, you'll get a black screen
- Force close it / it might crash
- Get into Desktop mode and navigate to your Steam library
- Select the game and choose: Manage > Browes local files
- Edit the "options.ini" file under Graphics and set: ''Driver = DirectX"
- Go back into Gaming mode and launch the game
My Atari VCS is a low end PC so set all graphics to Low and it runs :)
Just ran through some tutorials and set all graphics options to low and it seems to run OK
Changed to 30 fps
Small text, built in magnifier unavailable with use of controller
Can't always hold 30 fps on medium settings
Works out of the box on Steam Deck. Already set to DirectX.
Had to do the same as Siosm suggested for the overall Linux report:
- Launch the game once, you'll get a black screen
- Force close it / it will crash
- Get into Desktop mode and navigate to your Steam library
- Select the game and choose: Manage > Browes local files
- Edit the "options.ini" file and set: ''Driver = DirectX"
- Go back into Gaming mode and launch the game
Set limit to 30FPS/Hz
Text is pretty small on the Steam Deck screen itself
Start minimized - Alt+Tab to bring it on main screen
I have more than 270 hours on this title. All on linux
When running on Wayland, the game can only run using DirectX (which must be manually changed in the options file to be able to launch the game). Even then, I had occasional performance issues (framerate falling to single digits).
On x11, it works fine with the default OpenGL renderer (as well as DirectX), and I found it runs better (more fps with exactly the same options and DirectX, both on x11).
Occasional, restarting the computer fixed it
had to edit an ini file as mentioned in another report -
Launch the game once, you'll get a black screen Force close it Go to game folder: Manage > Browes local files Edit the "options.ini" file and set: ''Driver = DirectX"
black screen but with audio without changing the .ini file driver to directX. after that everything seems fine. not played a full MP game to really test though. but so far its fine.
Opening video is black screen and never reaches the menu
The game doesn't run as of leaving early access.
If you are ok with small text it is great. Switching to directX fixed the game breaking bug. But I noticed it performs slightly less smooth.
Some text is a little small. + look like - but they are green and red so that helps.
A few minutes in you get a blue screen. I switched the game from proton to DirectX in the game settings and I'm hours into a play without an issue.
Review is desktop mode, will test gaming soon
Runs OOTB, no tinkering, Flawless.
Flawless
Fullscreen turned blue
Fullscreen turned blue. Cloud not resume playing.
- Launch the game once, you'll get a black screen
- Force close it
- Go to game folder: Manage > Browes loca files
- Edit the "options.ini" file and set: ''Driver = DirectX"
The game sometimes freezes and then resumes normally
On starting a new game, just get an infinate 0% to 8% loading loop
While i can load an old game (like, really old), if I try to start a new game (battle for arrakis, kanly duel), it goes to the loading screen and just infinatly goes from 0 to 8% and back again.
I've tried may proton versions, uninstalled, reinstalled.
DirecteX, windowed
OpenGL (black screen)
The game does not install with an options.ini, and the wrong settings will cause it to crash on launch.
To work, needed to create an options.ini in the game folder. This is the options.ini settings that worked on my system:
Edit at your own risk! You can delete this file to revert to default settings.
General
Language = en
ServerRegion = NorthAmerica
ShowTutorials = true
LoadingTips = true
IntroVideo = true
AutoSave = 5
ProfanityFilter = false
Graphics
Driver = DirectX
DisplayMode = Borderless
Monitor = 0
Resolution = 1920x1080
Framerate = 60
VSync = false
UiScale = 2
AntiAliasing = false
Bloom = true
TerrainQuality = 3
ShadowsQuality = 3
FogQuality = 2
VfxQuality = 2
Wind = true
Brightness = 5
Contrast = 5
Audio
AudioEnable = true AudioMaster = 10 AudioEnvironment = 10 AudioMusic = 10 AudioUI = 10 AudioVoice = 10
Gameplay
AlertAutoPause = false
PauseGameInMenus = true
PauseEffect = true
Need to modify nonexistant options.ini before you can even run the game.
There is an incompatability under Linux/Proton with VSync causing a black screen. Editing the config file options.ini solves this on my PC.
File: options.ini in game folder. Set Driver = DirectX and VSync = false
On my laptop, using an NVidia card it works out of the box. My AMD RX6800XT apparently needs VSync to be turned off. So the question whether a typical user would enjoy this game when launched straight from Steam without tinkering is very dependent on the hardware used. The game runs using the default Proton version.
Sí pero hay que tener en cuenta que el juego esta todavía en early access y la optimización no es del todo buena.
Parones de frames pero que también me pasaban en windows 10. Sólo he jugado una vez y puede que sea un problema de shaders.
Con el paso de los turnos empezaron unos parpadeos azules muy breves
the game is working very well but is still an early access videogame and the performance is not the best.
Tried different versions of Proton with no luck.
Game starts to launch but then just goes away. Tried using GE-Proton7-49, Proton 6.3-8, 7.0-6 and Experimental with same results.
It had worked before so I am guessing it has something to do with the January update?
Game opens as a black screen, no gameplay. Audio works fine.
Tried deleting/editing various files, system configs and Proton version.
This was working but the January 18th update has broken it on Proton, it now only shows a black screen
Tried it on recommended and Proton experimental.
No problem while playing with 3 friends
Switch rendering mode in-game to DirectX
Once over a dozen units is involved in a single region, the audio stutters from time to time
Blue screen after a couple minutes when using the default OpenGL rendering mode
Once OpenGL rendering is fixed, it may be superior to the native Win version performance-wise
Blue screen during play
Game seems to run and control fine but after so many units or building are on the map the game just goes blue. Unplayable on Steam Deck
Everything working, I did not feel anything wrong
To make it work, you need to switch the graphical driver from opengl to directx, and the blue screen disapear, I played 10 minutes, nothing wrong from my side.
Blue screen after creating a refinery. Attempted DirectX and OpenGL switching.
