Return of Reckoning

Hopefully someone knows what's going on.

I can load up RoR fine but after 10 secs the game just closes on me. Any tips or advice?

Cheers

Hey, hard to tell with this information but a few questions for you:
1. Have you played fine before or is this the first time you try to play?
2. Recently, the RoR team added a "Repair" button in the game launcher (you need to click on the small cogwheel at the top-right corner of the launcher window), have you tried using that one to fix any client files that may be corrupted?

Run in 64 bit - settings in your launcher. Keep graphics to a minimum and work your way up testing capabilities.

I'm getting a similar issue as well. I can load in the game and have a crash occur within the same timeframe. I made sure to use the new launcher, run in 64bit and toning down graphics settings does not seem to solve it either. If the game does allow me to play, zoning into a scenario almost always will crash.
One attempt that allowed me to get in, I asked in the /Advice chat and was told to delete my cache which did not solve the issue either.

I ended up deleting all the files from my pc and start from scratch and that worked but now my PC thinks the launcher is a Trojan

Findy210 wrote: ↑Thu May 21, 2020 11:29 pm I ended up deleting all the files from my pc and start from scratch and that worked but now my PC thinks the launcher is a Trojan

Which has pretty much nothing to do with this topic, shares the exact same issue with a dozen other already answered topics, and is covered in the link in big red box at the top of this subforum.

You need to whitelist the WAR folder. The launcher will get flagged pretty much anytime we update it because of how it works and the fact that it is a relatively unknown file. Over time as antivirus companies pick up the automatic submissions and review them manually, they will remove it from their heuristic flagging as the launcher is safe. We're not stupid in thinking that adding viruses to the launcher is a potential way to gain players, it's just a false positive driven by heuristic scanning.