Hiob

You‘re right. Nothing to add…. and though I can help myself around computers and come up or at least make use of some workarounds like this, I have to admit that I can’t keep record of all the necessary little tweaks and tools and workarounds. So I often find myself doing the same stuff over again when somebody brings it up.

That's actually a god idea! worked for me. Did you try the hyperlink he provided?

@cfrag you are 100% on point. The search function in the user files is borderline useless (though I might speculate that the actual problem is the indexing of the contents). No matter the cause the result is that it is a tedious chore to find anything interesting in the user files. @BIGNEWY please take notice, TY!

I remember that the official MB-339 had issues with G-spikes from taxiing (leading to damage and blackouts). Probably related.

Isn’t that just about the visual effect? I don’t think that it affects FFB.

Unlikely. FFB effects are enabled on a per module basis and from the module developer. And other modules seem to work as usual.

Well, you get g-spikes in the z axis from taxiing, but that seems a bit excessive. Unless they swapped the suspension struts for T-bars… Maybe they forgot to put a smoothing average over the raw data…..

There’s room for improvement. Granted. But „unflyable“ is a bit of a stretch…..

Admittedly the Thunder is one of the very few modules I don’t own, but it would be the only module (afaik) that offers FFB ground effects…. interesting.

Won‘t happen. DCS checks the checksum hash for every file to ensure the integrity of the installation. For user modified content there are two options. a) the savegames folder and b) a mod manager. Choose whatever fits your needs best. But don’t expect ED to bend over backwards because you’re unwilling to do it the proper way.

Problem with "realism" in this regard is, that a fixed device (edge, mask whatever) direktly in front of your face will be filtered by your brain (as is your nose e.g.) and not consciously perceived. Whereas put on screen, it can't be ignored. Blurry or not...... In favour to bind it to the pilots model, but strongly against forcing it!

Some people are just desperate for the chance to tell everyone "see, told 'ya!"....

Yeah, sorry. I‘m a bit behind reading the rest of the internet…..

missed that. So we‘re wasting our energy on an apple to oranges comparison? great….

When 1-2 cores are hogged by some process (bug or otherwise), that‘ll definitely have impact on performance. The CPU has a limited budget for power and heat. (Unless it’s just a misreporting, can be easily cross checked by monitoring the temps and watts) @SpecteRED do you guys have the same bios version and chipset drivers installed?

Shh, shh….. don‘t say that too loud! Some are easily spooked when the status quo is questioned…..

This in particular is a matter of taste. I for once absolutely despise pilot bodies. VR or flat. But fortunately it can be toggled in realtime, so I have no issues with it. And when you offer a pilot model, at least make it pretty! Patch seem to cause some headache for ED. It’s getting late…. brace yourselves.

Adjust the gamma in realtime during a flight. Choose the one that suits you best. Sometimes it’s just easy.

I feel the same. There isn't one gamma setting that works for all modules. I find some of the newer Modules have particular dark cockpits and some older are too bright. Maybe the problem is more pronounced on an oled, since there is no backlight to brighten up the blacks....

Epic wrist watch!

BN already confirmed, C-130 is NOT coming this patch.

You should AT LEAST verify, that you and your buddy, have the same system settings (game and nvidia control panel) and the same exceptions (or lack thereof) for AV. E.g. somebody entering the server may(!) (I don't know) cause some pre-cashing of assets (aka loading from disk), which may cause latency and a momentary drop of fps. This may trigger the AV to scan the loaded files. Just an example for a possible chain of cause and effect. Since your FPS drop to around 60ish, it may also be V-sync related. Remeber V-sync will drop to the next lower tier if it can't hold 120,60,30,15 fps. (Unless fast V-sync is enabled or V-sync is disabled altogether) But there is more possible difference. What do you guys have running next to DCS? (Like Hardware Telemetry, RGB crap, proprietary software from Logitech etc. ...other stuff) is it all the same? probably not

There are a ton of other variables (in game and in windows *and in bios) that could affect this. Buying hardware to solve this is a complete waste of money. It won't fix anything other than by pure chance. non-exhaustive list: (some may not affect this remotely, others might in unforseeable or unintuitive ways mind you) - preload radius - V-sync settings - pagefile settings - anti-virus - background processes - gfx settings - how the fps limit is enforced etc. pp.

n/a response lost its cause while typing

Well, a bit of expectation management doesn't hurt. Appreciated.