Rptd: VR causing dublicate image parts for each eye in 3rd person views

[PointyPuffin 5,055]

Hello everybody,

 

I have recently purchased a HTC Vive Cosmos and, of course, I wanted to play War Thunder in VR.

It is, generally speaking, working very well, especially in aircraft.

 

On tanks, however I ran into an issue that makes them unplayable for me and since the M4A3E2 was strongest affected in my tests, I'll use it for the visualization.

 

First off, here is a screenshot of the issue and what each of my eyes sees:

 

 

As you can see, around the barrel of the machine gun and the main gun, there are areas, in which the game creates duplicates of what is next to the object.

Which leads me to my theory of what might be causing this.

 

This also applies to close objects in 3rd person view in aircraft (the gunner view seems to count as 3rd person with the camera in the gunner's seat):

 

 

And here is what I think causes this:

 

The game bases its information on what you can and cannot see on the regular view, I'll call it the "2D view" from now:

 

 

However, in VR, you get two view points, which are to the left and the right of that view:

 

 

 

Of course, these viewpoints see objects from a different angle and can see things that are hidden from the 2D view.

 

 

Now the game only uses the information available to the "2D view" to generate the objects you can see.

In the picture above, I have used the left eye's view and the "2D view" as an example.

According to the "2D view", from the commander's point of view, you can only see half of the gun barrel to the left of the machine gun. The left eye has a different angle though and could see the entire barrel and a bit of ground.

 

Now what the game does is the following: it has no information on the area the left eye can see that is hidden from the "2D view". And it just duplicates what the "2D view" sees next to the mg barrel (the next object that both views can commonly see) to fill the gap. In this example, it uses the areas I marked in cyan and puts them where the white marking is.

 

For this example picture it means:

 

Purple areas: fine, since they are covered both by the left eye and the 2D view

Red areas: fine, since the 2D view knows them, but they are hidden from the left eye

Blue areas: bugged, since only the left eye's camera can see it and the game fills it with the next information that is available to the 2D view

 

 

I hope, I could explain this in a comprehendible way and I hope that it will get fixed soon.

 

I have opened a topic on this a while ago in the tech section, before getting an idea for a cause and got only few responses.

 

In the other topic, there are also sources that show that I am not the only one affected and that it also is not exclusive to my VR headset.

 

It can easily be reconstructed by going into a test drive in the Jumbo Sherman with the long gun in VR and looking down. It is especially dizzying while moving.

 

 

Thank you very much in advance for any help. o7

 

PointyPuffin

[KnightoftheAbyss 3,385]

Hi

 Is the HTC Vive Cosmos "FULLY" Oculus Rift compatible?

,
Please ensure that your reports comply with the guidelines.  These are in colour and bold immediately above the Start new topic button.
You agreed to these conditions when you clicked the checkbox just before the Start new topic button.

It is also in the Header of this Forum.  In colour and Bold.

Quote

PLEASE, READ THIS BEFORE POSTING !!!

To make the report valid and useful, the initial post MUST follow Graphic and Devices Issues guidelines.  Any report that does not meet the guidelines will not be approved. If you require any assistance regarding Bug Reporting, please contact a Technical Moderator.

Please, follow "One Issue = One Thread" rule (do not post DIFFERENT / ISSUES THAT LOOK SIMILAR in existing threads, or start a topic about multiple issues).

You can also click the links on the splash screen or the bold yellow hyperlinks in the header.

There are three places where it asks for specific information to be provided to the Developers so the Technical Moderation team and Developers can investigate your issue.   
If you fail to add this clearly asked for information, then this only adds to the 'administration time' for reports.  We can either ask people for information that has already been asked for
three times, OR we can spend that time actually investigating your issue.  Which do you think is the more efficient and effective methodology?  I know what my answer is.

 

We are all volunteers in the Technical Moderation team who are either ICT professionals or ICT Uni students.  With the Global pandemic and large numbers of people either working or studying from home,
or in lock down; Unsurprisingly, our 'real employers'(the ones that pay us!) also need more of our time, as do our family and friends.  By providing all the information 'up front' this will speed the
issue investigation and resolution process a great deal.  We all have to do 'our bit' to help.

 

Thanks

[PointyPuffin 5,055]

Hi, 

 

The game supposedly supports the HTC Vive. And everything works fine, there are no issues with the camera movement or with stereoscopic 3D.

 

Replicating the error is fairly easy:

Use any tank, preferably one with a rooftop mg directly below the commander's viewpoint (the M4A3E2 is ideal for this) in VR. 

Since I have seen the same issue in all videos by Youtubers, who have shown tanks in VR since 2016, I think that the issue is not related to the model of VR headset. 

 

If my theory is correct and the game uses the regular "2D view" to determine, which objects are visible and which aren't, then the fix would be to make that "feature" inactive when the "VR mode" box is checked

(I think, I can recall something like this system has been talked about back in 2015 to prevent players on low quality settings to spot enemies through objects, which I believe, is why it does not affect actual 1st person views, like cockpits). 

 

Here are the clog and DxDiag files:

 

 

2021_01_05_15_31_58__23524.clog DxDiag.txt

Edited January 5, 2021 by PointyPuffin

[KnightoftheAbyss 3,385]

Thanks for that.

[TinyTinkerTank 170]

I just tested the issue with my Oculus Quest 2 with the official Oculus Link feature (wired PC connection) and I have a very similar issue but with a weird shimmer / cloak effect. Many objects look like they are surrounded by some weird glass that bends light. This issue is present since I first tested the VR mode like 1.5 years ago with a Rift S.

On a tank it's mostly visible at the MG handle and under the barrel and at the antenna.

 

Here my CLog: 2021_01_06_13_07_45__16976.clog

Here my DxDiag: DxDiag.txt

Here a video showing the issue on a Jumbo and a B7A2 back gunner:

 

Edited January 6, 2021 by TinyTinkerTank

[KnightoftheAbyss 3,385]

@TinyTinkerTank

 

Update your NVIDIA driver.  It is not the latest and re-test please.

[TinyTinkerTank 170]

3 hours ago, KnightoftheAbyss said:

@TinyTinkerTank

 

Update your NVIDIA driver.  It is not the latest and re-test please.

... Did that ever fix any issue?

I just updated my driver and restarted my whole system and the issue is still exactly the same. Here my new DxDiag: DxDiag.txt

Here a new in game screenshot of the issue which is unchanged:

[PointyPuffin 5,055]

Hi, I'd just like to confirm that what is shown in the video by TinyTinkerTank is what it looks like in motion. 

 

Without the bushes on the tank, it would be a lot more visible though. 

[KnightoftheAbyss 3,385]

On 07/01/2021 at 09:30, TinyTinkerTank said:

Did that ever fix any issue?

Yes. It has. Many times!  That's why we ask for it to be done!   Sometimes, you also want to be able to rule out causes!!!  What a concept!!

 

 

 

[KnightoftheAbyss 3,385]

Hi
  Thank you for your interest and help improving the game.  

Your information has been forwarded to the Developers for their consideration.  

If there is anything further regarding this report a Technical Moderator will contact you.

Thank you again for your support.