rob10

The WW2 planes have more detailed damage modelling. They are being used as a test bed for a new damage model and ED have indicated that it is planned to come to the newer planes. No idea if that's just around the corner or a couple of years out. It will likely just show up out of the blue in a patch some day.

Reality is that single thread is approaching end of life, so I wouldn't expect ED to spend a lot of time fixing stuff in it (even if it was an easy fix it would still take a bunch of testing time to make sure they didn't break something else).

I wasn't going to bother responding to you again, but you seem don't seem to want to understand that (even if I had the aircraft installed to be able to attempt to reproduce it) me dropping aircraft in a mission is meaningless because (as the others who've responded said) who knows if you've got one small setting different that causes or doesn't cause the problem. That's why the dev's will ask for a track so they can ACTUALLY SEE THE PROBLEM without having to waste time going on a wild goose chase to create it. And NO there is no guarantee that a dev "just creating a track" is going to capture how you have it set up where the problem shows. It also allows them to see if you have a mod installed (even one that you may have forgotten about and might respond with "I have no mods" if asked). Rather than just saying a 2nd time that they would want a track file, I tried to help you understand why they would ask for that, but apparently you don't care. They've been down enough rabbit holes trying to recreate "issues" that I don't blame them for tagging threads as "missing track file" (considering how simple it is: at mission debrief screen "SAVE TRACK", come back here and add it to a post) Good luck getting a response. You can keep posting "DCS/Dev Group... ?" but I'll be really surprised if the response you finally get back from them isn't a tag of "MISSING TRACK FILE"

Almost for sure an issue of using COMMUNICATION MENU binding when it works on the ground but not in the air. If you don't have EASY COMMS on (easy comms won't work in many missions) you have to use the "COMM Switch - COMM 1" and "COMM Switch - COMM 2" bindings (depending if you have the frequency tuned on COMM 1 or COMM 2) to pull up the menus in air (they actually work on ground too).

That's the way it works. See here:

Add a small deadzone in the axis tuning (start with 1 or 2). Sounds like you're still getting a small input when you release it. Warthog throttles used to be notorious for that, although I thought they had final improved it more recently. And definitely check for double binds as Foka said. Also worth scrolling down and checking the Thrustmaster subforum in the INPUTS section of the forums.

There is a reported bug regarding only the 1st round of weapons exploding and anything replaced by unlimited ammo option don't.

It should, although I have seen a post or two from people where it wasn't. Just start it up and in the in game splash screen it should say "multi-thread preview" (or something similar) before the version number in the bottom right of the screen and you'll know you're in MT.

Is it really that difficult to post a track? It would likely make it that much easier for the dev's, especially when, as an example, you didn't mention this happens at 5x speed in your original post. The dev's would have wasted a bunch of time setting things up and totally missed the conditions where this is occurring. That's why they ask for a track.

Yes, for any older missions you will need to reload any bombs on player aircraft so they have the new fusing. Not sure I'd call it a bug, just the game evolving and moving on.

You'll get a lot more traction if you post a track file of this happening.

For the record, that's a bad example since that's intended and realistic behaviour (assuming you're intending to jettison the HARM).

Is this the same as what you're describing? Just started to happen to me and I'm just starting to try and figure out what's causing it. Always seems to happen on weapon impact.

Thanks, I was just wondering if I needed to do a repair (if you were seeing INST now).

Interesting. Does it still show INST next to the fuse when you change pages now? If not then I'd say there is a bug there, just not the one you were originally thinking.

Testing the mission, they don't actually "disarm" it's just missing the text to say INST beside the EFUZ on the Stores page. If you set it to INST, go to HARM page and back it will only show EFUZE but if you drop it it will blow. If you set it to OFF it still only shows EFUZ after you change to the HARM page but it doesn't blow. That might be a bug but I have no idea. But they do still work which is why there haven't been a bunch of reports of this. And further testing, this ONLY seems to happen with the HARM TOO page (changing to other pages it still shows EFUZ status when coming back. FWIW, I would be shocked if it was supposed to defuse when you moved off the page, esp if you haven't deselected it. If you deselected it then it would make sense, but since you have to leave that page "active" to get it to align it doesn't make sense that it would disarm.

There are reports that the latest Beta for that is causing issues again.

If you're using the new launcher it is causing that setting to default to ON (show them) every time you run it. IIRC it should be in the MISC section of the settings (could be wrong on that).

There is at least one person reporting on the forums that the latest Meta PTC update is causing them issues like this.

Since this obviously isn't a widespread issue, you should post a track and see if others can recreate what you're seeing in the same mission.

Have you tried RIGHT CLICKING in the appropriate binding box and manually picking what you want to assign it to (rather than moving the control to pick the assignment)?

You didn't mention it and reality is that, as I mentioned, I've seen too many threads that go on for pages of in depth troubleshooting only to discover in the end it was something that simple. So it's actually preventing wasting peoples time to make sure the basic steps are covered. It may seem obvious and be your 1st thing on the list to try but that doesn't mean it always gets done 1st. Thanks for coming back with what did fix your problem . That could help someone else down the road.

That could be your problem. If you look at minimum requirements it says Windows 10.

I'm sure other's can give you a better answer from the log, but if you're getting repeated shutdowns that would usually suggest a hardware issue and power supply does seem like a good starting point.

Not really related directly to the download folder itself, just you don't have enough disc space to download the update. It checks BEFORE it starts to download things and if there isn't enough space it won't start to download so that's why there's nothing in the download folder. The actual D/L might be bigger than the final needed space (because it will replace a bunch of existing files after it's downloaded/unpacked) but you'll need to find a way to free up space on that drive or else get a bigger drive.