Isn't there an occlusion culling true/false setting in the appearance properties for entities? and doesnt the Engine take care of some of that by default (lights/characters)?
I should add if you try to use the texture from L3DT then use that as the base texture layer in the editor, setting to "fit to terrain", there seems to be an issue with this setting saving correctly in the .sbx file. Luckily "Mack the Hack" has found a temporary solution.
ok, makes sense.
Not really a "fear of it" with me its just I have not gotten around to it yet so am currently trying to get a feel for pro's and con's.
M'kay so no real benefit then, I was wondering why write the XML then load an XML parser in Lua to read it to store the info in the lua properties.. when a .ini would simply fill in the blanks on load, the .ini would simply be something like:
idle_start=210
idle_end=234
walk_start=235
walk_end=259
ect ect ....
SetColor(Vec4(1, 1, 1, 1)) simply clears the changes you made using SetColor at the start of the 2D phase, no need to fetch the original colour and re-apply.
I think you will find that Max2D functions interfere with some Leadwerks functions.
Not sure I follow you on that, how would a "Getcolor()" command help here?
The simple rule of thumb is if you turn it on .. remember to turn it off when done..