Maxwell Render | Official public forum

We want to show you things we are working on / we already have done. And Fernando has come with the idea of this guessing game. So... with that image. Can you guess the improvement?

hmmm..

the detph layering in that image is quite puzzeling!

that yellow self reflection on the simball kinda looks like an additive material, doesn't it ?

I don't know, it's the default material in the simball scene. This particular image is Production, but this improvement works on gpu too.

I know!! I know!!...

It's the new swirly yellow simball modifier?

Scatter along curve ? )
altho looks a bit strange that bigger simballs are behind smacker blurred ones O_o

i was gonna joke about speed improvements that make the image render with speedy motion blur but after getting the de-noiser, speed jokes are pointless finally...maybe it's a hint about rendering animation from a single MXS file ?

Well, I can say, it's done using just 1 mxs, with just one simball inside. And it's not an animation. And no motion blur there.

so is it some kind of path or array instancing then?

or maybe a referenced MXS that has another MXS inside it ....?

choo-chee wrote:or maybe a referenced MXS that has another MXS inside it ....?

And we have a winner. Yes, now you can have mxs references inside mxs references inside mxs references. Even yourself.

oh yeah finally !

I was almost sure that nobody read about my problem here: viewtopic.php?f=109&t=44488
Now this should be possible, problem lied in mxs references linked to ARCHICAD as mxs reference.

That kind of situation was the seed of this improvement. AC plugin has that feature for animations that references the whole scene into a small file that contains only what changes: cameras and physical sky (for time lapses, etc.), this way you get fast exports with smaller file sizes; but that wasn't useful if you had references in the original scene, as they wouldn't show in render. I first asked for one or two extra levels of nesting, but Luis found easy to have a virtually unlimited amount of instances. Currently, we put a limit of 128 levels of nesting, but that can be changed.

And you can also do fractals with this!

Forum Moderator wrote:That kind of situation was the seed of this improvement. AC plugin has that feature for animations that references the whole scene into a small file that contains only what changes: cameras and physical sky (for time lapses, etc.), this way you get fast exports with smaller file sizes; but that wasn't useful if you had references in the original scene, as they wouldn't show in render. I first asked for one or two extra levels of nesting, but Luis found easy to have a virtually unlimited amount of instances. Currently, we put a limit of 128 levels of nesting, but that can be changed.

And you can also do fractals with this!

I have to deny things here. This wasn't easy at all. You can have instances inside references, instances of references, instances of references inside references that are instanced... and so on. But once I entered that world having 2 levels or 128 it's just a number. In my test 128 is fine for cpu, but it's too much for current gpus, 32 levels of nesting it's the maximum I tested right on my gpu. It can be used to do kind of fractals, as I allow self-references. But I can't recommend it in production as it takes a lot of memory. If that field of use is highly demanded a memory improvement should be done.