Hi all even with a brand new empty project it maxes out around 40ish fps. It seems the cpu is flying up for no good reason.
Any ideas? I have disabled all extra apps on the mac. It should not be this slow. Using the latest Unity version (release) on the latest version of Big Sur. VSYNC is also off.
Which Unity version is this? We have not seen this locally. What does the profiler say?
[quote=“Tautvydas-Zilys, post:2, topic: 827546, username:Tautvydas-Zilys”]
Which Unity version is this? We have not seen this locally. What does the profiler say?
[/quote]
Hi this is 2020.2.3f1
I installed version 2020.1.17f1 and it is over 2500 fps, it is a bug with 2020.2.3f1 for me, m1 macbook pro latest big sur. The rendering in the editor looked slightly different also - in the new version the transparency was more ‘solid’ - possible that something is being thrown off in that version? not using metal? (says it is)
Regarding the profiler: can you show the timeline view? That graph is not useful in determining where the issue lies.
yeah sure here you go. 
This is a blank project, it works fine in 2020.1.17f1, the moment it comes into the latest - boom. down to almost 40ish fps.
Can you switch the profiler to the “Editor” mode? Looks like the game itself runs fast (frame completes in 0.23 ms translates to like 5000 fps), but the rest of the editor for some reason is very slow.
Also, we tried Unity 2020.2.3f1 on three of our Apple M1 machines, and could NOT reproduce what you’re seeing 
.
Another idea: could you try changing the editor interaction mode preference and see whether that helps at all?
unfortunately same result, gets locked to around 40ish fps on average, I will post up an image of the editor profiler mode tomorrow. as soon as I go back to that other version its absolutely normal and fine.
Here is the editor profile. 40ish fps, blank scene again. Latest version (release) - something is very wrong in this one I lose over 2000 fps with no changes apart from new version.
Hi,
could you try using the Standalone Profiler (Window → Analysis → Profiler (Standalone Process)) for this? That frame just shows the cost of drawing the Timeline view of the Profiler Window itself.
No problem here you go. 
Thanks, that’s looking way cleaner. Could you please drag the splitter between the main and the render thread down a bit and zoom in so we can see what’s going on in that PlayerLoopController sample? And also show a bit more of the Render thread for that same stretch of time? Looks like something in there is waiting on the Render thread which is preparing a render target.
Do you happen to have both the Game View and the Scene View open at the same time? And are they on the same monitor?
Also, could you please check your Game View’s resolution drop down to see if it is set to vSync. And your projects Quality Settings too.
Hey thanks, so I added a few more here for you: https://imgur.com/a/8MyCNmr
It happens no matter what quality setting (vsync set to off) or project complexity, can be an empty project fresh from creating it or my own project imported in. Something seemed to have changed with how opacity was rendered in the main scene view with this version - I was not sure if I imagined it but then I noticed this problem. I have the scene open and game view open at the same time.
It helps slightly when the game view is maximised.
They are also on the same monitor (even tried disconnecting my external and using it just on the macbook pro but same thing.
Only thing that makes it return to normal is to use the older version and then i get thousands of fps no sweat.
edit: so I just tried to enable vsync in game view and it hits a solid 60 cap. As soon as I disable vsync, it goes back down to 40ish fps. So this version seems to hate it when vsync is off… in the game view? very odd issue here.
Edit 2: it seems to have started around version 2020.2.1f1 while 2020.1.17f1 is absolutely fine. This also happens in the 2021 beta, this is unusable if it carries on without a fix. This is also a fresh and brand new M1 Macbook Pro, updated to the latest big sur patch.
Well, in the screenshots it looks like it it first waits for the last frame to hit a vBlank, then renders it purely on the main thread and waits for the next one. Is multithreaded rendering on? Also I think it’s around both game and scene view being open at the same time and maybe turning on vSync gets them to be in sync and not miss that vBlank?
Also, please ignore the FPS counter in the game view for performance comparisons over the 2020.1 to 2020.2 version transition as in 2020.2 we changed that to be actually accurate and include EditorLoop time, instead of artificially calculating it out.
Well this is on ‘desktop’ so I cannot set multithreaded to anything else afaik. The whole editor is sluggish after I hit a 2020.2 update - Just tested on a windows machine and the same does not happen.
I was able to reproduce the issue with 2020.2.3 on a M1 Mac Book Pro 16 GB (BigSur 11.2.1) in a new universal render pipeline project. (Interaction Mode set to No Throttling)
With just either the scene view or the game view open the performance seems ok (80 - 120 fps) but as soon as both are open at the same time the performance drops to 35 - 45 fps.
Another thing I’ve observed is that in both cases the performance seems inconsistent. With just one view the frame rate would sit comfortably at around 120 fps for a while and then drop to around 80 for a while seemingly completely randomly but that might be a hardware throttling thing.
After some more testing I discovered that the issue only seems to occur when both the scene view and the game view are on the same monitor. If the game view is in a separate window on a separate monitor everything seems fine. Definitely looking like a V-Sync issue.
Can you report a bug on this?
