- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 142
- Reaction score
- 7
Been messing around with internal hooks lately and hit a wall with ARC Raiders.
I managed to get the DX12 render hook running smooth, but I'm consistently running into the THEIA crash. It triggers regardless of whether I'm hitting the render thread or just performing basic memory reads. It doesn't seem to be a standard signature detection or a ban wave trigger, as the account remains untouched, but it definitely feels like some form of anti-tamper or memory integrity check kicking in.
Has anyone encountered this specific crash when hooking ARC? I'm trying to figure out if it's a pointer validation issue or if their anti-tamper is flagging the hook entry point during repetitive access.
I'm relatively new to the internal scene, so I'm curious if the devs are using a custom exception handler to catch illegal memory access or if there's a specific routine I need to bypass to keep the hook persistent.
If anyone has experience with this engine or has successfully bypassed this check, drop some wisdom. Are you guys hooking the swapchain or going for something deeper? Any tips on masking the hook or handling these repetitive reads would be massive.
I managed to get the DX12 render hook running smooth, but I'm consistently running into the THEIA crash. It triggers regardless of whether I'm hitting the render thread or just performing basic memory reads. It doesn't seem to be a standard signature detection or a ban wave trigger, as the account remains untouched, but it definitely feels like some form of anti-tamper or memory integrity check kicking in.
Has anyone encountered this specific crash when hooking ARC? I'm trying to figure out if it's a pointer validation issue or if their anti-tamper is flagging the hook entry point during repetitive access.
- Environment: DX12 hook using standard ImGui overlay.
- The Issue: Instant THEIA crash on repetitive memory calls or frame injection.
- Current Status: Account is UD, so it's likely a protection/integrity trap rather than a server-side ban.
I'm relatively new to the internal scene, so I'm curious if the devs are using a custom exception handler to catch illegal memory access or if there's a specific routine I need to bypass to keep the hook persistent.
If anyone has experience with this engine or has successfully bypassed this check, drop some wisdom. Are you guys hooking the swapchain or going for something deeper? Any tips on masking the hook or handling these repetitive reads would be massive.
