Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

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

Discussion in 'Editor & General Support' started by Gillissie, Apr 13, 2019.

  1. Gillissie

    Gillissie

    Joined:
    May 16, 2011
    Posts:
    294
    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?
     
  2. tchapman222

    tchapman222

    Joined:
    Oct 18, 2017
    Posts:
    1
    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)
     
  3. RREALITY

    RREALITY

    Joined:
    Jul 17, 2013
    Posts:
    6
    Had the same warning, uncheck and check again the reflection probes worked for me.
     
  4. vfxjex

    vfxjex

    Joined:
    Jun 3, 2013
    Posts:
    93
    for LWRP 2019.2.3f1 - I untag my camera as main and it works.
     
  5. Scientist28

    Scientist28

    Joined:
    Mar 11, 2019
    Posts:
    1
    " 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)
     
    vfxjex likes this.
  6. Sab_Rango

    Sab_Rango

    Joined:
    Aug 30, 2019
    Posts:
    121
    In scene mode, I was holding the camera, Then I start to hold other object such as the plane ,, it worked !!

    LWRpipeline//
     
  7. jay3sh

    jay3sh

    Joined:
    Dec 30, 2013
    Posts:
    18
    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.
     
  8. NGC6543

    NGC6543

    Joined:
    Jun 3, 2015
    Posts:
    227
    This still happens on Unity2019.2.9f1, and @vfxjex 's solusion worked for me.
     
    vfxjex likes this.
  9. sky-coding

    sky-coding

    Joined:
    Oct 26, 2018
    Posts:
    5
    I'm seeing this error in 2019.2.10f1 when I have my camera game object selected and I enter play mode.
     
    BunnyViking, kenjdav and Sheppio like this.
  10. ProToeType

    ProToeType

    Joined:
    Nov 6, 2018
    Posts:
    2
    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.
     
  11. ratneshpatel

    ratneshpatel

    Joined:
    Oct 10, 2017
    Posts:
    21
    For me simply reloading the scene solved the problem
     
    Alex787 and yaboie like this.
  12. OfficialHermie

    OfficialHermie

    Joined:
    Oct 12, 2012
    Posts:
    585
    You need to file bug reports!!!!!!!!!!!!!!!!
     
    khaled24 likes this.
  13. GregoryFenn

    GregoryFenn

    Joined:
    Feb 13, 2018
    Posts:
    43
    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.
     
    Outsorceress likes this.
  14. unity_5Dz1MMLzkdBUSg

    unity_5Dz1MMLzkdBUSg

    Joined:
    Mar 15, 2020
    Posts:
    1
    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
     
    Ghosthowl and sordidlist like this.
  15. yaboie

    yaboie

    Joined:
    Jul 29, 2018
    Posts:
    3
    Reloading the scene did it. Thanks
     
  16. melos_han_tani

    melos_han_tani

    Joined:
    Jan 11, 2018
    Posts:
    77
    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.
     
  17. darkesco

    darkesco

    Joined:
    Mar 19, 2015
    Posts:
    61
    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.
     
  18. coward

    coward

    Joined:
    Jan 9, 2013
    Posts:
    21
    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!)
     
    yininghu and rboerdijk like this.
  19. wm-VR

    wm-VR

    Joined:
    Aug 17, 2014
    Posts:
    123
    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)
     
  20. ahmedaniss

    ahmedaniss

    Joined:
    Sep 18, 2019
    Posts:
    98
    problem fixed here :
     
    fonycas, Jr_Antipasto and sbeeson like this.
  21. Jr_Antipasto

    Jr_Antipasto

    Joined:
    Oct 10, 2019
    Posts:
    1
    This one worked! Thanks.