demostenes Posted September 5, 2012 Posted September 5, 2012 After importing terrain, I am creating normal texture. Process itself is without problem, but generated terrain normal texture contains visible artefacts: http://www.dropmocks.com/mBkpQl There is nothing like this on my diffuse texture 4097*4097 and height map is 4097*4097 16bit. What can be the cause? Intension? Is normal texture derevied only from height map, or even from diffuse? Btw, I noticed, that even if I pick resolution for normal map 1024, it is 4096 when exported. Bug? Thanks for any clues.
Rob Posted September 5, 2012 Posted September 5, 2012 I had a similar problem, you can read about it here https://developer.unigine.com/forum/topic/1152-solved-terrain-coarse-normalmap-stepping-issueartefacts/page__hl__stepping__fromsearch__1 I solved it by exporting a normal map for the terrain with World Machine and use that instead of the default Unigine generated normal map
demostenes Posted September 5, 2012 Author Posted September 5, 2012 I had a similar problem, you can read about it here https://developer.unigine.com/forum/topic/1152-solved-terrain-coarse-normalmap-stepping-issueartefacts/page__hl__stepping__fromsearch__1 I solved it by exporting a normal map for the terrain with World Machine and use that instead of the default Unigine generated normal map Thank for link. Interesting is, that I have no problem with quality of generated NM (detail is very good), there is only problem with moare. On the other side using external tool for generating NM is workaround and why not use internal functionality, which in some cases can save lots of time, for example after modifying terrain after import you need new normal map....
Rob Posted September 5, 2012 Posted September 5, 2012 Thank for link. Interesting is, that I have no problem with quality of generated NM (detail is very good), there is only problem with moare. On the other side using external tool for generating NM is workaround and why not use internal functionality, which in some cases can save lots of time, for example after modifying terrain after import you need new normal map.... Ye it is only a workaround but we only use WM to generate and modify our terrain so it works for us
demostenes Posted September 5, 2012 Author Posted September 5, 2012 Ye it is only a workaround but we only use WM to generate and modify our terrain so it works for us I understand. In our case we must do some finetuning after import, so this is complication for us. So question for Unigine team, how big problem is to fix this? Thanks.
manguste Posted September 12, 2012 Posted September 12, 2012 After importing terrain, I am creating normal texture. Process itself is without problem, but generated terrain normal texture contains visible artefacts... Is normal texture derevied only from height map, or even from diffuse? A normal map is created from a height map. So it's possible that it is the culprit. Do you set minimum necessary Height when importing it? Because if the value is too high, this leads to steep height gradations and results in artifacts. What is the step used? Anyway, we need a minimal test scene to investigate. Could you send it to us at engine-support@unigine.com or attach here on the forum? Btw, I noticed, that even if I pick resolution for normal map 1024, it is 4096 when exported. Bug? Thanks for any clues. You pick the resolution of a coarse normal map. The one you can check on Terrain tab, at the bottom. Exported is a normal map that contains all per-surface normal maps glued together.
Recommended Posts