GP2Mem - live memory editor for GP2 (Safety car/additional slipstream)
Posted: 21.12.2025, 14:54
Hey folks, I finally put together something I’ve wanted for ages GP2Mem, a Windows tool that hooks into GP2 and lets you view/edit a bunch of live race/car values while the game is running.
And the fun bit is that the first Safety Car for GP2 (as far as I know) is now available. It’s implemented as a built-in script that manages the pack by controlling speed/spacing during an SC period. There’s also a slipstream script (boosts engine power when you’re tucked in behind another car) if you want crazier racing.
Project/downloads/source:
https://github.com/ilya-ssh/GP2Mem
How to use it (quick and practical):
Start GP2 via DOSBox or x86GP2_inline.exe (GP2Mem supports both)
Run GP2Mem and make sure the process name matches (default is x86GP2_inline.exe)
Start a quickrace (AI-only recommended for this step)
While you’re on the grid and the AI are revving, click Find Base (Grid) in GP2Mem this is the lock-on step so it can find the live car structs in memory
After it finds the base, you can exit the quickrace and start your real race/practice/quali
You’ll usually need to redo the “Find Base (Grid)” step each time you restart the game that’s on purpose so it stays compatible across older GP2 builds (DOSBox) and older x86 versions
What you can do in the tool:
Overview table for all cars (lap/pos, speed, throttle %, fuel, damage, etc.)
Click a car and edit stuff in tabs (Race / Timing / Controls / Flags / Tires / Aero...)
Write for one car or All to apply to everyone
Full struct browser if you want to poke around offsets/flags that aren’t fully identified yet
A couple warnings:
It’s a memory editor, so yes, you can break things if you go too hard
Avoid the replay feature while using it - it can mess up the race state
The release exe is PyInstaller, so AV warnings can happen (PyInstaller gets abused + this tool edits memory)
If anyone wants to test, suggest offsets, or help identify unknown flags issues/PRs are welcome
And the fun bit is that the first Safety Car for GP2 (as far as I know) is now available. It’s implemented as a built-in script that manages the pack by controlling speed/spacing during an SC period. There’s also a slipstream script (boosts engine power when you’re tucked in behind another car) if you want crazier racing.
Project/downloads/source:
https://github.com/ilya-ssh/GP2Mem
How to use it (quick and practical):
Start GP2 via DOSBox or x86GP2_inline.exe (GP2Mem supports both)
Run GP2Mem and make sure the process name matches (default is x86GP2_inline.exe)
Start a quickrace (AI-only recommended for this step)
While you’re on the grid and the AI are revving, click Find Base (Grid) in GP2Mem this is the lock-on step so it can find the live car structs in memory
After it finds the base, you can exit the quickrace and start your real race/practice/quali
You’ll usually need to redo the “Find Base (Grid)” step each time you restart the game that’s on purpose so it stays compatible across older GP2 builds (DOSBox) and older x86 versions
What you can do in the tool:
Overview table for all cars (lap/pos, speed, throttle %, fuel, damage, etc.)
Click a car and edit stuff in tabs (Race / Timing / Controls / Flags / Tires / Aero...)
Write for one car or All to apply to everyone
Full struct browser if you want to poke around offsets/flags that aren’t fully identified yet
A couple warnings:
It’s a memory editor, so yes, you can break things if you go too hard
Avoid the replay feature while using it - it can mess up the race state
The release exe is PyInstaller, so AV warnings can happen (PyInstaller gets abused + this tool edits memory)
If anyone wants to test, suggest offsets, or help identify unknown flags issues/PRs are welcome