All Activity

With the patch installed the game crashes after the intro thats even with the no cd fix it still crashes after the intro

Hello everyone! Today I bought the game and encountered the same issue. Searching for solutions, including disabling GSync, changing the monitor refresh rate, and toggling all other relevant settings in the game, in the Nvidia Control Panel, and in Windows yielded nothing. I can confirm that the only working solution is the one discussed in this thread. Since the patches are long outdated, I spent some time examining GameAssembly.dll and want to share a working method to manually fix the stuttering issue in the current and potentially any future version of the game. We already know that the issue arises from the static update timer setting of the Unity engine, and editing GameAssembly.dll is required to synchronize the engine timer (specifically, the fixedDeltaTime function) with the FPS you are playing at. I will try to describe everything as detailed as possible so it is helpful for players without any IT background. I am almost certain that in-game graphics settings do not affect the problem, nor do the relevant parameters in the Nvidia Control Panel. I haven't tested all possible combinations, but in my case, it is set up and working as described below. Game settings: Build 21464562 from 23 January 2026 (https://steamdb.info/patchnotes/21464562), Steam version, all settings on maximum, fullscreen mode. Nvidia Control Panel settings (global for all games): VSync depends on the application (i.e., enabled since the game has no VSync setting and it's enabled by default), GSync is enabled in fullscreen and windowed modes, 118 FPS cap (for reliable GSync operation), Low Latency Mode is set to Ultra. System: Win 11 Pro 25H2, RTX 5090, Nvidia Display Driver 591.86, 120Hz monitor. Now let's edit GameAssembly.dll. I didn't arrive at this method immediately; at first, I tried to find the necessary offset using Il2CppDumper and analyzing Assembly-CSharp.dll via dnSpy, but came to the conclusion that the easiest way is to... test the 3 offsets in GameAssembly.dll one by one 🙂 Yes, it turned out to be that simple. The library contained exactly 3 occurrences of the value 0.02 (the fraction of a second that passes between two logical engine updates), which is the engine timer for 50 updates per second. So let's begin. Method for build 21464562: Find a HEX editor of your choice. I use the classic HxD, but in this tutorial, we will use https://web.imhex.werwolv.net for simplicity. Locate the GameAssembly.dll file, it is in the game's root directory. Right-click the game in Steam -> Manage -> Browse local files. Make a backup of the file! Open the file in the HEX editor via File -> Open File or by dragging and dropping. Perform a search via View -> Find. In the Find panel that opens, select the Numeric Value mode, enter 0.02 in the Value field, select the float type from the dropdown list, and click the magnifying glass icon. It should find 3 offsets: 0x01F983D8, 0x022972B8, 0x0234A9B5, but there might be more, fewer, or different offset values depending on when you are reading this tutorial and how many updates have been released. If your offsets do not match the tutorial, proceed to the method of testing values one by one below. We need the second offset 0x022972B8. Double-click it in the search results panel, and in the editor panel, you will jump to this offset. Copy the required FLOAT (not HEX and not FPS) value (without spaces, just the value) from the list below corresponding to your configuration or target FPS. Return to the HEX editor. To the right of the editor panel is the Data Inspector panel; find the float field there, make sure it says 0.02. If it is not 0.02, start over, you are doing something wrong. Double-click the float field and paste the copied FLOAT value into it, then press Enter to save the changes. Save the file via File -> Save As... It will download as file.bin, rename it to GameAssembly.dll, and replace the original GameAssembly.dll in the game folder. Launch the game and test it. If something went wrong, restore the file from your backup or verify the game files in Steam and start over. Method for any build: If your build is not 21464562, if more or fewer than 3 offsets are found, or if the offsets do not match 0x01F983D8, 0x022972B8, 0x0234A9B5, then the easiest option is to test the offsets one by one, thankfully there are only 3 of them. You need to do the exact same things described above but with all found offsets in a row. Follow steps 1-4, find a certain number of offsets. If there are three offsets, the second one is most likely the correct one. Edit it as described in steps 5-9, and launch the game. If it didn't work, restore the GameAssembly.dll file from the backup or by verifying files in Steam, try with another offset, and repeat until successful. If none of the offsets worked, it means the developers changed the engine update timer and it is no longer equal to 0.02. Here you will need to find a new value, but that's a completely different story 🙂 List of values for different FPS with and without GSync: These Float values are calculated with maximum machine precision (little-endian float), so the engine physics will work without losing synchronization, provided that your target FPS matches. FPS - FLOAT - HEX 58 - 0.01724138 - CB 3D 8D 3C 60 - 0.01666667 - 89 88 88 3C 73 - 0.01369863 - 38 70 60 3C 75 - 0.01333333 - 0E 74 5A 3C 98 - 0.01020408 - 05 2F 27 3C 100 - 0.01000000 - 0A D7 23 3C 118 - 0.00847458 - F3 D8 0A 3C 120 - 0.00833333 - 89 88 08 3C 142 - 0.00704225 - B4 C2 E6 3B 144 - 0.00694444 - 39 8E E3 3B 163 - 0.00613497 - DA 07 C9 3B 165 - 0.00606061 - 0C 98 C6 3B I hope I helped someone deal with this issue. I highly doubt I will return to this forum after beating the game, but I will monitor questions for a while if there are any left. Good luck with your playthrough everyone 🙂

I have a GamesSir Nova Lite controller and the game wont even start IF I have the controller connected to the PC (Dongle or USB), starting the game and connecting the controller later make the game not recognize the controller. Using the files on this topic I was able to open the game with the controller plugged on the PC and to select the controller on the game Control Options, but no input in the controller affects the game. Also lots of throtlling. It is already an improvement, so thank you. This solved the issue for me. Game start, no trothttling and controller working. Thank you very much.

Thank you. Works amazing.

@AlphaYellow Yes, i did read your description, but can you please make a fix for this exe? It´s from the current GOG Version. RCT3.exe

Sorry, I can't tell for sure if Jedi Survivor has the same problem with animation stuttering or if this variable exist in that game.

Hello! So if you're referring to my file, i used a hex editor, to get the changes in the first file, into the new exe from GoG. If you're using steam there was no such update. I hope that helps.

Is there something like this but for Fallen Order? That game is quite rough on older CPUs as well.

Hello! Does anyone know what changes have been made to the .exe file available for download here? I am asking because the GoG version with the latest patch - 1.5 (CS) GOG 0.2 dated by 2024.11.13 (as far as I understand made by GoG themselves) comes without an Ultrawide fix. That's understandable. Because of that, I am asking for help to understand what has been changed in the modded .exe file, so that there will be an option to modify the GoG-optimised .exe file. I hope that my point is clear.

Why isn't there a 1366x768?

Press Alt+Tab and return to the game later

Hello! Played with this fix a couple of years ago with some dll's to get the achievements work (steam version). Can't find them now, can smb pls post a link? UPD: found them 🙂 It turned out they are of no use anymore. There is a much more simple way to bypass new anti-cheat.