v3 alpha vdb not loading

[ThaRaven]

thanks i will try that in a larger sim. guess its a language barrier issue that i didn't get you the first time. Sorry for that

[azen]

thanks i will try that in a larger sim. guess its a language barrier issue that i didn't get you the first time. Sorry for that

Glad to see that you have your vdb sequences up and running. Are there any other issues you are having with it at the moment? Any suggestions to make working with sequences more intuitive would also be appreciated.

Cheers,
Azen

[Norman_Stansfield]

i see what you did there.. i renamed File jim_0000.vdb to jim_.vdb and now its working

Yes, I wrote about it in a feature description and in my very first answer to you here about that, mentioning exactly how this filename must look like in your case...
This Jim_.vdb is just used when you disable the sequence (digits to "0"), but it is not used when the sequence is enabled. So you will still need the Jim_0000.vdb for the frame "0"... So, don't rename it, just copy it to the default named one.

Jim, what is that feature description you are referring to?

I've managed to make sequence of vdb's from fumefx working with octane volume in 3dsmax.
If someone has problems, here is what to do in one post:

1. Export your fume fx sim with vdb extension. By default fumefx writes fxd, just change the extension in output window of fumefx parameters.
2. Create octane volume, add scattering map to a material slot. Click on file button, point to first file in sequence, but firstly right click and rename it by deleting four zeros (or four numbers) from the first file. It should be like fumefx_.vdb then. Frame zero can be empty, but frames first and further should update in octane viewport in realtime.
3. Adjust emission parameters to avoid overbright spots, etc...

My question is, however, why does user have to make this trick with changing names. It is not intuitive and it could be easily done under the hood, I presume.

thanks for v3.0, anyways
happy customer,

[JimStar]

My question is, however, why does user have to make this trick with changing names. It is not intuitive and it could be easily done under the hood, I presume.

You don't need this in most resent plugin version (3.10 beta). It understands both approaches for sequences - pointing to the initial file name and pointing to any other "sequenced" file name.
Always try the most recent versions when you are evaluating the testing versions of the plugin.

Anyway the point 2 from your description is wrong - you should have read this thread carefully. If you use the "pointing to default file name" approach - you don't need to rename the first file to another name, you need to copy it. So that the whole sequence remains intact, just a default-named file for static render of any frame is added.
As I said - if you want you can point to any other file from the sequence starting from 3.10.

[ThaRaven]

Hi Jim

is there any possibility in the Future for octane to render VDB Files directly within the FumeFX container? So we can use the shaders like Black Body for example? would make things a whole lot easier.
having a realy hard time here to match the Look in the Octane Vollume object to the one already created in the fume Grid.

edit: also to have the smoke emission where it is suposed to be

Kind regards

[Norman_Stansfield]

Raven, I am not sure what do you mean to render straight from fume fx. It is very easy to create octane volume now. The only problem worth investigation is that octane volume places vdb file shifted in xy direction in relation to fume fx grid, even if these are both in the same point. It can be matched in octane viewport in visual way, however.

I make first production render tonight. Its blacksmoker, both enviroment volume and smoke volume underwater. Octane is very fast with volumetrics, even in 4k. Vray cpu takes hours per frame with vray volume fog. In octane it is matter of minutes. And it looks awesome, realistic.

Great job guys, thanks.

[ThaRaven]

might be that im not that skilled with the new octane container. what i mean is that the Fumefx grid itself already is a Container holding the vdb. so i hope in the future we can just hit render in octane and it displayes the simulation instead of creating a new seperate container and havin to do all the adjustments again we already did in the Fumfx settings

[JimStar]

Guys, I have the plans to investigate the possibility to get data into Octane volume directly from third-party FumeFX plugin. But currently I have too much other urgent work (and with other projects too), so I don't have time to reverse-engineer what data is available by 3ds Max API from FumeFX plugin... So far I don't even have the FumeFX license to start playing with it.
So, will look into it later...

[ThaRaven]

sounds awesome. nice work jim looking forward to it in fute releases

[ThaRaven]

Hi Jim,

not sure if i should open a new toppic for this but since its still revolving around VDB il post it here.

i found another bug. VDB files in the Octane Vollume Object jump arround during animation.

2 Renders attached. 1 is the Vray render straight from the FumeFX grid (so no vrayvollumegrid)
and the second is the Octane render where i tried to match the output from the First frame. (low res test render 100 samples)

all rendered from the same camera.

Edit:

Never mind. was a FumeFX VDB bug and seemes to be fixed in V4.03