Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

@Mai Lavelle (maiself) I guess this one is for you? ;)

Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Ah ok… well, can confirm then :(

Thanks, can confirm the issue…

Uh, yeah… think Campbell reasons make sense in T47770 in fact… so thanks for the patch, but will close it for now.

Weeelllll… cannot reproduce so far…

Can’t confirm the crash here. Please try the latest build from our buildbot (and please void submitting such huge files as bug demo, this is really not good practice for a lot of reasons :/ ).

@Mike Erwin (merwin), @Martijn Berger (juicyfruit), thoughts?

Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Cannot confirm that with current master, so would assume this has already been fixed. Please try the latest build from our buildbot.

@Howard Trickey (howardt) backtrace seems to point to Bevel issue?

Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Thanks for the report, but no bug here, this is just a mater of point of view/reference system… Front view is used as ref here, so right view indeed show view from the right of the front view, left view, from the left of the front view, etc.

Just a note about FBX and instances: if you have modifiers on your objects and export them in FBX, then you obviously export one different mesh per object, maybe that’s what happened for you?

No, lgtm and seems to make sense indeed… and can’t think of any bad corner case so far.

Not sure… would doubt this is due to remapping stuff, though, afaik dupli handling is beyond data-blocks handling.

OK, think I understand mostly what’s going on here, and new result definitively looks better than old one, so patch LGTM.

Odd… very odd…

Can’t confirm that here for FBX, it does export and re-import as a single mesh… Are you sure you are using correct version of FBX addon (should be 3.7.7)?

Thanks for the report, but no bug here, this is expected behavior (when you parent an object to another, at least when using the operator, you store the inverse transformation matrix of the parent, such that parented object can “visually” keep same world position as it had before parenting.

Can’t confirm this here, most probably you disabled somehow the "Global Undo" option in user preferences, Edit tab?

Thanks for the report, but newer FBX files (FBX2016) are not supported by Blender currently, AD decided to break format on binary level again afaik, even our 'fbx2json.py' script (which merely reads binary blocks and write them in human readable json format) can't handle them.

Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Ok makes sense, will commit then, thanks for the patch.

Humpf… yes, this will work nicely with modern python, but… according to the doc, gzip.open only accepts file objects as parameter since py3.3, would not be an issue if this script was to be run with Blender, but its purpose is precisely to be run outside of it…

I’m not sure to see the point in changing target after binding? Explanations of the report are rather… unclear to me.

Thanks for the suggestion, but we do not accept feature requests or suggestions on this tracker (use forums or bf-funboard ML for that).
Please do not create design/todo tasks, they are reserved to developers.

Will commit this…

Can’t seem to confirm this here on Linux… might be a windows-specific issue, this is likely in OCIO lib itself anyway I’d think, @Sergey Sharybin (sergey)?

@Sebastian Koenig (sebastian_k) said pretty much everything, except that you may have 'world' (aka 'real') dimensions by enabling Global option on top of Transform panel, in Edit mode…

Thanks for the diff, will check on it asap, but adding an extra task is not really needed here.

Archiving for now then.

Did you try loading factory settings?

More than a week without reply. Due to the policy of the tracker archiving for until required info/data are provided.

More than a week without reply. Due to the policy of the tracker archiving for until required info/data are provided.

@Sergey Sharybin (sergey) automatic draw did not changed, @domlysz (domlysz) says he already had to change that for 2.77, so nothing new in 2.78 here…

More than a week without reply. Due to the policy of the tracker archiving for until required info/data are provided.

More than a week without reply. Due to the policy of the tracker archiving for until required info/data are provided.