As far as I know, using the PhysX API, the only way to get NxActor is by an example of NxScene CreateActor The law is really annoying me, I want to keep my code clean, but I feel that there is no alternative to moving the scene from the constructor to the constructor so that classes can make reference to artists. Be there I think, Alternatively, I can make Visual World (EECH!), But I do not think the global variable is a good idea. One thought that my classes were just to store an NXAct DCCC (and message it to them The scene was provided to make an actor through sending), but they really need references to the NXActor so that they make changes with the actor Programmed to sink.
Either way, I want to see what the insights of others can be. Do you think I am going right about this (passing NXSCN at all places)? It seems like icky, but maybe I'm just crazy. If not, how can I create a model class like that with NXactor which is more elegant? thank you in advanced!
If you do not want that you want objects directly with the cast, suggest a different approach to you The objects can come in a way of registering to update physics. Then the modules which are registered with those objects, provide each object for an actor, which is used to set the information of objects periodically. In this way you have only one module with actor / physax management and objects, an interface that requires them to update with the information of physics.
Comments
Post a Comment