Seconding BlackDeath4’s report - getting the same access violation
It doesn’t crash immediately, but it randomly just freezes up after a while and just crashes, giving the same error code.
Doesn’t seem to affect campaign of any sorts, but it happens 100% of the time w/ Skirmishes.
As long as you have even 1 cheat on it’ll crash at some point no matter what.
I was alerted that this specific trainer was installed with a trojan, i highly suggest staying away from this one in particular. Doesnt work that great anyways @MrAntiFun
Dont worry it’s a false positive. We would for sure not upload a virus in our trainers we are a legit company that is clean of any virus. Some trainers get through AV and some get caught but can assure you its 100 % safe
The bigger problem is that its crashing in Skirmishes, which really blows considering you can only replay so many times the campaign…@BlackDeath4’s report still stands
does this work in coop skirmishes? if your friend doesnt have the cheats installed? or is it something clientside and it wont end up working. i want to give a small spook to my friend lol. thanks if anyone answers!
Hey there again. Im pretty sure this was already talked about before. But i’ve been experiencing Memory Access Violation error in skirmishes. It happens every match, i’ve tested it out myself. Hoping soon for a fix!
Hello there again! The trainer says that it cannot be loaded; Your game version may not be compatible with the trainer. You can try activating it later in game.
Used to work fine 2 months ago lol… Anyone else with this issue?
Also getting memory access violation error that crashes the game. Don’t know how to request an update in WeMod for a game that it says “up to date” on.
Generally happens after trying to place >16 PATRIOT’s or PIVADs on a skirmish, but regardless ends up killing the match within about 5 min of loading the map. Tested 1v1 and 1v7 skirmishes.
Tried uninstall, no antivirus, tried running both as administrator, tried different sequencing (game then WeMod & vice versa), all result in a memory access violation crash.
Extremely frustrating issue.