As a preface, I’m planning to purchase an indie license of Unity 2 sometime after Christmas. While I bide my time I’m trying to put together some of my own assets so I can start throwing together a nice looking prototype just minutes after the installation. Most of my questions I’ve found answers to, but this was one I wasn’t sure about.
Would I need to make a custom shader to add normal maps to the terrain created with the new system or is there a way to “shoe horn” them in? It may end up being too much of a performance hit to be worth it, but I thought it might be good for some types of terrain like clay or mud. See the attached image as an example.
Also, if you have a terrain with per-vertex lighting only and a bumpmap, and then have explosions with pixel lights, is the processing of the bumpmap still being computed somehow even though its not being rendered until an explosion? Or is this actually an ideal method?
looking forward to hearing if the terrain engine can support this…
AC
This limitation is one of the reasons why I decided not to use the new terrain system for my current project. If you use a mesh for your terrain, you will be able to use this ( http://www.unifycommunity.com/wiki/index.php?title=TerrainTwoLayerBumped ) shader from the Wiki when it gets modified for 2.0.
Thank you. I didn’t think so, but thought I’d ask. Now I know I don’t need to spend a lot of time making normal maps for my terrain textures. Thanks also for the link to the work-around, bigkahuna.
