(IN-59257) Fully immersive apps render with aliasing, even with multi-sampling enabled

[puddle_mike]

Hi, we have a fully immersive app (using the legacy Metal rendering backend), and we see aliasing on geometry when running on device. We have 4x multi-sampling enabled in Quality settings, but it does not appear to render with multi-sampling on device.

Here’s a screenshot from the editor:

And on device:

(You can ignore the color differences seen above, I have a separate thread about that, due to issues rendering in gamma colorspace on device)

Is there a way to get anti-aliasing when running on device? Thanks!

[ryan_bednar]

I ran into this as well today. Here’s what I found from another thread:

@mtschoen

@DanielTJones

Lastly, the edges of the shapes were super aliased/jagged in VR mode compared to passthrough. Is this to be expected, and is this how it will always look in this mode?

For now, this is expected. We need to make some engine-side changes to enable foveated rendering which will enable us to render at the full resolution of the display.

[puddle_mike]

Thanks for some insight on what’s going on here. To make sure this is addressed for folks like us that are fully immersive (i.e. using the Metal rendering backend) AND using the built-in render pipeline (i.e NOT URP), I created a simple repro project in the following Unity bug:
IN-59257

[funvr]

Hello, are the any updates on when this would be fixed in the PolySpatial plugin?

[da_sxr]

I’ll second that, as the current state of fully immersive rendering using URP and Metal is quite terrible, to be frank.

I guess that implementing dynamic foveated rendering in Unity is not an option since even Unity (as we) don’t have access to eye tracking?

[puddle_mike]

Any updates on this? We’d like to analyze performance with our target visual fidelity (i.e at full display resolution/anti-aliasing settings), and this holds back that process. There is a repro project available associated with bug IN-59257…