Art-J

Just a sidenote - keep in mind the water layer in DCS is always continuously rendered below the whole map (and thus affects performance accordingly) no matter if you see it or not.

@Hoirtel For whatever reason documentation section of DCS website contains pretty much only manuals of aircraft developed by ED and Belsimtek. I believe there's a single exception (Viggen), but other than that you will not find many (any?) 3rd party module manuals there. I wouldn't count on F-15E becoming exception then. You can either download the manual now from link provided by its author, or wait for module release and find it in module's "doc" folder. It's still going to be the same file, though, unless Baltic_Dragon manages to include some last-minute changes.

@GunnerFlyboy Keep in mind that repair and cleanup commands affect only files in main game folder. They don't even touch your Saved Games / DCS location and that's where some of the corrupt files might be, as the log entries suggest. So, apart from slow repair, get rid of any custom mods in the Saved Games and then see if it helps.

I think Tau made a bit of a mental shortcut. Just switching to manual won't help in itself, 'cause the prop becomes a fixed pitch one and thus it's going to windmill and overspeed as well if not adjusted accordingly. By the way, in auto mode we can't even get to 3000. In a steep dive the engine will rev up to about 2900-2950 in twelve'ish seconds and die. I suppose the only reasonable solutions available for now are: a) bind manual pitch to some easily reachable two-way switch on your HOTAS or; b) perform dives shallow enough NOT to get above current redline of 2750 or; c) just try not getting in a situation when you need to perform a dive to the deck at all. Moreover, since compressibility lock of elevator doesn't seem to be simulated anyway, why not trying to pull up near the redline? Won't help against 190s, but at least the 109 will more likely struggle to follow.

Maybe a recent post "straight from the horse's mouth" in the other thread will reduce speculation somewhat (or not, some guys just love conspiracy theories anyway):

One more reason to use Magic Zach's default skins repaints. I know we shouldn't rely on his work to fix things ED haven't found time to improve themselves, but for the time being it's the only solution we've got.

Some time ago I did try to compare level airspeed at 42" @ 2550 with levers split and connected, at 5k and 10k ft maybe? I don't remember now. There didn't seem to be any noticeable difference, but I admit it was a quick and half-as..ed test, so who knows if that power loss we're discussing here is simulated in DCS Jug at all or it isn't. More thorough and accurate testing would definitely be needed.

A couple of extra notes if I may ;). 1) @Ala13_ManOWar a bit of an accidental typo here maybe? "Whispering death" moniker applied to Bristol Beaufighter (which I'd love to see made to DCS standards by the way!). Corsair was indeed the "whistling" one, which in all versions before -4 was related more to the air going through wing radiators at high speeds rather than by supercharger. Thus the sound can be heard on videos of various restored Corsairs if only they fly by fast enough, no matter the engine variant; 2) Any Double Wasps apart from very rare variants like -18, 30, 32 W had all-mechanical drive for their internal supercharging stages, so I'd say this awesome birdcage mentioned above isn't really going to sound any different than other -1s flying during airshows. Even if they had proper, original engines fitted, we wouldn't hear their extra stages kicking in is because outside of ground tests these would not be used in typical low altitude airshow flights. The birdcage probably won't use it often at airshows either. Kudos to owner and restorers, however, for sticking to factory spec! It's going to be a great and rare plane to see in the sky again.

That's interesting and worth trying then. Still, finding someone willing to spend hours/days and having some payware storage site account sufficient to upload 17 gigs of data (which exceeds standard free google account limit I think?) is a bit of a stretch. Do you have a buddy or place at your work with usual all-Windows PC, where you could temporarily install DCS with both free maps and copy it to external drive? That might be a faster option.

Even if you got the folder from someone, I'm not sure it would work (ie. become "visible" and fully functional in game). Unlike MSFS, DCS uses its module manager for installing, uninstalling, activation and deactivation of all official terrain and aircraft content. From various posts in bugs section of the forum I seem to recall trying to move folders in or out manually only causes problems.

For the third time - as mentioned, go to London or Paris and check the building detail so that we know we're on the same page when troubleshooting this issue. Your screen suggests, however, you might indeed still have 1.5 activated instead of 2.0. Field textures are one thing, but It seems to me the infrastructure textures of that little farm on the left are low resolution as well. For comparison, this is how the same location should look like in 2.0, with date set to June and "Terrain Textures" set to "High":

I don't use Steam version, but recall other Steam guys reporting similar issues. I think It was something related to too many Normandy-related items ticked in the DLC list. Search around the dedicated forum section for the Normandy 2.0, especially later pages of the FAQ thread. https://forum.dcs.world/forum/1084-dcs-normandy-20/ If everything's installed correctly, you will generally see the map in the game still referred to as just "Normandy" (as it was previously), but you'll get bigger map area with London and Paris, and when you fly to these cities, you should see high resolution textures on all buildings, airbases and structures. Use F11 free camera to check them out faster.

Understood. Thanks for the info.

That's just old Normandy with terrain extension, ie. version "1.5" indeed. It seems the bug which causes 1.5 to be installed for trial users instead of full 2.0 hasn't been fixed yet.

Expectations need to be managed. In old newsletters they planned to develop and release F-8 by the end of 2019, but we can see how it panned out. At some point later the relevant hints were removed from the store page of the A-8 and F was said to be "planned but long ways off". Nowadays, I'd say it seems to be in the same place as Me-262, ie. not cancelled, but not being actively developed either.

Moreover, this video (and most of the "scenic" ones out there) is made during mission set for "golden hour" morning / evening. That's a simple and old video creators' trick as DCS looks great during such hours even with potato settings, let alone with maxxed ones.

There never was an "official" list that I know of stating this. Rudel has been working on the A6M5 model for years and showing WIP pics, but as a private hobby project at first, outside of his M3 commitments (he talked about it in last year's podcast). With that being said, the plane has indeed been popping up in recent teaser Corsair pics more frequently than ever, so it's very possible that they decided to develop and add it as an AI asset after all. These are only clues and not evidence, so the whole thing is a wishful thinking at this point, but who knows. Fingers rossed! And few years down the line, after MiG-21 revamp and Crusader are done, maybe we'll get a flyable Zeke as well. Let's just wait and see.

Not only for high altitudes, but on the ground right after engine start, if you want to follow real Pilot's Notes fir Mk IX and XVI that is. Then you can pretty much forget about it. DCS manual misses this step for some reason.

Mind you, you can use MT in DCS Stable now as well, in the same way as in Beta (launching with separate exec). Though you'll probably be happy with Beta anyway. As for the 3D CPUs, have you followed recent posts in this thread? Lots of useful infor there: About the RAM question, that depends on how you play DCS. Guys who play complex multiplayer missions on Syria map with lots of scripts and units (worst case scenario in DCS now it seems) report going well into 40-50 GB of RAM usage easily. Others don't use that much.

It's a DCS simplification rather than Mosquito problem. Smoke (any type of it) in this sim is generally not affected by airplane prop or helicopter rotor wash, only by the wind.

Just like the remaining German piston engines in the game, this one features a direct fuel injection rather than pressure carburettors as in all Allied warbirds. Thus I suppose priming is not a must-have, but rather nice-to-have if fuel pressure drops while cranking (but that isn't simulated I believe, at least not as long as both pumps are working correctly), or when weather is very cold (but I admit I've never tested that really).

Fuel tanks and valves mismanagement maybe on the left and right side? Mosquito does not have crossfeed system, so one has to monitor and manage them separately. Although if you say you didn't touch anything, both should probably be set the same way in autostart mission.

Thanks very much for the explanation about putty and waxing. I do have some aero engineering background and understand that part, just ain't knowledgeable enough about German birds. That's a nice extra touch for historic detail and all I needed to know then. The .lua part just burns my eyes by looking at it, but I'll save it as a precious reference and get back to it when dealing with any custom skins shenanigans I encounter every now and then in DCS.

I believe Nealius is talking about climbing through 5k-6k altitude where turbo, which used to sleep till that point, wakes up, realizes there's a 42" job to do and starts boosting in a very sensitive, non-linear manner. That being said, I also use left Warthog throttle lever to control it (no curves or deadzones) and can confirm that with correct working hardware it should be relatively easy to keep MAP within +/- 1 of that 42. Output should be sensitive, but not spiking.

OK, gonna need a bit of help here. Although these skins are little masterpieces, I'm neither THAT interested in Dora, nor do I have enough disc space to keep them all. I'd like to use just a couple of them, but the fact that some skins use textures from the other skin folders, and that the description.lua mumbo-jumbo might as well be written in Chinese for me, makes it difficult to figure out which folders I have to keep and which I can delete. By looking at references in descriptions of those skins I want to keep, I left some "source" skin folders ones as well, but today I stumbled upon the issue seen on the shot below. It's 12_SL_54 skin I think. Should it really have front part of the wing darker semi-gloss and the aft part lighter flat, or did I miss some file in some other folder and have roughmets messed up in this one?