I am not a student, or at least in any school. I am a self taught python coder, getting the hang of it,
I would like to contribute, but don't think I fit into Gsoc as I only have a little time here and there, here is my idea..... */\/\/\/\/\/\/\/\/\/\/\/\/\/* I want to get started looking into the logic brick -> bullet linkages, and how constraints are handled, I would like for all constraints to have a python api like Target, etc, it would almost make sense that the we make a sensor to collect data from constraints, and trigger logic, as well as an actuator to modify the constraint, like Sensor-Constraint-RBJ/6dof X min X max------------------and---------------(Motion) so if the objects x offset is from min to max (or inverted)----------trigger logic the property x offset will be accesable like sens.offset.x sesn.rotOffset.x etc. Is this a terrible idea? I think people don't understand why I wish to do this, 1- grappling hooks etc in game 2- real time balancing via logic 3- better ability to make physical rigs that behave just like a regular armature 4- Custom camera controls - Physics based 5- using sensor linked with keyboard to not allow triggers when Rbj is to far out of alignment, so if I am tilting forward, play death 1 etc. a 6dof constraint linked to another item with no limits set would *ONLY* feed the offset angle and distance, so this is to get more power over the RBJ and receive more output data back from it, _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
