Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.1.0a11
2019.2
2019.2.10f1
2019.3
2020.1
Issue ID
1197494
Regression
No
Console Window filter stops displaying the used Value after entering Play mode with Maximise on Play option enabled
Reproduction steps:
1. Open the attached project named Case_1197494
2. Open the SampleScene
3. Enter Play mode
4. Observe 15 messages in the Console window
5. Enter any value into the search field to filter out all of the messages
6. Check if "Maximise on Play" setting is enabled
7. Play the scene again
8. Check the console window
Expected result: The value in the search field remains to show how messages are filtered
Actual result: The search field is cleared, however, the messages are still being filtered by the old value
Reproducible with: 2019.1.0a11, 2019.2.12f1, 2019.3.0b11, 2020.1.0a14
Could not test with: 2017.4.34f1, 2018.4.13f1, 2019.1.0a10(Console filtering option was not available)
Workaround: Entering any symbol into the Console search bar will reset it
Notes:
1. The console filtering option was introduced in 2019.1.0a11
2. For the issue to occur the Console window must be docked and "Maximise on Play" setting be enabled
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0a20
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.6f1