CINEVERSITY

Thank you very much, Harry, for the ticket.
I'm not running the Site Issue forum, and I have no access to customer data. We take privacy here pretty seriously, way above what the law asks us to do. I wouldn't want to have access even.
So, I do not check here often in the Site issue forum.

The simple answer is that generators, like the SDD, generate new Geometry, and that doesn't include any MoGraph ID.

An alternative could be:
CV4_2025_drs_25_RSci_01.c4d
Enjoy your weekend

Hi Max M.,

I'm happy to look into it, but I have nothing to look into right now.

Images may contain some information, but looking at an image to identify what's wrong insight a project setup can lead to a list of questions. Over the decades, it has become clear that this is not an effective way to work.

As usual, images are supportive sometimes, but I need a Project file.

An empty file, such as a disc, and the material will suffice, typically below 1MB, and can be attached here as a C4D file directly.

Cloud services used here include Dropbox, Google, WeTransfer, Adobe, and Apple. Files were uploaded without compression, and the URL was pasted directly into the text without an HTML wrapper. For security reasons, I do not touch any other options.

However, I would create those patterns in Photoshop; hence, I currently have no idea how parametric this can be.

All the best

Hi high-spite,

Thanks for the feedback. Like with textures, where the suggestion is to have, at least, 1.5 times the resolution, to not noticeably lower the quality if the render (the 1.5 here means if the camera comes close, that this ratio is given, as it is nearly impossible with shaped objects to match each pixel from texture to render. Similar to that is the size of an object, since we have a very small one, typically with Particles. Here, the particle has a shape, which needs to "translated into the final pixel raster.

Like with any pixel movement that deviates from the next pixel position, changes that are longer or shorter will lower the quality. Lens distortion correction is a type of movement that affects quality.

The post effects can only "see" the scene through the rendering (the raster of the resolution), without any knowledge of the actual scene.

The Nyquist Frequency is a good way to explain it. Living in a cave and emerging only every 24 hours will give the impression that it is always night (or day, etc.).

Another point is that objects, especially particles, move, plus the camera might add screen movement for them as well. So they move through that raster of the final image. A typical example is Analog audio sampled into digital, which can lead to many problems if the resolution is not high enough.

But I get carried away here. I think the idea is clear, and I apologize for going on about it, but perhaps a few readers might find this supportive to know.

Cheers

Hi fordmar,

The slow down is typically done to produce 30fps (29.97) with the same duration as the 24fps (23.976), perhaps 25fps for different TV specifications. Your idea sounds different.

Either way, slowing down is not as simple as it is often "sold". It works great on high-speed footage used at low fps, where things are already slower. Typically Motion analysis is applied. Even then, some things can and will typically cause problems. (Crossing items, transparency, or patterns on reflective objects.

The Time stretch in Ae also needs an adjustment in the Frame-Blending.

With your relatively fast-moving content, the problems of this technique become very apparent.

Please render the sequence of the file below. Since it is an image sequence, set the sequence to any FPS you start with in Ae. Leave the C4D project settings, so I can see more what your results are. Then set up your slowdown workflow.
I hope my project setup can effectively demonstrate what's happening.
CV4_2025_drs_25_RStr_01.c4d
The quality is set to low, so I can see noise and the rendering is fast. PNG is typically not my format, but you mentioned it.

Thanks for the video. When you watch the second part of your link, go frame by frame with the "," or "." key, and you'll see that it repeats A-B-C-D-D each time. Here is the reason for the "jitter" as you call it. Even if you use a blend A-B-C-D-"D/A", the movement will stop because there is no progress added on D/A.
Screenshot 2025-07-31.jpg
Blend> Pixel Motion (Compare the refections, they don't match the texture, just to name one example)

To perfectly "time stretch" each frame of the new sequence needs to change, which is often not possible.

Do I get your problem so far? Please let me know. Then we can take a look at what would work better. The question of Motion Blur might be a key point to render a higher number of frames…

Chhers

Thank you very much for the feedback, atomician!

My best wishes for your project!

Hi charity-chance,

I would suggest using the Preferences: Import and switching to Standard Physical, while leaving terms like trash out of this forum. OK!? Thank you.
https://help.maxon.net/c4d/2025/en-us/Default.htm#html/PREFSIMEXPORT-PREF_IMEXPORT_MAIN_GROUP.html#PREF_IMEXPORT_NODESPACE

Preferences> Import> Target
Screenshot 2025-07-30 at 11.18.08 AM.jpg

I tested this with a current Mixamo FBX, and it works just fine.

Take care.

Sorry, I checked on the Liquids, Gloria,

The Speed of the particle is pretty high. Perhaps start with 75.

Place a Collider Modifier (from the particle menu) under the particle Folder.

• In the Attribute Manager> Mode> Scene> Simulation> Particles> Substeps is set to 1.0, explore, e.g., 60, then dial down.

The Substeps check if there is a particle that might collide. If that number is higher, it checks more often.

https://help.maxon.net/c4d/2025/en-us/Default.htm#html/OPBDSCENE-PBDSCENE_FP_GROUP.html#PBDSCENE_FP_SUBSTEPS

I hope that helps. I don't have a fast enough computer to fine-tune this.

I call it a day now. (…past midnight)

My best wishes

Thank you very much, Gloria! Very kind of you!

Thank you for your patience with my moderator's wishes about structure. Very much appreciated.

Whenever you have any questions, please feel free to just ask. I'm happy to look into it.

My best wishes for your project!

Thank you very much, AlexC.,

For the reply and feedback.

If you need an alternative to this at any time, please let me know.

Enjoy

Thank you very much,

I mentioned the time here that I tried to see all (?) variables in this "game", and explored a few. (Like placing the position change into a Color Vertex Map, while using a range mapper to tame the results, then using this Color Vertex Map to drive the Displacement. The model exploded here and there 😉

Time is one part of the game, but my main idea is that a problem comes back until it is solved. Sadly, with the forums 1-3, around 15+ years have passed. Since things change, that is not a problem, as more experience will lead to different outcomes.

However, sometimes I can't solve things, and the developers have to do it inside the code and provide a solution, whereby I can only share a process or workaround. The idea of having it solved in the app sounds to me more teamwork-friendly.

If you have any XPresso ideas, but something is missing, perhaps a little piece, I'm happy to look into it. Often, questions like yours need some "storage" to keep data for a moment. In the past, I used a copy of the model; these days, I add the Color Vertex Map into the mix. Perhaps the Joints can be a good driver in this case…

Anyway, sorry for the longer text, but your kind reply made my (Sun-)day. Thank you for that.

Enjoy!

THankss for the reply, steal-shelter,

Fingers crossed it provides what you like to have.

Thank you for the question!

Cheers

Hi philosophy-chemical,

Please have a look here:
https://discussions.apple.com/thread/255762577?sortBy=rank&page=1
Add your vote please.

In my private opinion, it seems like something Apple needs to address. Yes, there could be a workaround, but that might be eliminated when Apple fixes it. Meaning, all previews set up with an app based solution might miss the images then. This puts every non-Apple developer in a difficult position.

Yes, having no solution after so many months is annoying; I agree.

My best wishes.

Hi nopopoch,

Thank you for the file and the care in the file.

To have two objects "cap" to "cap" connected via a Connector is relatively close, not like superglue. Perhaps not what you expect, at least that this will get anywhere near what I get from the text bubbles above them.
Suppose they were 100% like a belt, a stretching object would have an influence on the connected part. Which needs to go in both directions, and enable a Feedback loop. That is my observation so far. Below are a few examples, with or without animation. Please mess around with them to see how some parameters influence the results. Yes, the documentation could have a table with all combinations and interaction results.
CV4_2025_drs_25_SIct_02.c4d
CV4_2025_drs_25_SIct_03.c4d
CV4_2025_drs_25_SIct_01.c4d

Documentation
https://help.maxon.net/c4d/2025/en-us/Default.htm#html/TPBDCONSTRAINT.html?TocPath=Simulate%2520Menu%257CThe%2520Simulation%2520System%257CThe%2520various%2520Simulation%2520tags%257CConnector%2520Tag%257C_____0

It tells, like for the Rigid Body, what to expect with the Connector.

The question would be, why split something that needs to work anyway, like one object?

Here is an alternative, just joints turned into Dynamic via IK tag, since your file showed what you like to have, but no context, this might work, or is completely off.
CV4_2025_drs_25_CAdy_01.c4d

I'm not sure if I was of any help here; a little bit more context might help me.

All the best

Thank you very much for your reply, atomician.

My best wishes for your project.

You're very welcome, ne.____.il,

Enjoy your project