Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.50f1
6000.1.4f1
6000.2.0b3
Issue ID
UUM-107398
Regression
No
Multiple warnings are thrown when importing Terrain URP Demo Scene to the Project
*Steps to reproduce:*
1. Create new Unity project
2. Import Terrain Tools package
3. Once imported press on “Download URP Demo Scene from Asset Store” button in 4. Package Manager
5. Download and import Demo Scene to the project
6. Observe the warnings
*Actual results:* Warnings are thrown after importing Demo Scene
*Expected results:* No warnings in the Console after importing Demo Scene
*Reproducible with versions:* 1.0.3 (6000.0.50f1, 6000.1.4f1, 6000.2.0b3)
*Tested on (OS):* MacBook Pro, 2021, Sequoia 15.5 (M1)
*Warnings:*
* The GUID inside 'Assets/TerrainDemoScene_URP/Scripts.meta' cannot be extracted by the YAML Parser. Attempting to extract it via string matching instead. Please verify the file does not contain unexpected data.
* A polygon of Mesh 'Rock_A_03_LOD00' in Assets/TerrainDemoScene_URP/Prefabs/Rocks/Models/Rock_A_02.fbx is self-intersecting and has been discarded.
* Shader Graph at Assets/TerrainDemoScene_URP/ShaderGraphs/SpeedTreeURP_Branch.shadergraph has 1 warning(s), the first is: There is a newer version of this node available. Inspect node for details.
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Resolution Note:
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration, we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues due to the limited amount of resources available to us.
We understand that this might not be the outcome you hoped for, and we sincerely appreciate your patience and understanding. Your feedback is always valuable, and we encourage you to continue sharing any other concerns or ideas you may have.