Svsmokey

:thumbup:

One thing i will consider between the two is vram . DCS Vulkan implementation should land during the next gen's lifecycle . Given equal or near-equal performance , whoever offers more vram wins for me .

Did i read somewhere that the Rift S cable unplugs from the headset ? A long shot maybe , but have you tried unplugging/replugging ?

Nvidea "power"= "max performance" Texture quality = "max performance"

CH stuff tends to last forever ...i still see the CH sub-forum , it is just moved "up" from where it was .

I get that a lot :) There is no "n" .

Yeah , i understand what you are saying , but the fact is it is yet a month or more too early to ask the question . Even with the hardware in hand , it's gonna take a couple weeks or more to tune and evaluate .

Exactly . I wonder if lot of this is more about bragging rights than realistic performance increases .

No one is saying the tech is mature . We all look forward to better hardware and software implementations . But many of us see gravy with our potatoes :)

Indeed , i have found them helpful and well-presented .

Wow . Wasn't expecting this so soon...

Whatever distance you like . Figure 300 feet of altitude per mile .

So what is the point of your OP ?

When i was running 1080p , i thought 2x msaa and 1.5x ssaa looked very good .

Me too , if only to rid myself of forced updates . That will be a factor in my next headset selection .

True , but as all those are viewports , it does make a significant difference .

Works very well for me wearing headphones over the Rift . No longer have to keep an eye on the IFEI climbing after a pass...it is a muffled "boom" sound kinda like a delayed gas grill lighting :)

I'm thinking more along the lines of a jetseat .

The new usage is to undesignate to return the pod to snowplow mode . Alternatively , you can flip the flir swith to standby , and back to operate .

Absent information about hardware or settings , one can only make the most general of observations . In my experience , the occasional micro-stutter is to be expected . However , one can gain a generally very smooth experience by a framerate cap , and adjusting settings to provide a decent amount of headroom over that level . This works particularly well with 60hz monitors as you can check vsync in the DCS settings , and adjust settings as stated . You can also cap the framerate in Nvidea settings (and presumably AMD) or Rivatuner . The basic idea is to lower settings to provide headroom over the frame-cap sufficient to allow ai , clouds , cities weapon firing etc . I assume you are running on an ssd ?

Well done ED !

Agree , unnecessary fluff .

Dreamer ! :)

You are correct re: option 1 I take no offence , and hope you don't either . Note that i am currently running an S , and don't run Steam VR . Have downloaded it (twice) , but i find Open Composite for sims that would otherwise require it runs better . Perhaps we can end this excursion , and allow The G2 topic back on to the rails ?

(1) pointless to argue further (2) Thank you , i will :)