Jump to content

Recommended Posts

Posted (edited)

I keep getting these black squares/blanking in VR since the latest patch. It's incredibly annoying.

 

 

Normal one frame:

 

 

 

WWDAfAi.jpg

 

 

Black squares the next

 

 

veCH61B.png

 

 

Seems to be related to MSAA. Enabling it at all causes this issue for me.

Edited by FoxTwo
Posted

same here. i also get strange artifacts in one eye when on NVGs where parts of the cockpit are displaced in one eye and overlay the picture making it impossible to fly with NVGs

Posted

I had that in the index. Turned off msaa, deleted fxo and Meta. Loaded in and it was gone so, Turned Msaa back on, rebooted, hasn’t happened since.

This seems to work for some, not for other’s

I9 (5Ghz turbo)2080ti 64Gb 3200 ram. 3 drives. A sata 2tb storage and 2 M.2 drives. 1 is 1tb, 1 is 500gb.

Valve Index, Virpil t50 cm2 stick, t50 base and v3 throttle w mini stick. MFG crosswind pedals.

Posted (edited)

i tried that already. unfortunatly it didn't work for me. first i thought it works but it came back after a few minutes on the carrier deck. only solution for me is to disable MSAA entirly which is not a solution.

btw. i have exactly the same hardware as you :)

Edited by mono6020
Posted

Yeah, its crazy how these things seem to have a mind of their own! What works for some, not for others.

I know zip really about anything other than the basics.

I will tell you that before the sc came out, I was having pretty good results but read a post about turning in game pd way down, and stream resolution slider way up (and I have headset set for 90). I think I’m at like 275 ish?

Anyway, the “double vision” as I call it where it looks great until a fast flyby, then you get 2 planes smeared has gone. And still runs 45 fps. So I wonder if the pc is somehow dropping that “interpolated” frame leaving the screen blank?

Dunno, wish I could help others because it’s frustrating for sure .

I9 (5Ghz turbo)2080ti 64Gb 3200 ram. 3 drives. A sata 2tb storage and 2 M.2 drives. 1 is 1tb, 1 is 500gb.

Valve Index, Virpil t50 cm2 stick, t50 base and v3 throttle w mini stick. MFG crosswind pedals.

Posted

yea i'm on 90 too. would have loved to use 120 hz but DCS struggles to hold 60 fps in most situations so im better with 90/45.

in steamvr i'm on 100% (no SS) and in DCS my PD is 1.2.

With MSAA on 2x it worked and looked prefectly fine for me, but now i can't use MSAA no more

Posted
yea i'm on 90 too. would have loved to use 120 hz but DCS struggles to hold 60 fps in most situations so im better with 90/45.

in steamvr i'm on 100% (no SS) and in DCS my PD is 1.2.

With MSAA on 2x it worked and looked prefectly fine for me, but now i can't use MSAA no more

 

That is so strange! Makes me

Wonder what will happen when I log back on. Flew 3 or 4 times

Over the weekend. Caveat being always mp. Haven’t gone back to sp in a while.

I9 (5Ghz turbo)2080ti 64Gb 3200 ram. 3 drives. A sata 2tb storage and 2 M.2 drives. 1 is 1tb, 1 is 500gb.

Valve Index, Virpil t50 cm2 stick, t50 base and v3 throttle w mini stick. MFG crosswind pedals.

Posted

i also fly multiplayer only.

just tried the newest nvidia driver without success, black squares still there.

i wonder if this comes from the latest steamvr update. do you use steamvr beta?

maybe that's worth a try for me.

anyway thx for the help

Posted

Exact same problem here on Valve Index. Turned off msaa, deleted fxo and Meta with no effect. Seems to happen when the island is in view. Haven't noticed it if I'm on cat 1 or 2 facing forward. Single player only for me.

Posted (edited)

I'm also getting this in the air, depending on the mission.

 

I was trying out the Piercing Fury campaign, but it is unplayable due to all the black distortion that takes over the screen

 

I am also noticing some objects (ships, clouds) render only in one eye at certain LOD distances. I think this is an unrelated issue tho.

 

Turning off MSAA seemed to work for me.

 

 

What is FXO btw? FXAA?

Edited by NakedSquirrel

Modules: A10C, AV8, M2000C, AJS-37, MiG-21, MiG-19, MiG-15, F86F, F5E, F14A/B, F16C, F18C, P51, P47, Spitfire IX, Bf109K, Fw190-D, UH-1, Ka-50, SA342 Gazelle, Mi8, Christian Eagle II, CA, FC3

Posted

What is FXO btw? FXAA?

 

I'm no expert but I beleive fxo is one of a set of folders people seem to delete when having issues: username/Saved Games/DCS.openbeta/fxo

Posted
I'm no expert but I beleive fxo is one of a set of folders people seem to delete when having issues: username/Saved Games/DCS.openbeta/fxo

 

Thanks. Deleted.

 

Still haven't had black screen issues since removing MSAA... the only downside is not having any AA x.x

Modules: A10C, AV8, M2000C, AJS-37, MiG-21, MiG-19, MiG-15, F86F, F5E, F14A/B, F16C, F18C, P51, P47, Spitfire IX, Bf109K, Fw190-D, UH-1, Ka-50, SA342 Gazelle, Mi8, Christian Eagle II, CA, FC3

Posted

MSAA off does work, but that's no way to fly. So far I've only seen it with MSAA on while onboard Supercarrier. The old Stennis and the new Kuznetsov work with no problem.

Posted
MSAA off does work, but that's no way to fly. So far I've only seen it with MSAA on while onboard Supercarrier. The old Stennis and the new Kuznetsov work with no problem.

 

+1

Posted
MSAA off does work, but that's no way to fly. So far I've only seen it with MSAA on while onboard Supercarrier. The old Stennis and the new Kuznetsov work with no problem.

 

+1

 

However I have notice the issue when not near any of the carriers. Always seems to be when some form of aircraft light is on.

RTX 2080ti, I7 9700k, 32gb ram, SSD, Samsung Odyssey VR, MSFFB2, T-50 Throttle, Thrustmaster Rudder Pedals

Posted

Honestly I think it's something to do with the in game Quad Plain used for the LSO overlay.. if you stop and try and replicate this which is VERY replicatable it's at the same angles each time and is caused because your 'clipping' through an object plain with one eye but not the other, giving you a massive shadow because as far as it's aware with that eye it doesn't need to render anything further across at the moment as it's being Culled, due to you being right on the edge of the geometry.

 

It's either that or a rogue shadow map plane.

i7 13700k, 64gb DDR5, Warthog HOTAS, HP Reverb G2 VR, win 11, RTX 3070

TGW Dedicated Server Admin, Australian PVE/PVP gameplay. (taskgroupwarrior.info/2020)

Posted
Honestly I think it's something to do with the in game Quad Plain used for the LSO overlay.. if you stop and try and replicate this which is VERY replicatable it's at the same angles each time and is caused because your 'clipping' through an object plain with one eye but not the other, giving you a massive shadow because as far as it's aware with that eye it doesn't need to render anything further across at the moment as it's being Culled, due to you being right on the edge of the geometry.

 

It's either that or a rogue shadow map plane.

 

 

I didn't understand any of that ;), but you got me thinking that the minor geometry differences between the different carrier islands might make a difference. It does not. Get black squares on all three Supercarriers with both Hornet and Tomcat.

  • 3 weeks later...
Posted

FWIW this happens to me in the channel map, at sunset, in the spitfire. Haven't tried other planes yet.

 

 

Guessing this is a systemic problem with either light rays or shadows.

  • 3 weeks later...
Posted (edited)

So I think I've resolved the issue on my end. After several hours of playing with settings, different AA modes, in both SteamVR and DCS, I've found that the SteamVR Advanced Supersample Filtering was the cause. Or at the very least I've not been able to recreate the issue since disabling it.

 

 

Edited: This didn't entirely fix it but it did lessen the effect significantly in most cases. On the supercarrier it's still an issue, and gives you a twitchy, blinking feeling as if your eyes were closing on their own. It's very, very, very disorienting. And ED will likely never acknowledge or fix it.

 

 

 

HlG1DYc.png

Edited by FoxTwo
  • Recently Browsing   0 members

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