eaglemmoomin
Published
Had game on different drive, would not start. Moved it to main boot drive where my home partition resides. Game starts. Changed graphics settings. Get a permissions error. Game no longer starts! Deleted wineprefix game now starts again. Played through initial introductory section and then saved.
As previously noted you have to change the executable name as others have done. Then the game works perfectly, have played nearly 30 hours without a crash. If you leave the game idling for a long chunk of time it minimises itself and in my case I need to put the res back to 1080P when I tab back to it, but I think that's minor personally. Don't know how the game performs on Windows but mostly the game runs around the 120ish fps mark with occasional dips to 90ish.
Game is not stable. I don't know if this has been caused by the recent patch. Game is kinda unplayable.
Tried using the -dx11 launch option. Also renamed copied the control executable then renamed the DX11 control exe to control.exe to try and force DX11 renderer to be used.
Also tried GloriousEggrolls 5.9-GE-5-ST proton build
Game would start failing to draw frames properly and would start drawing black frames on the monitor eventually making the game unplayable.
Game is not stable AT ALL. Level transitions are a toss up as to whether they crash the game. The game wiil lock up randomly and crash to desktop.
Game works with problems
Played the game for 90 minutes configured Colt on loadout screen before 'escaping' to Updaam. Game crashed while loading in Updaam. With some sort of DX error.
Game ran well, nice and smooth with no stutters to a cap of 120fps with V-Sync off. First section of the game was fine. Loading the next section of the game after completing the introductory section caused a crash though.
The game itself plays fine or seems to. The menus work and settings can be changed. But videos still do not play!! The games splash screen is not present, the intro is not present and cut scenes do not work. I played up to the tutorial boss and beat it and the videos at various stages do not play. I'm yet to try adding the dll mentioned in other reports but without any other twiddling the game now runs and is playable.
Game fails to start. dotnet 40 is installed in the wine prefix for the game. Without having to manually add it (trying to redo it with even the --force switch leads to winetricks ignoring the command)
After installing game it failed to start on hitting play. From the terminal had to run the following commands : "WINEPREFIX=//steamapps/compatdata/220440/pfx/ winetricks dotnet40" to install .NET4.0 (hit cancel to not install Mono, though I might already have installed it previously!) then had to repair the install by running "WINEPREFIX=//steamapps/compatdata/220440/pfx/ winetricks --force dotnet40" again with the --force switch. Now when hitting play in Steam I saw two error messages which I 'ok'ed. Game started up ok and I played through the first mission and beat the level boss.
The game itself is playable and still 'fun' from the 15 minutes or so I spent in the first level.
Was necessary to run up winetricks for the pfx eg navigate to location of pfx eg xxx/SteamLibrary/steamapps/compatdata/560430 then run WINEPREFIX=$PWD/pfx WINEARCH=win64 winetricks you have to "select the default wineprefix" then "select a Windows DLL or component" now locate the two packages vcrun6 and vcrun6sp6 in the list and check the boxes. Hit Ok and wait for the install to complete. Now select "Run winecfg" from the previous menu. When the WIne Configuration dialog appears, select the Libraries tab. Now in the "New override for library" dropdown select msvcrt and add it to the existing overrides. Now Ok that change. Exit out of Winetricks and run the game. The d3d camera error will now no longer occur and you can get into the game menu. After creating a save and try to start the game it might bomb out. On restarting the game select your previous save then start the game. You will start playing the first level
The game has some tearing as it does not support higher resolutions.
Wireless XBone controller was detected but prompts in game were for Keyboard/mouse. Not sure if is just how the game is but the controller does work in game.
The game is so old that it has a 30fps cap so it's smooth but slow.
The splash screens don't appear. I'm assuming the game has them! I started the first level multiple times to see if the game was consistent. The game might possibly also have an issue with cutscenes. Second time starting the first level I saw the classic Indy red dot on a map. Third time didn't see it. Might try a GE custom with media platform stuff in to see if it makes a difference.
Can't play the game. Have requested refund.
Game is unusable. Does not work with XBox One wireless controller or Xbox 360 wireless controller to control cars. No ability to steer to the right. Both controllers work on other games.
Controller do not work
Game runs really well with Proton 5.0.7 The standalone configuration tool works. The game starts correctly without having to rename the game executable in my experience with the game. My XBox one Wireless controller also works correctly.
Game starts in windowed mode. Configuration options work. But on starting a new game it exits back to the steam library page
Initial menus work but actual game fails to run with 3.16-8 Beta. Don't thing the intro videos can be played. Looking at the proton log file looks like a Media Foundation library related problem. Manually installing Proton 4.2-1 from my Steam Library > Tools then restating the game seemed to do the trick. Was able to play through to third save point.
Game starts informs you Nvidia driver is out of date, gives you the option to continue anyway. You get a warning about photosensitivity. Game bombs out. Update to 430 Nvidia driver the game no longer warns you about the driver but still bombs out after the photosensitivity warning. Haven't enabled proton logs to see what is causing it to bomb out. The game apparently has a vulkan renderer AND denuvo.
Updated to new Proton version (It has a Rage 2 specific fix) and the game now runs as expected. Can mess about in menus, game starts and is playable. Played up until just after the Ranger Jersey part when you get some additional gear.
So I initially thought the game was running perfectly until I had to use the world map/mission log then switching from the game world to the map would break the game (black screen) on attempting to return to the game world. After multiple goes at this the fix for this, appears to be to set the game into the borderless windowed mode. After doing this I was able to play for well over an hour going into and out of the world map/log without the 'crash' reoccurring.
Works no fiddling
Game runs at 1440p no problem. Audio works fine. Remember to rebind the movement keys to WASD and that for mouse rebinding you need to use the left and right arrow keys to access the possible binding for your mouse buttons. Mouse wheel is not supported in the bindings menu but I don't think it's that necessary.
Game controlled much better with the Keyboard. Did try reducing the polling rate on my gaming mouse. Helped a little.
Played the first mission through to the end. No signs of any issues once I'd configured the graphics settings and odd cover mechanic to my liking (M+K setup oddness makes cover mechanic look like it's glitching, it's not).
Game does not respond to game controller
Using an XBONE controller via the dongle and Xow the game requests a controller be plugged in. Will not respond.
Plugging in a wired x360 controller the game does not recognise that either unless Xbox configuration is enabled in the Steam controller settings. Once that's done it will get to the splash screen. The game displays "Press Start" however it does not respond to the controller
The game is unplayable. Does not respond to the keyboard.
6.10-GE-1 GloriousEggroll
I had an issue with my XBONE and XBox 360 controllers not working. Initially
I had to enable the XBox Controller support in my Steam client settings and enable both the Steam overlay and Steam Big Picture controller option for the overlay.
Once that was done the game was fine.
