- User Since
- Oct 7 2010, 12:19 PM (384 w, 5 d)
Implemented import & export of camera focal length in FBX now, so will re-assign to @Sybren A. Stüvel (sybren) for the Alembic part of it…
I suspect this file uses advanced FBX features we do not support… but hard (impossible) to tell with such a big fat FBX, please try to reproduce same issue with dead simple file (like, only a few cubes, without any addition like materials, textures, animation, etc.).
Fri, Feb 16
@Manuel Rais (g-lul) Nope, in fact if a bug does not affect current master, there’s no point in reporting it, since it has already (presumably) been solved. :)
Thu, Feb 15
Yep, would appreciate a report about this, relocate *should* work (but indeed most likely not all corner cases with ugly proxies are ironed out yet :( ).
Tue, Feb 13
Ok found the core of the issue.
Well, at least library relocation (rightclick on a lib in outliner, Relocate) does work correctly it seems.
- Cleanup: remove asyncio version of Amber, and Claude, from branch for now.
- Cleanup/internal renaming.
- Add last missing piece of asset engine API, load_post callback.
Mon, Feb 12
Sun, Feb 11
@marco.barrero (Modelfan23) Next time you do that your account will be disabled. In case reasons are not obvious enough, let me summarize them for you:
- Initial report is totally, blatantly useless, empty, and not following the rules;
- After asking for it to be closed, you start messing with its triaging settings, and keep doing this even after being warned you are not allowed to do so;
- You savagely nuke the content of original report, which is also very disrespectful and bad for anyone trying to figure out what may happens here.
Sat, Feb 10
Fri, Feb 9
Yeah, made it more resilient to utf-8 decoding error recently (like, in last January)… Note that fbx exporter is buggy here, as official FBX docs state that all strings in an FBX file should be encoded in unicode utf-8!
Thu, Feb 8
Agree with choosing third option, we want to keep that code as quick as possible. Patch LGTM.
Wed, Feb 7
Tue, Feb 6
Mon, Feb 5
Fri, Feb 2
Thu, Feb 1
Indeed not really a bug, and imho it’s more valuable to allow some extreme values that may come in handy in some cases, even if at the cost of a minor 3DView glitch… Thanks for the report anyway. :)
Wrong commit message, sorry!
Actually fixing T53975, sorry for the mess…
Can confirm the issue, not that this is not related to datatransfer modifier, this is an issue common to all 'Modify' modifier afaict. Will investigate further.
Wed, Jan 31
Yep, as @Philipp Oeser (lichtwerk) said, there is absolutely no way for Blender to guess where this module would come from, it’s just assumed to be 'somewhere' in our py path, that’s all. Append/link can definitively not deal with that, they only deal with relations between actual data-blocks anyway.
@blend-it (blend-it) thanks, done.
Eeeeek! I think this commit should not have been backported to 2.79a at all, my bad, will revert it.