► Terrain to Mesh ◄

It looks like you are using very old (and now not supported) version. Update to the latest version.

 

Is it possible "not" to rotate any of the detail objects upon export?
I created a scene using the basic Unity prop painting and sculpting tools.
I painted both massive enviroment objects and tiny detail objects. "Quixel Props".
Once placed. The terrain has been artisiticly sculpted around the props to embedd them convincingly.
Things are exacctly as I want them.

Once I got the Amazing converter.
I see that massive objects are considered detail.
They rotate upon export no matter what.
0 will uniformly set them all to the original state.
And of course 360 and random are also all rotations.

Can they just not move?

Many thanks.

 

I will check.

 

Hello, I seem to be having an issue with the packages shaders. This happened after I foolishly moved around the folders in my hierarchy but I can't seem to fix it despite undoing my adjustments. I have attempted deleted everything regarding the package, reinstalling, and reimporting to no avail.

The error I am facing is: Shader error in 'Amazing Asssets/Terrain To Mesh/Splatmap': Couldn't open include file 'Splatmap.cginc'. at line 738

If I could receive any assistance it would be greatly appreciated!

 

Try recompile Splatmap shaders as described in the Manual file.

 

Hello, thank you for the quick reply!

Unfortunately, the recompilation steps provided in the manual did not seem to resolve the issue. Here is some additional information:

Unity Version: 2021.3.17f
Using URP
The package was working perfectly before I made the mistake of rearranging my project files. Never doing that again . I attempted to undo the rearrangement to the best of my ability but may have missed a thing or two.

a better screenshot of the error:

 

Hello,

After doing some testing, it seems like removing the normal maps from each of the terrain textures makes it render properly. That being said, the error is still present in the console. Is there a reason this would happen?

 

Amazing Assets/Terrain To Mesh folder can be moved to any location inside project. It is not mandatory to have it in the main Assets folder. Just keep original Amazing Assets folders hierarchy.

Your error only indicates that shader cannot find Splatmap.cginc file. Make sure it is inside Amazing Assets/Terrain To Mesh/Shaders folder.


Try, delete projects Library folder. This fill force full project reimport and recompile.

 

Hi there, I can confirm that the Splatmap.cginc file is in the folder. Would there be a specific reason why it isn't being detected. I am a bit paranoid that deleting the library folder may harm my project which I've sunk a couple months into.

 

Not sure what has gone wrong when you rearranging project files and then restored them. Looks like something has messed up. References has been lost or incorrect paths are used now.
Removing TTM and re-importing should have fixed it.

 

Yeah unfortunately it doesn't seem to matter how many times I reimport TTM : L
For now, the error doesn't seem to be negatively effect my project in any way as Im able to convert my terrains with no issue. It will just be annoying to have that error there. I guess I will take this as a warning to not rearrange files when not necessary.

 

Try new version for Unity 2021.3.

 

I wanted to ask: why is the source code not available and all the C# code is precompiled into a .net DLL? On that note, why is it the case with most (if not all, correct me on that) of your assets available on the asset store? I really want to know the reason behind this decision.

 

I installed the Universal package and manually updated the shader, but edgefall is pink. After upgrading to URP material, it looks strange. Can you help me? Unity 2021.3.13

 

Edgefall uses Unity's default Lit shader. You can't update it.
Screenshot looks correct. You can change edgefall texture in the generated material.

 

Is there a setting to get the terrain to bake shadows onto itself?

 

Do you mean Lightmap baking?

 

I'm having some problems with the T2M package and the Curved Worlds package.
I want to turn my terrain into a mesh and use the curved worlds package to bend it. However, the resolution of the textures that T2M produces when I use the custom curved world lit shader is low compared to the original texture on the terrain.

Here are the material settings in T2M:



and here is a screenshot of a part of the original terrain:



here is the generated mesh:



As you can see, I have set the resolution of the basemap to 8192 but it still looks blury.

Does anyone have any advice or help with this? Thanks in advance!

 

You need to have a tiled layered image.

 

Why not use Splatmap material, it renders textures in their original resolution. Instead of baking them all into one Basemap texture?

 

Yeah, I managed to fix it. Got support from the asset dev. The thing I was missing was to activate Curved World shader transformation for T2M shaders. Once I had done that the splatmap material worked.

 

Hello, I would like to ask, can this product depict terrain with point clouds in unity with agx plugin

 

I noticed when baking lightmaps in subtractive mode in URP14 (Unity 2022.3.10). All Materials with the Splatmap Shader stay black, althought correctly baked lightmaps are shown in "Baked Lightmap" View. Does not happen with Shadowmask or Baked Indirect. I already did the Splatmap Shader Updating in the Documentation, no change.

 

Just did the quick test and at my side all light baking had the same results (Unity 2022.3.11 URP):

 

How would I enable per chunk UV? I cant seem to find an option to toggle it in the TTM window. There is a tick box on the terrain object itself in the inspector window, but a message there says to not adjust anything in the inspector window.

 

Also it seems like my generated terrain comes with very poor texel validity. Is there a way to tune this? It is generating very poor lightmaps.

 

Enable Basemap baking with Export Per Chunk:

Are you using High compression for generated mesh? Try lower compression.

 

Hello!

Doing some research into exploring terrain optimisations for a flight simulation game. I need to render terrains very far away since the camera will be flying around in the sky and I think Terrain to Mesh could be the solution? I'm just looking to have a sense check done to confirm my workflow design will work before I buy.

1. Convert Unity Terrain using Terrain to Mesh multiple times at low, mid, high resolutions for multiple LODs
2. Assign generated models to LOD group for each terrain chunk
3. Do occlusion/frustrum culling on the Camera end

Would it be that simple in practice?

I also have the following 2 concerns I could potentially struggle with.

1. Would there be any potential issues with 'seams' or 'gaps' between meshes if they're rendered at different or low LODs?
2. I saw there was a generate collider toggle in the documentation. Is this collider an accurate representation of terrain shape? Is it something I can toggle on and off at runtime to save memory?

 

1. Yes.
2. Yes. You have to manually set up LOD groups as TTM has no such feature.
3. Yes.

Concerns:
1. Yes, meshes with different vertex count will definitely have gaps and seams. However they can be minimized or 'hidden' by generating meshes with 'Edge Fall' option enabled.
2. For collider TTM generates similar mesh, but with user controllable resolution related to the main mesh. For example if the main mesh has 100x100 vertices and Generate Collider Resolution is set to 0.5, this will create similar mesh but with 50x50 vertices.

 

Excellent! One last thing - I want to utilise satellite imagery for the terrain textures (using another asset like WorldComposer) then modify if needed with roads, (say from Easy Road) I assume as long as end result is a Unity terrain, once I turn it into a mesh the textures will carry over?

 

If WorldComposer uses Unity's built-in terrain shader, then TTM includes similar shader but supporting only 16 layers rendering or all terrain textures can be baked into one Basemap texture.
As for roads, pay attention to the exported mesh vertex count, if using low resolution mesh export settings, details of the roads from the original terrain may be lost.

 

When i tring to convert terrain from this asset (https://assetstore.unity.com/packages/3d/environments/unity-terrain-hdrp-demo-scene-213198) to mesh with detail mesh with option: "combine by prefab" i get this error:
[Terrain To Mesh] Encountered an error with terrainData 'Terrain_3_2_77e49ac9-7f8e-47c2-ae00-57296acecb1c (UnityEngine.TerrainData)'.

 

Fixed. Download new update v2024.1

 

I have some objects like a rocks and other, they are child of terrain. Is it possible to copy they like a detailed mesh to inside of generated terrain prefab?

 

No. Tools work only with TerrainData asset and not scene gameobjects or other prefabs.

 

Do you have any recommendations for setting up mesh blending with the terrains this asset generates? I've been hunting for a while, but it seems like a lot of mesh blending solutions rely on the unity terrain system.

 

Hi, i bought the tool and i have a problem. There are seams between converted terrains. Not between chunks, generated by terrain to mesh, but definitelly between previously existing unity terrain chuinks. (geometry looks ok. problem is probably faces) What to do?

 

Hi Arkhivrag,

I'm writing to express my appreciation for the excellent Terrain To Mesh asset. It's been a powerful tool for my projects, and I'm currently using it in combination with Terraland for an exciting AR app.

However, I've encountered an issue with edge fall while converting terrain to mesh. Changing the "Edge Fall" value (extruded edges) seems to have no effect. I understand the default is -50, but adjusting it to -20 or even -1 doesn't make the baseboard thinner as expected. I've attached an image to illustrate the issue. By the way, the size of this terrain is 60 km x 80 km.

My question is: is there a way to modify the edge fall values to achieve a thinner baseboard? The current thickness unfortunately hinders my AR app's functionality.

Thank you for your time and assistance. I look forward to your response.

 

Sorry, currently I have no solutions for that case.

It looks like mesh is generated using High compression method. That is expected behavior. Entering game mode fixes it.

Which Unity version and render pipeline are you using?
How about bigger values like -200 or -1000? If it is a bug, such huge values also shouldn't work.

 

It is not fixed in game mode:

edit:
oh and found the compression setting. it is on low. i tryied setting it on medium / high, and it did not help.

 

Does generated prefab has TerrainToMeshConversionDetails script attached? And is it enabled?

 

Thank you for confirming! Would you ever consider developing this as an additional feature in the future? It would be highly useful for terrain/scenery development.

I have found outside solutions, but they require a lot of modification to work with the terrains this asset generates.

 

I will check what can be done.

 

yes

 

Contact me on support email (support@amazingassets.world) with asset purchase invoice I we will check it in details.

 

Hi there! No rush, was just wondering if you had given yourself the chance to look into this. I've tried doing some alternatives, but can't get usable results. I am curious on the feasibility of this.

 

Currently no update regarding mesh blending

 

All good! It's more of a curiosity than a necessity for me, although I'm sure a lot of people would love to see it!

I do have another issue for you though that I was hoping you could guide me through. I have had a terrain that has been increasing in layers throughout the past couple months. For the longest time, this has worked great but it seems like a 12th layer breaks the camel's back.

Essentially, with a 12th layer, TTM is generating a terrain where the 12th layer does not exist. The only fix for this is to regenerate the entire terrain by throwing the original unity terrain back through the TTM asset, but this seems to only work *sometimes* and, even if it does work, the 12th layer will break again if you close and re-open the unity project. I read on the documentation that the TTM asset supports up to 16 layers. Is there something I am doing that is hindering me from adding a 12th?

I've attached 3 pictures. The first is the Unity terrain I am trying to convert. The second the result that TTM outputs. The third is my TTM settings.

Unity Terrain:


TTM Terrain:


TTM Settings:



Additional Info:
Graphics Card: RTX 3080
CPU: i7-12700KF
Memory: 2x16GB @ 3200 MHz
More than enough disk space

Unity Version: 2021.3.17f1
Render Pipeline: URP


Got any tips? Thanks in advanced!

 

Export terrain directly from TTM editor window and send me generated package file on support email (with purchased invoice) - support@amazingassets.world, I will check it.

 

Hi there, I was actually able to solve this one by simply deleting the entire TTM object and starting from scratch. Since then the 12th texture works as expected. If you still want me to send this over I can.

I do have another issue that i wanted to run by you though. I believe I posted it in here a while back but ended up just moving past it with a quick-fix. I keep getting these splotches on my terrains when baking my lightmaps (photos attached). I've tried a couple things to get around it including increasing lightmap size, increasing all the different sampling sizes, changing baking methods, etc.

My go-to solution was to just have a custom lightmapping parameter for the terrain that stretches 15 lightmaps across 400 terrain chunks. This essentially 'smudged' the splotches away and worked for a while, but now I'm wanting to get a bit more detailed with my terrain, which requires proper lighting. This *might* be because of poor texel validity but I'm unsure.

Photo Mid lightmap bake, ignore the blacked out tiles. The white snow does not have those visual artifacts prior to baking.


Let me know what you think!