rob10

Saved games/DCS/config/input If your device ID's change you may need to change the file names to get them back into game. There are a few files around to automate that process in case you need to use the backup.

That's a weird random issue that pops up occasionally. No real reason and it seems to be individual people rather than widespread when it happens so likely corruption on their install for no apparent reason.

Work around that may work is put a soldier unit inside and use it to detect hit. In some cases they'll sit inside so you won't see them, but they may sit on top so may or may not work.

Some of us are slow readers, so please give us access to the manual a good bit of time in advance so we can actually fly when it releases. Please. (full disclosure, I'm actually a fast reader, but claiming to be a slow reader makes a better argument in favour of this )

If you're using the launcher, there is a sqlite file I think that's been causing people issues. Do a search and you can likely find out what one it is and deleting it has solved some problems. I disabled the launcher as soon as it came out so I haven't paid enough attention to remember what the file is.

Likely you were using the Stennis carrier. It's "non-supercarrier" so has never had the full new deck crew. It used to have original deck crew but that was removed until ED can figure out how to have the original crew on it but the new crew on the others, so currently it has no crew at all.

That is a good point that the actual MFD displays also don't need SimAppPro (they're just an extension of your windows desktop being displayed).

1st thing to check/do is an exclusion from your anti-virus for DCS folders, then try a SLOW repair because your AV has probably quarantined some files. If you can't get it to run a repair try restoring the files from in your AV.

Depends what you're running. For controllers like stick, MFD buttons, throttle you don't need it to run for inputs. HOWEVER, for the lighting of A-A, A-G buttons to sync with DCS or for the UFC to actually display info from the game you do need SimAppPro running. Although I agree it's not the greatest software, generally it doesn't cause a lot of issues.

You're never going to even get rough estimate until it's basically ready to go. The reason is, if today they said "we're aiming for June 2026" and then in Feb 2026 came back and said "nope, gonna be July 2026" the uproar on the forums would be epic (and sadly this isn't an exaggeration) with all kinds of accusations of "you promised June 2026". It's not worth the grief it causes to try and estimate considering how difficult it is to estimate anyway.

I flew solo in SP for many years. I had a negative view of MP due to all the noise about cheaters and griefers etc AND it's pretty intimidating (even for someone who is pretty computer literate) to just know how to actually start into MP on a software/hardware/connection level. And that's before you have to actually know details about procedures etc. I finally dipped my toes into MP because I was running out of missions/campaigns and started browsing some sites and discords for virtual squadrons. I got extremely lucky and stumbled on a great group that I love flying with and have learned so much from that I never would have learned on my own. It was quite a learning curve up front (even as a reasonably experienced flier) but well worth it in the end. Looking at other groups I can definitely see how I might have sworn off MP again if I had landed in them because it wouldn't have been a good fit for style of play or just the personality things others have mentioned.

What other mods do you have installed? That is typical of a mod issue. Doesn't matter if you're using the mod or not, if it's installed it can cause issues.

Have you tried deleting the FXO and Metashader 2 folders in your DCS Saved Games folder yet?

You can pause the download. Just hit cancel and when you start updating again it will continue from where it left off. It can be confusing because because it will start at 0% again, but if you look at the total to download you'll see it's smaller than the original download amount.

I suggest you do some searching on the forums regarding this. The new pod is deliberately (and correctly) worse than the "existing" pod in the F-16 because the previously modelled one was much clearer than it should have been vs IRL. There are also tips on how to get a clearer picture (don't fly the F-16 much currently so I can't tell exactly what will help).

They are using totally different tools than what DCS users have with trackfiles. For them debugging having the correct inputs likely lets them see how they are interacting with the program. While I'm sure this is true to some degree, I think too many people who make or watch these videos assume that everyone watches them (they don't) and greatly overestimate their value to promoting DCS.

MSI in this case is referring to MULTI-SENSOR INTEGRATION in the Hornet and is completely unrelated to your graphics card. The same acronym is just to confuse you and throw off any spies looking into it MSI in the Hornet is what they've recently added and are still working on and since it touches a lot of stuff with the radar it's why things got broken.

ED doesn't typically talk a lot about stuff that's in progress (mainly because the forums start whining "you promised"). That said, there are lots of examples of things that people had wrote off and said were never coming even when ED said "we're working on it" multiple times (Multi-threading is a great example) that eventually showed up. Yes the wait is painful and they aren't giving any details. But history shows that they often are actually "working on it" and it will eventually show up.

Ya, I don't remember if 256 used to even be an option (I think it was just 512 and 1024) and when they added it it overwrote the whatever had previously been selected. In fairness, they changed that section a bit ("every frame" is now a checkbox rather than part of the dropdown list) so likely they changed exactly how it was stored which reset it to default. But that's one that really should have been highlighted in the changelog IMO.

Check what your Cockpit Displays Resolution is set to. It had set mine to 256 (rather than 1024) after the last update. It messed with a number of things in my cockpit including the on knee kneeboard in the F-18 (although it didn't actually mess with the pop out one). May not help, but worth a look.

Start by removing your mods and trying it again. Mods can have unpredictable and seeming unrelated impacts. And actually it's worth running a slow repair (with remove extra files) after you do that. And if that fails, try renaming your saved games folder as you may have missed a mod in there and a repair won't touch it.

I think the key here is they said "Several negative drag errors in logs - fixed". They didn't claim to fix them all. What you're seeing is "normal" (at least in the sense that it's in virtually every log).

Attaching a track file from a session where this is occurring (short as possible, preferably on the Caucus map) or a copy of the mission will help the devs figuring out the problem. There are way too many variables that may influence things and mess with trying to reproduce this from scratch. You can save a track file from the debrief screen when you finish the mission.

I actually read through the whole changelog usually but could have missed, but I went back and checked and it's not mentioned in F-18 or general sections at all.