Can't import f3d cache from stokeMX

[jstrob]

Hi,

I am trying to reproduce this tutorial from Thinkbox: http://www.thinkboxsoftware.com/stk-...ng-fumefx-sim/

Except I want to do it with phoenixFD instead of fumeFX.

the first step works great. I can use the stoke custom field to influence my phoenixFD sim. You can see the sine wave pattern in this image:


But the next step is to export the velocity from the stoke field in f3d format and load it in a first phoenixFD sim and then use that sim to set the velocity of a second phoenix sim. Tha way the second sim should follow the sine wave more exactly.

But that step does not work. When I try to import the f3d cache sequence in the input of the first phoenixFD, I don't see anything in the list of imported channels. I should see the velocity from the sine wave in stoke.

I notice that it doesn't work neither in my version of fumeFX 2.1c. So I guess it was added specifically in fumeFX int v. 3.

Do you think you could allow phoenixFD to import f3d or vdb fields from stoke?

[vlado]

So much for portable file formats... it could be that the velocity channel is named differently from what Phoenix expects.

Can you post an f3d cache that doesn't work?

Best regards,
Vlado

[jstrob]

Here it is:

http://www.phylacterecola.com/strob/...cache_v001.rar

I opened it in notepad just to see but it's written in extra-terrestrial language!

[kostadin.petkov]

Yep, they are using different channel names.
I will let you know when we resolve the issue.

[jstrob]

Ok thanks!

[Svetlin.Nikolov]

Hello! We addressed the f3d import issue and also made some tweaks to allow using an external velocity field.

With tomorrow's nightly you can try the following:

1. Enable Grid Resimulation. Basically the Grid Resimulation feature uses the velocity from an already simulated cache to drive whatever fields (smoke, rgb, liquid) there are in the grid. These fields are emitted by sources the standard way, it's just that Phoenix will not simulate it's own velocity in this mode. We just allowed the use of f3d's and vdb's along with the standard phoenix aur caches.
2. Still in the Resimulation rollout, choose the f3d caches as the Resimulation Input Path (there is currently an issue with vdbs from Stoke, so please use f3d's instead)
3. Resimulation rollout: Amp. Resolution = 0.0 (no up-res); Amp. Method = Interpolate (you need Phoenix-generated UVWs for wavelet turbulence, can't do it with f3d/vdb); and Conserv. Quality = 0;
4. Now you can add the sources you need to emit matter and run the (Re)Simulation from Start as usual. No need for a second simulator.

Hope this helps

[jstrob]

You are amazing! Thanks I will install and try this nightly tomorrow!

[Svetlin.Nikolov]

Hope it does the trick I have to mention that you can just as well use Amp. Resolution - it will stretch your f3d's velocities and keep on going. Also - beware that the dynamics rollout's gravity and conservation will not work in this mode, but all others should be fine.