Cheat Engine

paul44 · Last edited by paul44 on Mon Aug 05, 2024 10:50 am; edited 2 times in total

I have a user playing Watch Dogs, and my table makes the game crash. Following my instructions, s/he can produce following error:
[ https://ibb.co/mGhzbnM ]

I can not recall ever been confronted with this kind of error. Despite several suggestions, no breakthrough sofar. My question:
What can i ask/instruct gamer to do in order to pinpoint the - possible - offending cheat ? Based on the image/error, is there anything i can check out myself ? (fyi: i can not recall having crashed once while building the table, unless for "obvious" reasons ~ like pop-ing but not push-ing eg Shocked

)

thx in advance for any suggestion.

Some considerations:
1. he's the 1st to report crashing (and the table has been downloaded quite a few times)
2. he can not reproduce the error specifically: either following a specific event/path and/or using/enabling specific cheats.
3. however: he confirmed using additional mods (nexus); one of which almost certainly involves opcode injection(s)
=> i did ask to runtest on a clean installment (reply pending...)
4. none of the other tables/trainers make the game crash...

Dark Byte · Posted: Sat Jul 06, 2024 10:13 am Post subject:

The stack looks like it's a directx hook that might be malfunctioning/setting invalid return parameters

try making him run in windowed mode only

paul44 · Posted: Sun Jul 07, 2024 6:52 am Post subject: directx exceptional...?

I assume that seeing them directx_dll there on the stack are not what one can expect normally ?!
I'll pass on the info, but considering he hasn't replied back since last week - and his responsetime is usually within a day - I'm going to assume he is on (student) holiday...
I've put the request on hold - for about a month - and close it thereafter with (whatever) outcome...

My suggestions to him:
1. try windowed
2. run with "clean" game_files (no mods)
3. and/or do not enable FOV (only option in my table that could "directly" related to directx)
4. update directx/vc++/gpu drivers
5. disable (temporarily) any gpu-related tooling
6. other Cool

thx for quick reply btw.

-EDIT-
user reported back earlier this month: indeed, one of the nexusmods interfered; restoring original gamefiles cause no crashing...

tip: if you encounter same issue, either contact that user @FRF or check nexusmod forum in WD topic