Art-J

As mentioned by BN in the other thread, they have to wait for the Steam sale to end later today before remaster becomes available.

Gyro AH not self - correcting in any phase of flight has been a DCS problem for many years and affects all warbirds. Brit ones are just affected the most since they lack cage/uncage AH feature that US and German ones have. We've been recently told it might be reviewed in the future. More info here:
 

To each his own, but from my own experience I still believe using "load profile" button in control options screen to import old bindings from backup files is faster and easier way of getting the controls sorted on new PC / Windows than faffing around with creating new diff.luas and renaming them (or copying their contents).
The bloody button is there for a reason, why not using it then. True, it only allows importing backup diff.lua files one by one (per each aircraft and each controller), which will require some extra mouse clicks, but it's still faster and more foolproof method in my opinion. No extra apps or batch files necessary either.
 

Not sure about all versions of J79, but in the one I saw at museum, the first stage behind supporting struts was variable inlet guide vane stage - ie. it doesn't spin, only adjusts AoA of blades.
So what you see on the video might be roughly correct, but I'm sure devs will chime in and reply.

Sounds very much like other axis (most likely on other device) is bound to throttle lever as well.
Unwanted, duplicate assignments are "normal" in DCS, double check axis option screen again and get rid of them.

I've read in the other thread that it happens if you still run DCS in single-threaded mode.

Since the problem is somehow default controls-related, have you tried clearing first ALL default throttle assignments, including keyboard ones? THEN restarting DCS and trying to reassign again? When I had similar problem with F-86 axes, I had to restart the game to make the changes "stick" and red marks disappear for good.
For reference, grab my diff.lua for warthog throttle, which works OK for me in 2.9.6. Obviously, it won't work on your PC because of USB ID, but maybe you'll be able to compare its lines with your old diff.lua. For the record I use left lever for throttle and right one for prop RPM. Also, screen shows how they look on my controls options page.

Throttle - HOTAS Warthog {839B5A00-446A-11ea-8002-444553540000}.diff.lua

It seems 2.9.6 patch turned easy comms option on for many (if not all) users. That might be the culprit in your case as well.

It's been explained elsewhere in one of similar threads on this very subject that warbirds damage and AI behaviour has not been programmed with missiles in mind so such combo just isn't going to work correctly now or in forseeable future.
I suppose only period-correct WGr 21 and R4M can yield more plausible results but haven't tried them myself.

You might take a look if you've got folders called _downloads and _backup located in your root DCS folder and if there's any trash left there (leftovers from failed update process and from modded files being replaced with stock ones respectively).
Other than that, however, 228 GB is pretty small size for DCS and not unusual if there are any maps amongst these "3-4 modules" of yours.

What do you mean? Threads to discuss the latest newsletters? These are located in  newsletter section of the forum now:
 

Do the usual DCS troubleshooting then: make sure there are no active mods not only in game root folder, but also in Saved Games location, then run repair command, preferrably the "slow" one. What you see is just some texture files missing, if there are no mods interfering with the game, repair will download and reinstall these.

Keep in mind that by definition tracks in DCS have never been  backwards-compatible, especially if an update is a big one and contains many changes to this or that module. I don't think the replay system improvements introduced in 2.9 were meant to change that, they were supposed to increase replay accuracy but within the same version number.
If some of the older tracks still work after an update or two, it's an exception rather than the rule. Expect them to become broken eventually.

Well, the last thing that needs to be tried then is temporary removal of all custom mods and apps from Saved Games location, whether they are 109-related or not. You've got quite a few of these, judging from your log. Then launch the game and see what happens.
Keep in mind that repair and cleanup procedure fixes the main game folder only, but does nothing to content in Saved Games folder at all, so if source of the problem is hidden somewhere there, it's going to be still there no matter how many times you're executing repair command.

As Kerosene noted above, it's most likely caused by some custom mod located in Saved Games (remember that repair command checks only the main game folder but doesn't check Saved Games location!)

They're fine here. Latest OB, MT mode. Screens below.
If you're experiencing missing textures, do the usual troubleshooting: disabling mods, removal of fxo & metashaders, then repair & cleanup.
 

Also, remember to temporarily remove or rename your Saved Games/DCS folder. Reinstalling the core game only won't do anything good if there are still any modded leftovers in Saved Games.

You've ben answered in the other thread you started:
If you launched DCS at least once, then there is a folder created on your system partition here:
C:\Users\[your windows user name]\Saved Games\DCSworld\
It might be hidden by Windows, but it's certainly there. Un-hide it if needed.
You have to go there, create \Mods\Aircraft\ sub-folder manually and extract A-4 archive over there. It's the only way to make the A-4 mod work.

If you're talking about distant layers jumping slightly up and down then yes, it's a DCS thing since new clouds tech was introduced in Spring 2021. Apparently it's more or less noticeable depending on players resolution, screen vs VR etc., but it's always there to some extent.
I know it's difficult to un-see it once you saw it, but get used to it, there's no fix.

Size and number of files and folders is correct. As razo+r pointed, that's Normandy "1.5" you're looking at. All the detailed stuff that comes with version 2 is just hidden/locked until its license is purchased and activated.

Yes, module licences are tied to your account, not to your physical installs, which you can have many of on your computer.
As long as you log into your OpenBeta with correct login and password, and if all your purchased modules were installed in enabled in your Open Beta as well, they will be accessible allright.

About the bars, you've got some cockpit mod leftovers in Saved Games location (repairing and reinstalling doesn't touch that folder, so don't bother - they can't help). That was the culprit for the same problem, found in the other thread (though the guy didn't mention which mod exactly caused it).
About green tinge, it's part of new dynamic reflections. It will depend on sun position and terrain you're on / over.

^ I think he's asking why the trim gauge doesn't react to cockpit light then, like other instruments which were painted with fluorescent paint for that reason.
@SlippaWe know that complete cockpit retexturing of the Spit is in the works. I suppose they won't bother with fixing the old textures when these are soon going into a bin anyway.
However, if the problem persists in the new pit, you're free to unleash the report bumping fury 😄 .

1) There are two Spitfires in the game, clipped and non-clipped one. The game sees them as separate units (even though they're functionally the same), hence two folders in Config/Input. ED somehow managed to get around this in newer P-47 module, but older Spit is still programmed this wacky way;
2) Repair command only affects core game folder and it doesn't do anything in Saved Games folder, so don't bother with repairing. That also means, however, that there was something messed up in these Spit controls profiles of yours. You said in the other thread that you imported them to other planes for further tweaking (bad idea in the first place). Well - there you have it - you just imported the same error to remaining planes. Now we have to figure out what the error is and where in diff.lua files it's hidden. Personally, I'd rather start with clean sheet and redo the controls. It would certainly take less time to do it than this whole troubleshooting process.
3) Do you still use Game FM or switched to simulation FM in the end? Were the Spit control profiles you used as a basis for remaining planes originally made for game FM or sim one? I don't even know if it's possible to import game FM profile to sim FM profile, but I suspect it could cause unforseen issues.
 

I recall it was related to setting specific mission options in the editor and restarting the game afterwards, but I don't remember the details. Take a look here for hints: