energy preservation?

[losbellos73]

Hello Team,

Is there a way to see that the heat fills up the container some way like heat being passed to neighboring cells, or other ways like fill up with a container with liquid(or air), and then heat it by a box and see as it warms up. As I try it seems that is disappears just like that without cooling.

Also the size of the wind icon doesnt seems to do a thing, maybe it would be useful...
Any ways to make some sort of vetillation?

Otherwise its great, its fast

[losbellos73]

BTW the normal method to add velocity doesn't seems to work only trough scripting. Could that be that the velocity is numerically limited to 1000 in the phoenix source that is why?

An auto min-max value for velocity/temperature etc would be great in the preview.

Also the units could be displayed, for example cm/s or kelvin like thing or something..
A double clipping plane to have better clue whats happening inside, maybe this should affect meshing too. Some sort of meshing or rendering method describes the vectors of the cell, also the there could be a weighted vector display as well (only one triangle per cell, but this allvecs must remain as well).

sometimes subdividing the participating mesh seems help if leaking.

Oh yes, the injected velocity should not be cell count dependent, it should be only velocity. Or it needs more because the velocity injected cells are becoming smaller? I am not sure.

A helper to tell the user the actual location and size of the phoenix cell based anything for example injector.

for now:
phoenixcontainer = $
phoenixpos = phoenixcontainer.pos
cellsize = phoenixcontainer.cellsz
xcount = phoenixcontainer.xc
ycount = phoenixcontainer.yc
zcount = phoenixcontainer.zc
inphoenixpos = $lolphoenixpos.pos
theleftcorner = [(phoenixpos.x-((xcount/2.0)*cellsize)),(phoenixpos.y-((ycount/2.0)*cellsize)),(phoenixpos.z)]
thex= (abs(theleftcorner.x - inphoenixpos.x)/cellsize) as integer
they= (abs(theleftcorner.y - inphoenixpos.y)/cellsize) as integer
thez= (abs(theleftcorner.z - inphoenixpos.z)/cellsize) as integer
thebasegrid = 3
cnt = 0
thevelocity = 500
for k=1 to thebasegrid do (
for i=1 to thebasegrid do (


format "% \n" ("A_SetV " + (thex+i) as string + " " + (they+k) as string + " " + thez as string + " " + ([0,0,thevelocity]) as string)

)
)

[losbellos73]

there is one more thing, after inceting velocity the water level increases significantly LOL!

A_SetV 12 10 8 [0,0,7500]
A_SetV 13 10 8 [0,0,7500]
A_SetV 14 10 8 [0,0,7500]
A_SetV 12 11 8 [0,0,7500]
A_SetV 13 11 8 [0,0,7500]
A_SetV 14 11 8 [0,0,7500]
A_SetV 12 12 8 [0,0,7500]
A_SetV 13 12 8 [0,0,7500]
A_SetV 14 12 8 [0,0,7500]

[losbellos73]

increasing quality didnt solved this last issue..

[Svetlin.Nikolov]

Hello,

First off, which version of Phoenix are you using? I would suggest you mail the support at support@chaosgroup.com and request permissions to access the nightly builds, as I think some of the issues are already resolved there.

What is the setup you are trying to achieve? You are talking about both heat and water - they do not exist simultaneously in Phoenix. Once you enable Liquids, the Temperature channel is instead reused internally to hold the liquid density.

To answer your questions one by one:
- The heat is transmitted between cells only through velocity. If a cell has temperature over 300 (our units are something like Kelvins), then the cell will create upwards velocity, which is then multiplied by the Gravity option. On the contrary - temperature below 300 tends to create downwards velocity. With zero gravity, hot or cold content will not move in either direction.
- If your resolution is low (below 1M), temperature and everything else will dissipate while moving because of the nature of grid simulation, I'd guess that maybe this is what happens in your scene? Try increasing the resolution.
- Only the Wind Strength is taken into account.
- You could achieve ventilation if you create a source and use a negative discharge. Note that the emitter geometry must be set to NON-Solid from it's right click Phoenix properties.
- When you access cells through maxscript, make sure that first you call A_SetSystem(), to specify if you'd use voxel space, world space or object space. In the nightly builds it already uses voxel space, but in the official build is used world space. Check http://docs.chaosgroup.com/display/P...n+to+MaxScript for more info.
- Preview Auto min-max is already present in the nightly builds.
- The velocity units are in cells/second.
- In the nightlies and in the official Phoenix 2.2 there is the preview options "Draw just a slice". It does not work for mesh preview though, but works for cell preview, as well as for particles.

[losbellos73]

yeah-yeah thx,
When do you think there will be a new demo version? I am not owning it just tested the demo.
just draw a slice option seems interesting.

[Svetlin.Nikolov]

The next demo will come with the next official release, which won't be too far in time, but it's not so soon either.