Search Issue Tracker
By Design
Votes
0
Found in
5.5.0f3
Issue ID
870092
Regression
No
Using Mesh.SetUVs instead of Mesh.uv won't work with Mesh.GetNativeVertexBuffer
Steps to reproduce:
1. Download Repro.zip and open "test" scene
2. Disable the Blast and enable the Ribbon gameobject
3. Press play notice that top line has gradient
4. Go into Player Settings and type BUG_SETUVS in the Scripting Define Symbols field. (This switches the UV creation from Mesh.uv to Mesh.SetUVs)
5. Press play, notice top line now green.
Mesh.uv and Mesh.SetUVs switch is done in PopcornFX/Scripts/Runtime/PKFxManager.cs at line 1594.
Expected results: Mesh.uv and mesh.SetUV should produce same results.
Actual results: It seems like UVs created with Mesh.SetUV won't read back the UV component in the vertex buffer.
Reproduced with: 5.6.0b4, 5.5.0p4. 5.5.0f3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Standalone profiler process is hidden in macOS dock
- Shader warnings are being thrown after building Mixed Reality Template
- Error is thrown when entering play mode with build profiles docked and standalone profiler open
- The Player hangs when activating another maximized application
- [XR] Input is not registered and headset view is headlocked after entering Play Mode with Meta XR SDK on 6000.0.0b16 and higher
Add comment