rob10

You can tweak it's location in the lua, but pretty sure that breaks IC.  That's the only "permanent" solution I know of.

Unfortunately 10 GB is likely not enough space for the update to download and unpack itself for install (since likely at least some of the 10 GB is tied up by Windows too).  Your solution is to find a way to make more space on the drive or expand your storage.

Post a track and you'll get much better answers.
Did you slew a TPOD or anything to get on target?  If so, did you cursor zero to get rid of the offset after weapon release?

The UH-60L and/or MH-60R mods are causing issues for some people with the current DCS build.  You may have to wait for those mods to get updated to use them again.

I believe that SPACE is the default trigger binding, which is why pressing it first works (you're sending "trigger" (space) rather than "weapons release" (right alt space)).

ED have already publicly stated that FC3 will NOT get any further aircraft.

SLOW DOWN! 🙂  Seriously, if you're going too fast (especially when you engage it) your front wheel will start to slip and you won't turn (or may turn odd directions even though the wheel is turned).  Even more noticeable on ground runways.
EDIT TO ADD: and too fast is not very fast at all (i.e. you don't need to be flying across the deck to be too fast)

Nineline posted a pretty detailed explanation of why you won't be getting any sea on the Afghanistan map.
 

Your HUD is indicating what direction your nose is facing.  The DIAMOND you are pointing at in the HSI page is the GROUND TRACK (i.e. what direction you are actually moving in relation to ground).  It's not always intuitive, but because the BOAT is moving, so are you (even though you are parked on deck with wheel brakes/chocks).  If you look at about 205 deg on the HSI you'll see a line on the compass rose.  That is own ship (i.e. your plane) heading indicator (i.e. where your nose is pointing, rather than what direction you are actually moving).
You'll also see that disconnect if you're in the air and have a significant side wind.  Your nose will face one direction, but the diamond on the HSI will be slightly off because it's showing where you are actually travelling since the wind is pushing you sideways.  This shows up more on the boat because you are at nearly 90 degrees difference.
On the ground your nose and what direction you are moving will be the same (or nearly so), so they will match up.  Notice the line on the outside of the compass rose in this case matches up with the diamond.

I'm guessing you're using Oculus VR?  See this thread.

Make sure you are in 1/2 or FULL flaps when you take off.  If you take off in AUTO flaps you can have this issue.

Console dimmer control, middle of panel to right of your seat IIRC.  There are a bunch of controls there and play with them to see which one does what you want.  Also kick master lighting to NIGHT or NVG.

After you turned off your anti-virus, Windows Defender would automatically be activated.  Have you tried setting exceptions for the DCS folders in it?  And to confirm, you had antivirus off when you did repair?  It may have quarantined a file or two such that they are now missing.

What are you running for Antivirus?  That has been causing some issues with the latest update

Just carry on.  As much as there is talk about "unification" all it means is that they are only releasing one build at a time for both of the "old" systems.  All stable was was an older version of OB.  Now instead of OB getting a number of updates then Stable getting one update to bring it to the same spot there is only one build released at a time for everyone.  Sounds like they may clean up folder names down the road, but for now you can run with whatever you have currently and you won't notice a difference. Both old OB and Stable people will be running the same thing (even though it may reside in OB folder on one persons computer and Stable folder on anothers).

Uncheck the PTC option in your Oculus and restart.  It should downgrade the version of Oculus software and solve the issue.

Your log is showing at least remnants of the UH-60 mod which has caused crashing issues with current build.  Try removing anything related from Saved Games (repair won't touch anything in there).  Worst case RENAME your DCS Saved Games folder (so that you can change it back if it's not the cause) and try running again.  If it does, then something in that folder is the problem.

To expand on the answer above: when you have a MAV SELECTED (IR or LASER) in STORES, it takes complete priority of the RAID/FOV button.  Doesn't matter if the MAV is up on a DDI or if a MAV is up on DDI but doesn't have priority, the RAID/FOV button will work on the MAV (which really only does anything for the IR MAV since you can't change FOV/sensor type on LASER MAV's , but behaviour is the same for both).  You CAN have them loaded and still use the RAID/FOV button to change FOV/IR/CCD on the pod as long as no MAV is selected in the STORES page.

Yep.  IIRC around the same time they lifted the limit on how far you could see with the ATFLIR, but a bit ago now it got pushed out from 8 nm to 15ish.

I use AutoHotKey (free) to push the required buttons to set things up.

Only other think I can suggest is RENAMING your Saved Games folder and see if your bindings file is messed up somehow (don't delete it in case it doesn't solve your problem you change name back).

Have you changed the callsign for those units?  Currently the info in that tab defaults to whatever the Callsign is when you place the unit and don't update when you change it.  Would that make sense to what you're seeing?  Definitely a pain.

Yup.  That's as IRL, so correct as is.  If you look closely it's where the 2 pieces of the HUD overlap (and are at different angles), so depending the angle you are looking at it from it looks like a blank zone.

Since one of the last couple of builds the EXT LIGHTS MASTER switch is no longer ON by default.  You now have to manually turn it on yourself in a cold start if you want external lights.

Any chance you have a modifier "stuck" ON or a modifier switch that you've forgotten about that you've managed to switch on?  In either of those cases a keypress isn't sending what you think it is which might explain the symptoms.