Art-J

Not going to help here much, but just to chime in, I was having the same symptom with my current old'ish rig, albeit it was intermittent, happening occasionally every few weeks or so. No stability or any issues otherwise at all. One of BIOS updates for my Gigabyte Z390 mobo seems to have fixed it for good. Granted, being a boomer not interested in tinkering with hardware anymore, I run my rig with all stock settings and whatever XMP profile that was suggested by new BIOS.

@Thamiel Just for the record, as the post on top of this very page says, first rollout will be 110 GB, while it's the future complete version that is estimated at 205... for the time being that is (in my opinion it will probably bloat a bit beyond that). With that being said, even though I'm a Pole and would love to see more Polish airbases, I agree one has to draw the line somehere, especially when talking about areas on the edge of the map.

None of above are applicable at all to gaming scenarios, though (unless someone like Reflected wants to create a detailed historic single player campaign set at some clearly defined period). I'd rather point out here (once again, as it's been done already) another aspect, which is much more relevant to DCS: a) all five ED warbirds, which are more or less usable for mid-'44 scenarios, have standard (conservative) max boost or manifold pressure settings, so why should Anton and Anton only be improved in this regard?* b) thus, if we gave Spit, Mossie, Thunderbolt and Mustang an option for mid-'44 higher boost / MP settings just like we gave it to Anton, wouldn't we end up back in square one? Anton would become faster, but so would all the others. * Granted, P-47 is a bit of a freaky exception, as it can already be ridiculously overboosted in a dive beyond standard max power rating, but It can be done only by diving to sea level and flying straight, so it's not very useful in all offensive situations.

@Tank50us Note, there are two holes in your suggested scenario: a) Why would Ron want to sell code, 3D model and whatever IP assets related to F-15E to ED if he can still re-use them partially for planned MSFS / "new" Microprose projects. They're still worth money even when/if his relationship with ED ends for good; b) Without Galinette and M2M aboard nobody will develop these modules further anyway, no matter who owns the code in the end. And judging from their responses on other communication channels, they do not seem to be in hurry to become subcontractors directly for ED (nor do we know if ED would like to hire them at all).

^ Got it. I should have rephrased - was thinking more about aircraft and units mods. Skins are not that harmful indeed (for many years I used to throw all of them into Bazar folder myself), but I think the sooner OP starts getting used to idea of placing all custom content in one dedicated location, the better. Just to minimize bugs troubleshooting problems in the future.

No no no, you don't duplicate the whole Mods folder with its contents. You do have to create a correctly named folder tree / path, however, if you want to place custom skins there. Generally - Saved Games location is a place where all your customized changes and addons go or should go: controls, edited kneeboards, missions created in the editor, screenshots, shapviews etc etc. It's also recommended (sometimes even mandatory) location for custom skins, planes, units, any unofficial content really. It's better and safer NOT to put it in Coremods folder, as it can result either in cutom content not showing up in game, or even official modules not working correctly. Official modules are by default never installed in Saved Games, although some of them create small sub-folders for some extra data they write on a disc when they're used. That's probably the F-4E sub-folder you noticed there, but make no mistake - most of your F-4E files are stored in main DCS folder. To sum it up, don't put the Croatian skin in coremods. It may or may not work there, but if you put it in Saved Games / DCS, it will work for sure, as long as you unzip .dds and .lua files to properly named sub folder ie. : Liveries/MiG-21Bis/Croatia - kockica

Can you post a screenshot? There was (maybe still is?) a reported bug with Spit mirror glitching out when rain droplets option was ON and weather conditions were set to cloudy and rainy. Without screenshot though, it's difficult to say if it's the same known issue or a new one.

In theory there are four locations where one can try to install custom skins in, but "Saved Games" is preferred one just to avoid creating an unnecessary mess in your game folders. I've just downloaded and tried the Croatian MiG-21 skin above and can confirm it still works correctly in latest DCS version. If you don't have MiG-21 folder created in Saved Games, see the guide Silverdevil posted above. For example, the path on my PC is: C:\Users\[my user name]\Saved Games\DCS.openbeta (yours can be named different)\Liveries\MiG-21Bis\Croatia - kockica (note: the last folder is unzipped).

After testing the upgrade for a while I decided to go back to stock textures. Improved detail of upgraded ones is great, but with gamma 2.2 I use they just seem to be much darker then the ones in 4k-modded Kurfy or stock Anton. Too dark, more of a faded black rather than RLM66 dark grey. I can only presume SAB0T used the same base colour as in Kurfy mod, so maybe it's just the question of how (imperfect) DCS lighting and shading engine works? In either case, I'd love to see a somewhat lighter version someday, more in line with Kurfy cockpit repaint. Love the Kurfy and Mustang mods, though, I'm keeping these!

^ Please keep in mind that repair command affects only main DCS game folder, but it doesn't affect "Saved Games" folder. So, if something is wrong in that one, repair will not fix the issue.

With Wolfpack 2 campaign getting closer to release, I've decided to refresh my P-47 knowledge a bit, engine "torture-tests" included. Most of us remember heated debates in (closed now) threads about max RPM the engine could temporarily sustain before suffering from the dreaded master bearing failure. 3050'ish RPM being mentioned in real wartime manuals, but us not being able to get anywhere near that figure in DCS etc etc. Well, I don't want to jinx it, but it appears that this aspect of engine simulation might've been tweaked somewhat again by ED in one of recent patches, without being mentioned in the patch notes. I've just done a dozen or so high speed dives from 40k ft in an air-start mission I used in the past to investigate the controversial engine durability. Back in the day, letting the engine overspeed in a dive anywhere above 2750 RPM was a guaranteed damage, with extent of damage depending on how far and how long above 2750 you were. Steep 50+ degree dives were causing 100% reproducible failures after 12-15 seconds above the 2750 redline, every single time even in power-on condition. Today, out of these dozen'ish attempts, I've got engine failure only twice, both possibly slightly above 3100 RPM. In the other attempts, the engine kept running fine even after 20+ seconds of 3000-3100 RPM (I ran out of altitude to keep it overrevving longer ), oil temp within limits and all. I even did one 3000 RPM overspeed test with power reduced to increase master rod force reversal effect and "encourage" master bearing failure. That didn't happen though. So, a risk of random engine failure due to overspeed still exists and has to be considered in combat, but it seems to be much smaller now. All and all, thanks to ED for making the engine more durable (even though a relevant patch note would be nice).... ....unless it's an unwanted side-effect of February WEP-code change - in that case, please for the love of Flying Spaghetti Monster DO NOT "fix" it to where it was . EDIT: my test mission was using D-30 "Early". I don't think there's any difference in engine code between that one and "Late" or D-40, but you guys feel free to test these two as well.

Ouch, IF the glitch turns out to be launcher-related indeed I hope it gets investigated and fixed sooner rather than later. I disabled the (useless for me) launcher soon after it was released and would rather not have to turn it back on only for a single module.

^ What Silverdevil said. Take a look at this thread, it includes more info and tips about the issue:

Err..... Read again. He clearly mentions that despite having radiators full open and temps within limits, he got an engine failure. I watched the track and he also stayed within rated limit of 64" even though the plane can be overboosted much more. @Cool-Hand ever tried to repeat the test at combat RPM of 2550 instead of 2700? I haven't "torture-tested" P-47 in recent patches, but last year one could fly at 71" until water ran dry and the engine would take it no problem (well, minus oil getting a bit hot) as long as I kept it at 2550.

If it goes out for any reason other than fuel starvation (which in DCS can be a result of either drop tank mismanagement or trying to fly too high with booster pump off), then yes, it's really dead, period. Healthy engine which was turned off by mistake in air doesn't require any voodoo to restart. Windmilling prop + fuel on (mixture included) + magnetos on is all what's needed.

If you don't use SkateZillas utility, you'll have to do it "manual" way, by typing required command and previous DCs version number in command window or powershell. More info in this guide here (note: table with older version numbers is available in second post of that thread in "currently active branches" hidden content):

I've never used that mod, so can't advise, but you'll be better off searching through a couple of last pages of the thread dedicated to it: Keep in mind that the mod might not be fully compatible with the latest version of DCS, judging from recent posts in that thread.

Because we've read what they (HB Team) wrote multiple times already. They do what they can - send the files to AV providers for checking, but unless you're a big publisher, It takes 3 to 4 weeks to get the file whitlisted. Also, you're right NOT to disable the MS defender completely, but you also don't really have to do that. Module reinstall is is not required either (defender removed only one .dll file, why would you want to waste time resinstalling the whole module then). Defender allows you to exclude only chosen files and folders - use that option to exclude F-14 folder, or DCS folder in general (makes loading times much faster). Then use repair to restore the missing file and your Tomcat will work again.

It's an old and reoccuring issue. Most likely your Defender or Antivirus deleted one of .dll files required for the module to work. Exclude your DCS folder, run a repair (to restore the file) and you're done. More details here:

Follow the readme instructions added to K4 mod. No, you can't delete anything. Yes, you have to extract the zip. For example, the final path In in Dora's case should be ....Saved Games/DCS/Liveries/Cockpit_FW190D9/Sabot fw190d9/. This is where all .dds files and description.lua need to go. Then, once in the game, go to special options for Dora or Kurfy and click "customized cockpit" window to select between default and Sabot's one.

Removal is available in mission editor already, in one of aircraft properties tabs.

One could argue that these "other sims" probably don't calculate even half of the stuff that works "under the hood" of DCS F-4E for example. There's no free lunch and I'm not sure I'd prefer improved atmospheric effects for a price of reduced aircraft systems fidelity. I don't think we're there yet to "have it all" with hardware currently available on the market.

Maybe it's a similar issue to the one PawlaczGMD had with his Moza?

^ They won't appear until you take a seat in the cockpit and use snapview key command for the first time (RAlt+Num0 ? Or sth like that, I don't remember, you'll have to google around). Then, the relevant aircraft section should appear in snapviews.lua file. For example, the Phantom section will begin with line: SnapViews["F-4E-45MC"] = {. Mind you, we're talking about snapviews.lua file located in your Saved Games/DCS/Config/View folder, not the one in actual game folder.

Mustang, Thunderbolt, Mossie. 4 still to go, unless either of them got it by accident without relevant patchnote but I don't think that happened.