Search Issue Tracker
Fixed in 2017.4.0
Votes
0
Found in
2017.3.0a5
2017.4.12f1
2017.4.37f1
Issue ID
1135871
Regression
Yes
Profiler does not record the data when logging via scripting with Profiler.enableBinaryLog
For this to reproduce, do not record via Profiler window.
To reproduce:
1. Open attached project "prof.zip", scene main
2. Enter Play mode, and observe the console
3. Exit Play mode when logging is done
4. Go to %AppData%\LocalLow\DefaultCompany\PROF and find the file "profilerLog"
5. In Editor, load the "profilerLog" file via Profiler
Expected: data is recorded successfully when using Profiler.enableBinaryLog
Actual: data recorded fails to load to the Profiler
Reproduced in: 2017.3.0a5, 2017.4.37f1
Not reproduced in: 2017.3.0a4, 2017.4.38f1, 2018.3.14f1, 2018.4.22f1, 2019.1.14f1, 2019.2.21f1
Note: the only data that's available after loading is the count of frames that were recorded
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Add comment