Search Issue Tracker
Fix In Review
Fix In Review for 6000.5.0a5
Fixed in 6000.4.0b5
Votes
0
Found in
6000.0.65f1
6000.2.15f1
6000.3.3f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131099
Regression
No
Project Directory is opened when Opening the Editor Log from the Console Window and the Editor is launched with the -nolog argument
Steps to reproduce:
- Launch the Editor with the "-nolog" argument (either in Hub or from CLI)
- In the Console Window click the kebab menu
- Select "Open Editor Log"
Actual results: The Project directory is opened
Expected results: Nothing is opened or a Warning is log indicating that logs are disabled for the Editor
Reproducible with versions: 6000.0.65f1, 6000.2.15f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Tested on (OS): Windows 11
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
Resolution Note:
Editor: Fixed an issue where the Editor Log menu item was shown even when not available.
Resolution Note (fix version 6000.5.0a5):
Editor: Fixed an issue where the Editor Log menu item was shown even when not available.
Resolution Note (fix version 6000.4.0b5):
Fixed in 6000.4.0b5