Terrain Tools: Install errors and Noise not working

Hi,

I've just installed the Terrain Tools package (1.1.2) and it's full of great stuff, thanks!

But I ran into errors when installing it in a brand new HDRP project (See attached image)
I still can use the Terrain Toolbox and all the sculpting tools except the Sculpt/Noise tool that doesn't generate any preview and spams the Console with the following error:

UnauthorizedAccessException: Access to the path "D:\Unity\TestProject\Library\PackageCache\com.unity.terrain-tools@1.1.2-preview\Shaders\NoiseLib\Fbm\Billow.hlsl" is denied.

System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32 bufferSize, System.Boolean anonymous, System.IO.FileOptions options) (at <1f0c1ef1ad524c38bbc5536809c46b48>:0)

System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32 bufferSize, System.IO.FileOptions options, System.String msgPath, System.Boolean bFromProxy, System.Boolean useLongPath, System.Boolean checkHost) (at <1f0c1ef1ad524c38bbc5536809c46b48>:0)

(wrapper remoting-invoke-with-check) System.IO.FileStream..ctor(string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare,int,System.IO.FileOptions,string,bool,bool,bool)

System.IO.StreamWriter.CreateFile (System.String path, System.Boolean append, System.Boolean checkHost) (at <1f0c1ef1ad524c38bbc5536809c46b48>:0)

System.IO.StreamWriter..ctor (System.String path, System.Boolean append, System.Text.Encoding encoding, System.Int32 bufferSize, System.Boolean checkHost) (at <1f0c1ef1ad524c38bbc5536809c46b48>:0)

System.IO.StreamWriter..ctor (System.String path, System.Boolean append, System.Text.Encoding encoding, System.Int32 bufferSize) (at <1f0c1ef1ad524c38bbc5536809c46b48>:0)

System.IO.StreamWriter..ctor (System.String path) (at <1f0c1ef1ad524c38bbc5536809c46b48>:0)

(wrapper remoting-invoke-with-check) System.IO.StreamWriter..ctor(string)

UnityEditor.Experimental.TerrainAPI.NoiseLib.GenerateHeaderFiles () (at Library/PackageCache/com.unity.terrain-tools@1.1.2-preview/Editor/TerrainTools/NoiseLib/API/NoiseLib.cs:613)

UnityEditor.Experimental.TerrainAPI.NoiseLib..cctor () (at Library/PackageCache/com.unity.terrain-tools@1.1.2-preview/Editor/TerrainTools/NoiseLib/API/NoiseLib.cs:40)

Rethrow as TypeInitializationException: The type initializer for 'UnityEditor.Experimental.TerrainAPI.NoiseLib' threw an exception.

UnityEditor.Experimental.TerrainAPI.NoiseUtils.GetDefaultBlitMaterial (UnityEditor.Experimental.TerrainAPI.NoiseSettings noise) (at Library/PackageCache/com.unity.terrain-tools@1.1.2-preview/Editor/TerrainTools/NoiseLib/API/NoiseUtils.cs:76)

UnityEditor.Experimental.TerrainAPI.NoiseUtils.Blit2D (UnityEditor.Experimental.TerrainAPI.NoiseSettings noise, UnityEngine.RenderTexture dest) (at Library/PackageCache/com.unity.terrain-tools@1.1.2-preview/Editor/TerrainTools/NoiseLib/API/NoiseUtils.cs:143)

UnityEditor.Experimental.TerrainAPI.NoiseSettingsGUI.DrawPreviewTexture (System.Single minSize, System.Boolean showExportButton) (at Library/PackageCache/com.unity.terrain-tools@1.1.2-preview/Editor/TerrainTools/NoiseLib/NoiseSettingsGUI.cs:297)

UnityEditor.Experimental.TerrainAPI.NoiseHeightTool.OnInspectorGUI (UnityEngine.Terrain terrain, UnityEditor.Experimental.TerrainAPI.IOnInspectorGUI editContext) (at Library/PackageCache/com.unity.terrain-tools@1.1.2-preview/Editor/TerrainTools/NoiseHeightTool.cs:225)

UnityEditor.TerrainInspector.ShowPaint () (at C:/buildslave/unity/build/Modules/TerrainEditor/TerrainInspector.cs:1375)

UnityEditor.TerrainInspector.OnInspectorGUI () (at C:/buildslave/unity/build/Modules/TerrainEditor/TerrainInspector.cs:1784)

UnityEditor.UIElements.InspectorElement+<CreateIMGUIInspectorFromEditor>c__AnonStorey1.<>m__0 () (at C:/buildslave/unity/build/Editor/Mono/Inspector/InspectorElement.cs:445)

UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

My setup:
Unity 2019.1.0f2
Windows 10

Thanks,
Alex

 

I got this as well and it's reproducible all the time in 2019.1.3f1. Console error shows up right when I start Unity with my project, no terrain selected. If you want me to test something or need an example project, just hit me up. I can submit a bug report as well if you prefer.

 

Uploading ... for some reason the upload to the Unity servers takes a long time. I guess it'll be done within an hour. I'll bump this thread once it's finished.

 

Thank you for the tools

It's report "(Case 1159025) System.UnauthorizedAccessException".

Do you have access to it using the id? In the mail it says it's not recommended to share the link, i. e. "Note that sharing it will also share all your other cases and email conversations in them." If you need the link, let me know and I'll send it to you via pm.

 

No, I can't edit the files. The errors don't go away when I run the Unity Hub or Unity Editor in Administrator mode.

(Win 10 Home Edition)

 

@wyatttt It appears the file has flag "Read only" and that's why it can't be changed. When I remove the flag, the error goes away, but then other hlsl files follow with the same error. When I remove the "Read only" flag on all of them, I get this:

Shader error in 'Hidden/TerrainTools/Noise/NoiseBlit/NoiseBlitFbm': incorrect number of arguments to numeric-type constructor at /Test/Library/PackageCache/com.unity.terrain-tools@1.1.2-preview/Shaders/NoiseLib/Fbm/Billow.hlsl(53) (on d3d11)

Shader error in 'Hidden/TerrainTools/NoiseFill/NoiseFillFbm': incorrect number of arguments to numeric-type constructor at /Test/Library/PackageCache/com.unity.terrain-tools@1.1.2-preview/Shaders/NoiseLib/Fbm/Billow.hlsl(53) (on d3d11)

Shader error in 'Hidden/TerrainTools/NoiseFill': incorrect number of arguments to numeric-type constructor at /Test/Library/PackageCache/com.unity.terrain-tools@1.1.2-preview/Shaders/NoiseLib/FBM/Perlin.hlsl(53) (on d3d11)

 

I have come across a null reference exception when Terrain Tools is installed, and any item in the hierarchy other than the scene root is selected and showing in the inspector.

I have logged a bug report but the email ID hasn't come through yet, so I thought I'd mention it here too.

 

Hi guys,

It seems to be related to a locale issue:
By default, my computer regions settings are set to French(Canada) with the decimal symbol set to "," instead of "."
When I switched to English (United States) all the errors went away and I'm now able to use the Noise brush properly.

So on Windows, just go to Control Panel/Clock, Language and Region/Change Location and set the Format to English.


I hope there will be a better fix going forward, as I had similar issues with Houdini Engine curves some time ago.

Thanks!
Alex

 

Hi, I'm working with @ChekbooM_EM .
Here's more info:
UnityEditor.Experimental.TerrainAPI.NoiseLib.GenerateHeaderFiles(), generates the shader code in memory and compares the code with the package shader files (e.g: Shaders/NoiseLib/FBM/Billow.hlsl).
Depending on Windows region settings, the locale will change the decimal symbol used while converting float to string (comma instead of dot):

Code (CSharp):

1.     ret.warpStrength = 0,5;
2.     ret.warpOffsets = float4(2,5, 1,4, 3,2, 2,7);

Since it's different, it will try to write the file which is read-only...

Looks like the source of the problem lies within UnityEditor.Experimental.TerrainAPI.HlslInput.GetDefaultValueString():
ToString() and string.Format(...) should likely pass CultureInfo.InvariantCulture. I'm not sure whether a wider solution could be implemented, I leave this up to you
Note: There might have more locations where this is needed, I didn't dig any further.

P.S:

IIRC, I deleted the project Library/PackageCache + Library/ShaderCache in order to reproduce the issue after changing the system locale

 

What about my ticket, should i ask to close it? I don't want anyone waste their time in checking it out when a fix is already on the way. I'll update the ticket by mentioning this thread.

 

@wyatttt I just tried to fix it myself when I noticed several of these hardcoded paths:

Would it be possible to make those paths relative? Or is this the way the packaging stuff is supposed to work, I'm not familiar yet with that stuff

 

Thanks wyattt, on Monday i'm going to test it and i'll give you a feedback. Anyway, all the new terrain stuff seems to be very promising, the only thing that is missing is just the material part. Add that and it will be a killer package!

 

Thank you. One more question if I may: I understand this is required for explicit addressing of external packages and getting unique addressability without name clashes. But what about contents within the same package? Shouldn't there be a placeholder variable or something so that whenever the package structure changes you don't have to correct each and every occurrence of an address? That kind of reminds me of Unity when variables are referenced as strings rather than object reference. Makes safe refactoring rather impossible.

 

It works perfectly, thank you so much @wyatttt

 

Hey @wyatt I scrolled through here to find a solution to my problem but I don't think there is, so I just need you to verify this. Is the terrain tools not supported in Unity 2020.2? I can't find anything in the package manager, so I went to the Asset Store, and imported the terrain tools sample thing, but I only got the samples, no tools at all...

 

I still have this error. Running on Deepin Linux and Unity 2019.4.9f1 and I get:

The following files have the same name but only differ in casing and will be ignored:
Packages/com.unity.terrain-tools/Shaders/NoiseLib/FBM
Packages/com.unity.terrain-tools/Shaders/NoiseLib/Fbm
Case sensitive file systems are not fully supported, please move or rename these files.

However if I remove or rename the folders and .meta files. They appear again.

 

Yes I also got the email on my bug report but the question is "when the fix will be released?"

 

HI! I've just installed terrain tools v2.6. i have of the same 40 errors which say (isReadable is false;ReadWrite must be enabled in import settings) I also can't create a terrain in terrain tools. Is there a fix for this?