Automobilista 2 March 2023 Development Update

It's a game(engine limitation and therefor track design) issue for 100% sure. I tested with OpenXR with and without foveated rendering but also with SteamVR. I tested ALL Nvidia settings, ALL ingame settings, all different kind of resolutions, I tested ALL tweaks that I could find that COULD have influence on it like "NearZ" with every possible value(insanely low to way to high(gives other artifacts)), the vr sharpness tweak, with MSAA, without etc.etc.

I spend days on finding a way to solve it but it's IMPOSSIBLE, so I just saved you a lot of time if you wanted to try to find a way to solve it.

It's 100% sure in the game engine BUT with proper track design it could be avoided for 100% sure. Because not all object got flickering textures and it happens mostly to "very thin" objects with something close behind them. So if the track designer TEST the track first before releasing it, he can solve the flickering textures one by one for sure. There are also some tracks that almost don't have flickering textures and there are some tracks that got such a massive amount of flickering textures that it really ruins the immersion.

I'm not sure IF this issue is at the agenda of Reiza AT ALL. Because I never saw the commenting on this (IMO biggest VR) bug of AMS2. And that's really a sad thing because it's the biggest issue that I personally have with AMS2. It really ruins the experience.

I honestly believe that their beta testing is mainly done on 2D screens, because they also implemented extra "metal sparks" in a previous update a while ago and those sparks simply don't render correctly at all in VR. On one eye the metal sparks are rendered a couple of meters away/differently compared to the other eye. It's 100% bugged, but never hotfixed after the release. So for that reason I think that the Reiza developers don't have a high res VR HMD for beta-testing/bughunting before release sadly enough... Maybe some day...

 

We are off topic a little but, all things considered, I believe the VR implementation is really good. Though I do wish we did not have to turn on parallel projection in pimax settings (no longer req'd in rF2) I do see some shimmering in my 8KX but I thought it was not very significant and maybe I just got used to it.

I run 16x Anisotropic with Medium AA (4x) with texture quality High and power at prefer max in Nvidia cp and feel that helps.

 

Yes the VR implementation is VERY good(I would even say "the best!" together with DR2), so I think that you 100% misunderstood me here. That I'm disliking the VR performance of AMS2 and that's absolutely not the case here. I'm talking about a very specific issue here! Not the overall VR experience. AMS2 is my favorite VR sim racing title by far in almost every aspect and especially VR. So I'm not sure why you're disliking my post here??

The issue that I stated is true for all VR users(some are irritated by it, some not(you?)) and it IS solvable and when that issue is solved the image will just be way more stable around all tracks. The flickering textures and misaligned/wrongly rendered metal sparks in VR(in 2D this does not happen!) are just ruining the immersion.

Now you have great tracks with minor texture flickering like Adelaide for example, but also tracks with MASSIVE texture flickering like Long Beach and tracks in between like the historic Bathurst. It would be amazing if everything simply looks good and those textures bugs are fixed, if I had the chance then I would even fix all those tracks for free, I've designed game maps before so maybe I could even do it but of course I've got zero experience with the Madness Engine. I'm certain that it could be solved by changing the thin subjects to some thicker meshes or by changing some other small variables on the bugged textures/objects.

 

Hopefully no flickering textures this time

Ricciardo to drive Red Bull F1 car at the famous Nordschleife circuit | Formula 1®

 

And then we're going to have the DLC today on this injured Friday in Brazil on the Nurbugring 1928 track.

 

Come at me

 

DR2 VR performance with Reverb G2 is catastrophically bad. I could only run low graphics settings with my OC 3090. Now I can run High with my OC 4090.

 

Any chance that this might help?
Reddit - Dive into anything

 

@TurboHenk - Oops sorry my bad meant to click agree. On my phone screen fingers too fat & clicked wrong icon, now fixed.

 

Update???

 

Amanhã ou domingo

no Twitter eles falaram q ia ser esse fim de semana

e isso se não adiarem

 

Wallacella ei ole kaikki muumit kotona!

 

No ei oo joo, eikä taida hissikään mennä ihan yläkertaan asti.

 

not again spamming every thread mate, its getting old very quickly........ @WALLACE ALMEIDA MARINHO

 

@Renato Simioni
please release or forum goes nuts and there will only be

 

I'm freaking out here

 

I suspect the VR performance is only good in ams2 because it was good in pc2. Otherwise reiza have not touched the graphics of ams2. They could have improved the anti aliasing, improved the darkness of the night sky, improved the post processing or added fsr/dlss etc, but there has been zero improvements in graphics.

Correct me if im wrong, but i believe the version of openvr that ams2 uses is absolutely ancient or something.

 

Patience my friends... We're already 21 days off schedule, 1-2 more isn't that big of a deal.

 

I had issues with the Steam VR implementation on DR2.0 before the Oculus SDK released. Maybe check your resolution/super sampling settings. Steam VR kept forcing the render resolution to 2-3x. I'm not sure if it's just bad optimization or Steam VR underestimating how intensive the game is.

 

There's two things I'd like to be improve in AMS2:
- Own car reflected in mirrors. In VR its asbolutely immersion braking when no part of the car can be seen behind
- Some storm clouds move at a crazy pace. Its the same in PC2. Can't we get rid of them? They are very low and move like 5000 km/h while at the same time rotating. Just delete them or make the texture transparent or smth.