MJV

The simple solution here would be an animated boolean to reveal the chair, a very easy process, and the cushion animation should be pretty easy as well using C4D's new (or even the old) soft body dynamics. As far as the T-1000 liquid terminator bit at the beginning is concerned, I would just omit that altogether.

What is a sun texture?

Like the sound of vinyl, record covers, double albums and mixtapes.

Yes. It's always been possible with Mograph but, without the auto conforming. which is the main great innovation here.👍

Thank you for that comprehensive analysis. Do you know if when I import SOPS into LOPS to render with Karma, if literally the entire scene is being cached/written to my hard drive in USD? I saw and read some clues that say yes, but it seems so inefficient.

I think every Windows user who ever used Cinema wants to know this. 😅 It's not possible as far as I've ever heard.

Many of the previously missing icons are now present, but some are still missing. In my layout, the following are missing: Wireframe, Isoparms, (those two bother me the most) Skeleton, Display Filter, Save as Startup Layout, Close Project, Close all Projects, Go to First Marker, Go to Previous Marker, Go to Next Marker, Go to Last Marker (To be fair I never use those marker buttons anyway and should remove them from my layout) Use as Render View, Go to First Key, Go to Last Key, Lock Camera Pivot, Calculate FPS, Frame Project Settings, Frame Preview Range, Go to Start, Got to End, Frame Range, 50%, 200%, Show Text, Show Line, Pixel Aspect, Vertical Tags, Object Information, Convert Object Selection to XRefs, Unfold Selection, Fold Selection. Wow I wasn't expecting this list to be so long, but to be fair again many of those last ones I listed I use text menus only and I just turned on the icons to see if they were there or not.

Even if one accepts that were true, I don't look to NASA when considering transportation options.

There is nothing very special about how Solaris can place or interact with lights, and as I said before, you would have to leave LOPS if you actually wanted to do very special things with lights, such as animate their positions or copy them to points.

There is nothing special about lights in Solaris. Basically just some fancy looking sliders and takes. If Solaris was a plugin for C4D the developer would go bankrupt. It's mostly a bunch of marketing BS, and if you need to do really complicated light setups where the light positions are animated and whatnot, you will have to do that in another context and import it into LOPS. USD is just another reference and file interchange system which Solaris just helps facilitate, but is overkill for what most people need. Look dev is a marketing term for takes but from from what I've seen so far Solaris is not very good at, as it's mostly focused on static product visualization.

Now explain why anyone needs USD scenes in productions or what Look Development is. I'll wait.

In that case I would check to make sure that the render settings are really the same for both. RS has been incrementally adding some incredibly complicated and poorly documented ACES color space workflows in recent versions with differences in color space and results depending in what context or viewer you are rendering in, so that could have some impact as well I guess. If you are absolutely certain that the render settings are exactly the same and the results you are getting are pixel perfect the same, then it is likely a bug and should be reported to Maxon.

Of course! 🤣 What was I thinking

I've spent almost a year now trying to figure this out and there is no end to it and you won't find or get any answers about it from searching. What you will hear the minute you start doing something in one network is you really should be doing it in another network. You're doing something in LOPS? You should be in SOPS. Working in SOPS? You should be in LOPS. Trying out somethings in DOPS? You should really be doing it in SOPS. Trying something in SOPS? You should actually be doing it in DOPS. Trying to parent something are you? You should be doing that in OBJ, unless you need to do it in SOPS, or LOPS, or DOPS, depending on why you need to do that. Need a camera or lighting in your scene? That's what LOPS is for, unless you need to parent or animate any of those things, in which case you should do it in SOPS and reimport into LOPS, unless you want slick looking sliders for your lights, in which case you must go back and do them in LOPS, as long as their positions don't need to be animated, but if they do maybe you can drop into a SOP Create, but it's a work in progress but don't worry it will get there someday. Trying to stay in one context or another, you should really be using each for its strengths and bouncing back and forth. Try doing that and then you will be told it's a waste of time. Why does LOPS even exist? No one knows but a lot of people have their theories. For one thing it's the only context in which you can render with Houdini's new render engine Karma. Why does Karma only render in LOPS? No one knows.

Are you rendering the first frame of the animation in the picture viewer or a later frame. If a later frame, that would explain the reason for being slower.

I think he probably means Octane, because you hear that alot but my personal experience is very different. I absolutely love Octane, except for their lousy support, and have never had issues with stability, regardless of what I ever threw at it

For the last bit try enter model mode, select all objects, enable axis tool and then zero the rotations in the coordinates manager. Thereafter all the objects should have the same rotation provided they aren't children of different objects.

View center command.

Center object to parent command?

Does $20 even pay for the electricity it took to render the video? You should get an amount you feel good about or not give it to them at all.

There is no such option.

The thing to know about Cinema vs Houdini is that Cinema was designed from the ground up to be easy and intuitive for the non technically minded artist to use while Houdini was designed by technical engineers for technical engineers. In recent years Cinema has been teasing scene nodes in an attempt to attract Houdini type users while maintaining its reputation as an artist friendly tool, while Houdini has been trying to simplify itself to attract more Cinema type users while maintaining its reputation as a technical powerhouse. Houdini has a well deserved reputation of making hard things easy and easy things hard, while Cinema has a well deserved reputation of making everything it can do as simple as possible, but with the limitation that trying to fly too close to the speed of sound will see your Cinema 4D flight disintegrate into a ball of wreckage and fire and tears while the Houdini flight passes safely by and into hyperspace territory. And that's pretty much where things currently stand except that to date Maxon has delivered not at all on the scene node promise while Houdini is making slow but steady and sure progress toward approachability.

Thanks for your other perspective. I'm not discounting the future of sds weighting by any means and will readily welcome new tools and methods that do work, but I never use the tag as is.

My opinion on this is one should absolutely never, under any circumstances, for any reason, use a weight tag. Learn to sds model using edge loops exclusively or use a different modeling method altogether. The weight tag was added to Cinema because it sounded good in theory but most users find it useless or actually harmful in practice. Use edge loops instead.