[Kevron]

Hi,

What is the best way to render particles simulated in rf2013?
I have tried several ways, but through rfrk 3 (renderkit) nothing is rendered.
And the standard way by importing rf particles does not either show up in render.

I have only tried via c4d, which I have to use in the end regarding all the frames.

This could easily be a brainfreeze on my part, but I would appreciate some pointers.

I also have pcache if that is a viable solution.

Thanks!

[JDHill]

And the standard way by importing rf particles does not either show up in render.

Hmm, you mean using .bin files and such, through the RF Cinema plugin? The problem is, I am not on RF2013 yet, so it will take me some time to investigate and see if new incompatibilities have perhaps been introduced. It would be good if you could please check some of your files in Studio using MaxwellParticles, to see if there is a similar problem loading them there, too.

[Kevron]

Yes, I will test tomorrow if it works in studio. I can also share an .bin file to you for testing. I reckon it is because of the new version, but since next limit owns both ip's, I hope they synchronizing all plugins as fast as possible.

Thanks for looking into it!

[Kevron]

Hi, here is a link to a particle file from rf2013: https://dl.dropboxusercontent.com/u/105 ... 25.bin.zip

I cant get it to work either with studio or through C4D. It "hangs" when you press "FIRE" or send it to maxwell render.

Here is a warning that comes up when sending to Maxwell : https://dl.dropboxusercontent.com/u/105 ... rticle.png

Cheers,
Tor M

[JDHill]

Thanks for checking that, and for the screenshot, at least this confirms that the plugin is indeed writing the particles object, with that info making its way through to Maxwell. I am still in the process of getting set up with RF2013, so I'll let you know when I have more information. If it's not too much trouble, I might also ask if you could please also upload the RF project (preferably, a minimized version of it, which still produces the error), so I can take a look at that as well.

[Kevron]

I am also in contact with next limit tech desk, this is the answer from Luis:

Hi Tor,

You are right. It is seems be a problem rendering the particles with the
Maxwell plugin for cinema. If you press F6 in RealFlow you'll that the
particles are rendered properly. I'm going to ask to Maxwell team about
this. I'll let you know.

Kind regards,

luisM.

I´ll try to upload a scene to you.

Cheers,
Tor Martin

[Kevron]

Here is the Realflow project: https://dl.dropboxusercontent.com/u/105 ... _files.zip

Cheers,
Tor M

[JDHill]

Thanks, I'll take a look and see what I can find.

[JDHill]

Following up on this, I am not yet able to determine any particular reason for the problem (which is: the renderer appears to get stuck indefinitely in voxelization). I can only say for sure that it is not plugin-specific; it works the same when removing the plugin from the equation and using Studio alone. It appears to be a problem with the 2.7.20 MaxwellParticles extension; RF 2013 includes its own version of this, which looks to be newer than the one in Maxwell 2.

[Aniki]

jumping in as I have problems with the mesh loader, current realflow plugin with current mw plugin, the mesh doesn't get exported, so it renders without the mesh.

[JDHill]

Is there any particular variable that seems to be in play? Checking here with RF for Cinema 2.3.0 RF Mesh Importer (I assume this is what you mean by "mesh loader") and some RF2013 mesh bin files, there doesn't appear to be any problem. As an emergency workaround, you should be able to use Current State to Object on the RF Mesh Importer to obtain a polygon object for rendering.

[Aniki]

Seems to be another issue with the Extension. Ill pass you the scene via pm.

[JDHill]

Thanks for the file, there were two factors in play with it: 1) you are using the "Scale" parameter in the RF mesh object, which is not matched up to anything in the resulting MaxwellMesher, and 2) Maxwell FIRE is rendering this with 90 degrees rotation. For the first, I will look into globally scaling the output object by this factor, let me know if you have opinions on this. For the second, there is nothing to be done about it at this point in time, but regardless, it only affects FIRE, and not Maxwell Render.