rob10

It's usually almost all modules that are on sale during sales, so while I get where you're coming from, not sure it would be worth the effort. The announcement for the sale lists all the modules on sale and what level of sale they're at too.

You've only got a 4,096 MB pagefile with 32 GB RAM. I'd bump that to 32,768 MB fixed and see if that helps. You had C000005 error crash, but could just be you're running out of memory.

For the record, I'd start here: https://forum.dcs.world/forum/1340-quick-action-generator/

At this point it's reported and BigNewy has said the dev's have reproduced it, so not sure what purpose more pics will actually serve. It's an issue, for some, and ED is working on it.

Interesting. And good to know. I don't pay that much attention to my programs (I just assume they're doing what I want) so I probably wouldn't have noticed.

That sucks, but it's an issue for SOME users but I would argue not the majority. Why should everyone else have to downgrade (I have really crappy download speeds so that pretty much puts me out for a day)? It's been acknowledged and reproduced on their end, so hopefully ED can hotfix this quickly for those having the issue.

In fairness, the specs do not indicate needing a continuous connection. It says "internet connection required for activation". I think most people would interpret that to mean you need to authorize with internet, not that you need to have continuous internet (or maybe I'm just old and that's a holdover perception from when you had to go online once when you installed it and you were good after that). This requirement has changed somewhere over the last year or two and ED has never communicated that change or commented directly on it and that lack of communication bothers me (I haven't ran into the issue myself, so it's just the lack of communication that I'm having an issue with). The "offline" mode has been around forever, but I used to hook into my wifi when I booted DCS, then turn it off to save a tiny bit of load on my marginal computer and never had issues with it booting me.

Thanks for the better and more detailed response!

Been a long time since I flew this, but do you not have to drop practice bombs or something on the camp?

That seems to be the case. I played with it and updating the fuzes in the re-arm menu in the planner and had mixed results, but I didn't actually try fully replacing the bombs which is likely the best way to work around this.

Because there are a number of presets (think versions) of DLSS that the DLSS version now included can use. I'm not fully up to speed, but I think it defaults to something like preset "C" but the general consensus seems to be that preset "K" provides better results. But some prefer preset "J". And likely some prefer "C". So ED has to choose one to include by default and I guess they decided to go with an older one (for whatever their reasons are, maybe good, maybe inertia to leave it the same), so recommendation is to add that in the autoexec to get the one the "crowd" thinks is the better one.

Clearly an issue for some, but I think saying "MOST" people are having this issue is exaggerating the problem or it would be much more widely reported. That's why ED didn't pick up on the issue. I'm on an AMD 9800 X3D (albeit 2D) and hitting 45-50C max in game with setting pretty cranked up.

Interesting. This seems to be specific system related. I normally don't pay any attention, but my temps have not changed on high end AMD system.

Sure, the other stuff is likely something different. But exactly what did ED do to change your DCS between yesterday and today? So why are you automatically assuming it's ED's fault that it's now taking so long to load in?

Long boot times is often related to your Anti-virus scanning stuff as it's loading in.

And the AV decided today there was a problem with some of the files. Completely random why it's affecting your other modules but not your terrains, but not unusual really. Windows Defender isn't immune from false positives (although some others (i.e. Kapersky, ESET) are way more likely to throw false positives).

Remove your mods. They often cause issues (even if they are unrelated to the module where you're having an issue).

I'd love less "pop in" for stuff at range. But in NO WAY does NVIDIA "sponsor" ED. The NVIDIA splash screen on startup is due to licensing requirements for using DLSS tech in DCS requiring it. ED also said very clearly (before DLSS was added) that they were focusing on it (DLSS) because a very high percentage of DCS users were NVIDIA users vs the small number with AMD or other video cards. They were initially not even planning to include any FSR until they had DLSS fully implemented, but they did end up including it at the start for non-NVIDIA users.

Start by removing your mods. There are errors related to B2 at a minimum.

Probably your anti-virus blocking something. Check it hasn't quarantined it.

You should start by removing your mods. There are a whole bunch of errors in your log long before it ever gets to the the anti-freeze.

Have you checked your email junk filter (either in you email client or your providers website)? Chances that they aren't responding are pretty slim, so I'd be looking for why you're not getting it.

You're making a huge assumption there. Yes, ED could just dump the files for the new DLSS in and who knows what the unintended consequences of doing so (and quite possibly on things you might not think are related) are. That's why ED have already stated that they intend to update to a newer version, but they need to find dev time to thoroughly test it before just dumping it in.

Not sure what it might be blocking, but if it works once then not again I'd be checking your anti-virus logs. Sounds like it might be blocking something.

Listen to Muchocracker. Very high probability it's the wind. As you said previously above you've seen it with the F-18 before. CAGE your HUD and it will be in centre, uncage it and it will go back where you are showing in the pictures. It takes a fairly hefty crosswind to cause it. Try turning 90 degrees to your current heading and see if it's still that way. Only other likely reason would be something messed up with your INS alignment.