None of these helped with the "Access Violation" error. * applied the 4GB patch from the recent test result here. * tried reduce graphics details (to minimum), and 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!).įWIW I did found that thread and tried setting: not restarting the campaing after applying patch. I couldn't find any mentions about applying the patch "on the fly" - i.e. 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. The crash happens *always* - except if loading a saved game (saved without the community patch). 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). That user says the crashes happen "randomly", which implies they do not happen every time. Thanks for your reply! I've found that thread, and tried that (after posting). Lowering the texture quality to medium (or below) should solve the problem. The problem could be caused by a memory issue with the display server, Remastered games, crash when loading levels and Steam game launch options as %command% -windowed. Mode with the argument -windowed and then set a proper screen If the game screen is not properly scaled, then launch the game in windowed Homeworld 2 Classic, game screen not scaled and menus off Steam game launch options as %command% /window. Not properly scaled, then launch the game in windowed mode with the The game allows to choose only 4:3 screen resolutions. Homeworld 1 Classic, game screen not scaled and menus off Steam game launch options as %command% /noglddraw. For the latter, if using Steam, the argument can be set in the Games from the command line, or as an argument for the HW:RC The argument can be set as described in the section How to launch the Launch the game with the argument /noglddraw. Homeworld 1 Classic crashes at startup with the message Fatal Error -Ĭouldn't initialize default rendering system. the classic versions of the games are not affected by this issue.this issue does not occur when using NVIDIA and AMD proprietary.Variable MESA_GL_VERSION_OVERRIDE=3.3COMPAT before launching If the compatibility profile is supported by your setup with the command Supported by the Mesa drivers starting from version 18.2.0. The games require the OpenGL 3.3 Compatibility Profile that should be This is a known issues that causes the remastered versions of the games to Issues with Mesa drivers - OpenGL 3.3 Compatibility Profile Wine "$game_path"/HomeworldRM/Bin/Release/HomeworldRM.exe To launch Homeworld Remastered Multiplayer dlccampaign HW2Campaign.big -campaign Ascension \ dlccampaign HW1Campaign.big -campaign HomeworldClassic \ Wine "$game_path"/HomeworldRM/Bin/Release/HomeworldRM.exe \ Wine "$game_path"/Homeworld2Classic/Bin/Release/Homeworld2.exe Wine "$game_path"/Homeworld1Classic/exe/Homeworld.exe /noglddraw /window (see notes in the Troubleshooting section): However most users may want to use the arguments (in the Wine "$game_path"/Homeworld1Classic/exe/Homeworld.exe If using the Steam version of the game, launch Steam first, otherwise theįollowing commands will not work. ForĮxport WINEPREFIX="$/steamapps/common/Homeworld" Steam version of the game), and the path to the main game folder. Set the path to your Wine prefix, the path to the Steam folder (only for the In the collection, bypassing the HW:RC launcher. The following shell commands can be used to directly launch one of the games
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |