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.

Missions I have made on this map using modern equipment are having issues. Using the Viper and locking on to stationary ground targets with the Tpod with JDAM bombs. The Tpod is on the target and all looks great and the bomb is released. The bombs hits way off target, like several city blocks off target. This is being done in the Dunkirk area. I aim at a radar site and it impact several hundred feet before the target. I even tried hitting a stationary cargo ship and the same thing happens. It seems like the Tpod is showing you locked on the target but the info you get is for a different spot or on different ground level then what we are seeing. I even place a target right on the beach and it show a ground level of 10 feet in the Tpod but the impact is a totally different impact point. This is about the best way I can explain it. I shoot Mavericks and they go straight to the target so confused on what the problem could be.

Yeah I came here looking before I hit buy. Minsky pretty much answered that. Working a double so will get in the morning. Thanks for the answer.

I tried different vehicles as well. So it wasn't just on type. I am glad you were able to recreate it. After the update it was a huge improvement because I could see SAM units 58nm away that were off road with TGP. But on road I was struggling to see even to a few thousand feet or less.

I check to see if this has been posted and didn't find. Was on Persian Gulf map yesterday. Since the FLIR update whether in White hot or Black hot, the vehicles are matching the roads heat signature. Making it almost impossible to see or find the target on a paved road. I have tried brightness and contrast adjustments and can't see them. Any info or help would be appreciated. This is in the Viper just so you know.

I just noticed that myself today. Maybe the pilot is strong with the force and just holing it there. Sorry forgot to set single eye shot mode for my VR.

I was thinking the same thing. I own both maps. They originally state that if we already owned both it would be a smaller upgrade fee. Which I agreed with and thought was fair. But, they also may have forgotten to add the part of "if you own both". Because I was looking for the "and" part. Since already purchasing ⅔ of region. Now saying well if you only own ⅓ for small fee we give you the other ⅔. So, why should we have to pay the same upgrade amount to only get ⅓ of what we don't have.

I'm with him. I have the reverb g2 as well. I found that taking the time to line it all up made a huge difference. I went on a night mission and even the street lights were lined up. Understand that this is an area suppression weapon not a sniper rifle. It takes some practice and knowing the range you have it set for if in manual. Plus the auto is not dead accurate. Also not everyone's eyes are the same and go with what works the best for you. Trust me I have had my share of where the F... did those rounds go.

But the real pilots didn't have this feature either! Sorry I had to say it. It is hard to get used to I have pedals but have know feeling in my feet so I am screwed no matter how they set it up. I would be happy with holding a button for NWS while taxiing feature would be nice. . I just started flying the A4 and made several missions. So I am struggling with the Dif Braking. But I will find away to make it work. It is also a struggle with some of the warbirds as well.

Sorry guys work and life does put delays in things. Problem solved, I found that the sync HOTAS was checked and I unchecked it and ran the mission I had the issue to begin with. The Hind just sat there. I lately have been teaching myself to no longer use the RCtrl+Enter function. I is funny how there were no control inputs made by me that was causing this. The stick is in its neutral position and throttle pulled all the way back. So, not sure what was causing the stick to show in that position. After unchecking the sync box and tested in single and multiplayer it fixed it and I thank all of you for the help. I have been flying the Hind since release and never had the issue until this last update. I am glad it was a simple fix. Again thank you all.

Will check later. But it is just the Hind.