Sandman1330

Ctrl numpad works again, I actually came to the conclusion that it no longer works when OTT is open, but works fine otherwise. It was when I did some testing awhile back, turning all settings to lowest then working up, that I found this problem. Even lowest settings, 45fps...

You may want to consider comfort. I’ve flown in an HGU-55, and now fly in a 56, and neither are very comfortable for long periods. Just a thought.

I think I know what you mean, it’s just the frame jumping from one to the next due to the lower frame rate. This is actually pretty much what ASW is designed to alleviate, which it does nicely. The trade off for this is of course the artefacting. Hopefully ED will implement support for ASW 2.0, which is supposed to greatly reduce the artefacts.

Best advice I can give, have your wallet ready because once you try it there is no going back! On a serious note, as far as DCS is concerned, mostly plug and play. Lower settings as necessary to get acceptable FPS. If you get stuttering or squiggly artefacts, try ctrl + numpad 1 to disable ASW. Happy flying!

He’s actually pretty correct, especially regarding point #1, which has been a pet peeve of mine for some time in game. Wrong section of the forum, perhaps.

I am CPU limited, I know that already. It just seems odd that it's exactly 40. Though the other day, after disabling ASW it was at 40 for awhile, then started to fluctuate back up to 50-60. I then turned ASW back on (as an experiment), and it dropped to 40, then would not go back up once I disabled ASW again. Strange. And yes, I am 100% sure ASW is actually disabling, as I know what artefacts to look for that indicate it is on (The squigglies and such).

I just tried it, and I felt it as well. Let me ask, are you using VR? The reason I ask is, with the hill directly in front of you on start, you are in prime position for something called "upslope illusion." This is the illusion that makes you feel that you are very nose down, because the apparent horizon to you is up in the sky (the top of the hill). The psychological impact is that you naturally want to raise the nose to bring it level to the "horizon," but of course it isn't the real horizon. Having done a mountain flying course fairly recently, I can tell you that this is a VERY powerful illusion. I can see it having an effect at the start of this mission, when you first pull into the hover. The other possible point is that you are so low on fuel, your C of G may be fairly far back - though the placement of the fuel tanks on a Huey is pretty close to the mast, so this shouldn't have a profound impact. I think it's the upslope illusion that you're feeling.

Interesting! I’d still like to figure out why I’m locked to half frame rate though, whether we look at frame time or FPS, I’m still capped at 40, very consistently and seemingly independent of where I look. I’d expect it to improve if I look at sky, but still no change. I’m going to try messing with Nvidia CP settings.

Thx Wexler, I just have to find time to try it out! I thought the same, but after some research it seems ATW works by filling in dropped frames on a frame by frame basis, rather than always replacing every second one like ASW. It doesn’t work by locking the frame rate, so that shouldn’t be it. I’m thinking vsync, but I also think I’ve already verified it’s off in the past. Hoping to check nvidia CP tonight and see if it’s gone back on or something...

Yes, ASW is turned off, that is what us Oculus users are trying to say. I’ve confirmed through three different methods and via the removal of the artefacting that it is definitely off. Reprojection is a non issue as oculus users do not even use steamvr, oculus is natively supported by DCS. Something else is locking our headsets to half frame rate, it is NOT ASW. https://forums.eagle.ru/showthread.php?t=201746

It’s definitely off in DCS, I need to dig into Nvidia CP and elsewhere to see if it’s being overridden somewhere...

Are you remembering to turn on the hydraulics as part of your cold start? Hyds off will cause cyclic interaction with collective movement, which can be felt and resisted in the control in real life but not in game.

The issue would be triggers - it would somehow have to also save the state of all the flags and triggers.

I used Ctrl+1, the OTT, and the oculus debug tool to disable ASW. All said it was disabled, and the artefacting (squigglies) were gone. I am 100% certain that ASW was disabled, yet I was still locked to 40 (Rift S) and 45 (Rift CV1). There is something else going on. https://forums.eagle.ru/showthread.php?t=201746

I’m having the issue connected to vanilla USB 3.0 ports, unfortunately. I am not sure if they are straight from the chipset or via an ASMedia controller, I think they are half and half, so maybe I’ll try a port in the other stack of 4 (I have 2 stacks of 4 USB 3.0, I think one is off the chipset and one off ASMedia)

ASW is definitely turned off, I’ve used the keypad, OTT and the debug tool. Further, the telltale squigglies go away. I’m grasping at straws with the steamvr theory based on a reddit post, but I think it’s a red herring as I also do not use steamvr, it isn’t even running when I play DCS. Yet, something is locking me to half frame rate (first 45 with CV1, now 40 with S) I’m stumped! I may put in a ticket with Oculus...

It’s ASW I’m trying to turn off (and everything tells me it is off), but something is still locking me to 40fps on Rift S. I had read a reddit post that said it might be steamvr since DCS runs over steamvr.

Thx, unfortunately this isn't it. I'm using Oculus, rather than WMR - I don't even have MixRealityVRDriver installed.

Still having issues, except now at 40 vice 45 for a Rift S. Tried to help out the team by submitting FPS numbers as they requested, but I’m locked solidly at 40fps. OTT and debug tool both confirm ASW is off, and the artefacts are gone. I read that steamvr needs to have reprojection disabled as well, but it was an older post and that option no longer exists in steamvr. Anyone crack this nut yet?

OpenBeta: Locked at 40 (ASW definitely off, but this is typical behavior - I haven't been able to figure out why) Stable: Also locked at 40. Appears this was a waste for me as I've still got some issue with Oculus locking me to 40. I'll continue to troubleshoot... Edit: Nothing I do works. Tray tool and Oculus debug tool both tell me it is off, and the typical ASW artifacts are gone - yet I'm capped at a very stable 40. So for what this is worth. Oculus Rift S Graphics Settings: ["graphics"] = { ["DOF"] = 0, ["LensEffects"] = 0, ["MSAA"] = 2, ["SSAA"] = 0, ["SSAO"] = 0, ["anisotropy"] = 4, ["aspect"] = 1.7777777777778, ["chimneySmokeDensity"] = 2, ["civTraffic"] = "", ["clouds"] = 1, ["clutterMaxDistance"] = 1500, ["cockpitGI"] = 1, ["effects"] = 3, ["flatTerrainShadows"] = 1, ["forestDistanceFactor"] = 1, ["fullScreen"] = true, ["heatBlr"] = 0, ["height"] = 1080, ["lights"] = 2, ["messagesFontScale"] = 1, ["motionBlur"] = 0, ["multiMonitorSetup"] = "1camera", ["outputGamma"] = 1.5, ["preloadRadius"] = 87700, ["rainDroplets"] = true, ["scaleGui"] = false, ["shadowTree"] = false, ["shadows"] = 1, ["sync"] = false, ["terrainTextures"] = "max", ["textures"] = 2, ["treesVisibility"] = 10000, ["useDeferredShading"] = 1, ["visibRange"] = "High", ["water"] = 2, ["width"] = 1920, PD = 1.3 System Specs: Ryzen 1600X @4ghz EVGA 1080Ti FTW3 Samsung 960 Evo 512GB 32GB Ram @ 3033mhz Nvidia 430.86 Oculus Public Test 1.38.0.256587

Yup. It only happened once for me as well, but that was after deleting the folders. Heatblur has already acknowledged that this is fixed internally.

Don't think so, just had it happen to me.

Just ran into this myself. So not only do we not need efuz to inst, but if we select it, the bombs won't come off the rails at all? Edit: confirmed, efuz must be off.

The HT setting is not where it was in Wags’ video. When you select TGT UFC, in addition to Posn you also get TERM, when you select that HT is an option in there

AIM 54 in SARH / STT mode is a beast though, works very well but basically acts as a super sparrow, you have to maintain STT lock. TWS so far is ineffective.