Art-J

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:
 

I'd download and install standalone, non-Steam version, temporarily, just to see if that one launches at all. It might help to narrow down if it's strictly a DCS problem or Steam related one.

Do you use game flight mode? It's known to be somewhat bugged in Mosquito and to prevent picking up speed on takeoffs.

These are just old DCS clouds - although not supported anymore, they're still in the game and will be visible if the mission is old, or if players specifically turns them on in the editor.
Campaign mission you mention was last updated in February 2020, while the new clouds were implemented in April 2021. The campaign has just never been updated to work with the new ones. You can do it manually yourself, but since you're finishing the campaign anyway, I suppose it's a bit too late for that.

@Jef Costello Took a look at your last four tracks and found the culprit I think - you've always got fuel/MW selector set to "fuel" (down) position (see page 99 of the manual), which causes slow fuel system contamination with water and methanol - thus making the engine quit after a few minutes.
The selector by default shouldn't spawn in the wrong position in any mission (cold start / air start) unless you've got it assigned to some switch on your HOTAS, the switch sends the signal to the game all the time plus synchronize controls with HOTAS option is on. That's what most likely happens in your setup. I don't remember how this selector is called in controls, but that's what I'd check if I were you.

That's because default editor view is too zoomed in. Scroll up-left and you'll see the rest of the terrain. As YoYo pointed, everyone has new areas now, they're just either in low- or high detail depending on whether the Normandy 2 license did activate properly or not. The only way to confirm it is to check the texture resolution on buildings in London and Paris.
The main menu icon remains as it was ("1944").
I don't own Steam version, but check the FAQ thread, lot's of advises from Steam guys there on how to make the map activate for good.

Maybe you do actually have the terrain installed correctly. In the mission editor zoom out a little and scroll the map up/down, not all new areas and airbases can be seen with default editor zoom. 

Isn't it intended, though? Game flight mode was removed from DCS in January 27th OB update (check the patch notes), so that "easyradar" should be gone for good.

DCS Mustang and Spit have been suffering for years from the same controls-loading bug explained here:
https://forum.dcs.world/topic/307188-confusion-with-non-cw-and-cw-control-bindings-bug-and-workaround/#comment-5150395
Maybe that's what you're stumbling upon, depending on which variant you load first after starting the game?
About the Mustang, check the path ManOWar pointed above and see if you've got two Mustang folders over there. One should be called "P-51D-30-NA", the other just "P-51D". If any of them is missing, create it manually, fill it with folders copied from the other one and you're good to go. Controls should load correctly everytime you start DCS and go flying Mustang, no matter if it's -25 or -30.

I was not part of the Kickstarter endeavour, but from what I've read I understand rewards depend on how much you "invested"...
https://forum.dcs.world/topic/105692-dcs-wwii-rewards
... plus, you should be able to log in to your account and check what you've got access to:
https://www.digitalcombatsimulator.com/en/personal/backer/

Yup, a known issue currently: