Hi Jenandesign, thanks for reaching us.

With regard to your request, the reason of the change is due to the new Python console brought out since R20 where by dragging a parameter from the UI in the console provides the user with the complete "route" to propelry evaluate the parameter.

This is by design and won't be reverted back in future releases.

Best, Riccardo

Thanks a lot Baca and I apologize for the hurried and shallow answer.

Looking deeper in the argument the Computer Animation: Algorithms and Techniques reports: "While it should be obvious that interpolating the translation is straigthforward, it is not at all clear how to go about interpolating the rotations. In fact, it is the objective of this discussion to show that interpolation of orientations can be a problem. A property of 3x3 rotation matrix is that the rows and columns are orthonormal. Simple linear interporlation between the nine pairs of numbers that make up the two 3x3 rotation matrices to be interpolated will not produce intermediate 3x3 matrices that are orthonormal and are, therefore, not rigid body rotations. It should be easy to see that interpolating from a rotation of +90 deg about the y-axis to a rotation of -90 degrees about the y-axis results in an intermediate transformation that is nonsense.
So direct interpolation of transformation matrices is not acceptable. There are alternatives representation that are more useful than transformation matrices in performing such interpolations: fixed angle, Euler angle, axis angle, quaternions."

Considering your answer providing a reasonable solution using quaternions, I've played something similar using fixed angle

def MatrixBlendFixedAngle(mxA, mxB, t): # get mxA scale AScale = mxA.GetScale() # get mxA offset AOff = mxA.off # remove from mxA the scale to retrieve rotation mxA.Scale(c4d.Vector(1/AScale.x, 1/AScale.y, 1/AScale.z) ) # retrieve the HPB representation of mxA AHPB = utils.MatrixToHPB(mxA) # get mxB scale BScale = mxB.GetScale() # get mxB offset BOff = mxB.off # remove from mxB the scale to retrieve rotation mxB.Scale(c4d.Vector(1/BScale.x, 1/BScale.y, 1/BScale.z) ) # retrieve the HPB representation of mxB BHPB = utils.MatrixToHPB(mxB) # execute the linear interpolations for offset, scale and HPB COff = (1 - t) * AOff + t * BOff CScale = (1 - t) * AScale + t * BScale CHPB = (1 - t) * AHPB + t * BHPB # calculate mxC from interpolated HPB mxC = utils.HPBToMatrix(CHPB) # add the interpolated scale mxC.Scale(CScale) # add the interpolated offset mxC.off = COff return mxC

Finally with regard to your quaternion solution, for those who are interested in, a discussion on how to make use of quaternions is on GameDev.

Cheers, R

Sorry I was not clear enough.

Your answer (polygon object is "enabled" by definition) triggered me and now I understand.

Thanks and my best wishes for a great 2020 for you, your family and your Maxon family.

-Pim

Thank you all for the response. Appreciate a lot.

Specially for the sample code provided by @m_magalhaes as this is my code relating to rendering.

Hello,

That's a more wide discussion about how to code. We can say that as long as it compile and your plugin is working, your code is fine.

Cinema 4D is provided for both Windows and OSX, so differences can be introduces. Using our datatype guaranty (unless a bug) that your code will work the same on both OS. (of course there's always exception, don't jump on them 😉 )
Same goes for external librairies.

Another example is our thread/job system, some external librairies can interfere with cinema4D in a badly way.

Cheers,
Manuel

@r_gigante
Hi Riccardo,
Thanks for the explanation.
I wasn't sure that a "Solved" thread would still get revisited by SDK team members.
As Manuel mentioned "I'll come back when I got more information", but the thread was set to solved, I wasn't sure the thread would get an update.
Also, others visiting the forum (now or in future) might be misleaded by the state of the thread, thinking that the bug has been fixed, while it actually isn't.

But now I understand a "bug fixed" tag is being added. Seems I need to pay more attention to the tags, as I assumed these tags were added by the creator of the thread. As such, I never really paid any attention later on, as I assumed the tags I added were the only ones to be available for that thread, and only the unsolved/solved state would change as a result of a resolution.

Thanks for clarifying.

@kbar @m_adam Thanks for the help lads, the markers were already added thanks to Kent suggestion in his previous reply.

Now the only things left are a little "GlTF-fighting", and some more polishing, packaging and testing before updating the plugin with a - hopefully - nice animation support !

I'll let you know when that's done (probably not before 2020 though 😉 ).

Cheers,
Loïc

Hi, @r_gigante
Thank you for your reply. With your help, I finally traced the source of the problem. As you said, the reason for the error(Critical Stop) is that there is no Container at all. Because of a very hidden error in somewhere, I wrote the wrong data type to BaseContainer.

The mode specifies how data can be read from the Morph Tag.
By default, they are presented in a compact way (aka only modified points are stored for some internal optimization).

But if you SetMode with c4d.CAMORPH_MODE_FLAGS_ALL | c4d.CAMORPH_MODE_FLAGS_EXPAND then all the points are then readable from outside of the morph Tag.

I adapted the Python documentation to match the C++ documentation so it will be available in the next documentation update. But I would say the C++ documentation for SetMode is pretty self-explanatory, what is the part you don't understand?

Cheers,
Maxime.

THank you so much! 😸

The way it's described in the SDK docs, I do not get any error message:
Screen Shot 2019-12-16 at 12.08.48.png

By diving into the location in the API where the error is thrown, I might have found that it's a nullptr error.
Screen Shot 2019-12-16 at 12.04.55.png

@m_magalhaes

Oh gotcha. Thanks for the reminder. Totally forgot they UNDOTYPE_CHANGE have a different placement thant UNDOTYPE_NEW

Thanks again. Have a great day ahead!

Hello,

We've talked about this issue in our morning meeting. Contrary to what I've said, it's Core related and not API related. (limitation of cinema4D itself in fact)

You have to open a ticket in our support. Tell them you are coming from our forum and it's not related to the API and it's a Core Problem.

Sorry for wasting a bit of your time but we need to keep organized.

Cheers,
Manuel

Still not I will update you as soon as I have some news.

Cheers,
Maxime.

@m_adam said in Reverse iterators, how to use them?:

Hi @C4DS

Here the message from the development team which confirms what I said to you previously.

Hi Maxime,
I didn't doubt what you said earlier.
I only wanted to point out that it wasn't clear from reading the documentation which collection could be used with reverse iterators.
It's nice mentioning in the documentation about RBegin/REnd, Range based loops, etc ... but not everyone looks into the collection implementation to see which types do have RBegin/REnd or are range based, ...

HashMap doesn’t support -- so you can’t use a reverse iterator for that.
It wouldn’t make sense anyway because HashMap iteration is unordered.

Having used std::map some might expect HashMap to be ordered, but it isn't mentioned anywhere it isn't.

But the point has been made, and it is now clear how to use reverse iterator.
Topic well be closed as "solved".

@C4DS Thank your reply! I had to come back to this because I had problems with switching back to object context and this solved that!

ah... ok, now i understand the picture !
thanks, manuel

I marked the thread as solved

thanks a lot!
for others and myself here a reference to the python SDK

https://developers.maxon.net/docs/py/2023_2/modules/c4d/C4DAtom/GeListNode/BaseList2D/index.html#BaseList2D.GetInfo

Great, I will do that. 🙂

Hi @turrican welcome in the plugincafe community.

I moved your topic in the correct category and assigned tags, see (How to Post Questions) Please do it for your next topics.

Regarding your question, yes it's possible to do it in python. however, I suggest you contact maxon support to report the initial bug regarding the FBX importer.

Now you have to keep in mind here we don't code for you but help you to achieve what you want.

So the steps in python for doing it are:

Loops over each material. Retrieves their name. Create a Bitmap Shader and assign it to the correct channel of the material (normal).

To loop over each material, keep in mind that material in Cinema 4D is BaseMaterial which is a child class of GeListNode so to loop over all material use

# Retrieve the first material of the current document mat = c4d.documents.GetActiveDocument().GetFirstMaterial() # loop over each material while mat is not None: # Do the things for each mat mat = mat.GetNext()

To create a bitmap shader (c4d.Xbitmap) and assign a texture to it find an example in shader_create_bitmap_r13.py.

To know the ID of the normal channel, just drop and drop it into the console, see Python Console - Drag and Drop.

Cheers,
Maxime.