Skip to main content
10 events
when toggle format what by license comment
Oct 19, 2016 at 16:47 comment added batFINGER That'll do it 8^)
Oct 19, 2016 at 16:45 comment added M - @batFINGER you are correct. I did notice that the .obj file still retained a high level of precision on each vertex. Being a python newbie, I just opened it in a text editor and manually deleted all instances of .000000
Oct 19, 2016 at 15:25 comment added batFINGER Further to above on line 233 (for example and in many other places) of io_scene_obj/export_obj.py 6 decimal places are hard coded in fw('v %.6f %.6f %.6f\n' % (ob_mat * pt.co.to_3d())[:]) to the output using a format string. You could do a global replace on %.6f to %.1f to have the format round the floats to 1 decimal place.
Oct 19, 2016 at 15:04 comment added batFINGER Not sure about getting 50% reduction on export to obj, A vert at (1, 1, 1) will be exported to v 1.000000 1.000000 1.000000 in the obj file wont it? Running the rounding script over the obj file (or editing exporter to do so) would be more likely to help in this regard.
Oct 19, 2016 at 6:32 comment added kheetor Note that you are trying to edit mesh named "meshname". If you want to evaluate the variable it should be bpy.data.meshes[meshname] but can't really tell from this excerpt. The mesh.vertices is read-only which only means you can't assign a list of vertices to that variable. But it doesn't mean that all the data below would be uneditable and you should still be able to change vertex coords, layers data etc by accessing it like you are trying to.
Oct 18, 2016 at 22:25 vote accept M -
Oct 18, 2016 at 22:20 answer added Jake Dube timeline score: 5
Oct 18, 2016 at 21:41 history edited M - CC BY-SA 3.0
added 304 characters in body; edited tags
Oct 18, 2016 at 20:46 answer added Nikita Zeulin timeline score: -1
Oct 18, 2016 at 19:57 history asked M - CC BY-SA 3.0