search

IntelSDM / RustDMACheat

Small DMA Cheat For Rust
MIT License
182 stars 55 forks source link

Error on 25 line in BasePlayer.cpp (delete BaseMovementInstance;) #14

Closed MaRf1Mm closed 8 months ago

MaRf1Mm commented 8 months ago

Good day, everything was working fine for 2 weeks, but after the recent update, this error started to appear (Exception thrown at 0x00007FFE20935BB6 (ntdll.dll) in RustDMA.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.) as well as (Unhandled exception at 0x00007FFE20A0F279 (ntdll.dll) in RustDMA.exe: 0xC0000374: A heap has been corrupted (parameters: 0x00007FFE20A787F0)). After which the console closes. Checking with the debugger, the error occurs on line 25 in BasePlayer.cpp. I checked and rechecked the offsets and everything from .scripts, they match with the recent game update. I've been trying to solve the problem for 4 hours and decided to seek help here, I would be grateful for any advice.

IntelSDM commented 8 months ago

Sadly, my DMA card isn't exactly working right now. I pushed an update to address this issue. I changed the BaseMovementInstance to be a smart pointer, which it should have already been, so there shouldn't be an error deconstructing it, it will do it automatically. I also updated whatever offsets and classes I could see were outdated. All of the BasePlayer fields seemed to be shifted by 16 bits(0xA). Since I couldn't test; some stuff could still be outdated.

MaRf1Mm commented 8 months ago

Sadly, my DMA card isn't exactly working right now. I pushed an update to address this issue. I changed the BaseMovementInstance to be a smart pointer, which it should have already been, so there shouldn't be an error deconstructing it, it will do it automatically. I also updated whatever offsets and classes I could see were outdated. All of the BasePlayer fields seemed to be shifted by 16 bits(0xA). Since I couldn't test; some stuff could still be outdated.

No problem, take your time, I didn't even expect such a quick response. I'll go check the update and report back here if anything changes.

MaRf1Mm commented 8 months ago

So, first off, this fixed the error and everything is now loading correctly. However, now every time the console outputs BAD DTB: PID=27548 DTB=40000007587a7000, errors pop up on the screen. Any ideas? image Upd: Errors on screen disappear after some time but i still get this error in Rust DMA console

IntelSDM commented 8 months ago

The bad PID issue is fine, don't worry about it. The text on the screen is saying that the console system interaction is incorrect. I will quickly look into that.