Jump to content

Recommended Posts

Posted

I've been searching on Google but haven't found much. At one point I had it looking pretty sharp minus text on guages or dials but I forgot what I set them too.

 

I think it was VR preset with texture and terrain to high, everything else default, hdr on, and msa 8x and aa 2x. One of these filtering options made it smoother looking I can't recall if it was msaa or aa and if you only need one or both.

 

Sent from my Nexus 6P using Tapatalk

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

Posted

Indeed, what is the story about msaa and AF? Do they compliment one another? I must do some more testing of these settings, I'm very new to 2.1 & nttr..

i5-7600K @ 4.8 | 32GB | 1080 | Rift S | TM MFD & WH HOTAS-10mm ext + TFRP

Posted
I noticed if I keep deferred shadows on it makes the map too bright, almost washed out kind of at least on nttr.

 

I was reading something on a post that mentioned hdr on helps with the visibility of the labels. I think I noticed 4x msaa is a bit more choppy than 8x which is weird.

 

I noticed the seating position is odd too. It's like I'm sitting on the edge of the seat. Couldn't find a way to calibrate the seating position the rift shows you in the a-10. But I noticed if you press numpad 5 it centers it but it's too close up. If you lean your head in and press numpad 5 again it zooms it out just a bit.

 

I'll try and find that post from Wags. I think 2.1 still needs some optimization for VR. Even with a pixel density of 2.5 it didn't seem to make the labels more clear..probably since the seating position is so close. It did make the head movement just a tad slow but not unplayable.

 

Sent from my Nexus 6P using Tapatalk

 

 

You can manually move the pilot position around the cockpit using in-game keybinding. I re-assigned mine so I don't remember default but I belive someone posted the answer on page 1.

 

I spawn plane

Hit VR reset

then manually move myself around with my keyboard left/right/up/down etc until right.

Now I know exactly where to move each time and takes little to no time/effort

Posted

Mostly 1.0 but sometimes 1.2 just to test the diff..

 

I do have my "digital vibrance" up to 70% in the nvidia control panel.. I read that may help.. I can tell colors are better but not sure on dial clarity.

 

Also read to turn off most of the nvidia controlled stuff in DCS VR and let the game take over. (so many opinions on the internet lol)

 

btw, just noticed that the latest dcs update only allows msaa 8x & aa 16x

Posted
I think there is a fix to that.

 

You need to edit the file HUD_base.lua. File is located in ..\M-2000C\Cockpit\VTH.

Change this line:

local mask_material_TFOV = MakeMaterial(nil,{204,255,204,5}) -- light green

To this line:

local mask_material_TFOV = MakeMaterial(nil,{0,0,0,5}) -- black

 

Let me know if it helps!

 

 

Mine is a .tga file... how are you guys editing this file?

 

Maybe I am looking in the wrong place.

 

 

 

and on the gamma 1.5 thing, how would this help? isnt that making your screen brighter??

Posted
Mostly 1.0 but sometimes 1.2 just to test the diff..

 

I do have my "digital vibrance" up to 70% in the nvidia control panel.. I read that may help.. I can tell colors are better but not sure on dial clarity.

 

Also read to turn off most of the nvidia controlled stuff in DCS VR and let the game take over. (so many opinions on the internet lol)

 

btw, just noticed that the latest dcs update only allows msaa 8x & aa 16x

 

Ok thanks, but have you tried boosting your PD and reducing msaa/aa level? I'd like to know what would come out best and your opinion on it.

I'm a bit reluctant to even use msaa with higher PD because it seams like they both do the same thing (supersampling?). My experience is that it becomes a bit choppy even with 2x msaa and PD level at 2 and i have a pretty high end system and the 1080 TI

I might be wrong, that is why I would like someone with the knowledge to clarify the subject.

Posted
Ok thanks, but have you tried boosting your PD and reducing msaa/aa level? I'd like to know what would come out best and your opinion on it.

I'm a bit reluctant to even use msaa with higher PD because it seams like they both do the same thing (supersampling?). My experience is that it becomes a bit choppy even with 2x msaa and PD level at 2 and i have a pretty high end system and the 1080 TI

I might be wrong, that is why I would like someone with the knowledge to clarify the subject.

I use msa 8x and AF at 4x with PD of 2.0 and I rarely notice any choppy behaviour. My settings are about one page back but looks like now I need to look into that article posted above.

 

I notice very little difference in PD of 2.0 and 2.5. Only slight improvement from 1.5 to 2.0 too. It's not that the text is hard to read its readable it's just blurry. If I could get it a tad bit less blurry I wouldn't get nauseous which is odd because normally I'm fine.

 

Sent from my Nexus 6P using Tapatalk

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

Posted

I will test later...

 

 

Hey, btw.. I didn't realize VR has zoom feature in DCS, I have been missing out!!

 

go to controls, open the aircraft menu on the top left and scroll down to UI Layer, and you'll find the VR UI Zoom option in there.

Posted
I use msa 8x and AF at 4x with PD of 2.0 and I rarely notice any choppy behaviour. My settings are about one page back but looks like now I need to look into that article posted above.

 

I notice very little difference in PD of 2.0 and 2.5. Only slight improvement from 1.5 to 2.0 too. It's not that the text is hard to read its readable it's just blurry. If I could get it a tad bit less blurry I wouldn't get nauseous which is odd because normally I'm fine.

 

Sent from my Nexus 6P using Tapatalk

 

Tried again with your setting and no other objects in the map and the frame rate was was fine, the mistake i made was loading up a mission with lot of objects in it.. I do however feel that the background is still very hazy. Maybe the above thread will have a solution. Please do post if you have new settings and you are happy with it. I kind a feel the same way about the nauseousness.

Posted
Strange, I don't get nauseous when flying dcs (maybe a little at first)..

 

Is that a frame rate thing? I see you guys have PD pretty high, maybe thats causing it?

I only get nauseous when looking at the cdu or trying to read the guages, etc. The text is readable but has a blurry effect. The HUD is super clear with a PD of 2.0 so I dunno. I'm about to mess around some more with my settings. Will post back.

 

Sent from my Nexus 6P using Tapatalk

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

Posted
Have you tried using "Night Mode" in VR? it works really good for daytime flight in DCS.

 

I would not fly night missions in night mode though..

 

_________________________________________________

 

I highly recommend turning on tool tips, this way when u highlight a dial you can read the big white lettering..

 

I also turn on both antialasing options up to 16x. works well for me. (sorry forgot the names..

 

Never turn on v-sync in VR!!

 

----------------------------

 

If your PC is not super powerful maybe supersample dcs to 1.2 from 1.0 (any higher and you may regret it with stutters.

 

Oh and don't waste frames on your cockpit dsplays.. I have my to stupid low 256..see them just fine. (MAKE SURE IN GAME TEXTURES ARE ON HIGH(not talking about ground textures))

 

Just a few things.

 

I get that I can use the Night mode. I have a few times and t helps, but not much. I personally don't like night mode anyway, even at night. I prefer the green HUD. But it is still a work around no matter how you slice it, and it's something ED has acknowledged is a bug/problem. So I'm sure they will fix it but until they do I'm not going to use it at least for the A-10C during the day.

[sIGPIC][/sIGPIC]

Posted
I think there is a fix to that.

 

You need to edit the file HUD_base.lua. File is located in ..\M-2000C\Cockpit\VTH.

Change this line:

local mask_material_TFOV = MakeMaterial(nil,{204,255,204,5}) -- light green

To this line:

local mask_material_TFOV = MakeMaterial(nil,{0,0,0,5}) -- black

 

Let me know if it helps!

 

Thanks for the tip BD. Once I get my rig back from the shop I'll try it and let you know.

[sIGPIC][/sIGPIC]

Posted

So I tried keeping my settings like I posted on the second page and increasing cockpit textures to 1024. No difference in clearness of the dials or guages. Seems like keeping it at 512 is fine.

 

So I lowered my PD to 1.5 and while it's ok, I didn't like it at this setting. So I tried 1.6 and that was about the same. I also kept msa x8 and af at x2 or x4 I think. I think I settled on 1.8 at this point.

 

Also hdr on just seem to make the map glow a but more, I guess a little brighter but not a huge difference, it kind of adds a washed out look even with gamma at 1.5.

 

I think optimal PD is anywhere between 1.6 and 1.8. Things become a bit more clear to read but still somewhat blurry at 2.0. I prefer mine at 2.0 because I can see the UFC and cdu, and nav computer screen better. Didn't notice any choppiness except when making crazy fast turns, I got a bit of a stutter just one time.

 

Honestly I don't think I going past 1.8 offers any more readability. I may keep mine at 1.8 or 2.0.

 

I didn't mess with lowering msa below x8 but I do wonder what AF at x16 does. Maybe we don't need msa at 8 if AF x16 does something.

 

Sent from my Nexus 6P using Tapatalk

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

Posted

I'm now set on PD 1.5, maxed out MSAA and AA. I'm done.

Things will be blurred out no matter what settings i put.

I think it comes down to the resolution and the optics inside the oculus.

I also noticed that i have to look straight ahead to see a clear picture.

When you normally would look down or in a direction without moving your head it gets nauseating. You focus, and get tricked.

Hopefully next generation VR set's will come with eye tracking and better optics.

Posted

I don't notice the issue with seeing a clear picture if you only look straight. It seems pretty smooth to me with only lettering being blurry.

 

I think if dcs used smaller font spacing the letters and numbers would be a bit better to see.

 

What does AF x 16 do since you have it on that ?

 

 

Sent from my Nexus 6P using Tapatalk

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

Posted

It's supposed to smooth out lines and textures although I'm not sure i cann tell any difference. Maybe 16 is a bit overkill since the resolution does not justify it. I just put on max since it did not impact the frame rate much.

 

Sent from my GT-I9300 using Tapatalk

Posted

No sorry. AF is supposed to improve texturing. More detailed textures from near to far. That's the way I understand it..

 

Sent from my GT-I9300 using Tapatalk

Posted
No sorry. AF is supposed to improve texturing. More detailed textures from near to far. That's the way I understand it..

 

Sent from my GT-I9300 using Tapatalk

That's the only one I don't have set to max. I should record my fps and set it to x16 and see if I notice anything. Visually maybe on the surroundings.

 

Sent from my Nexus 6P using Tapatalk

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

Posted

A good way to check an difference in quality would be to place yourself at end of a runway with external view and look with an down angle at the other end. Where's if you had no AF it would look more and more blurry but with it on should look consistent or at least keep some degree of texture quality.

 

Sent from my GT-I9300 using Tapatalk

Posted

I'm seeing better performance running dcs 1.5 alongside 2.1. I mainly use the mirage 2000c in 1.5 as I just started learning it.

 

1.8 pixel density sometimes 2.0 but I found out about the VR zoom feature. I was about to give up on the mirage just because I could never tell what numbers my radios are dialed into.

 

I'm running shadows low, water and civ low, everything else high, no hdr, msa x2 and aa filtering off. But I also tried AF x16 and saw no difference.

 

The a-10 cockpit is the most readable for me in VR. I actually had to bust out the track IR for the mirage just to be able to read the dials. Having them in French is also more of a pain but you only need to know like 2 french words: arete which is off and marche for on.

 

Lettering could be better in VR for the mirage but the VR zoom makes reading the dials in VR much easier. Lots of people complain about it but I only use it to input radio commands or INS info.

 

I noticed no hiccups at all in 1.5.

 

Sent from my Nexus 6P using Tapatalk

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

Posted

When you normally would look down or in a direction without moving your head it gets nauseating. You focus, and get tricked.

 

try moving the HMD on your face. if you get warping when you look round then you dont have your eyes in the sweet spot for the lens.

 

took me a couple of weeks to figure this out.

 

try moving it up or down slightly on your race.

 

you can also pitch the screen up a bit. as having it pitch down really makes it warp for me.

My Rig: AM5 7950X, 32GB DDR5 6000, M2 SSD, EVGA 1080 Superclocked, Warthog Throttle and Stick, MFG Crosswinds, Oculus Rift.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...