Using Unity 2021.1.0a9 and Profiler.enableBinaryLog to record profiling data from a Win64 Player seems like only CPU usage is actually saved. You can find such captures in bug-report Case 1300171.
When I load the recorded profiling data in Unity’s Profiler window, most information is not available.
Is this by design? @MartinTilo
Starting from 2018.3 you can specify which areas/modules you want to capture profiler data for. This is either informed by which modules are open in the UI or via the Profiler.Get/SetAreaEnabled API. This is on purpose to give you finer control over what profiling overhead you want to incur. I’m not aware of any defaults changing for this in 2021.1 though but maybe a Profiler with only CPU view on connected to he build?
Thank you for the quick reply!
No editor was connected to the build. I guess the default is CPU only, which is fine to me since I can change it via SetAreaEnabled as you pointed out. I wasn’t aware of this method.
