tngreene

Related to #450, since the recursive collection algorithm is needing to sort things correctly.

Its been decided that being able to use weights on the Objects is weird enough, better to kill this off then implement another way to be tricky.

Related to #575

xplane_bone.py: - Sometimes uses a hard-coded 5 xplane_light.py - Rounds axis_angle_theta in autodetection_algorithm to a hardcoded 5 digits xplane_helpers.py - in floatToStr, FLOAT_PRECISION = 8 is used to round numbers...

- 4252dadf8 - xplane_config.debug/log removed - 28fb74cde (and later b68193) - Remove XPLANE_OBJECT_TYPE_* constants - Other dumb TODO comments removed in this time region

c97a96411ee448cf1 - Renamed the terribly named "getWeight" method.

Annoying uses of hasattr are not uncommon. For instance ``` if hasattr(mesh, 'calc_normals_split'): # split normals mesh.calc_normals_split() supports_split_normals = True if hasattr(mesh, 'polygons'): # BMesh mesh.update(calc_tessface = True) mesh.calc_tessface() mesh_faces...

Wonderful. This is just awesome. Btw, if you ever want to quickly know what Blender version a .blend file is, it has a magic string at the beginning of the...

Btw, I think there is a pretty major bug with Default lights and the VLIGHT table - ``` co = light.blenderObject.location self.lines.append("VLIGHT\t%s\t%s\t%s\t%s\t%s\t%s" % ( floatToStr(co[0]), floatToStr(co[2]), floatToStr(-co[1]), floatToStr(light.color[0]), floatToStr(light.color[1]), floatToStr(light.color[2])...

Not only is the location used straight, it is also relying on some bizarre global state problems that make this take the location from keyframe 1. Unit tests where an...