CINEVERSITY

I had asked you for a moment to wait, as there were some indicators that needed to be cleared. I mentioned that was not about how to answer the technical part.

Opening a new thread instead, is not helping.

Perhaps ask via Maxon Training: [email protected]

Do you have a website?

Sorry for all the trouble.

The tech is not the problem.
We at Maxon have other concerns.
Until we can't clear those…

Thanks for the reply, RemoGambacciani,

Perhaps this might work
CV4_2024_drs_23_MGdc_11.c4d

Please note that the information after the Connect Object is limited, as you have noticed.
Since the Connect object reproduces everything, individual ID numbers are lost.

On the other hand, if a second cloner produces the data or a connected object, it will be nearly the same work. Eventually, there is a way to create the initial setup via a matrix object and inherit that then to Many Cloner objects.
However, it isn't easy to get an example that does not represent hints as to why the Connect object is needed.

All the best

Thanks for the reply, raise-trade, and for taking the time.

My best wishes for your project.

Hi RemoGambacciani,

Yes, never update during production if there are no serious and urgent reasons.

In my experience, a new version, like 2023 being old and 2024 being new, the new version creates its folder and has all needed parts in the separate new folders.
However, memories and knowledge are lovely to have, but things change, which means this is a valid question.

Here is the exploration with my little side iMac. I used the Maxon App and updated it to 2024, while the 2023 was the latest on this Mac. (I have no Windows machine here.
I started 2024 after that and 2023 simultaneously, both are running. I typically download my versions to handle my different computers and licenses without repeating downloads.

All is fine here. Since you are in a project, perhaps include the 2023 into your daily backup first. Just to feel 100% safe.

All the best

Hi Shawn,

Please test what your configuration is getting, in terms of speed, with the current version; for example, the CPU has improved with over 12 cores.

Besides, the whole core has been heavily rewritten to make it faster than ever.

What the future of the old Hardware Viewport is - I can't tell (NDA), but I think the signs of what will happen are pretty large in the new announcements.

I do not understand myself here as a salesperson, nor am I supposed to be tech support; sadly, I have no idea what else to tell other than to test the new version and compare. Perhaps that is already the answer.

Please note that you must compare equal qualities when discussing render times. Se the GI to off, for example, or the samples in Redshift to 0.1, Then recheck the render times.

All the best

You're very welcome, Pitchi. 🙂

Thanks for taking the time.

My best wishes

You're very welcome, education-common!

My best wishes for your project.

My short answer is: don't. This rig is designed for Mixamo, not to have any other rig, that has many more elements, been used with it. You might explore to set up several arms during the initial set up, but it wouldn't be a Mixamo compatible rig anymore.

The medium-length answer is: (Start at: 00:34:36)
I would suggest tuning in tomorrow, Monday, at 09:00 a.m. Pacific time and asking this exact question.
https://www.youtube.com/watch?v=j-VGxPgLE0c
( I QA and Timestamp the shows, so I'm super curious about the replies you get. Learning rigging should be based on as many sources as possible.)

The long reply is this link below:
To get an idea about the inner workings, there is so much in these templates that I would even start to explore to hack into its structure.
If you would like to change the template, that is explained in a more extended series and is a little bit old (interface.
https://www.cineversity.com/vidplaylist/creating_a_custom_template/
When you see how much instructional data is provided, I have no idea how to communicate this in a single thread, nor would I know how to communicate about the Python content. In other words, changing this template or structure is not my advice.

If you explore the rig, you will find that it is not one rig; it is pretty much three rigs, plus the eventually connected Mixamo from an external source.
This means the whole setup is based on four rigs; otherwise, why use the Mixamo if you don't connect it to the external rig?
You show me in the picture that you have placed just a few joints somewhere. Those will have minimal impact, as nothing previously used (external, IK, FK, nor bind) will provide them with individual information.
To call it a Mixamo rig at that point would be false.

My suggestion: make the rig edible (Character Icon active, press the C key) and place the extra joints where you like to have them.
The setup as IK/FK and Controllers can follow the same way as the default joints. Set the constraints to the IK/FK options are given as for the rest of the rig.
Weight the extra elements to the mesh, and perhaps smooth areas where previous and new weight needs to be defined.
With an Animation System, Animation Clips, that shows the same Hierarchy, it is easy to mix animation sequences.

All of that said, based on the information I got, while images have nearly no information as a project file would have, just for future questions. Thank you.

My best wishes for your project

Thank you very much, Pim,

This feels like sitting in a cinema theater. Love it.

Very nice of you to take the time!

My best wishes for your project

Hi appointment-insect,

Thanks for the demo.

Here is a scene file that allows us to see a fresh start; I have placed a Mesh Object to it for precise comparison. When this works, we can take a look deeper. Use a new scene for new tests.

CV4_2023_drs_23_SIsc_01.c4d

I would just start over; I have tested this scene with 2023.1 and 2023.2, just in case. The pale-greenish shape should be the same. The Triangle is just another check.

Screen Shot 2023-09-09 at 10.28.58 PM.jpg

Let me know if that works for you.

All the best

P.S.: I hope an affordable device for your DJI drone will be soon available. (I have the same problem, but my pilot license needs renewal, so I have no time pressure currently.)

Hi background-permit,

Since I wrote in a forum, I have to explain it on that level, not an evaluation of anyone's knowledge.

Ani polygon object has an axis; this Axis is the "sub-world" for the points.
Points are typically not connected to the World space, and it would have many problems if they were.

If an object is only moved by Axis, the information of the points (e.g., position) stays the same.

.
To work around this, you need a copy of that object and have it not moved. You can place its Axis to the World Axis, but it can be anywhere, as long as it is not moving, while the target is purely moving points. This is how I understand your target. Now, the object that moves in a hierarchy moves the object and the points. This new position can be transferred to a static copy of that exact mesh.
Now, the Axis stays, but the points are moving. This new object can now be cached or used for PLA (Point Level Animation).

After caching, switch the XPresso off.

Example

CV4_2023_drs_23_CApa_01.c4d

Please note that I do not have your file here, and any answer might be flawed, as nothing beats a project file in a forum-based communication.

All the best

Hi sweet-boyfriend, You're very welcome.

I hope you get what you need over there.

My best wishes

Thanks for taking the time to reply, horse-end!

My best wishes for your project.

You're very welcome, entry-newspaper.

Let me know if you encounter any obstacles.

Cheers

You're very welcome, nothing-tennis.

Have a great day.

You're welcome, Anton Kovalevsky.

Some additional notes: Is it somehow possible to match object sizes as well? The tick "scale" doesnt't have any sense as all obects have scale = 1 by default (except for imported models). The only solution is manually Copy-paste numbers?

You're very welcome, deal-blinet.

Have a great long weekend