Topics created by fwilleke80

Ha, right, I should've thought of that ^_^
Thank you, it works!

Cheers,
Frank

Hello @fwilleke80,

thank you for reaching out to us.

I noticed that, in C4D 2024, the return value of BaseContainer::GetDirty() does not always change after changing a value in the container. Is this a bug? I am using BaseContainer::GetDirty() to detect changes to a container, and now this doesn't work anymore.

While this certainly sounds like a bug, without something more concrete we can do nothing to help you here. Which parameter types have been changed? The context somewhat implies that this does happen when writing custom data types? We will need code to do anything concrete here.

If a fairy granted me three wishes, I would greatly appreciate ...

I think the problem with both are custom data types and that our tech team is probably a bit reluctant to rely for collision resistance on external developers (when we would offer a CustomDataTypeClass::GetHashCode). We could of course implement it and then not use it ourself, but that is not how we tend to do things.

Cheers,
Ferdinand

Ok, thanks! 🙂

Hi Ferdinand, thank you for the clarification!

Super, thank you!

Very informative, thank you Ferdinand!

@ferdinand said in Can't debug C4D 2023 and 2024 on macOS:

first, thank you very much for investing more time into this and with that saving time for me, truly appreciated.

You're welcome. If any of this get any of us further it's worth the time.

@ferdinand said in Can't debug C4D 2023 and 2024 on macOS:

But let us discuss the details per mail.

Okay!

Cheers,
Frank

I already tried using 8 bit greyscale. Still doesn't work in 2023 on macOS, but on the other C4D/OS combinations.

Will try RGB, too.

If that doesn't work either, I'll be back and try to write a minimal example.

Cheers,
Frank

Hey @fwilleke80,

you are right, it does indicate an error, hence my example from above. When I searched in our internal code base for similar code, I found a lot of

return NodeData::GetDDescription(node, description, flags);

calls. While there are certainly node types which customize their description handling, this seems to be more a precaution for the case when we decide that we want to implement something in NodeData::GetDDescription in the future. Or something has been there in the past and we optimized it away. In any case, one should not take my comment about calling the base implementation being pointless too seriously. It is best to leave the call in, although it currently has no practical effect and probably will never have.

Cheers,
Ferdinand

@jana sorry, I forgot to flag it myself. All solved, thank you 👍

Woot, it works! 🕺

Hello @fwilleke80 ,

without further questions or postings, we will consider this topic as solved by Thursday 01/06/2023 and flag it accordingly.

Thank you for your understanding,
Maxime.

Thank you, that fixed it.

Hello @fwilleke80,

without further questions or postings, we will consider this topic as solved by Thursday 01/06/2023 and flag it accordingly.

Thank you for your understanding,
Maxime.

Hi Ferdinand,

thank you! In deed, that looks pretty simple. Wonder why I couldn't get it to compile...

I'll test this and report back in case it doesn't work. Since I guess you found it in active code, I'll mark this thread as solved for now. thanks again!

Cheers,
Frank

@m_adam said in macOS Monterey - Can't run source processor anymore?:

So you have to link for example from /usr/local/bin to a python installation, I personally have Python 3.8.9.
Xcode itself ships with a python version you could link to (its in Contents/Developer/usr/bin of the application package).
So with that path you can call call sudo ln -s PATH_TO_PYTHON /usr/local/bin/python in terminal.

Hi Adam!

That is in deed what I tried, creating a symlink that points to Python 3. I didn't use the paths, though, but just linked the word "python" to "python3". I guess that was my mistake.

Wouldn't it be easier for Maxon and everybody else, if you just changed the preprocessor call in the projects' PreBuild events to "python3", instead of having to go the symlink way and change things on users' computers (which, I guess, will have side effects when users later decide to install Python 2.7 for some reason)?

Cheers,
Frank

Okay, thanks!

I've changed this back to "Normal topic".
It was a question, and it was answered, but since there's no solution, I didn't want to mark it as "solved.

hi,

sorry i didn't had time to investigate yesterday. I'm happy that you find out the solution.

Cheers,
Manuel

I already did 😉 If they didn't contact you, it strengthens my suspicion, and I can simply ignore further mails from that contact.
Thanks!

Cheers,
Frank