Nealius

The only sure way to have statics and avoid handler/director issues is to use uncontrolled AI spawning on the slots. The drawbacks to this are that you have little to no control over where they spawn, you get jets spawned where there should be helo parking, you can't add cranes or tugs, and the spawn slot sizing issues online causes "delayed to start" issues with Tomcat clients. Who then, once spawned in, have their fuel weight doubled from an unsquashable bug that's been around for the better part of 5 years now, severely degrading their flight performance.

Delay AI spawn by 1 second and they will skip the sixpac slots. Not lua editing needed.

We should have a lot more trees, especially in the Korengal area mountains.

This is correct. Squadron code and letter code have the same placement regardless of port/starboard. Typically squadron code always forward of the roundel, aircraft letter aft. There are some exceptions like the Mosquito where this is reversed because there's not enough space between the roundel and wing root for two letters--some squadrons using smaller fonts crammed them in there though. Some P-51 squadrons had the aircraft code on the vert stab instead of fuselage, etc. 
The system thinks L1949 is the serial number, BI is the squadron code, and L is the aircraft code because the system is designed to work with real codes/serial numbers that follow that logic.
(Fun fact, L1949 was registered to a Hawker Hurricane that was lost in May 1940. BI doesn't appear to belong to a specific squadron but was allocated to RAF Holme-on-Spalding Moore.)

SH70 mod would need to be installed on the server as well.

GATOR system. Basically landmines scattered by cluster munition cannisters: https://en.wikipedia.org/wiki/GATOR_mine_system

This is normal. Track files only work when played back on the same version they were recorded on.

Demos will vary based on who's doing it, but the official routine with their parameters (speed, G, altitude, etc.) and descriptions is publically available in AFMAN11-246V1, downloadable direct from USAF e-publications site.
Despite it being public and unrestricted I cannot post it directly here since it's post-1980.

It works for you with the VAICOM PTT bound to RAlt+\? I haven't used VAICOM since we got the commands to cycle through the comms menu, but for me when I press RAlt+\ the PTT switch moves, receive/transmit light indicates transmission, I hear a click, but no comms menu ever pops up. 
The Mossie manual still says RAlt+\ for realistic communications as well. 
 
 
Found the problem:
Update enabled Easy Comms by default.
@NineLine why are updates messing with user settings like this? Our settings should remain untouched by updates.

Make sure wind speed is higher than 6kts and aligned down that runway. DCS in general has issues with ILS not being turned on unless the winds are specific directions and speeds, but it's particularly bad on Caucasus map for some reason.

App hang was starting to expand to other missions as well, even ones created by other users. Potential fix was clearing the DCS folder in AppData/Local/Temp. 

I brought this up not too long ago because I also found the SEAD task logic to be......illogical. Basically to get them to attack designated targets and ignore TOO, set their task as Gound Attack (or just keep SEAD task and disable the SEAD action), then set attack group/unit and such as desired.
 
 

The Viper has a confusing Bingo system. More info here:
 

I use the Quest 2 as well. There's a couple different things at play here. Like others mentioned, there's the fact that some units haven't been updated for the new FLIR, and units have to have their engine(s) running or have recently fired their weapons to show up as hot. 
What I've found challenging is having to reprogram my brain to look for smaller, oddly-shaped heat signatures after years of unrealistically glowing vehicles. Now we have a more realistic representation of only the vehicle's hot areas appearing as hot, so you won't be seeing a silhouette of a vehicle, and rather a blob around the engine compartment, or a hot tank barrel. This makes it more challenging to find the targets. 
As a side note, this being a question/discussion and not a bug report, nor in the bug report section, I find the tag "cannot reproduce and missing trackfile" unneeded. 

Brochure numbers are minimum 200ft maximum 550kts (I think?). In DCS any drop below 500ft results in the rocket motors failing to ignite, and anything below 800-1000ft won't allow a proper vertical shot into the runway. 
In my tests, something like 600ft 500kts the impact point is so low the sight wouldn't even be visible, so it's literally guesswork using the dashboard as a fixed sight.