Cyborg71

I'm guessing this 'region' of the attitude hold model wasn't fixed in the last update. I'm still experiencing oscillations after engaging att hold having entered in a steady hover. Whether it 'holds' or not seems intermittent. Will check control bindings again, but it was working very well until 2.9 dropped.

12900k, 64gb ddr4 3600mhz, 980ssd, 4090, win 11

"Shack!!!!" This absolutely solved the stutters and hang ups for me. Now running MT at locked butter smooth 60fps. Thank you for sharing. Knowledge is power!.

Thanks to those directing me to the non "mt" exe. Single thread is consistent and reverting to it has removed stuttering entirely, though updated features (I've no idea how many) seem effected by this. For example, the grass no longer moves under a hovering Apache. I tried mt in various scenarios and settings (win/nvidia/dcs) and removing overloaded cores (no.8 in particular) but this had no impact on the stuttering. Problems lie in the mt - for me at least. Thanks to Bignewy for responding. Good to know its being addressed.

May I ask, where the exe. for running 2.9 on single and not multi thread is? I was unaware that I could start 2.9 in single thread mode. In anticipation.......thank you. Edit...... I will try the cpu core 8 infinity removal method as suggested by others here and report back.

12900k, 64gb ram, 4090, 980 ssd. Page file win11, dcs all on same ssd. Single player maps. I aim for 60fps locked with vsync. Not bothered about 200+ fps contests. Same as above posts. Frequent and random stuttering. Same freezing in game and menu. Core 8 pegged at 100%. Have tried the affinity fix, seems to help out with freezing, but stuttering continues as another cores (sometimes 9 or 10 or 13) becomes equally overloaded. Other cores no load at all. Single thread offered butter smooth locked performance in both 2d & vr. MT performance is pretty dire for me.

Same as tusler. 12900, 64gb, 4090, everything on the same samsung 980 ssd. Previously on ST, butter smooth 60fps 2d and smooth vr. (Oculus rift) MT causes frequent stuttering and hitching in 2d and vr. Slow loading and freezing in menus. I will go through the list of usual suspects to try and eradicate this. I've noticed that one core seems over loaded (usually no.8) removing that core does little to improve.

On a similar note, is the general cockpit noise (in which I mean the background rumble) accurate? Whilst sat on the ground at Idle, it sounds as if the engines are at full military power. I had to keep checking to see if my throttle axis was faulty, which it was not. Is that just the standard F15 electronics ambience (like in the f18?) I agree about the AB sound. A little "thump" would be useful.

Either way, when I finally fired the first Lima and it performed that little Tokyo drift before going ballistic I let out a silly satisfied giggle. I didn't know if it was accurate to real life - but it just looked correct. Great work.

Thank you. That seems like a potential solution to the excess range of motion.

That did it. So much more to learn. Thank you kindly.

Thanks for the quick response. Will give it a try.

Is it correct that CP/G George is intended to be used by the pilot? When instructing George to look for a target he will do so. He will offer target options for selection, but his dashed target cross in the pilots hdu does not lock to the chosen item. It stays centred and boxed (diamond). This is corroborated by the dot indicator at the bottom hdu display is stationary. His head is also not moving? This creates problems for turning towards a locked adversary as I've no idea where it's situated relative to the aircraft. I may have missed something obvious, is it me or is it a bug.....

My greatest concern will be the "swing" at the business end of the grips. I use the virpil ka50 collective. It's a great peripheral. But even with the smallest cam installed the movement action from bottom to top is already enormous. (For me anyway) With the extra length of the apache collective, the swing will be gigantic. I'm all for granularity in control feedback, but pumping your left arm up and down by inches rather than mm will feel unrealistic. I hope they have some plan to deal with this (even smaller cam maybe) and the additional weight.

Thank you for your replies. I have been using the method (2) up to this point, but will now try the ftr held as suggested. Again, contextually, I'm using Komodos Apache cyclic, so the buttons are roughly in the right places. To echo Floyd1212's comments, it's pretty awkward to persistently hold that button up whilst finessing the cyclic. I accept (of course) that the sizing, feel, feedback and operation of what I use is not the irl version.

Just a final clarification in relation to force trim (excluding hold modes) please. When using force trim to achieve the intial trimmed position, should the force trim button be - 1. Held in the "on" position whilst cyclic adjustment is made and then when happy, the button is released? 2. Cyclic adjustments are made and when happy a quick 'click and release' of the force trim button to establish the new trimmed cyclic centre? For context, I'm using an unsprung clutched cyclic. Recent chsnges to open beta have improved a previously sketchy hover hold for me. In flight attitude and altitude modes not so much.

Is it possible this attitude hold problem is related to ffb settings in game. I was experiencing no attitude (hover hold) issues prior to update. I have tried 2 set ups with 2 different results. I have a hydraulic komodo cyclic replicating force trim (set as ffb no springs) Hover hold possible prior to update. Since update, the ability to select the mode is intermittent (even from a trimmed hover). When it does engage, oscillations commence, eventually causing control loss. I did notice (with the controls indicator on) the little green cross (fcs?) was making some random severe movents from centre of the cycic indicator diamond. In forward flight attitude and altitude modes work ok. Using a standard sprung warthog stick (central trimmer mode) hover hold works everytime. I want to blame the komodo cyclic, but all was fine prior to the update. Is the ffb option bugged?

Your comments are much appreciated as they answered what I needed to know. Many thanks.

In 7 years of DCS, I've never used multiplayer in its standard format. I'm building up to that, but I'm not convinced my internet speed is good enough for it to be a positive experience. The only online I've engaged in ever, is xbox Halo. So, consider my overall knowledge less than that of a visiting outer space alien.... I have 2 PCs. Both are very DCS capable. I have a single private wireless network. Each PC has DCS installed with the Apache module. Identical maps etc. I only have one DCS account and one Apache module (everything just replicated on both PC's) Is it possible for me to use both PCs at the same time on the same map to either, a) fly with a wingman b) fly with a cpg or pilot using both pcs to operate the same aircraft. I'm assuming at the very least I will need to create a different DCS account and buy a separate Apache module for one of the PCs. Then I've no idea how to go about setting up a private closed map to play on if that's even possible. My wifes a helo fan and thinks the Apache is cool. With the right set up I think she could be a muderous cpg. I wait in anticipation of being educated by the community. Cheers.

I have no idea if my use of the Nvidia control panel to force vsync 'on' has any impact on fullscreen status in DCS. I can say that GPU usage (%) is lower. FPS is more stable (60). It's effectively back to pre-patch for me. The overall presentation is smooth. Occasional stutters exist. But they've always been there. Drops from 60-59 stand out blatantly to me, even if only for a fraction of a second. I may just be over sensitive to stutters. Some people just don't see them. Lucky bug***s. Oh I agree it's not solved. I found a solution for my specific issue. I would love to have that Alt + Ent feature returned. A quick key stroke is preferable to spending hours locating a work around.

Ok. Firstly apologies if this is unhelpful to others posting here. Those for whom the Alt+ Ent issue is still a sorely missing feature (vr mainly or multiscreen) it is probably of no use. After 6 hrs of fiddling I resolved my individual issue. In Nvidia control panel I set max frame rate off (had been set 60 to match monitor) I set Vsync to ON (had been set to control by 3d application option - thinking DCS would take care of it) All other nvidia settings are at default. In DCS vsync is ticked, Full Screen is ticked.(my defaults anyway) This simple change fixed performance problems in both graphic fidelity and returned my GPU load back to below 50%. Go figure. Thanks to all for the input. I will mark this resolved (for me) I hope others can find solutions as well. Cheers Big Newy.

Absolutely agree. My intent was to establish if this is a problem in my case only. Obviously it's not. I'm trying to understand why it looks like I'm in Fullscreen, selected options indicate Fullscreen, yet my GPU metric data is feeding back the opposite. What (and I've said this already) is odd is I could actively impact the workload of GPU positively from 85% plus to 60% plus/minus by pressing Alt + Ent. Something was happening when the combination was pressed, and it was beneficial. Now the GPU sits 85-90%. Period. The fact that others (the majority) are fine is of course primary. I am fortunate that I rarely have issues. Even then, there's often a work around. I think Spock or Kirk said something about the needs of the many........ I will do further tests. But I think I've tried everything obvious.

If I set the solution it was accidental. I have reset it.

I am actually seeing a performance reduction though. Not necessarily FPS, though I'm seeing more drops from 60 to 59 which has a visual impact of micro stuttering. Unless a gpu is doing better at 90% effort than 65%. Vsync is always on for me. The tearing with it off is immersion breaking. I guess my gpu could be a problem, but it's only weeks old. But why the easing in gpu workload with Alt + Ent? I am exclusively in 2d incidentally.