SharpeXB

I use Arrow Up for my center view since it seems universally assigned in flight sims for plane control, which I don’t use. Plus it’s easy to find. Now that I read this I don’t recall deliberately un-assigning this in DCS. Have you tried simply using a different key? Just to test. (Oh I see you tried F12) Could “-“ be hard bound somehow? Maybe check the General category as well as the aircraft module.

It’s funny that there are forum rules about writing in all caps because that’s odd and distracting. But not rules about excessively bad writing, grammar or spelling. That’s actually more distracting. Yes English isn’t everyone’s first language but that’s true for readers as well. Someone who doesn’t read the language well won’t understand your post. A simple “excuse my English” in the signature line might be appropriate. It’s especially laughable when people (from English speaking countries) can’t bother to spell or write the aircraft names correctly. Oh and the plural of aircraft in English is aircraft.

I had a 13900K which ran DCS just fine without overclocking, the gains from that are rather minimal. I would be very careful about using anything but the Intel defaults with those chips after that degradation problem. I don’t notice any trouble running my 14900KS on the defaults. I have an Asus Z790 and don’t see the options you mention, maybe that varies between product lines (I have similar choices just called something different). I selected defaults via F5 in the BIOS and do not have the motherboard OC activated.

Yeah I don’t really know why this restriction is there but it must be for a reason. I won’t speculate on how that could be used for cheating.

Sure but you can use any of your own gameplay or tracks to evaluate this. A standard track seems like an easy logical solution and in many ways it is. Yet it hasn’t been done, probably for all those reasons above. It’s worth remembering that the track feature was meant as a debugging tool. Not other uses like a benchmark.

Again my guess is that pure textures are enforced to prevent cheating. So any custom textures will have to deal with that restriction.

Custom liveries are very cool. But the only way for other players to see them is to have them installed. That’s not too likely. If there was a way for players to submit these to the devs and then have those released as official packs, that would work. But I don’t see that happening.

What’s the point of using custom liveries online? Nobody else will be able to see them as it’s unlikely they will have those installed. My guess is Pure Textures are enforced to prevent cheating.

I just find changing the rate to feel clumsy especially if it has to be 125. I would change it back to 1000 after exiting DCS

No The problem can still occur with GUHB off, but I have it on in order to change the polling if I need to.

Right, players shouldn’t have to mess with Windows to run the game. I don’t think core parking matters one way or the other though.

I’d rather not mess with that. It’s easier to just Tab out to GHUB and change the polling rate whenever this happens. I run other things besides DCS and changing things like that every time I run it is too much work. The mission was the F-4 Marianas Cold Start both times. I only have one. The other ID might be from a previous Windows install. That device was turned off during this session. The Wolverine was powered off and disconnecting devices continually is a pain. Again it’s easier to just Tab out and change the polling.

I kept the rate at 1000 in both those logs. The stuttering doesn’t always happen. Those two logs were made with the same mission and settings. After I restarted DCS the stuttering didn’t happen.

I don’t believe the AH-64 uses that to land on a ship if it did. Does it?

Setting a higher polling rate for the mouse causes stuttering. Logs attached, one with and one without. The effect seems to occur randomly. DxDiag.txt dcs no stutter.log dcs stutter.log