Hi,
That's the sort of thing that annoys me about other 3D engines - they incorporate a lot of functionality that would be better incorporated at the programming end (to give greater control and versatility).
Well, the 'scripting engine' (that term's a little vague for me...) will have exactly the same access to Max3d as will the host language, so it's not like you'll ever *need* to use it, or it will have some extra magic access or anything.
What I mainly like about the lua stuff at the moment is really just the debugging/testing potential it adds. In particular, I want to add a Quake style 'drop down' console to Max3d, and having lua as the 'console interpreter' will really be cool I think.
As for taking scripting further, eg: for event handlers like OnUpdate() or whatever, that's something I might well explore further down the road. But I can't ever see it being 'more capable' than just doing your own updating in the host language.
That's the sort of thing that annoys me about other 3D engines - they incorporate a lot of functionality that would be better incorporated at the programming end (to give greater control and versatility).
Well, the 'scripting engine' (that term's a little vague for me...) will have exactly the same access to Max3d as will the host language, so it's not like you'll ever *need* to use it, or it will have some extra magic access or anything.
What I mainly like about the lua stuff at the moment is really just the debugging/testing potential it adds. In particular, I want to add a Quake style 'drop down' console to Max3d, and having lua as the 'console interpreter' will really be cool I think.
As for taking scripting further, eg: for event handlers like OnUpdate() or whatever, that's something I might well explore further down the road. But I can't ever see it being 'more capable' than just doing your own updating in the host language.