Low End VR settings that "work"

[VO101_TB]

Do you guys able to join multiplayer sessions with the shader mod?

 

 

Sent from my iPad using Tapatalk

[hansangb]

Do you guys able to join multiplayer sessions with the shader mod?

 

 

Sent from my iPad using Tapatalk

 

 

In the thread, there are files that you can remove to pass the integrity check. It's one of the later (towards the end) posts that reiterated what files.

[Harlikwin]

Ok, quick update...

 

FORCE IPD!!!

 

IF you haven't played with this setting do so.

 

Figure out your IPD and then force the game IPD to near that value and change it by .5mm increments around it. I got a large increase in clarity of the rift and overall more clear FOV by doing this. Prior to it I was seeing like the center 1/3rd kinda clearer than the rest of the FOV, after this fix its more like 80% of the FOV looks good, and I can finally see the MSAA mask window. Not sure if this applies to headsets other than the rift, but I don't see why not. My IPD is near the large side, so I think whatever the default is must be near the low or mid end of the range. Geeze that only took 2 weeks of having a rift to figure out. (I calbirated it before in occulus home) but never forced in DCS.

[Fakum]

Thanks for this thread OP. I have been on the fence with this for a long time, primarily because of what it will cost to upgrade, and the uncertainty of what headset to get. All of this chatter seems to be revolving around Single player activity, yes? If so, is there a more concerning impact when it comes to running in Multiplayer? I ask because that is primarily what I do. Thank you,

[FragBum]

As an observation MP seems to impact more on CPU then GPU although MP will use more GPU VRAM and more system RAM.

 

As for PD vs MSAA, it seems MSAA is post PD, that is for a given amount of MSAA the PD amount delta ramps up GPU and CPU usage hugely. Just have a look at taskmanager as you change the PD value. Personally I prefer MSAA processing with a small amount of PD but that is very much a personal preference and very dependent on hardware, if I can I also add a bit of AF even *2 or * 4 even better but you can work that out.

 

Lower clutter and visible range and textures.

 

TBH your choice is pretty much made, Rift doubly so if your on standalone DCS version. Also follow Harlikwin 's guide, it's a matter of what eye candy you can accept for FPS/smoothness.

 

 

I'm not sure but maybe the last patch changed frame rate aka processing overhead but I had some other hardware issue to work sort out at the same time though. Bah Humbug. :cry:

 

YMMV :)

[Harlikwin]

Fakum,

 

Your system is better than mine. You shouldn't have many issues with a rift. The 980mobile card has like half the performance of your 980ti. And your CPU is running 1.2ghz faster than mine. So you should be fine with a rift at least. That being said it seems like guys with higher end stuff aren't really running much nicer settings than me so who knows.

Edited January 26, 2019 by Harlikwin

[Harlikwin]

On other update. I'm on 2.5.4 stable now.

 

With my PD 1.2, MSAA 2x, and medium settings for most things aside from textures. I'm pulling 20-30fps stock game. mid 30's-45 with the shader mod on (plane/situation dependent). So thats basically similar what was going on with 2.5.3.

 

I recently tried enabling the stero shared parser mod (graphics.lua set to true) I'm still evaluating it, but 2 things that are noticeable. The first is I don't see any additional graphical artifacts. Secondly some planes that were marginal like the mig 21 are now more usable, albeit still at lower frame rates, I have a 2 on 4 scenario over the caucus with the mig that I've been using for bench-marking. I think enabling the shared parser got me a few more fps based on what I was seeing before its mostly running in the mid 30's with some ups and downs which is playable for me. Similar results for a Gazzelle mission I was running. On the runway without the mod it was mid-high 30's on startup, and its now in the low 40's.

 

I'll post my updated settings at some point.

 

Also, this is all single player, I haven't really ventured into MP due to time/noise constraints.

[Svsmokey]

Thanks for the update !

[Fakum]

Fakum,

 

Your system is better than mine. You shouldn't have many issues with a rift. The 980mobile card has like half the performance of your 980ti. And your CPU is running 1.2ghz faster than mine. So you should be fine with a rift at least. That being said it seems like guys with higher end stuff aren't really running much nicer settings than me so who knows.

 

 

True, but Im flying helos right now, and the grass and all are pretty nice to have when your that low, I see yours is shut off completely. Just make me wonder how well off I really would be. Then there is the "Which Headset", especially if I wear glasses.

[Lensman]

True, but Im flying helos right now, and the grass and all are pretty nice to have when your that low, I see yours is shut off completely. Just make me wonder how well off I really would be. Then there is the "Which Headset", especially if I wear glasses.

 

You'll be fine with that rig. I have the same cpu as you and had a smooth experience with the RIFT before I upgraded from the GTX 980, and mine wasn't even the Ti version :)

[Fakum]

Hmm,, sounds enticing! Thanks guys

[Harlikwin]

True, but Im flying helos right now, and the grass and all are pretty nice to have when your that low, I see yours is shut off completely. Just make me wonder how well off I really would be. Then there is the "Which Headset", especially if I wear glasses.

 

Ive got grass n trees on about half. Ill post updated settings. If you fly Helo's VR is a mind blowing must. Prior to VR, I could barely land one, now I'm zooming around 2-5 meters above the (not exaggerating that) terrain in the gaz at 200kph with zero issues. Under power lines, zipping down city streets etc. There is a 1000% difference for Helo's and VR.

Edited January 27, 2019 by Harlikwin

[Fakum]

Oh,,,,, your killin me! can you talk to my wife for me ? LOL

[Harlikwin]

Here they are. This is with the VR shader mod, and the stero render parser enabled. I'm getting high 30's to 45 most of the time in the Gaz, similar in other helos. No judder or other issues. IF I use the Viviane sight it drops the frames into the 20's but I'm in autohover at that point and just cope with it, and just shut off the screen during flight. Most of the good planes hang in the 40's, the mig21 is in the 30's now, almost playable.

 

I also changed the driver settings. Mainly to fewer pre-rendred frames.

 

Anisotropic filterin (app ctrl)16x in game

Antialiasing FXAA off

anitaliasing gamma on

Antialiasing mode enhance

Antialising setting 2x

anialiasing trnasperancy off

Max pre-render frm 1

monitor tech fixed refresh

MFAA on

OpenGL auto

optimize for compute perf on

power management max performance

shader cache on

Texture filtering on

negative lod bias allow

texture filtering quality high perf

texture filtering trilinear opt on

threaded optimization auto

triple buffering on

vertical sync use 3 app setting

vr pre rendered frames 2

Edited January 28, 2019 by Harlikwin

[Fakum]

Have you tested any other headsets besides Rift? Thats my next step, trying to figure out which one. Comfort is a major concern, especially if I have to use my glasses.

[Harlikwin]

Sorry no. My system is low end so I figured the Rift hungers for the least pixels. I can't comment on glasses but I think there are guys that use the rift with it. Also, I think at least some headsets come with the option for prescription lenses.

 

 

Other than that for "next gen" I'm actively looking at the Oddesy plus (seems to have comfort issues) or Pimax 5k (maybe not that much better than rift) but I'll have a much higher end system for those, which I'll probably get summerish. I'm also waiting to see if the Vive Cosmos is higher res, or whatever new headset occulus will launch. I've come to the conclusion that that whatever comes next just needs a shitload more pixels for DCS, which unfortunately means a better gfx card/proc, plus whatever ED does for VR optimization. So until then the rift is it, and it might even serve into next year if something "better" doesn't come along. The main "winner" from what I can tell is the O+, but its currently sort of a shitshow getting it to work, plus people have mentioned comfort issues. I'm not sure pimax actually offers any better "res" than the rift or O+, and I really don't care that much about FOV at the moment. I think the main focus needs to be to get the current FOV to a good resolution first, then expand the FOV.

 

also just posted the updated nvida settings to go with the DCS settings.

Edited January 28, 2019 by Harlikwin

[Fakum]

Thank you sir,,, great feedback, much appreciated

[Svsmokey]

True, but Im flying helos right now, and the grass and all are pretty nice to have when your that low, I see yours is shut off completely. Just make me wonder how well off I really would be. Then there is the "Which Headset", especially if I wear glasses.

 

I wear glasses . Currently , i don't wear them in the Rift for fear of scratching the lenses . I have some lens-covers coming and will use those until i get the prescription rift lenses and frames .

One factor in my choice of the Rift was , as Harlikwin inferred , balancing performance and resolution . Higher resolutions with the same frames are gonna require better hardware .

Other factors were comfort and refinement . I had the Rift on for 3 hours at one stretch today , and it was just as comfortable when i took it off as when i put it on .

Incidentally , i have "grass and clutter" set at about 60% thus far .Your GPU is comparable to mine , so i don't think that will be a problem .

Edited January 28, 2019 by Svsmokey

[Fakum]

Thanks,, oh man,,, the opinions out there are ENDLESS! So difficult to decide. Since you mentioned glasses, are they really that close to the lens that it may be a concern? im gonna have a hard sell with the wife as it is,,, to buy special lenses is gonna be a BIG issue. I also watched a video that shows a guy with glasses putting on the Rift and the Samsung,,, what a difference,,, the Samsung was hands down the winner,,, but there are SO MANY more differences. This is going to be difficult. I want clarity in the cockpit (who doesn't, right). Thanks,,,

[Svsmokey]

Thanks,, oh man,,, the opinions out there are ENDLESS! So difficult to decide. Since you mentioned glasses, are they really that close to the lens that it may be a concern? im gonna have a hard sell with the wife as it is,,, to buy special lenses is gonna be a BIG issue. I also watched a video that shows a guy with glasses putting on the Rift and the Samsung,,, what a difference,,, the Samsung was hands down the winner,,, but there are SO MANY more differences. This is going to be difficult. I want clarity in the cockpit (who doesn't, right). Thanks,,,

 

One can wear glasses in the Rift , but putting on some lens-protectors is strongly advised . The ones most used are made for watch-face covers , as they are curved , and so fit the Rift lens . $18 on Amazon . Thing is , the Rift lenses are not replaceable , so scratching them is a big no-no .

 

As for the wife , a Rift with prescription lenses , and the one-piece frame made for them available on Ebay , and a set of lens protectors should you allow another glasses-wearer to demo will total a bit over $450 .

 

There are a lot of factors to juggle and , as always , a lot of conflicting info to sort through . I hope you will be as happy with your choice as I am with mine ...

[Harlikwin]

I mentioned it in the other thread, the stero parser enabled does seem to help some in terms of frames, but it also seems to cause 2 things: First I think its causing a random occulus crashes (DCS runs/tracks in pancake mode) but the headset is blacked out. Or DCS just plain crashes.

 

I had a few nights with these crashes, turned the stereo parser off and no more crashes last night.

[imacken]

Have you tested any other headsets besides Rift? Thats my next step, trying to figure out which one. Comfort is a major concern, especially if I have to use my glasses.

All I can tell you is that the Vive Pro is, for me, way more comfortable than my Rift was, and also I can easily wear my glasses with the VP, which I couldn’t do with the Rift.

[DeltaMike]

What does terrain texture do? I was reading a manual for an older version of DCS and back then it sounds like it had something to do with the number of buildings that would be drawn in. If that's still the case, setting that to low might help low end systems, although I wonder if that won't have more of an effect on CPU.

 

I didn't notice much difference in VR with it low or high, so I left it low. But I was flying round in the boonies at the time, so...

 

Fortunately a lot of the adjustments I made to accommodate VR don't have much effect on the experience flying around at angels 20. I imagine helicopter pilots feel differently; imagine they want the grass, trees, shadows and terrain detail I can live without

[Fakum]

What VR headset do you have?

[Harlikwin]

What does terrain texture do? I was reading a manual for an older version of DCS and back then it sounds like it had something to do with the number of buildings that would be drawn in. If that's still the case, setting that to low might help low end systems, although I wonder if that won't have more of an effect on CPU.

 

I didn't notice much difference in VR with it low or high, so I left it low. But I was flying round in the boonies at the time, so...

 

Fortunately a lot of the adjustments I made to accommodate VR don't have much effect on the experience flying around at angels 20. I imagine helicopter pilots feel differently; imagine they want the grass, trees, shadows and terrain detail I can live without

 

I haven't noticed anything different graphically with terrain high or low. So I leave it low. My understanding is that the only difference is VRAM used based on an old thread. Regular textures I leave high as it does help with gauge readability and overall cockpit look and its not a big performance hit.