rob10

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.

Change the 1st 2 numbers to 0 (so (0,0,600,700) and that should put your kneeboard in the top left corner of your main screen.  With my numbers it will be trying to display off the right hand side of you main screen and below your MFD's (I have my MFD's stacked vertically beside my main screen).

It's a current bug that has been reported in multiple threads already.

I use Elevenlabs.io
It gives you lots of options for voices and you can tweak the voices to create even more different voices.  You need to play around with what you use as text to get the results you want.  Sometimes you need to spell things more phonetically rather than grammatically correctly to get it pronounced the way you want (for example for co-ordinates, I use co-ordinits to get it to sound the way I want.  Also using 2 comma's will give you a slightly longer pause between words (or numbers) i.e. when giving co-ordinates (i.e use "North 2,, 3,, point 4,, 3,, 4" rather than "North 2 3 point 4 3 4").

You DON'T want to set it as A-A for guidance to tanker.  Just set it the same way you set it for a ground station.
A-A is strictly for fighter to fighter and just provides distance information (no direction).

In fairness, there are a number of people in that and other 403 threads who said they didn't have it bound but then came back and reported it was bound and that was their problem.

It should say MT Preview in front of the version number at the bottom right of the splash screen.

I check your Sinai mission and I can confirm you have no waypoints, so it's doing what it should.  You can set it up the way razo+r mentioned or set a sequence of waypoints for them to follow with an "advanced waypoint option" of "switch waypoint" to set it back to the 1st one you want it to start at.  This will make it go around and around.

No, TCN compass spinning is NOT related in any way to INS.  When the TCN is spinning that means that it is powered ON but has no valid signal coming in (ie out of range of tuned TCN, wrong TCN freq entered etc).  It was reported fixed in today's hotfix, but in the 1st version of 2.9 if you were in MP and didn't have Voice Chat checked in both client and server you got a really restricted range (like 20 nm).

If it's an AWAC's datalink contact that's all you should need to do (assuming the server is set up correctly, and I'm going to guess that it is).
If you want to link to one of the other friendly fighter aircraft you put the SA captains bars over it and press on of the two OSB's on the bottom left of the SA page.  Wags did a good U-Tube video that you can find in the Hornet mini-updates thread that I'd highly recommend you watch.

Known bug if you try to use the Stennis and don't have the Supercarrier module currently.  Reported to be fix in next patch.

The MAV needs to be boresighted to the TGP.  If you start from ramp you will need to do this yourself.  If you air spawn this will be simulated as already done so you don't need to do it.  Lots of info in manuals and forums on how to do this.

The destruction shouldn't really matter (although I would go switched just on principle since once can be a little funky sometimes IMO).  The tally trigger definitely wants to be SWITCHED.  The other thing to check is to make sure your names are IDENTICAL.  It's easy for a capital letter to sneak in or miss a letter and suddenly you're not playing with the same name.  Also having an output of your tally on screen after it adds (or even just when the add trigger fires) can help narrow down where the problem is.  If you can post a screen shot of your triggers or a copy of your .miz file to look at would help.

Are you entering the co-ordinates as Degrees Minutes Seconds (DDMMSS.SS) versus Degrees Minutes decimal Minutes (DDMM.MMMM)?  Change co-ordinate input on the UFC page of the HSI.  Co-ordinates in the briefing for this mission are DMS.

Just a weird one off bug then likely.  Maybe you hit the exact spot where there is a terrain issue.  INS should have no impact on being able to move the plane at all.

The little trick with the F-18 is the fact that ACLS (automatic carrier landing system) got added.  The first press of the D/L button brings up the ACLS controls and parameters.  You need to press it 2X (should have AIC at the top of the UFC options) then turn it on to activate the D/L function.  What you've been doing is just turning on the ACLS.  It's likely not updated in most documentation yet.

From what I read of your post it sounds like you are pressing the release button WHEN the 2nd release cue hits?  If so that's your problem.  You need to PRESS AND HOLD the release button any time after the 1st cue until you go through the 2nd cue and weapons release.

You can try RIGHT clicking on that cell and it should give you a drop down with options to select what you want.

If you have the gear warning and pulsing light then gear is damaged and that's your problem.  Saw that recently when I came in too high and tried to slam the plane onto the deck to catch the wire 😳 (yes, I should have waved off).  Used left throttle and right toe brake to limp out of the landing area, but no real steering.

Are you on a slightly older version that still allows you to use Game Avionics mode?  Uncheck that would be the 1st likely culprit.
Are your flaps at 1/2 (or full) when you're taking off?  If you have it mapped to a physical switch in your controllers it might be setting it to AUTO on the hot start even if you don't touch anything if it is physically set there.

I use 50 millisec on most, bumped to 75 or 100 in a few cases if I don't get it to register consistently.
If you use a UFC or keyboard you likely don't need to worry about this.  If you are using something else to emulate button press, DCS won't register the really quick press (near instantaneous) that it may send and you'll get inconsistent presses, thus you need to add a "hold it down" time to get consistency.

You get there indirectly 🙂.  Click on "DCS" in the upper left (that takes you to the main DCS page rather than the forums), then hover over the "DOWNLOADS" in the black bar on the main page (the same layout as you see on the user files page) and select "USER FILES" in the dropdown that pops up.  Hope that answers what you're looking for.