Difference between revisions of "Talk:Physics"

From BZFlagWiki
Jump to: navigation, search
 
Line 1: Line 1:
 
This page has confusing and almost contradictory statements as to which objects can use physics drivers and which can't!  Can someone "in the know" tidy it up?  [[User:Mr Burns|Mr Burns]]
 
This page has confusing and almost contradictory statements as to which objects can use physics drivers and which can't!  Can someone "in the know" tidy it up?  [[User:Mr Burns|Mr Burns]]
Done, but my wording probably needs some help.  Also, can we decide on a standardized way to do the code on these objects? such as: linear 0 0 5 #<x y z>        angular 0 0 #<x y>[[User:Tedius|Tedius]]
+
:Done, but my wording probably needs some help.  Also, can we decide on a standardized way to do the code on these objects? such as: linear 0 0 5 #<x y z>        angular 0 0 #<x y>[[User:Tedius|Tedius]]
 +
::2.0.9/2.0.10 servers will automatically convert [[box]] and [[pyramid]] objects to [[meshbox]] and [[meshpyr]] when you attempt to use physics drivers (or material references) on them, so you CAN use them.  I believe this is covered on the [[box]] and [[pyramid]] pages, though not in any sort of consistent way. -[[User:DTRemenak|DTRemenak]] 15:58, 25 September 2007 (EDT)

Latest revision as of 19:58, 25 September 2007

This page has confusing and almost contradictory statements as to which objects can use physics drivers and which can't! Can someone "in the know" tidy it up? Mr Burns

Done, but my wording probably needs some help. Also, can we decide on a standardized way to do the code on these objects? such as: linear 0 0 5 #<x y z> angular 0 0 #<x y>Tedius
2.0.9/2.0.10 servers will automatically convert box and pyramid objects to meshbox and meshpyr when you attempt to use physics drivers (or material references) on them, so you CAN use them. I believe this is covered on the box and pyramid pages, though not in any sort of consistent way. -DTRemenak 15:58, 25 September 2007 (EDT)