Search Issue Tracker
Not Reproducible
Not Reproducible in 6000.5.X
Votes
0
Found in
6000.0.66f2
6000.3.7f1
6000.4.0b7
6000.5.0a6
Issue ID
UUM-133777
Regression
No
VFX System Border text cursor is sometimes not visible
How to reproduce:
1. Create a new Unity project and install the Visual Effects package
2. In the Project window, right-click -> Create -> Visual Effects -> Visual Effect Graph -> Any VFX Graph
3. Navigate to any System Block title and enter a long string
4. Place a cursor anywhere in the text and use the arrow buttons to move the cursor
5. Observe the results
Expected results: The cursor is visible everywhere
Actual results: The cursor sometimes is not visible
Reproducible with: 6000.0.66f2, 6000.3.7f1, 6000.4.0b7, 6000.5.0a6
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note: The issue seems to be related to zoom, because zooming in shown the cursor
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
- 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
Resolution Note:
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.