We’ve just shipped Unity 2.6.1 out to the world. This release includes a Webplayer that is compatible with 64-bit Safari on Snow Leopard, and fixes for problems affecting terrain trees and some asset importing.
But aNTeNNa trEE edited her/his post and now we cannot have lightmap in Indie with objects…
Why? No shadows at all?
And what this bug means:
??
One last thing: if we can create lightmaps with another tools (MAX, Maya, etc) and also you teach us how to do (see resources page)… why then just not let the engine create the lightmap ???
Terrain lightmapping has never taken trees into account, as far as I know. There are workflows to do it by painting directly into the lightmap texture (you can automate this through a few different means).
Yes, it is worth upgrading… 2.6.1 has not added any known bugs or deliberately removed features… it was released to make Unity better
Lightmapped shadows on the Terrain has never been a feature of Unity Indie/Free. We did not remove it from 2.6 or 2.6.1. And yes, it is possible to export your Terrain as a mesh and lightmap it in a separate program. That’s what I do because to be perfectly honest Unity’s Terrain lightmapper is no match for a dedicated renderer such as Mental Ray.
Actually, its not a problem that 2.6.1 have, its just not a feature available :lol: . And yes, its orth, trully.
I agree with you aNTeNNa trEE, but I dont have resources to buy tools like 3DS or Maya, or any good renderer. I just thought that It could be great if Unity creates lightmaps with Indie version… but ok, I will not die without this feature :lol:
you can use "Gile lightmapper" it’s free an does good job for lightmapping and Global illumination stuff by the way cool update , tree doesn’t make unity crash and finally package from unity 2.6.1 doesn’t crash my unity iphone 1.5.1 :lol: should be a good day ^^
Blender is free, and works great for baking textures and lightmaps. It has the best UI of all the 3D apps, too, although they ruined it with the new version. (ducks and runs away)
Pixel lighting may be ok for small projects but not larger ones. Frame rate drop too big.
Moire pattern still exists on windows with full screen fx and 7300 cards. (yes, this is a lower end card but not a usergroup we want to lose and it never happened before 2.6)
There were some improvements at first with less ram usage but further implementation of pixel lighting and then the testing on windows full screen made it not worthwhile at this time for a project of our size.
edit: tried again and forcing OpenGL makes it work ok… Windows and directx has memory leak probs, still