"setting Anti-aliasing Of Already Created Render Texture Is Not Supported!" Error When Enabling Aa

Actually, all I did was change the quality settings in the editor to one of the pre-defined settings that has antialiasing enabled, and whenever I switch to the scene view, I get between 3-5 of these error messages. Of course, clicking the message does nothing to help me understand what it’s referring to. Anyone have any idea what this means?

I also had this issue in unity 2018.3.6f1. Mine will continue to produce errors until I turn it off. To fix it for me, I did the following:

  1. Turn off anti-aliasing in quality settings
  2. Disable all reflection probes in scene
  3. Turn on anti-aliasing
  4. Enable Reflection Probes again.

Your issue may not be reflection probes, but I would try disabling anything that affects render textures (like the reflection probes)

4 Likes

Had the same warning, uncheck and check again the reflection probes worked for me.

7 Likes

for LWRP 2019.2.3f1 - I untag my camera as main and it works.

12 Likes

" for LWRP 2019.2.3f1 - I untag my camera as main and it works."

Yes indeed! It works BUT it creates next error:

NullReferenceException: Object reference not set to an instance of an object
Player.Update () (at Assets/Player.cs:33)

1 Like

In scene mode, I was holding the camera, Then I start to hold other object such as the plane , it worked !!

LWRpipeline//

4 Likes

I get this error message continuously sometime. I’m not using RenderTextures or reflection probes in my scene. I’m using LWRP in 2019.2.8f1. What works for me is closing and reopening the scene.

3 Likes

This still happens on Unity2019.2.9f1, and @vfxjex 's solusion worked for me.

1 Like

I’m seeing this error in 2019.2.10f1 when I have my camera game object selected and I enter play mode.

3 Likes

Here was my solution, I went to Edit-Graphics Tier-Then adjusted my tier to the one I had set under my project settings. I noticed that even though I had the Lite rendering option under project settings my Graphics Tier was set to Hardware 3 instead of Hardware 1. Now idk if this is the solution but it fixed the error for me.

For me simply reloading the scene solved the problem

2 Likes

You need to file bug reports!!!

1 Like

Unity 2019.3.6f1: I get this error both in play and edit mode. To fix it I turned my camera off from “MainCamera” tag. In fact I made a new tag “MyMainCamera” and whereever my own code called Camera.main, I replaced it with GameObject.FindGameObjectWithTag("MyMainCamera").GetComponent<Camera>(). Note that this is expensive so should only be called in Start(), Awake() or OnEnable() messages, and then cached to a private field.

1 Like

This answer is for the Universal Render Pipeline!

I solved the problem by checking “Stop NaN” on the camera component under the anti-aliasing setting

2 Likes

Reloading the scene did it. Thanks

2019.3.10f1 - This also worked for me.

For me, the issue began when I added a second camera to the scene which was solely rendering to a render texture, which was then being displayed in a Raw Image under a Canvas.

I never use Camera.Main. It’s something else for me. Involving URP/LWRP AA and reflection probes. Before the crash I was getting strange warping around objects. Like a water smeared render texture. All scenes are refusing to play. Editor freezes and CTRL-SHIFT-ESC must be used to close it.

I still get this in 2019.3.13f.

It appears to be when I have the camera preview on the main camera. I noticed that a gizmo was rendering in the preview, and sure enough, the deselection of the camera, so as not to have a preview, works.

I guess the camera preview uses a render texture (makes sense!)

2 Likes

Disabling and enabling the reflection probe did the job for me

Setting anti-aliasing of already created render texture is not supported!
UnityEngine.GUIUtility: ProcessEvent(Int32, IntPtr)

problem fixed here :

3 Likes