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

Errors with Profiler.EndSample

Discussion in 'Universal Render Pipeline' started by StefanWo, Oct 8, 2021.

  1. StefanWo

    StefanWo

    Joined:
    May 24, 2015
    Posts:
    117
    Hi there. I just updated from 2021.1.23f1 to 2021.2.0b15 and found the deferred feature. I was happy, that finally the lighting was working for me (using Hybrid Renderer V2).

    But also every frame i get some errors, and i can't figure out what it is. It looks like a timing issue to me, it cannot find a endsample than its missing it...

    Any ideas? (when starting the scene)

    Update: it seems just happening when the Profiler-Window is open. Closing it will not cause the errors.. But still this is not good :)

     
    Last edited: Oct 8, 2021
  2. MartinTilo

    MartinTilo

    Unity Technologies

    Joined:
    Aug 16, 2017
    Posts:
    2,159
    Hi there, it's this bug, which we already have in our bug tracker and are looking at solutions for.
     
  3. StefanWo

    StefanWo

    Joined:
    May 24, 2015
    Posts:
    117
    Ah, perfect. Thanks for the fast response :)
    Anyway i got a bad exception due to burst compile error, with no explains when trying to compile. So I downgraded already :(
     
  4. StenCG

    StenCG

    Joined:
    Mar 26, 2015
    Posts:
    63
    still happen, 2021.3.5f1
     
    nogxx and modaka-cov like this.
  5. nopogo

    nopogo

    Joined:
    Sep 9, 2012
    Posts:
    24
    still happening in 2021.3.15f1
     
  6. Haapavuo

    Haapavuo

    Joined:
    Sep 19, 2015
    Posts:
    95
    We are experiencing this on Unity 2021.2.5f1 and thus cannot use Profiler AT ALL. This is very critical!!!
     
  7. MartinTilo

    MartinTilo

    Unity Technologies

    Joined:
    Aug 16, 2017
    Posts:
    2,159
    Hey @StenCG & @nopogo,

    The bugfix landed before those versions so what you are seeing must be a separate bug with the same symptoms. For us to be able to fix that, we'll need a new bugreport, possibly even 2, one from each of you, in case those are separate issues. We do not have any details that would point us at what else is still broken here.

    @Haapavuo as mentioned in a comment on the issue tracker page, the fix landed on 2021.2.12f1, so your version does not yet contain the fix. If you upgrade and still experience the same issue, a new bug report would also be needed from you for us to be able to fix the issue.

    Also, thank you for bringing it up that there is still more here that needs fixing :)
     
    StenCG likes this.