Sandman1330

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.

When I had the problem, that didn’t help. It was an issue with tracking, when you move your head it judders really bad, but otherwise was ok

It’s locked to 80 based on how ASW works. It needs to be exactly half the refresh rate of the panel, so 45 for CV1 and 40 for S. The reason is it replaces every second frame with an interpolated frame to give you full refresh rate with only half the frame rate.

I had the problem on beta, reverted to stable. I’ll have to try and avoid this stable update!

I find it extremely hard to use phoenixes in TWS mode for this very reason. They almost always miss because the track file gets momentarily lost while they are in flight. I am hoping TWS Auto, when implemented, may help...

All I get on final are tons of ‘nails’ calls from the ship’s radars!

I haven't had any issues with the throttle. It will loosen up with time and use.

Oh, I have those running in the background too since I have an ASUS Mobo... maybe?

I put them on the table, one beside the stick and one the throttle (left and right hands). I haven’t had any issues with the Rift S losing them that way. On a bit of a side note, did you notice that during guardian setup in the pass through, your (actual) hands showed up all white, as if the cameras were recognizing they were your hands? I’m wondering if they are working on native hand tracking... that would be a game changer!

1- I don’t think the buttons are bindable in DCS, but I’ve never tried; 2- right click is achieved by going palm up with the controller (turning it upside down). On the newer planes this corresponds with how your hand position would be to flip the switch up or down and makes a lot of sense when you think of it that way. Older planes like the A10C are a lot more confusing as they don’t follow this logic; 3- I just place them on the table beside my stick and throttle, usually easy enough to find

I find it much worse now. It’s good until there’s a hotter source, then it washes out to the point of unuseability (ie as soon as one target is hit and burns, the whole screen just washes out white) I know this is partially realistic, but the effect is extremely overdone.