Sangusan

Hmm, I was wondering about that, too, thinking I was just doing shitty landings. So I'm not the only one who can't seem to stop bouncing around. At least the carriage is sturdy enough to take it. Maybe it was tuned to be a little too springey.

Oh, wow. I was wondering why my reticle was acting in what I thought was the unrealistic manner in multiplayer. Weird decision to leave that stuff up to server hosts. Would also very much appreciate those two features being made default.

SD-10 Questionable Behaviour.zip.acmi I've been having similar problems with the SD-10.SD-10 Questionable Behaviour.zip.acmi

Much appreciated, Kate. Thank you guys for your hard work; take your time, I think most of us have plenty of amazing modules to learn. Looking forward to the Supercarrier when it's ready. Much love <3

I will leave you with this comment: https://forums.eagle.ru/showthread.php?t=256850&page=3 Apparently it's Datalink related. When I did my G-Sync testing I must have forgotten to turn Datalink on, and thus had no issues.

Using your .lua file the issue remained the same (albeit only in MP), with what I thought was a "workaround" no longer working; no matter which MFD I put it on, FPS would tank a tremendous amount. That said, I think I solved my issue: I turned off G-Sync for DCS in Nvidia control panel. G-sync, the way I understand it, compensates for low fps. Thing is, in SP my FPS are basically never below 80; it's just not very demanding in most cases. In MP however (in this case the hoggit servers) my FPS average around 40-50, which makes G-Sync inclined to try compensate. I'm assuming (a lot, I know) it has some weird interaction going on with the MFDs that causes it to freak out: When the FPS drop happens my GPU usage drops to about 40% from its usual 99-100%, and upon turning the MFDs off it hops back to normal. TL;DR: Turn G-Sync off and report back on the issue. Edit: Well, turns out the ground radar still murders my FPS, with the exact same symptoms as described above (GPU usage dropping down to ~5% even). Sorry for giving hope. So far still exclusive to Multiplayer.

See if the problem persists when putting the A/G radar / WMD Pod on the side MFDs. I have the same issue when it's on the native center MFD, but weirdly enough it's completely fine on either side MFDs. Edit: The problem occurred again, no matter the MFDs. Thus far only reproduced in Multiplayer. When using the A/G radar my GPU usage drops to about 5%, with frames tanking respectively, which is a very odd phenomenon. Switching away from it immediately restores frames, with GPU usage jumping back to normal. Edit2: Staying in A/G mode with radar active (but not shown on an MFD) still impacts frames. Switching to NAV spawns weird "artifacts" on the radar screen and returns fps to normal. Example shown: https://imgur.com/a/400EeN9 These artifacts disappear very quickly, but maybe it helps in finding the underlying problem.

Personally I am experiencing a massive FPS drop when using the center MFD for anything requiring a shader to work; WMD Pod or A/G Radar. Only since this patch, and weirdly enough I have zero issues putting them on the side MFDs. Sorry for being anecdotal, hopefully it helps somewhat identifying the problem, if it is indeed module specific.

I'm quickly becoming the "Malwarebytes causes stutters!" advocate. For me and many other players this was the cause; disabling Malwarebytes or excluding DCS from it fixed any stuttering issues. You seem to have figured out a solution for your rig, so I'm hopeful it stays that way.

Malwarebytes is a known cause for those random stutters you mentioned. If you're using it (or an equivalent) I suggest excluding your DCS install. Good luck!

Thank you, Nineline, for taking the time. You have the patience of a saint. DCS has its issues, but it's an amazing product, and most people would agree with me there I think. The reddit crowd especially is very vocal, and oft negative, but they wouldn't be so passionate about the game if they didn't love it as much as they do. Have a great day.

We already have the MI-8 as a big, bulky helicopter. Helis are amazing, but I'm personally not too thrilled at the prospect of another fat, basically non-maneuverable rotary wing.

Alright, so an update to my problem, for you future internet historians and people with the same issue. I upgraded to a new Motherboard / CPU a couple of days ago, and since then the problem has vanished. Old system: I5-6600k, Gigabyte MB (can't be arsed to look that one up though) New system: Ryzen 7 3700X, Gigabyte Aorus Elite MB. Nothing else was changed. I have no explanations to offer, at least apart from speculation. Intel vulnerabilities to things like Meltdown et al? Aren't computers mysterious.

Post the DCS.log in your Saved games/dcs/logs folder. It should give some insight.

People always get so hung up about the Gazelle FM, because it can do things like loopings and other very non-traditonal maneuvers for a rotary aircraft. The kicker is that it can do these things IRL and there's even youtube videos on it. The FM has been checked with people that have actually flown the gazelle, and most of the stuff that people were complaining about (like for example how flying inverted didn't break the rotor / engine) has been fixed ages ago.

Good idea to check for it. Just ran Memtest and it said everything was fine. Still, one more thing probably ruled out.

Thanks for trying to help, David. I've deleted the FXO and Metadata2 folder (and even all the other files, including input config, which I later imported back in-game), to no avail. I'm almost assuming it's a Windows 10 problem rather than DCS, as with Windows 7 I never had that issue. No idea where to start, though.

I have cleaned and repaired via DCS_updater about a million times, with and without deleting the flagged files. Two days ago I did a completely clean installation to rule out as many things as possible. Still the same issue.

Specifically the textures get corrupted. This is a clean install with clean settings and no mods. Open Beta. Flagged files: textures/mig21bis_02_nmp @ coremods/aircraft/mig-21bis/textures/mig-21bis.zip textures/mig21bis_01_nmp @ coremods/aircraft/mig-21bis/textures/mig-21bis.zip textures/mig21bis_damage_main_nmp_02 @ coremods/aircraft/mig-21bis/textures/mig-21bis_base.zip textures/s_75_rocket_normal @ coremods/tech/techweaponpack/textures/s_75_rocket.zip textures/rapier_fsa_blindfire_radar_1_normal @ coremods/tech/techweaponpack/textures/rapier_fsa_launcher_radar.zip textures/f18c_2_dif_roughmet @ coremods/aircraft/fa-18c/textures/fa-18c.zip models/lha_tarawa.edm @ coremods/aircraft/av8bna/shapes/lha_tarawa Also attached a log regarding the disconnect from a server due to bad models. I can connect and play on servers that do not require pure textures and pure models without issue. For instance, Hoggit GaW does not work, since as of now it requires the client to have both pure textures and models, but Hoggit PGaW / Training server works perfectly fine. This issue has been around for about five or so updates for me. I'm afraid I can't pin-point it exactly as I haven't been keeping track of it at the time. Edit2: Because clean install is apparently not clear enough: Repair and cleanup has been done a million times, before and after the clean installation, with and without deleting the flagged files. It makes no difference. Starting the game without the flagged files does obviously not work, either. Edit: Oh god IC Check failure. It clearly is too late for me to invent threads. dcs.txt