- User Since
- May 6 2009, 11:18 PM (562 w, 5 d)
Wed, Feb 5
A silent failure is more likely a bug than a limitation. I look at this.
Wed, Jan 22
Mon, Jan 20
Is the Alpha value of the Base color in the Principled BSDF Shader still used anywhere?
Jan 15 2020
This is not a bug, but maybe its a bad choice of default settings:
Jan 13 2020
Jan 12 2020
As far as i can tell all of the collada files which you provide in your zip file are fully OK.
Jan 10 2020
@Jean First (robbott) well... yes, you are right.
@Kent Davis (mac4kent) If you think this is still an issue, then please come up with a fresh description based on the newest Blender release and please make sure that someone familiar with Mac is available who can help to figure out what is going on. I am ready to help fixing this as long as someone tells me exactly what is wrong. Especially what exactly in the collada data is broken and how it would need to be fixed.
The collada importer is available from File -> Import -> Collada I am not aware of that it is disabled. I tested with a fresh build from this morning on Windows. So, maybe something has gone wrong with the latest builds for Mac ?
Dec 12 2019
Nov 27 2019
reopened temporary for organizational purpose
@Trevor Hendricks (TH) Thanks for the additional collada files!
Nov 26 2019
@Trevor Hendricks (TH) Could you please try to make a simpler animation that shows the same issue ? this list might help:
i can not reproduce this issue. For me both collada files import and they both contain meshes:
@Campbell Barton (campbellbarton) thanks for the fix!
Nov 25 2019
@Andy (DeepBlender) : The Collada memory leak is fixed. However when i run your test script again, then there is still another leak:
There is no need to check it before the import is fixed. I was just curious to know in advance.
Nov 21 2019
hmm, that is odd. I see where it obvioulsy goes wrong. I wonder though. It looks like an old bug. just out of curiosity: Have you checked if the memory leak also happens when you try with an animation that only contains trans/rot/loc and not matrix curves? I suspect that with that there is no memory leak...
Nov 12 2019
@Mike Lima (lunarbase) I believe this issue is fixed since Blender 2.80. Would you mind to test again and report back if it still is broken? And add a demo file please :)
@Chad Faragher (wyckster) In which way is exporting broken? I just tried by creating a camera and animating it as described in the report description. Then i exported the camera with sampled animation. That worked for me.
Nov 11 2019
Nov 9 2019
Yes, i figured out already :) and have added back F8 for me. However i am still a bit concerned about this issue.
Nov 8 2019
I dare to contradict.
Oct 31 2019
Oct 27 2019
Oct 9 2019
Just before you export you have the option to specify the file name to where the exported objects shall be stored. Isn't that enough? Maybe changing the name of the exported file depending on the active object might sound like a cool idea, but then the export filename of a set objects depends on the order they are chosen, which again may not be expected (or wanted) behavior.
Sep 27 2019
Sep 14 2019
Sep 11 2019
I do not know where else this issue should be handled. If there is a better place for this, please indicate where i should go. However...
Sep 9 2019
@Nathan Letwory (jesterking) I propose that we use a Collada fork for important fixes until we have migrated to another implementation for Collada or until collada has fixed their library them self. If blender won't host and maintain the fork, then i can offer to use my fork: