How can you see without labels in VR?

[falken76]

Is anyone playing this with labels off in VR? I'm trying to get used to playing this with Labels off in VR but the resolution is so bad if I turn them off I can't see anything. I was sitting on the runway when enemy aircraft were flying in, they were about 15 NM out and I could start to see the labels. I Kept hitting Lshift+F10 to turn them on and off. When those planes were less than 4 nm out and I turn labels off. I can barely see what looks like a smoke trail from the planes and that's from the position of a parked plane on the runway with the canopy open looking directly at them when knowning where they were with labels on to getting completely lost the second I turned them back on.

 

How does anyone see ANYTHING without labels in VR if I can't see them when I'm staring directly at them from a parked position?

 

Is it hard to see aircraft without labels on monitors? I've noticed that if I get into a dogfight with AI, if I try to run and lose them in the mountains it's VERY hard to shake them, it's like they're the invid tracking the protoculture fueling my plane. But if I play with a Human, I can actually lose them in the mountains easier. I assume it's already difficult to track aircraft without labels, but it seems almost impossible in VR.

[NeilWillis]

I have never had difficulties seeing out to 12 miles plus using VR and the Rift on a 980 graphics card.

 

Admittedly, at that range they are hard to pick out, but they're there, and they're visible.

[Firebird1955]

Not sure what you have the Pixel density slider set to, but anything above 1.5 causes the issue of visibility on my end. It makes sense as once the aircraft is a single pixel, the lower the density, the bigger the pixel.

[NeilWillis]

I have my slider set to 1.3 usually, but even on 1.0 I get good visibility of distant aircraft.

[Gladman]

We need object sizing back in the worst way.

 

 

How my group goes about it is by utilizing a modified .lua file. It puts a gray dot on the target from 3-7nm. What it does is give you the visual at a reasonable/realistic distance. Within 3nm you can see the object, outside of 7nm you wouldn't be able to see it anyway thusly the limitation. This affects both our VR and our 4k users so it was an easy vote.

[Kayos]

We need object sizing back in the worst way.

 

 

How my group goes about it is by utilizing a modified .lua file. It puts a gray dot on the target from 3-7nm. What it does is give you the visual at a reasonable/realistic distance. Within 3nm you can see the object, outside of 7nm you wouldn't be able to see it anyway thusly the limitation. This affects both our VR and our 4k users so it was an easy vote.

 

Can you share that .lua at all? Seems like it would be handy.

[Gladman]

Can you share that .lua at all? Seems like it would be handy.

 

 

 

You bet, send me a PM so I don't forget. I can get it to you after work.

[Kayos]

You bet, send me a PM so I don't forget. I can get it to you after work.

 

Thanks, Done

[nessuno0505]

Anything above 1.5 causes the issue of visibility on my end. It makes sense as once the aircraft is a single pixel, the lower the density, the bigger the pixel.

 

I have my slider set to 1.3 usually, but even on 1.0 I get good visibility of distant aircraft.

 

I play with PD =1 and no problem.

1.3 may be as good.

The issue is with PD higher than 1.5: too anti-aliasing --> single pixel not rendered --> you see the plane only when it gets closer