Jump to content
Jordan Walsh

Rotating Pyro Grid

Recommended Posts

Coming from a FumeFX background where you can rotate grid freely I was just wondering what do people do when they want the grid rotated (say 45 deg in the Y) for a more efficient sim (eg, long thin line of fire on a 45 degree angle)?

Surely the answer isn't to rotate your scene geo+ camera pre sim then rotate the results of your sim post sim is it?

Share this post


Link to post
Share on other sites

It isn't much work to plug in a transform before and after your sim is it?

Share this post


Link to post
Share on other sites

Why not transform pyro/smoke sim as you do with fumefx grid?

Attach Position data to pyro/smoke object (using Position DOP for example) and then write relative path to it in object.

m_20130109-gfdz-20kb.jpg

Edited by bloomendale

Share this post


Link to post
Share on other sites

+1 for what Bloomendale suggested -- I only came across this a few months ago when I accidentally left the mouse over the position data path for too long. I thought it was more complex than that. It's not. That being said, I think it should be in there by default.

Share this post


Link to post
Share on other sites

Hahahaha Solitude just showed me this a few weeks ago when i was trying to figure it out. It should be in there by default. It ends up being one of the first things I do when I start a pyro sim if I need it or not.

Share this post


Link to post
Share on other sites

well, actually not everything is working always, I still prefer to transform object and transform back after the sim.

Example file that shows incorrect sourcing of velocities.

the "position" node is bypassed, try to activate it and see that the velocity is not computed correctly

volumeOrientBUG.hip

Edited by MENOZ

Share this post


Link to post
Share on other sites

well, actually not everything is working always, I still prefer to transform object and transform back.

Example file that shows incorrect sourcing of velocities.

Forgot to attach file?

Share this post


Link to post
Share on other sites

Good to know! I didn't notice because I hadn't really had a reason to use it yet. I'll have to look for a workaround...

Share this post


Link to post
Share on other sites

well, actually not everything is working always, I still prefer to transform object and transform back after the sim.

Example file that shows incorrect sourcing of velocities.

the "position" node is bypassed, try to activate it and see that the velocity is not computed correctly

Good to know!! Has this been reported as a bug by any chance?

Share this post


Link to post
Share on other sites

yes, I reported it months ago, but I don't know if it's in progess of being solved, or if they give more priority to the bugs with more reports.

Maybe if someone else will report it again it gets more interest from sidefx??

Share this post


Link to post
Share on other sites

yes, I reported it months ago, but I don't know if it's in progess of being solved, or if they give more priority to the bugs with more reports.

Maybe if someone else will report it again it gets more interest from sidefx??

I reported it again.. They asked for an example file and I sent them the one you attached to this thread.. hope that's cool.

Share this post


Link to post
Share on other sites

I'm curious what is intended behavior of field with Position data provided. As said in help card transform is going after sampling. And it works so if you apply position data to one field. I attached simple example.

Then it should just sample anything in world space (let's say box at origin) and then applies Position data:

m_20130125-egxa-60kb.jpg

To get this behavior all you need is uncheck "SOP Output is in simulation space" in all Sop solvers in Fluid Source DOP because we don't need double transforms from sop solvers and Position data of the containers.

But if it should transform container without touching its data then it have to do it before sampling or resample all data.

So i think 1st behavior is what was planned.

3ak_fields_Position_data_PROBLEM.hipnc

Edited by bloomendale

Share this post


Link to post
Share on other sites

I know that this thread is much too old, but here is a file which fixes the issue.

I have modified /obj/dopnet1/sourcevolume1/source_tempvel so that the vel volume is sourced properly even in a rotated domain.

volumeOrientBUG_fix.hip

  • Like 8

Share this post


Link to post
Share on other sites

Was facing the exact same issue.  Your solution works like a charm, even with Pyro Clusters.

Thanks a lot jkunz07

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×