Search Issue Tracker
Fixed in 5.4.0
Votes
1
Found in
5.3.4f1
Issue ID
788011
Regression
No
[Cursor] Constantly updated custom cursor disappears after ~3300 frames
Steps to reproduce bug:
1. Open attached project and open the 'demo' scene
2. Click 'Play' and observe the 'Cursor texture update count'
3. Notice that when the count reaches ~3300 the cursor texture disappears
4. Stop and Play again
5. Notice that the cursor is not visible still
Expected: Cursor is visible all the time
Actual: Cursor disappears after ~3300 updates
Reproduced with: 5.4.0b14, 5.3.4p3, 5.2.3p3 (Windows)
Not reproduced with Mac (trunk revision efe86df75ff7)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment