Sh4rk

It doesn't happen only to helicopters. I'm experiencing this when flying the F-18 in multiplayer, in VR. While landed at Adana airbase in Syria, before startup, I look at F10 and come back to the cockpit using F1. The view is brighter and goes back to normal in a minute.

Probably a coincidence. You may also have had a PSU shortage of power issue - since DCS MT uses more CPU along with the GPU, it'll tax your system more than DCS previously did. Did you try plugging the headset to another display port, and maybe a monitor to the headset's current port to see if it is the issue?

Do you have labels on (as 'dots only'?) It looks like the labels could be being drawn even when above clouds, which would make sense if you actually have or want labels on.

I've been having the same issue for about a month (since previous [non-MT] patch). DCS seems to be using only half GPU power for a few minutes, then it stutters once, view flickers, and gameplay resumes in good fps. The only relevant thing on dcs.log that could be related: P.S. I was flying the F-18. No errors in DCS files, folder is clean, I've ran a full repair etc. After the log error FPS drops by half, then eventually resumes. Alt-tabbing from the DCS window seems to help.

I was in the F-18 and got the radar tracking beep and the locking tune from a SA-15, but not the launch warning. Lock tune was gone away shortly before I was blown out.

No, they removed the key bindings for it on the old Ka50 too.

Please do.

Rather not have it hardcoded if possible. Hardcoding it makes it very unclear as to why it's happening. You could make the default binding for view reset to be Numpad 5, but on the control bindings screen, like every other key.

In the Black Shark 2 cockpit, they're even identified: Sling load Auto/Manual, and Stabilisation and indication of hanger cable switch. And it's been like that since before slingloading was even implemented...

Well, the devs can say anything at this point. Since the Ka50 III is already in fiction territory (with the MLWS thing), it could just as well keep slingloading things, real or not. I don't think there's a single helicopter out there that can't really sling anything, specially military ones. It's such a vital operation (logistics) and one of the main advantages of having helicopters in an army aviation. This decision really reeks of something else. Like, "balancing", or a business decision to help boost sales of other helo modules than can still carry cargo.

Removing dbghelp.dll also worked for me as a temp fix. You may have other copies of dbghelp.dll somewhere else in your server (likely many copies). One of those may be the culprit. Likely in C:\Windows\System32 or under some other folder also in Program Files.

After your previous report, I tried changing all sorts of regional setttings and input methods on my PC (OS is already English). Didn't work, even though I set everything to just English, United States and US Keyboard with default date formats etc. So the cause can't be exactly the input methods even though it may be related to something like language and regional settings, -or- some 3rd party component that's installed by other applications including Google IME. On the other hand, one other player that was having the same problem, in Discord, said it worked for him after he updated Windows 10 to version 22H2. Which version is yours? If you want, or can, try updating to 22H2 to see if it fixes the problem.

Yes very much the same, I'm also still stuck to stable version. Open beta will still not load even after the hot fix dcs.log

I think you can safely set it to a minimum. Like 8 GB, 4 GB, maybe even just 1024 MB. I also have 64 GB and if I let Windows manage it, it'll set it to 64 GB. I'm hardly ever near using the 64 GB though, let alone needing the whole 128 (64+64)... Don't set it to disabled though, unexpected things can happen when Windows internally expects even a few kB of virtual memory being available. I used to run without without much issue, but a few apps would inexplicably crash without a paging file even with all the memory available.

I think it's not the same issue - people here are unable to launch DCS at all, either in 2D, VR or as a dedicated server. Can you attach your dcs.log just in case?

LOL what a joke. Report a bug and 5 years later they remove the feature instead of fixing it!?

Hi, I tried both things and the results as seen in dcs.log are always the same. Log is attached, same as above. dcs.log

Just to make sure it's the patch and not something about my computer, I downgraded to the previous openbeta. Runs ok. Update again, same issue. So definitely the patch it is. From dcs.log, the last line also is: 2023-01-26 04:11:31.500 INFO EDCORE (Main): Loaded C:/Games/Steam/steamapps/common/DCSWorld/bin/CockpitBase.dll And from the previous version's successful launch, the next lines should be: 2023-01-26 03:43:56.006 INFO ASYNCNET (4408): Login success. 2023-01-26 03:43:56.900 INFO ASYNCNET (4408): Got auth data. 2023-01-26 03:43:57.090 INFO APP (Main): Successfully got authorization data. So I think maybe it's not something about CockpitBase.dll but with the Login part. The login screen never pops up, even if I clear the network and login related files under Saved Games/DCS. I wouldn't be so sure a fix is already on the way, since apparently most players are just going on with their lives, and only a handful of us are locked out of DCS by this problem. Also I haven't seen the mods talking about this anywhere in the Discord or forums. So hey @BIGNEWYcan you give us a little help here?

It's not just servers, I'm also having that problem as a client! DCS won't load no matter what!

FYI Yes Oculus has switched to OpenXR and is deprecating the Oculus proprietary engine. The setting on Oculus is just so you can set Oculus as the default OpenXR in the case some other engine (say,WMR) "steals" the preference.

Externally yes. It can sling load cargo, and should have an indicator for it. I haven't seen that indicator work in years though.

The stick going 'limp' is exactly how it is for any FFB stick, and also the real aircraft. It should maybe be only a little damped (you may not be able to feel it depending on your stick). But it goes limp until you release trimmer, then stays in the position you trimmed it to. It may be the Pitch Autopilot acting once you release the trimmer. It'll always try to keep pitch the same as when you released the button, regardless of how the stick is trimmed. But with limited authority while at that.

That's a pathfinding issue most likely. Units are trying to find their path so they get slowed down as pathfinding gets stuck in a recalculation loop, usually bringing a server's FPS down with it.

Sadly, nope It won't be fixed in the foreseeable future, or there is no guarantee that it will unless it eventually does benefit from fixes to other modules (e.g. the Hind's new sights).

You may have some rogue keybinds being activated... Or do you get a cross X in your HUD when you try to fire?