rob10

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.

You can not "place" user aircraft on the carrier at all. It's a different mechanism to land airports and the behind the scenes coding won't currently allow for that.

Glad you got it figured out! Takeoff in the Mossie reminds me of AAR in modern jets. It's really hard to start and seems completely impossible (except that you know others are doing it so it can't be impossible). And eventually it clicks and you slalom down the runway but manage to get airborne only to bank and die because you were pulling up more than you thought. And then you manage to tame it and actually fly and it slowly gets easier each time you go up. I'm still working on landing because I seem to have a habit of getting hit badly enough by flack that I don't make it back more times than I'd care to admit so not enough practice at landing. But I have found doing low level, high speed straight in bombing to be a little safer (if harder to hit accurately). And if you try that make sure you set to 11 sec delay fuze so you don't frag yourself .

Unless you have a specific reason to use 4x32 (i.e. for BMS you had to do that a number of years ago and some other older games might also have limitations requiring that) it makes more sense to use 128.

And IIRC it's strictly an external visual effect (no change if you're in "pilot" view), so don't expect it to change anything if you're in the cockpit.

Mixing up my P-51 and Mossie I guess on the wheel lock. But what others have said: there is a lock the you need to press to unlock before you can use the gear up lever.

In fairness, ChatGPT is a TERRIBLE reference. It makes stuff up if it's not sure/doesn't have actual info. I would not trust any info you get from it. It might accidentally get something right, but the number of posts in the ED forums alone where it has provide plainly wrong information is mind blowing.

Also it's really easy (especially if you're used to a modern jet like the F-18) to not realize that you're climbing at an excessive rate on takeoff (you're viewpoint is much higher in the Mossie) and that can cause you to stall and bank and die. Took me longer than I care to admit before I realized that's what I was doing that was causing crash just after airborne. Keep a close eye on climb indicator and attitude indicator. Not a super easy aircraft to takeoff, but definitely doable if you do it right. Make sure you're lined up straight with runway (dif braking is a good way to crash on takeoff until you're more used to the aircraft). Set trim nose down and rudder to the right. Hold stick back to lock tail wheel and get power up SMOOTHLY but relatively quickly to get speed >60 MPH then let it off to get tail up and get rudder control of direction.

There is definitely a wait on Virpil, but generally it IS NOT 6 months. You can send Virpil support a message and they'll give you an estimate (may be off, but they'll give what they think is accurate). And if you've never actually flew with Virpil vs Warthog (which is good STARTER equipment) you are severely missing out as Virpil is very much head and shoulders above WH for bases (I do in fairness use and like the WH grips, but their bases suck relatively speaking).

If you read the post I replied to, it has nothing to with track replays "not working". It was regarding adding fast forward/rewind etc. Absolutely nothing to do with anything you posted in response to me.

Yes it has been discussed before. ED has already said they really can't do anything with the track system to make it "better" and it will require a new system to have what people are looking for in replays. And that will take time/manpower that currently isn't available so will have to wait until they can put some devs on it.

Just to clarify: is the Hornets on Cat 1 and 2 a "new deck crew" thing, because we took off tonight with "old" deck crew and no problems with it. And you've been around long enough to know that without a track file this isn't going to get looked at anyway.

Come on Mike. It's been explained before (and once again here) when you suggested this why it's (realistically) not an option. Unfortunately there's no easy solutions.

My personal suspicion is that this occurs if you have 2FA turned on (in order to enforce time limits on trials) but ED has never acknowledged or commented on this. I've physically disconnected my computer from my internet before to test and I've never encountered this (not sure I've tested long enough).

Known issue with the new DTC. If you change the modulation (i.e. FM to AM), press ENTER, then pull the COMM 1 (or 2 as appropriate) it should work.