Svsmokey

I run at 60 , and stay there except for airports and the supercarrier . Then i am at 30 with motion smoothing . I do not , however , run complex missions .

FWIW , i am also running my 9700k at stock clocks (at least at present) with similar DCS settings , and with far better performance on an inferior (as compared to a 3090) gpu . Have you run FpsVR to check for bottlenecks ? Also running CpuZ during a test will verify pcie lane usage . Another thing to check might be power to the gpu if fpsvr shows the problem there .

Also , it appears that you have Steam global resolution set to "auto" ? I personally had no luck with that setting . Try 100% instead ?

In your bios . "Memory" or "ram" section , "enable XMP" . This allows your memory to run at 3200 or 3600 as opposed to 2133 or 2400 .

Isn't that a view ? Stuck view key ?

Amen , brother . I guess it is human nature to be more concerned with what we don't have , rather than what we do..

As someone else said , "to what end" ? Do you really want ED to divert resources to modeling engine characteristics with different fuels under different conditions ? Do you really think that is the best use of their time ?

Can't say I find your post particularly helpful . Real pilots flying real aircraft have long-throw sticks and control-force feedback cues to assist smooth flight , and particularly out-of-trim conditions . Desktop pc pilots have neither . I do not feel that asking for a desensitised trim button function is an unreasonable request under those circumstances .

It seems the merest micro-flick of a trim button still overshoots the desired effect . While one can often compensate with a throttle adjustment after a pitch trim change , this is not always feasible , particularly when maneuvering low in a trim-sensitive aircraft like the L-39 . Even the Hornet suffers from this effect in in the roll axis when sequentially releasing individual weapons .

I find the rudder helpful when using a targeting pod as well . Unless you are flying exactly directly toward where the pod is pointing , you will see the reticle drift across the landscape before designating a target . Holding a little rudder can cancel this . Also , as previously noted , the rudder is very helpful for fine corrections when using the gun .

Thing is , in the aircraft i fly , (Hornet , L39 , Huey) the only times i may need to toggle the the pilot body off are when parked . I personally am willing to accept the compromise so i can be immersed when it counts-taxiing and flying .

It does occasionally happen here . I have no idea why .

Huey (i think) , L-39 also have pilots . I hope the MB-339 will as well !

I'm having a blast running the G2 at native res (Steam VR at 100%) - with a 6800xt . I actually prefer to run it at 60 hz , with motion smoothing (similar to ASW) off . I spend a lot of time very low , and morphing/ghosting buildings with smoothing on are not pretty . I run generally high settings in DCS graphics as well , and don't use any shader mods . Rolling , pulling and and view panning over cities is smooth , although i do get an occasional micro-stutter that does not appear to be related to the graphics load (like in the countryside with few trees) and with the gpu/cpu graphs in the green . I'm thinking its a Windows thing , and am gonna try a couple of tricks to resolve . Turning off memory compression for one , and i ran across a YT video on 6800xt tuning that mentioned turning off a couple of (very obscure) windows settings as well . Some complain about seeing a flickering around the edges of the view at 60 hz , some say they got used to it and it was no longer an issue after a few minutes . I guess i'm lucky 'cause i never saw it . Maybe it's only with Nvidea cards ? In any event , i highly recommend trying it .

Here https://authentikit.org/spitfire-chassis-lever-released/

Have you increased minimum clock ?

Understood and agree . When i had the RiftS , i ran pd1.4 . When i ran it with my old 1070 , i couldn't get past 1.0 . I was responding to the previous "motion vector" post . Motion smoothing works seamlessly with AMD in my experience . Again , raising minimum clock speed is key to smooth AMD performance .

I'm running DCS pd 1.0 and Steam VR res at 100% .

Motion smoothing works well with AMD . Motion vector at this point in time does not . The only time i see less than 60 fps is on airfields and the supercarrier . This with fairly high DCS settings and Steam VR res at 100% .

I know of no VR AA solution in the current engine , irrespective of headset resolution or graphics card maker . I use MSAA×2 , but that only ameliorates the problem under some circumstances , and decreases sharpness . I don't even fly the Syria map i purchased because of the aliasing .

Use custom graphics setting in Radeon software . Most importantly , set minimum clock speed to 100 less than maximum . Ramp up the maximum clock to whatever you're comfortable with . I run about 90% of max . Under the performance tab , set power level to 9 . Adjust the fan curves for a more pre-emptive setting . (Unsure if fan is under graphics or performance tab) . Run a Radeon stress test , and increment max clock if you have the temperature headroom .

I'm very happy running 60 hz . Allows me to run high Dcs settings and 100% resolution , and runs butter-smooth very low over cities while rolling , pulling and panning the view without any shader mods . Only time motion smoothing kicks in (seamlessly) is on airfields/supercarrier .

Authentikit has one for the Spitfire MK1 ... https://authentikit.org/spitfire-mk1a/ Not sure about a neutral though...

It can't come soon enough for me . I don't buy a lot of aircraft (I have Hornet , Albatross and Huey , and will first-day buy the MB339) simply because i can't fly too many competently , but i also support ED by buying maps (and the Supercarrier) , even though the Caucasus remains my favorite . I personally find it wrong-headed to threaten to cease purchases until the release of Vulkan/multithreading , as purchases support its development . I do get a little frustrated at times though , at the continued further loading of an already-struggling engine .