Wed, May 22
Sun, May 19
@Kévin Dietrich (kevindietrich) Glad you came back! Could you please update your patch D2388 for the current code, so we could review and make it to the master finally, cause it's very important for fluid rendering.
If there's something I can assist with, let me know. I'm not a coder anymore, but maybe a can help.
Fri, May 17
Also I am having problems with sequences again: https://developer.blender.org/T51820
I am not working on this anymore, although I could resume work. This approach was suggested to me by Campbell as a general way to import custom keyframes from alembic archives. The patch was uploaded for review a few years ago: D2324.
I think the approach is pretty nice, as it'll give us a way forward to animate other properties as well.
@Sybren A. Stüvel (sybren): yep, not for 2.80, but this is the way to go, right? [having a cache-fcurve-modifier]
Or is there another possibility [from the design point of view]?
@Philipp Oeser (lichtwerk) it looks interesting, but too big a feature to put into master for 2.80.
Just wanted to check the status on the import-of-animated-camera-focal-length issue:
Thu, May 16
More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.
Wed, May 15
indeed, that will makes things much more simple and reliable…
Fri, May 10
Wed, May 8
Tue, May 7
Hm, this mtl file has emmisive / Ke as a single value:
Hey, thanks for the reply, with this conversation I hope blender can have more compatibility when used side by side with another proprietary/supportive program. I wish you and the development team good luck.
Thanks for the report, but that is not a bug, we cannot do much if other apps decide to use the color value to tint the texture input… In Blender color value is just completely replaced by the texture when one gets linked in. Issue can also come from the simplifications we have to do to translate the Principled BSDF-based shader into the old-fashioned fixed pipeline description that is the only available option to describe materials in most formats (FBX should support proper Principled-like shader, but that is to be investigated/known todo).
Mon, May 6
What format are you using for import/export?
Sat, May 4
Thu, May 2
Yes seems like we have the same problem with Alembic export. FBX or obj export works correctly but Alembic doesn't.
Wed, May 1
If you open the UV map editor, press A to select all and then S to scale you can see that the center of transformation is somewhere in infinity around bottom-left quadrant.
Glad to hear someone replied. I had to remove the original UV and rewrap it to solve my problem.
We should not close reports just because we don't know how to recreate the issue.
Hi there is indeed something wrong with the UV map but after recreating it (and even moving it out of bounds) everything seems to be fine. Odd thing was that the center of transformation for UVs was somewhere in infinite lower-bottom part of the UV map space when you selected with B. But if you singularly clicked out all triangles and scaled the transformation center was where expected to be. There was no triangle hidden in lower left part, I was checking.
Fri, Apr 26
Thu, Apr 25
@Francesco Sorrentino (zeirus) : Can you provide a demo blend file so that i can be sure i am inspecting what you actually mean and not what i think that you mean ? Thanks!
Wed, Apr 24
sorry. Easter holidays stepped in between :)
Apr 21 2019
Apr 20 2019
Apr 19 2019
Apr 14 2019
This is now fixed in 5fdd91c09edf7c5a4794a3de4fbb1a7603d609f0
Apr 12 2019
I see the problem, but arent auto keyframes never supposed to do that? Should blender allow for that mess to begin with when setting autohandles from BPY?