Cueball

Was still having this issue and was going through others posting to find the one about the core mod F4 folder. After failed attempts, I went and excluded every F4 folder since just doing it to the DCS folder wasn't enough. After I added the Coremod F4 folder to the list and ran a repair again. It all finally worked. I was about scream at Heatblur and DCS that this is nuts. The game restarted with no authentication notices and could get on multi-player to select the F4. Only part that really sucked was spent all that time and now have to goto bed. I do thank all of you for posting fixes to try.

removed from exclusion then repair. put back in exclusion then repaired again then worked

Its not rude and not new to this. but all ran fine i do the update and all goes to <profanity>. Started with F4 not authorized then was 7 modules and 5 terrains. When running repair and cleanup it wanted to delete 700 files. quick starts and so on for for even the base aircraft. Did the anti virus thing more than once.

did newest update and got the window stating almost all maps and modules are not authorized. i did a clean up and repair still got it.

I took out the updated CJS Super Hornet mod. Ran a deep clean and restarted. Then worked fine and could create or edit missions. That was the only thing I added since the last update. Will try to install mod and see if it happens again.

Trying to open mission editor since update. It is stuck at "Terrain Graphics Init: 97. Caucasus ng5" I have done repairs and clean ups. Nothing working. But game itself runs fine.

This plus a video I saw fixed it. Thank you.

my other maps the RUN is highlighted green. But the RUN under my Sinai map is shaded out. not letting me run that map only

Thank you I will try this when I get home. I was very surprised when I saw the GBU 54's were part of the update. Those are vicious little boomers.

Since the update I can see the laser in broad day light. From the drone all the way to the target. It's a thin black line. Don't know if it is do to new settings or what. But found it humorous think wow VR got really sharper.

The Tpod was on target but the bombs we way, way off. Changed the date and they were spot on.

I ran it this same issue using modern planes in Normandy. JDAM bombs were way off. It never crossed my mind to check the date setting.

Is this the issue when doing a rearm and he sorta goes stupid in trying to slave to targets and so on.

Thank you that fixed it. Now I know. 🕹🕹

I will check that when I get home. It never crossed my mind to check the date. Yeah I even checked on waypoints and noticed where it was placed vs where the tpod was pointing. It was around 1.36nm off. Will let you know if that works.