Talk:Resident Evil: Revelations

This is a error that keeps popping up for me when playing this game during the beginning of Episode 4 and crashes the game.

What happened was the idiots at Tose or Capcom decided that their PC port needed to be a 32-bit executable. The game can't go over 2 GB of RAM without crashing, and Revelations starts up with roughly 1.4GB of memory. This 32-bit memory error is a hard limitation of software that can be read below. A famous example of this happening is the 3D Fallout games regularly needing an extended memory patch to not crash because of this error.

wiki dot tesnexus dot com/index dot php/2-4GB_game_memory_limits_and_solutions

There's 2 solutions.

1. Set the graphical settings to LOW and\or a smaller resolution. 2. Use a 4GB tool and a cracked Executable. The reason why you need the ceraked executable is that Revelations won't start normally with the fix applied.

Both of these are not ideal at all, but Revelations is hard coded unless someone makes a good fix.

Instead of needing a cracked executable you might be able to use the Steamless tool to unpack the steamstub protected EXE, works on most games at least.

As mentioned on the main page a custom resolution can be specified by editing the config.ini file, but trying to play the game afterward will result in a crash after the main menu.

The crash seems to be caused by game trying to look up the resolution in a table of known resolutions in the EXE (the list displayed in game settings), if it's not found there then game will crash.

Getting around the crash is a simple matter of just editing one of the existing resolutions in the list (eg. 2560x1600) to the desired resolution, that combined with INI edit seems to allow game to play fine without crashing.

Unfortunately even though the resolution list can be found unencrypted in the SteamStub'd rerev.exe file, editing that will then cause SteamStub to refuse to launch. (I think there might be a flag that can be changed in the .bind section to skip verifying EXE contents, but not sure about that)

I just used Steamless to remove the SteamStub layer first, and then the EXE can be edited fine without issue. (note that launching EXE directly doesn't seem to work, has to be ran through the Steam launcher)

I don't know the policy about recommending tools like Steamless in main articles though, so haven't added it there. Maybe asking users to edit both EXE+INI along with using Steamless tool is a bit much too... maybe I'll make a small DLL hook to edit it in memory soon.

Got a DLL hook for it working, didn't take too long luckily: https://community.pcgamingwiki.com/files/file/2343-rerevhook-allows-custom-resolutions-in-re-revelations/