Homeworld Remastered Collection

Homeworld Remastered Collection - Steam version

This is the Steam version of Homeworld Remastered Collection. The game is also available as DRM-free at GOG. These two versions are not compatible for multiplayer games (Steam players and GOG players cannot play all together).

The game can also be played using the native linux Steam client with Proton, check the HWRC Proton Launcher and the game entry in ProtonDB.

Additional reference links:

Application Details:

Version: Current
License: Retail
URL: http://www.homeworldremastered...
Votes: 1
Latest Rating: Silver
Latest Wine Version Tested: 5.7

Maintainers: About Maintainership

Test Results

Selected Test Results

What works

Homeworld -  game runs and loading levels works fine with custom command line

Homeworld2 - game runs and loading levels works with basic graphics

Homeworld/Homeworld2 Remastered - game runs and loading levels works with basic graphics with custom command line and force opengl version


VGA compatible controller: Intel Corporation UHD Graphics 620


3D controller: NVIDIA Corporation GP108M [GeForce MX150]

What does not

Original launcher

Doesn't work at all it requires .NET4.0 but even with 32bit wineprefix and installed all dotnet crap it is still failed to launch.

If you want to set LOD to maximum it will crash under wine5 you can eliminate crashes caused by some of LOD settings by installing winetricks 

  • glsl=enabled
  • ddr=opengl
  • rtlm=readdraw

but anyway with all high settings it will crash on load level it just allow to set few of them to high.

So my solution to use wine 4.21 where it works fine...

Homeworld Remastered

Again almost the same about high settings like in homeworld2. Just can't be sure about it because it's a bit random. Sometimes I was able to launch with highest texture quality. But looks like with options provided above it is more stable.

Intro video glitching like in a attempt to start play it over and over again till intro finished. First mission video works fine. About others I'm not sure I didn't  see them yet and I will not see them under wine5 because I will play this game as well under wine 4.21.
You can eliminate video glitching at start by installing winetricks directplay and directmusic. But looks like they caused more crash on high settings not sure because as I've mentioned it's a bit random for me.

The only what I can say for sure about settings, those are most affected and here stable values for them:

- TEXTURE QUALITY: 6-MEDIUM - works stable, higher values sometimes causing troubles on load level
- TEXTURE SIZE LIMIT: 2048 - works stable, any higher value failed to load level
- DEPTH OF FIELD: OFF - works stable, ON value works stable but significantly lower FPS (don't know how it is in windows)

So again I'm using wine 4.21 to launch it


Some work around in "What doesn't work" section. (but using wine 4.21 is a way better)

All off the below implemented in launcher script here

So below just some of the settings

Winetricks to install:

WINEPREFIX="$wineprefix" WINE="$winebin" winetricks -q vcrun6 vcrun6sp6 vcrun2003 vcrun2005 vcrun2008 vcrun2010 vcrun2012 vcrun2013 vcrun2015

WINEPREFIX="$wineprefix" WINE="$winebin" winetricks -q dxdiag dxdiagn dx8vb directx9 d3dx9 d3dx9_24 d3dx9_25 d3dx9_26 d3dx9_27 d3dx9_28 d3dx9_29 d3dx9_30 d3dx9_31 d3dx9_32 d3dx9_33 d3dx9_34 d3dx9_35 d3dx9_36 d3dx9_37 d3dx9_38 d3dx9_39 d3dx9_40 d3dx9_41 d3dx9_42 d3dx9_43

WINEPREFIX="$wineprefix" WINE="$winebin" winetricks -q tahoma corefonts fontsmooth=rgb

# actually this one below doesn't work insome reason

WINEPREFIX="$wineprefix" WINE="$winebin" winetricks -q mwo=force

WINEPREFIX="$wineprefix" "$winebin" start winecfg

when "winecfg" started go to "Graphics" tab and mark checkbox "Automatically capture the mouse in full-screen windows"

Homeworld parameters

waveout -1024 -safeGL -waveout -noglddraw -noswddraw -nofastfe -triple

Homeworld2 parameters

-w 1024 -h 768 -hardwarecursor

Homeworld remastered parameters

dlccampaign HW1Campaign.big -campaign HomeworldClassic -moviepath DataHW1Campaign -mod compatibility.big

Homeworld2 remastered parameters

dlccampaign HW2Campaign.big -campaign Ascension -moviepath DataHW2Campaign -mod compatibility.big

Homeworld multiplayer remastered

-mpbeta -mod compatibility.big

Every game support "-locale Language"

Additionally for homeworld 2 you need to force to set  opengl version 


General command to launch game looks like this
WINEPREFIX="$wineprefix" "$optimus" "$winebin" explorer /desktop=HomeworldRM,"$screenWidth"x"$screenHeight" "$exename" "$homeworldparams"

What was not tested

Actually gameplay of homeworld classic just passed tutorial.

And multiplayer never tried

Hardware tested


  • GPU: Nvidia
  • Driver: proprietary

Additional Comments

Actually as I've tested in wine 5.5,5.6,5.7 all of them has more problems than wine 4.21

Do not run game in 32bit prefix the FPS really lower than 64bit.

I've made script for myself with collection of tweaks and tricks to launch steam version installed into lutris or playonlinux (it should work with GOG version installed to playonlinux as well). 

So you can find some useful commands and actions there or just simply to use it. Additionally in readme there is more descriptions.

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
CurrentFedora 31 x86_64May 23 20205.7Yes Yes YesSilverYura 
ShowArch Linux x86_64Jun 01 20194.9Yes Yes YesGoldIsmo Toijala 
ShowLinux Mint 18.3 "Sylvia" x86_64Jun 23 20183.10-stagingYes Yes NoSilverJames Edmonds 
ShowLinux Mint 18.3 "Sylvia" x86_64Apr 06 20183.5Yes Yes NoSilverJames Edmonds 
ShowLinux Mint 18.3 "Sylvia" x86_64Dec 22 20172.21-stagingYes Yes NoSilverJames Edmonds 

Known Bugs

Bug # Description Status Resolution Other apps affected
47448 Homeworld Remastered Collection: Fullscreen broken UNCONFIRMED View

Show all bugs

HowTo / Notes

Issues with Mesa drivers - OpenGL 3.3 Compatibility Profile required

Last update: 2019-06-02

This is a known issues that causes the remastered versions of the games to not work with the Mesa drivers. It is discussed in the bug report 41551.

The games require the OpenGL 3.3 Compatibility Profile that should be supported by the Mesa drivers starting from version 18.2.0. Please check if the compatibility profile is supported by your setup with the command "glxinfo | grep version". If so, then set/export the environment variable "MESA_GL_VERSION_OVERRIDE=3.3COMPAT" before launching the games.

Please note that:

  • this issue does not occur when using NVIDIA and AMD proprietary display drivers;
  • the classic versions of the games are not affected by this issue.
Software Requirements

Last update: 2019-01-13

This version of HW:RC requires the following software:

Please refer to the AppDB entries of Steam and .NET Framework 4.0 for detailed installation instructions.

The LittleCMS 2 and the PNG libraries are provided in Debian and Ubuntu by the liblcms2-2 and the libpng16-16 packages respectively.


Last update: 2019-01-13

Homeworld 1 Classic crashes at startup
Homeworld 1 Classic crashes at startup with the message "Fatal Error - couldn't initialize default rendering system". To solve this issue launch the game with the option /noglddraw.

Homeworld 1 Classic, game screen not scaled and menus off screen
The game allows to choose only 4:3 screen resolutions. If the game screen is not properly scaled then launch the game in windowed mode with the option /window.

Homeworld 2 Classic, game screen not scaled and menus off screen
If the game screen is not properly scaled then launch the game in windowed mode with the option -windowed and then set a proper screen resolution.

Remastered games, crash when loading levels and cinematics
The problem could be caused by a memory issue with the display server, lowering the texture quality to medium (or below) should solve the problem.

How to launch the games from the command line

Last update: 2019-01-13

The following shell commands can be used to bypass the default game launcher and directly launch one of the games in the collection.
Please note that starting from HW:RC v2.1, Steam has to be running in background. If Steam is not already in execution, the following commands will only result in launching Steam and then the default game launcher.

Before using these commands make sure to set the correct wine executable (if needed), set the current game WINEPREFIX and choose the current game paths.

To launch Steam in background:

WINEPREFIX=<game_wineprefix> wine start /unix \
<steam_path>/Steam.exe -silent

To launch Homeworld 1 Classic:

WINEPREFIX=<game_wineprefix> wine start /unix \
<game_path>/Homeworld1Classic/exe/Homeworld.exe /noglddraw

To launch Homeworld 2 Classic:

WINEPREFIX=<game_wineprefix> wine start /unix \

To launch Homeworld 1 Remastered:

WINEPREFIX=<game_wineprefix> wine start /unix \
<game_path>/HomeworldRM/Bin/Release/HomeworldRM.exe \
-dlccampaign HW1Campaign.big -campaign HomeworldClassic \
-moviepath DataHW1Campaign

To launch Homeworld 2 Remastered:

WINEPREFIX=<game_wineprefix> wine start /unix \
<game_path>/HomeworldRM/Bin/Release/HomeworldRM.exe \
-dlccampaign HW2Campaign.big -campaign Ascension \
-moviepath DataHW2Campaign

To launch Homeworld Remastered Multiplayer:

WINEPREFIX=<game_wineprefix> wine start /unix \


The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Can not play with community patch (Access Violation)
by Ville Aakko on Monday October 7th 2019, 11:59

The community patch 2.3 (as of writing this) can not be used, as using it causes a "Access Violation" error dialog at start of campaign (any cinematics). I can load a saved game I've made previously, however I presume the game will crash at any cinematic (though I didn't test this thoroughly).

The community patch can be considered semi-essential since it patches gameplay issues still present in the latest official version. In case anyone can figure out how to run with community patch in wine, any tips are appreciated. (I've run game with additional arguments: "-workshopmod 2.3PlayersPatch.big" after placing said file in DATAWORKSHOPMODS).

Otherwise, the game runs fine with the workarounds posted here (even the launcher, though it is black and UI elements only become visible after howering mouse over them - I prefer and recommend launching manually).
RE: Can not play with community patch (Access Violation)
by /dev/fra on Monday October 7th 2019, 15:55
Check the troubleshooting discussion on Steam , comment #42. Do you mind giving the workaround there a try?
RE: Can not play with community patch (Access Violation)
by Ville Aakko on Tuesday October 8th 2019, 0:50

Thanks for your reply! I've found that thread, and tried that (after posting). That user says the crashes happen "randomly", which implies they do not happen every time. On my setup, it is impossible to start any campaign mission (well, at least 1-4, I played the first three before applying the community patch, and can not test subsequent missions). The crash happens *always* - except if loading a saved game (saved without the community patch).

I'm only assuming this is because of the cutscenes, but now that I think about it, it could also be that the community patch is not applied to the running game instance, if one loads a saved game saved before applying the patch. I couldn't find any mentions about applying the patch "on the fly" - i.e. not restarting the campaing after applying patch. With some mods in some games, one is not supposed to do that, but a restart is mandatory, to prevent weird breakage (but here: I can not restart, only load older saved games!).

FWIW I did found that thread and tried setting:
* Base Production Times,
* tried reduce graphics details (to minimum), and
* applied the 4GB patch from the recent test result here.

None of these helped with the "Access Violation" error. Those are the only workaround I've tested so far - in case there is something else I've missed, I'll be happy to try =)

Also, it's worth to note this is on the version (there is no (sub)entry for it here in the AppDB, not sure how to add one - and AFAIK these versions are practically identical, save Steam version requires a running Steam instance and has achievements and whatnot, so there could also be some subtle differences which could cause a crash on either one, but not on the other). I've also posted in the forum about this error.
RE: Can not play with community patch (Access Violation)
by Ville Aakko on Friday October 11th 2019, 12:46
Juut to clear some confusion: I'm using the term "community patch" here. What I meant was Players Patch 2.3, and while it was finished by the player community, there is a separate fan-made mod called "community patch" in Steam Workshop.

So, I mean this one: . Also and (all are the same patch). Sorry, I should have put the link(s) in the first comment!
Full-screen not working
by Linards on Thursday July 4th 2019, 2:52
As of wine-4.11 , the Fullscreen is broken and I cannot get game running in Windowed mode with any known switches or Launch Option command line strings. Last working version was 4.9
Launcher doesn't show
by Quentin Deldycke on Wednesday December 20th 2017, 2:20

The launcher does not appear, i have these errors:

fixme:dwrite:dwritefactory_CreateMonitorRenderingParams (0x1): monitor setting ignored
fixme:d3d:wined3d_check_device_format_conversion wined3d 0x21a680, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8X8_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub!
fixme:shell:URL_ParseUrl failed to parse L"Launcher.Content"
fixme:shell:URL_ParseUrl failed to parse L"Launcher.Content.resources"
fixme:shell:URL_ParseUrl failed to parse L"Launcher.Content.resources"
fixme:shell:URL_ParseUrl failed to parse L"Launcher.Content.resources"
fixme:shell:URL_ParseUrl failed to parse L"Launcher.Content.resources"
fixme:shell:URL_ParseUrl failed to parse L"Launcher.Content.resources"
fixme:shell:URL_ParseUrl failed to parse L"Launcher.Content.resources"
fixme:shell:URL_ParseUrl failed to parse L"Launcher.Content.resources"
fixme:shell:URL_ParseUrl failed to parse L"Launcher.Content.resources" [Load of them, seems to print in an infinite loop.]