MighT

As the project file I posted demonstrates, there is no need for a second object.

Albeit tedious, you could also use the Structure Manager in UVWs mode to adjust points manually.

It is definitely possible. I just had a look at an old project file and it worked back then and still works in S26. But I have to admit, I have no idea anymore, how I did it back then. I tried to compare my settings with yours, unfortunately I did not find the magic checkbox. As I have no time to revive my memories (if that is at all possible), I instead post a stripped down version of my old project. Good luck in finding the magic option... SnT_Transparency_Example_based_on_#11.c4d

My last post was upon your second screenshot. I have not much else to add, sorry.

I'm not a modeling expert, so I should probably keep my mouth shut. But I'd like to learn, too, so I just give it a shot as long as nobody more knowledgable has replied. From your screenshots, I'm a bit confused and the project file doesn't seem to contain the cut version. Maybe I'm going in the wrong direction... a) Your backside screenshot looks as if you'd want to adjust the Maximum Angle for Preserve Groups before extruding. b) Then I'd do a extrude with zero offset and afterwards use the Normal Move tool. As I said, if the result is bogus, just ignore my post and wait for some of the pros...

@Cairyn+1 for mentioning Buck Rogers @srek+1 for mentioning Perry Rhodan And now guys, please use this thread as a seed to provide me with the ultimate Perry Rhodan series. At least a single cycle, I don't wan to appear greedy.

This question has been asked multiple times in here already. So I'll just list a few options, for the links use the forum search or Google. Maxon's Dev Blog can be a good starting point to find the most important links to resources provided by Maxon. Namely: The Python SDK itself. Maxon has a growing collection of examples to be found on GitHub and documentation is slowly improving, too. Maxon's Plugin Café for free developer support. Cairyn, member of this very forum has a quite elaborate Python course/tutorial on his Patreon. Maxon's Cineversity also has a bunch of resources. One can also book me for 1:1 training/introduction. And this is certainly only the beginning from the top of my head. Use the search and you'll find more.

I do not even know, what FOLDALL is 😉 I doubt, you are on the right track. Here's a small example project: test_OM_lock_fold_unfold.c4d Attached to the Null object you find a Python tag. The Python tag has a user data parameter of type boolean, a checkbox. Depending on this checkbox the parent object of the Python tag gets folded or unfolded. As there can be up to four Object Managers, the tag folds/unfolds in all of them. The code is rather simple, but if you haven't scripted C4D before, it's certainly not obvious, how to do it. First line in main() reads the user data checkbox parameter. Then it gets the parent object of the tag itself. And the final four lines set/reset the "fold bit" per Object Manager. You can move/copy the tag around to use it on different objects.

You could put all children on a layer and set the layer to be hidden in OM. One could also write a small Python tag to force the Null object folded/unfolded.

You can PM me, I expect fair payment on "pay what you want" basis.

I love it, if such tools have a certain schizophrenic touch to them... What is the GPU load? I guess it is idling at zero percent, while C4D puts it under 97 percent load? Priceless! Anyway, lets hope the other values are more solid (recommendation CPU-Z and GPU-Z are really good, proven tools. There you also get graphs showing the temporal development of temperature). Then I'd say, nothing looking critical. Instead the GPU seems to be working full steam on whatever C4D/Redshift threw at it. Question remains, why is it so much slower than your laptop? The system seems not even sweating. With all caution, just from looking at these screenshots and assuming they are taken under reasonable conditions and NZXT Cam showing values roughly depicting reality, then I'd say, you are back to looking for reasons in software. Drivers, incompatibilities between drivers and installed Redshift version, (I know, you excluded this option) different render settings. I can't be of much help with this. Maybe some Redshift gurus here on the forum. Otherwise I'd probably ask Redshift and Maxon directly via their respective support channels.

You posted screenshots of idle conditions (at least to me it looks like so). More interesting is the situation under load. More ideal situation after some duration of load, lets say 30 seconds or a minute. Temperatures to rise under load is normal, it's the side effect of working (similar to us humans). The questions are, how much to they rise, where do they max out and why. Maybe I should explain, what we mean by throttling. Your CPU (pretty much same for GPU) is designed to do work at a given speed (clock frequency), the cooling system should be designed to dissipate the heat resulting from such work. If the cooling system is not able to do so (either designed too small, some assembly error or hardware defect (e.g. fan no longer working)) and therefore temperatures rising above a certain level, then, in order to protect itself, the CPU will start to lower its clock frequency (that's what we call throttling), so it will do less work and therefore create less heat. If everything is ok, under load one will see the temperature maxing out at some non-critical level, while the clock frequencies are in the range the CPU was designed to work in (oversimplified, it's all a bit more complicated due to power limits, boost mechanisms and what not). In the bad case, the temperatures under load will (hopefully) max out as well, but a) most likely on a much higher level and b) while the CPU clock frequency has dropped well below the value the CPU was designed for. It then runs throttled... Edit: Post was written before the second screenshot got posted.

To be honest, I didn't download the project file. 28MB for a few low-poly poly objects looked a bit over the top for me. But I'd suspect those Normal tags to be the culprit.

What are the temperatures in the new PC? Maybe it's constantly throttling? You could use CPU-Z and GPU-Z to check. These would also show you frequencies CPU and GPU are running at.

DID YOU CALL ME BLIND?!?!? 😉 Just kidding. I actually checked the list before posting and did not notice it is already available. Learned something myself. Actually two things. a) I'm blind (I still don't see it on the list). b) There's already such Token. I've had worse days than this.

It would be quite easy to implement such Tokens. Yet, I think, as Cineversity already has a collection of nice Tokens, there would be a good place to have it added. So, maybe you could try to convince them to quickly add such. If they deny your request, ping me again.

@bezoThanks for your kind words. Even more so, after you had been hit hard right at the start... I personally apologize for your bad onboarding experience and I can not thank you enough for making me aware of this bug.

We have just released an update to version 1.3. This update fixes the crash found by Bezo earlier in this thread. We definitely recommend every customer to update to this release (as always, update is free). The bug was present in all previously released versions and also, due to extreme development craftmenship, hit all Cinema 4D versions, the plugin got released for. SORRY!!! Existing customers will be notified by email and in Asset Juggler Discord. The demo version can also be used to update. Changes (more details in included PDF documentation): Fixed: Crash bug (in versions 1.0 to 1.2) Fixed: Border of popup dialogs was not shown in Cinema 4D S26

Bezo indeed found a pretty worrying, reproducible crash bug, related to Open Recent project. I will try to find the cause and release an update as soon as possible.

Sounds like, you can actually reproduce it? A video could be nice (though I doubt, you do anything unusual. And there shouldn't be anything unusual causing a crash anyway...). Even nicer it would be to get my hands on the crash log. But I don't want to cause you any more trouble. So I take what I can get. Hm, I doubt it, the demo only restricts the number of combinations, when baking. And in S26 I also used the demo version for testing.

I can not reproduce a crash with 25.117, either. I loaded a whole bunch of different test scenes (including the above one) without any issues. During the entire development I did not experience a single crash. So, I am extremely worried about yours.

The Count sliders adjust to the number of possible combinations. To be precise, this is only in one direction, if there are less combinations possible (defined by the Asset Groups and their contents), the count will be lowered. But it will not automatically increase again, as I feel this could terribly slow down things depending on number and complexity of assets. The manual recommends to roughly set up the Asset Groups, first. Provide Asset Juggler with something to play with. Then, while refining your setup, playing with chances, Rules and what not, it's the Preview Count slider, you need to care about. Set it to a value, everything is still fluent on your system (which for simple setups should easily be it's max value). Only before generating and baking you need to set the main count to the number of combinations you really want to bake.

Select the Asset Group you want to override, where it says "No Group". Up the number of combinations shown in Live Preview (where Count is set to 1, currently). Most likely you want to click the "Lock None at zero chance for all groups" button. The second from right in the title bar of the "Asset Groups" tab. But I'm more interested in the crash. Is that reproducible? I still had 25.115 running here. Currently installing 25.117 to double check. Though nothing in Maxon's changelog looks suspicious of introducing problems to me.

Whut?!?!?! Which version of C4D are you in? Not that it should matter, but you are the first to report a crash. And given it's written in Python, this should be an extremely unlikely scenario anyway.

An Asset Group of type "Material" can only set the material of one object, which belongs to this Asset Group. It's basically a "1 object/n materials" group. But you want to override the material objects belonging to another Asset Group, that's what the "Material Override" group type is for. So, in your project, simply switch the second Asset Group from "Material" to "Material Override" and select the first Asset Group.