there is 65 pages here and a tips page.
I don't have anything more to add, sorry
There is no new trick to give you here, and am sorry I cannot give you the answer.
There may be several users who we just cannot get the trainer to work for them. We wish that EAC wasn't being used and we could go about making normal trainers for this title and they had an offline single player mode that was separate and playable without all this rootkit kernal malware baggage added.
best,
Cal
Thanks your your awesome work as always Cal, maybe when the devs do another patch it might get sorted who knows ill just keep trying to figure it out. I understand the situation you guys are in just sucks that it appears to be a bit hit in miss for some of us is all. Thanks as always you guys are the best.
Edit for bad grammer
[Edited by muxacb07, 3/18/2018 6:42:25 PM]
Our 1.0.3 trainer is working fine for current legitimate 1.0.3 steam release. We do not own any special editions or other platform or editions or collector's edition or anything else.
best,
Cal
I definitely have the steam version can provide any debug or anything honestly to try and help. Been with CH since 2010, I know that some versions are wonky and what not but I have been through just about every troubleshooting I can think of from past to current methods. I know I am not alone with this issue as other have posted about similar activation without options applying correctly. I just hope that somehow the change between the previous version of 1.0.2 and 1.0.3 gives some insight as to where the new error occurred. My previous version of the game was already running at dx11 so I know its not a directx issue. Window anti virus seems to be one that many use that have no issues. I just have never had an issue with any trainer I have used that hasn't been fixed by going through all of the trouble shooting. Every time there is a post I check to see if there is something I missed but i have tried all 65 pages of different methods with no avail yet.
I too believe that it may be a directx issue. My next move is too see if my Nvidia software may be the culprit. Maybe its overriding the launcher setting it dx11 and forcing it to dx12 through the card. IDK i may be reaching but its worth a shot at this point. I do run the geforce experience so i will have a look at it tomorrow.
Thanks again to all who have taken the time to gather intel and try to help us all out. Hopefully with all of our efforts we can get to the bottom of this.
Thanks also to the moderators for their patience with us. :P