CINEVERSITY

I received this info today from Tech Support:

Thank you for reaching out to Maxon Support, and I apologize for the inconvenience you're experiencing.

The FAQ you are referencing is for a different issue with the CV Toolbox, not Planesmart.

That said, it seems you've encountered a known issue with the Planesmart we've documented and already reported to our development team. We still appreciate you bringing this up, as it helps us understand the scope of the problem and prioritize its resolution.

The only workaround I can offer at the moment is rolling back to 2023.2. The plane smart object does appear to work as expected in this version.

If you would like to roll back you can find the Cinema 4D 2023.2 installer here:
https://www.maxon.net/en/downloads/cinema-4d-2023-downloads

The timeline for a fix depends on various factors, including the number of customers affected, the severity of the issue, and our current schedule of updates and optimizations. Unfortunately, I can't provide a specific date for when this will be resolved.

Thanks for your understanding!

Hi physical-balance,

Please in English only. Thank you.

If you encounter a problem with hardware or anything related technical, please check with tech support.
https://www.maxon.net/en/support-center

Thank you, and enjoy your new machine!

My best wishes

Thank you very much, briggs, very nice of you!

Cheers

CV Swim still not working in C4D 2024. One of my most used plugins. Seems, there is an argument missing in the import funtion.

"
DEBUG:cvToolbox:Retrieved XML: <xml.etree.ElementTree.ElementTree object at 0x000002902D8B2920>
INFO:cvToolbox.core:Parsed Resource XML
DEBUG:cvToolbox:Checking for new tools since 1706274940, most recent update 1658401560.0
Traceback (most recent call last):
File "C:\Users\FSchmidt\AppData\Roaming\Maxon\Maxon Cinema 4D 2024_A5DBFF93\plugins\CV-Swim\CV-Swim\CV-SwIm.pypv", line 1127, in PluginMessage
File "C:\Users\FSchmidt\AppData\Roaming\Maxon\Maxon Cinema 4D 2024_A5DBFF93\plugins\CV-Swim\CV-Swim\CV-SwIm.pypv", line 1116, in AddCVSwimPulldown
AttributeError:module 'c4d' has no attribute 'MENURESOURCE_SEPERATOR'
PendingDeprecationWarning:Since 2024.0 Init has a 2nd argument 'isCloneInit' that is going to be mandatory in 2025.0
PendingDeprecationWarning:Since 2024.0 Init has a 2nd argument 'isCloneInit' that is going to be mandatory in 2025.0
PendingDeprecationWarning:Since 2024.0 Init has a 2nd argument 'isCloneInit' that is going to be mandatory in 2025.0
PendingDeprecationWarning:Since 2024.0 Init has a 2nd argument 'isCloneInit' that is going to be mandatory in 2025.0
PendingDeprecationWarning:Since 2024.0 Init has a 2nd argument 'isCloneInit' that is going to be mandatory in 2025.0
PendingDeprecationWarning:Since 2024.0 Init has a 2nd argument 'isCloneInit' that is going to be mandatory in 2025.0
PendingDeprecationWarning:Since 2024.0 Init has a 2nd argument 'isCloneInit' that is going to be mandatory in 2025.0
PendingDeprecationWarning:Since 2024.0 Init has a 2nd argument 'isCloneInit' that is going to be mandatory in 2025.0
PendingDeprecationWarning:Since 2024.0 Init has a 2nd argument 'isCloneInit' that is going to be mandatory in 2025.0
PendingDeprecationWarning:Since 2024.0 Init has a 2nd argument 'isCloneInit' that is going to be mandatory in 2025.0
PendingDeprecationWarning:Since 2024.0 Init has a 2nd argument 'isCloneInit' that is going to be mandatory in 2025.0
PendingDeprecationWarning:Since 2024.0 Init has a 2nd argument 'isCloneInit' that is going to be mandatory in 2025.0
Traceback (most recent call last):
File "C:\Users\FSchmidt\AppData\Roaming\Maxon\Maxon Cinema 4D 2024_A5DBFF93\plugins\CV-Swim\CV-Swim\CV-SwIm.pypv", line 943, in Load
File "C:\Users\FSchmidt\AppData\Roaming\Maxon\Maxon Cinema 4D 2024_A5DBFF93\plugins\CV-Swim\CV-Swim\CV-SwIm.pypv", line 615, in AddToQuickStorage
TypeError:argument 1 must be c4d.Vector4d, not ColorA64
"

Found this buried in the Maxon FAQ page:
https://support.maxon.net/hc/en-us/articles/9057076364572-Why-is-the-CV-Toolbox-not-showing-up-under-my-Extensions-menu-after-updating-to-Cinema-4D-2023-2-and-later-

Thanks for the kind feedback, Alex.

It is, as before, one of my favorite themes and any kind of projection! I love this work.

A complete projector simulation might also include the F/value of the used lens.
This always goes hand in hand with the surface it is screened on.

If the projector is not axial to the screen, that might require some extra care.

In my color training (Color Grading and Color Science) over the years, I learned that Cinema Theater has 48 Nits*, whereas HDR TV screens are between 600 and 4000 Nits, with an average of 1000 Nits. Yet the *Theater often looks more impressive and tends to increase slightly to cover the HDR dynamic.
The main reason is that the larger the screen and the darker the room, the more the impression is given that it is very bright. That calculation might not find its way into the plug-in.

I write about that, as often a precedent is put into one's contract, and the reality might be different; for those cases, I would like to share my expectation management here.

I hope you have a great Holiday Season and enough exciting challenges with your work.

Good luck, Dutchbird.

I made a feature request. So fingers crossed, something will happen.

The option above is a preview; I'm unsure if anything will be faster.

I checked on the official Open VDB site for Preview; I found nothing.

All the best

@regular-river I can't find that plugin. If you're looking, for CV-Splines, you can download it here: https://www.cineversity.com/vidplaytut/cv-splines_hanging_wires_chains_and_arches_with_cv-splines_3.0

Hi truth-dream,

The idea of this forum is about the content provided by Maxon.

Please check programming suggestions or questions in the Developer-Café.
https://plugincafe.maxon.net/
This is the correct place for it.

I feel somewhat uncomfortable having code here, in general, for various reasons.
The moderator of the Plugin Café is better suited for this.

All the best