@Dr-Sassi

Okay:

1. Doesn't change anything.
2. Also doesn't change, regardless of the project.
3. This does work. More, below:

So, if I create a new keyframe (regardless of the property) it greys out those tools. But the moment I move the keyframe bezier handle, it immediately brings those tools to life. Or, like you suggested, by clicking on the "undock a copy" of the timeline.

But clearly, something is wrong. This exact same thing happens on both my M1 Ultra and M4 Max.
Is it possible that I did something weird when I customized my pallets? But even then, I set each machine up, independent of the other. In other words, I didn't copy and reuse the custom layout prefs.

@Dr-Sassi

Ah, 500-pixels, thanks. And thanks for trying this on your end.

Here's my screen grab:

Just to make sure I'm describing this correctly, I can manipulate the keyframe / handle, it's all those other features (outlined in red) which don't become active, as they should. So, if I quickly highlight a keyframe, and want to zero the handle angle, I'm unable to do so.


I'm trying to load a 64k 960x540 jpeg. Something is wrong here...

Hi Dr. Sassi,

I'm wondering whether you can check on your M-Series Mac to see whether you can replicate an issue I've found with C4D 2026.
Specifically, in my timeline in F-Curve mode, when I select a keyframe handle, I'm NOT able to access any of the timeline tools. Quite the issue, to say the least.

I've included a screen cap, where you can see how all of my icons are greyed-out, despite having the keyframe selected.
For what it's worth, I've included the basic project.

This is happening on BOTH by M1 Ultra, and M4 Max MBP - each running C4D 2026 and OS 15.7.

Thank you!

2026 timeline bug.c4d

P.S. Something seems to be wrong with the image host here. I keep trying to post a jpeg screen cap (only 1920x1080) and I keep being told that the "dimensions are too big".

Thanks, Dr. Sassi. I'll likely do just that. But doesn't it seem odd, that it would open an older version? I've never before seen that. No idea if that's some glitch in Cinema, or more likely the Mac OS?

I just installed C4D 2026. It's on a machine with 2025 and 2023.
Oddly, when I double-clicked on a test project which had just been saved from 2026 (with C4D 2026 already being open, no less!) 2025 opened that file, instead.

Any idea why that would occur? This is on my M1 Ultra, running 15.7 Sequoia.

Thank you, Dr. Sassi.
I'll study these two projects, so I can incorporate the best method into the final project.
Have a pleasant weekend.

Morning,

Please see attached project and (very general) example[radial mograph issue reference.

I'm creating a radial design with Mograph, and want to add randomness to the "tics".
But I'm not sure how to go about this, because if I add the "random" effector to the primary Cloner Object, it affects each subsequently cloned line identically. But if I apply the random to the secondary cloner object, the whole thing goes nuts.

I'm sure I'm just missing a simple setting or procedure, but it must be too early for my brain to handle this, yet.

Thanks!

radial mograph issue.c4d

Hey, so sorry, Dr. Sassi. My original post is nearly worthlessly vague. I'll see whether I can find a minute to create a simpler proxy scene, so you can see precisely what I'm trying to accomplish.
But quickly, it's an animated effect, whereby I'm sort of turning the CAD part into a liquid-type shape, ultimately resolving in the shape of the original CAD piece. So the UV transfer has to deal with a frame-by-frame evolution of the volume / mesh builder.
More to come...

I'm working on a possible effect, where I'm building on a CAD part, via the volume builder and mesher.
All fine!
However, the original CAD part is already carefully UVW mapped. I've found that the "Transfer" function works really well, transferring those original UV coordinates to the meshed object.
However...it's exceptionally slow / laggy. So much so, that I'm not sure I'd want to risk trying to render something like this.

I can't exaclty post the actual project, being that it has client CAD at its core.

But in general, is it expected that transferring UV's from a simple shape, to a more complex meshed shape, will slow down?
(I kind of figure it should...)

Thanks!