Hi vincent.hardy,

Thanks for exploring it, and yes, as mentioned, memory can go up (store a value for every point). I think it is always good to know some more options.

Did I get the same scene again? I checked, and nothing was hidden via layers or Takes.

Code and Python, thanks for keeping it out of the forum. Whenever something is posted with code, I will not hesitate to take care of it. Code is powerful, and that makes it dangerous. Thanks for understanding!

According to the manual's comment, "alpha" in MoGraph is slightly smaller with Fields, but I hope that has not affected anything else. Please explore what information could be used.

Since Colors can be created via Ramp based on gray values, it is easy to see that R, G, and B (interpreted as Linear) could be used as three independent information channels — one drive gray values (for a Ramp), the next the alpha information, and a third something else.

If you find yourself limited and have an idea, please always use the "Share Your Ideas" here:
https://www.maxon.net/en/support-center

My best wishes for your project

View Tutorial
Tag: Cinema 4D | null

Thank you for taking the time to report your issue with this Cineversity tutorial.
We apologize that you encountered an obstacle with the material. We’ve created this template to help you clarify the issue you are having so we can assist you more quickly.

What's the specific issue you are having?

• Playback problem. If so, please refer to the FAQ: FAQ: Video's Aren't Working Correctly.
• Tutorial workflow problem or clarification.
• Version compatibility problem/UI changes.
• Other

Please include a timestamp (where in the video the problem occurs) if applicable.

What are the steps to replicate the problem?
What steps are you taking that seem to cause the problem?
What version of the software are you using?
Any and all info is helpful. Thank you.

If the question is not directly related to the tutorial, please refer to the Q&A forum

View Tutorial
Tag: Trapcode | null

Thank you for taking the time to report your issue with this Cineversity tutorial.
We apologize that you encountered an obstacle with the material. We’ve created this template to help you clarify the issue you are having so we can assist you more quickly.

What's the specific issue you are having?

• Playback problem. If so, please refer to the FAQ: FAQ: Video's Aren't Working Correctly.
• Tutorial workflow problem or clarification.
• Version compatibility problem/UI changes.
• Other

Please include a timestamp (where in the video the problem occurs) if applicable.

What are the steps to replicate the problem?
What steps are you taking that seem to cause the problem?
What version of the software are you using?
Any and all info is helpful. Thank you.

If the question is not directly related to the tutorial, please refer to the Q&A forum

Thank you, erwin, (I write it as you do, with an e instead of an E).

When I activated the Hair the first time, everything stopped. (M1 Max)
So I dialed it down. Switch the Dynamics (Hair) off for initial tests.

Caching will store only the Guides, not the Hair. Hair, in this case, is the interpolation among all the Guides. So, Caching helps, but not that much.

If you can live without Dynamic and Redshift for this, you can use Fur, which was created for that effect, to cover large furry areas.

All the best

P.S.: You never bother, if that was even meant in a serious way. Please feel always free to ask.

Hi erwin,

Start with less hair and segments.

I have one of the smaller M1 here, so I can't tell, nor do I have the time to wait for that kind of exploring with high values.(Sorry)

All the best

Hi tower-clue,

Please open a new thread. Follow-up questions, even similar ones, will render the forum less readable.
Think of the initial poster comes back with a question of the initial problem, it might be hard to find.

There is always an option to link threads if they become related.

CV4_2025_drs_MGfe_01.c4d
CV4_2025_drs_MGfe_02.c4d
Any questions about this, please in a new thread.

Thank you.

Hi contribution-stage,

I would not think of anything that would cause less effort than your setup, while not using code for MoGraph. I have suggested similar setups in the past, and so far, I have not gotten negative feedback on them.

However, here is an alternative:
CV_2025_drs_25_MGwv_01.c4d
Please test this in your setup carefully, as the Vertex maps will store a value for every point, which can get heavy.

With Python, you are between chairs here, as this forum is strictly code-free for security reasons. The forum for Python is here:
https://developers.maxon.net/forum/

When I get your full setup (not part of the file above, and thanks for leaving the code out!), then my suggestion would be to use the Python Effector to set the RGB and Weight (Alpha in your case) and use the data you have to influence the value that you need.
Less elements, but if that is less work - you pick.

My best wishes

Thank you very much, MaverickMongoose!

I also used the little Planes, with a selection of edges, to have an Edge to Spline. Which I then merged and connected.

I wish you lots of success with your project.

View Tutorial
Tag: Cinema 4D | null, Redshift | null

Thank you for taking the time to report your issue with this Cineversity tutorial.
We apologize that you encountered an obstacle with the material. We’ve created this template to help you clarify the issue you are having so we can assist you more quickly.

What's the specific issue you are having?

• Playback problem. If so, please refer to the FAQ: FAQ: Video's Aren't Working Correctly.
• Tutorial workflow problem or clarification.
• Version compatibility problem/UI changes.
• Other

Please include a timestamp (where in the video the problem occurs) if applicable.

What are the steps to replicate the problem?
What steps are you taking that seem to cause the problem?
What version of the software are you using?
Any and all info is helpful. Thank you.

If the question is not directly related to the tutorial, please refer to the Q&A forum

Summary:

Why correct "set survey data" is crucial,
while often completely ignored or misunderstood.

Here is a 17mm and 90mm focal length comparison that creates the same result, while the object has a different depth.

CV4_2025_drs_25_CMzm_11.c4d

In other words, if little information is available, the resulting idea of what camera was used to create one or the other render with identical Perspective lines will produce complete nonsense.
Hence my long discussion.

Click to activate one or the other camera. I have color-coded both. It is easy to see why no information will lead to weird ideas about setup.

I have done my first camera match over 30 years ago, for a larger architecture project of mine, in Photoshop 2.5. , Since then I have done a lot of those.

Enjoy