tx, i just wanted to report it...

Hello @a_block, Thank you for reaching out to us and pointing out these flaws. We are aware of these changes but since it was for quite some time unclear if these changes were intentional or not, we postponed documenting them. The changes to the look and functionalities of GeDialog borders will be included in an upcoming documentation. But since these changes effectively demand symbols or even function arguments to be deprecated, this would be more a developer's task than a documentation task. I can of course put a note into the documentation, but this would only be a band aid. I will try to find a clean solution by poking the relevant devs. Cheers, Ferdinand

Just for the info, calling the command to open the PictureViewer and RenderDocument with both c4d.RENDERFLAGS_CREATE_PICTUREVIEWER and c4d.RENDERFLAGS_OPEN_PICTUREVIEWER works just fine for me : c4d.CallCommand(430000700) # Picture Viewer c4d.documents.RenderDocument(doc, rdData, bmp, c4d.RENDERFLAGS_EXTERNAL | c4d.RENDERFLAGS_CREATE_PICTUREVIEWER | c4d.RENDERFLAGS_OPEN_PICTUREVIEWER)

Hi Jesse, thanks for the report those issue have been fixed and will be up in the next update of the documentation. Thanks a lot for reporting them and if you see other one please report them ! Cheers, Maxime.

First thank you Ferdinand, as always, you put so much effort in your answers, this is so great.. Related to my code, yes there are of course weird things going on sometimes :-), I am not professional and the API is sometimes like a jungle and so Python, so I am messing up a few things...This process is called "learning" But anyways thank you for your detailed and quick answer.... Sincerely Thomas

Hi Ferdinand, thanks for the quick and detailed answer, even trying to find workarounds. I had hoped, I could spare you this extra effort by saying, that it's no functional issue on my end. I am already satisfied with the confirmation. Often it is enough to be able to stop worrying about my own mental integrity. And while this new behavior certainly will not improve performance, I can happily ignore performance issues beyond my own responsibility. Regarding the GeDialog stuff: No worries, either. As mentioned back then, no future fix/solution can help me there and I went down a different route to get the project done with support for R19 to present. Yet, I'm thankful for your tenacity and that the issue is still being researched. Some meals simply need time to develop their flavours. Thanks and cheers, Andreas

Hi, thanks for the information. Hopefully it will get fixed in the future updates. Cheers, Arttu

Hello @WTools3D, without any further questions, we will consider this topic as solved by Tuesday, November the 2nd and flag it accordingly. Thank you for your understanding, Ferdinand

Hi @SteveJLV, the APPEND mode is not supported by the HyperFile. The FILEOPEN enum is also used in BaseFile, which is the underlying class used by the HyperFile. BaseFile properly support Append mode, but extra code in the HyperFile prevent it to work correctly. So far I don't see any workaround possible for you in Python, the only way would to first read the HyperFile and rewrite everything + the things that you want to Append (pretty inefficient). I opened a bug report, to support APPEND within HyperFile. I set this post to solved, and I added the tag ToFix t your topic, but don't worry we will keep you in touch when a fix will be available but we can't say when it will be available neither if it will be fixed. Cheers, Maxime.

yes exact, it's a bug not an error from your implementation.

Hello @kbar, I should have replied here since there is at least an implied request in your last answer. I have added a task for this in our documentation task pool and added the tracking tag to this topic. Without any further questions or replies, we will consider this thread as solved by Monday the 20th and flag it accordingly. But that does not mean that the topic is forgotten, due to its to fix tag. Thank you for your understanding, Ferdinand

Hello @indexofrefraction, without further questions or replies, we will consider this topic as solved by Thursday and flag it accordingly. Just for clarification: This does not mean that the bug is solved or that we won't track it, we simply do not want to keep the thread open until the bug has been fixed. The bug status is tracked with the to fix tag that has been added to the topic. We will report back here when the bug has been fixed. Thank you for your understanding, Ferdinand

Hey Andreas, no need to feel sorry. It is valuable for us to be aware of this, as this could cause more serious problems further down the road, even though it is hard to reproduce for now. We have pushed this off to QA for now, due to them having the required tools (hardware) to assess this more thoroughly. I do not see anything inherently wrong with that. But the only ones who could answer this with complete certainty are the developers who wrote the Cinema 4D core. And until we cannot say with a reasonable degree of certainty that this is a reproduceable bug that we want to address, I will not bother them with this, since there is other "stuff" in front of the queue for them anyway. I have forked your second part of the question, as I would like to keep this thread clean, as I would anticipate that QA will confirm this bug, it then going to the developers, and we will then report back here. Which will get a bit convoluted when there is a second question being discussed here. The topic can be found here. I understand that this is not the most satisfying procedure for you, as it will take a bit of time. The issue of yours must go through our bug tracking system now first, rather than taking the shortcut we sometimes offer here, of us talking with the developers and then creating an issue if we decide to do so. Cheers, Ferdinand

Hi @merkvilson, long time we didn't saw you, hope everything is fine for you But with the latest update of Cinema 4D (R24 SP1), we finally fixed this bug. Cheers, Maxime.

Hi with the latest update of Cinema 4D (R24 SP1), CCurve.GetTangents is now fixed. Cheers, Maxime.

Hello @blastframe, thank you again for reporting this But can we close this or are there any remaining issues? The thread has been added to the fixed issues pool, see tag in the first posting. This is how we track documenation and API updates that are the result of a forum thread. When this issue has been fixed, we will post here and remove the tag. So, closing this thread does not mean that we will ignore the issue. Cheers, Ferdinand

Hi, I've asked the devs, the example react the same so it's not on your side Cheers, Manuel

Hi Ferdinand, thanks for the confirmation and looking into it. While it's a bit unfortunate, I do not consider this a major road block. From my side this thread can be considered close. Cheers