Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
6000.5.0a7
6000.6.0a1
Issue ID
UUM-134650
Regression
No
[Windows] Project folder Editor.log directory is not displayed in Bug Reported after Editor crash
Reproduction steps:
1. Create a new project
2. Crash the Editor (e.g. import the attached “NewBehaviourScript.cs” to any of the GameObjects and enter Play mode)
3. Observe the Editor.log directory in the Bug Reporter
Actual result: Global Editor.log directory is displayed (e.g. “%LOCALAPPDATA%\Unity\Editor\Editor.log”)
Expected result: Project Editor.log directory is displayed (e.g. “My project/Logs/Editor.log”)
Reproducible with: 6000.5.0a7
Couldn’t reproduce with: 6000.0.68f1, 6000.3.9f1, 6000.4.0b9, 6000.5.0a6 (no Editor.log in the project folder)
Reproduced on: Windows 11
Not reproduced on: macOS Sequoia 26.2 (M4)
Note: Issue is not reproducible when opening Bug Reporter via Help > Report a Bug…
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment