Megabomb

[Magnum_design]

I´m having problems with a bomb I´m playing with.

First I can´t get the grid to expand enough. I have threshold 0.001 for smoke but it get cut straight off. Even though I have extra margin of cells. All axels open exept z(-)

The same if I use temperature threshold, it get cut off. I have value 600 and it cut it off through the fire that must be at least 1200 I guess.

And then the emmitters never lets go of the fire even though there´s no discharge since ling ago.

This was never a problem before?

[Svetlin.Nikolov]

Hello,

Are you using a nightly build or an official Phoenix?

The only case when the grid will not expand that I've seen is if it's too small at the beginning and the explosion expands too fast.

Can you share a video of how the issue looks like?

[Magnum_design]

It´s a nightly build. Im rendering a quick preview as we speak

[Magnum_design]

[Svetlin.Nikolov]

Wow, very strange. Would it be possible to send the scene or a stripped version of it to support or to link it here?

Also, before that - can you check what happens if you disable the "max memory %" option in the Grid panel?

[Magnum_design]

Ok. It will take awhile to sim, but I´ll do that and get back.

[Magnum_design]

Unfortunately the problem remains with Max memory disabled

[Magnum_design]

https://www.dropbox.com/s/mjtyk0xezj...abomb.max?dl=0

[Svetlin.Nikolov]

Thank you, got the file, you can take it down.

Now let's see what the problem is..

[Svetlin.Nikolov]

Hello,

The fix for the issue with the constant discharge will go into tomorrow's nightly build (11 Aug). Thank you for reporting that!

On the adaptive grid - it looks like it acted like there was not enough RAM - on our machines it works fine with 32 gigs. Would it be possible to ask you to send us the Phoenix log file, so we can check what happened - it is located in C:\PhoenixFD, corresponds to the version of 3ds max you are running (e.g. phoenix_maxver17.log is for max 2015) and is overwritten after each launch of 3ds max, so you'll have to get it just after simulating and hitting the issue. You can also check it yourself - if it says "preallocation limit reached!", then not enough RAM is the reason.

[Magnum_design]

Ok thanks. I´ve also got 32G of ram. I can sim that again and see. I´ll let you know later

[Magnum_design]

Hello,

The fix for the issue with the constant discharge will go into tomorrow's nightly build (11 Aug). Thank you for reporting that!

On the adaptive grid - it looks like it acted like there was not enough RAM - on our machines it works fine with 32 gigs. Would it be possible to ask you to send us the Phoenix log file, so we can check what happened - it is located in C:\PhoenixFD, corresponds to the version of 3ds max you are running (e.g. phoenix_maxver17.log is for max 2015) and is overwritten after each launch of 3ds max, so you'll have to get it just after simulating and hitting the issue. You can also check it yourself - if it says "preallocation limit reached!", then not enough RAM is the reason.

You´re right. I need more memory The funny thing is that I´ve been doing stuff like this before without a problem. Well, Im about to double the memory any day now so It´ll work better

",preallocation limit reached! 268294000 requested, 224674884 available"

[Magnum_design]

Btw I thought that if I ticked the "max memory" I would be safe from things like this. What´s the use for it otherwise?

[Ivaylo Katev]

perhaps the previous time when it worked the active applications were consuming less memory, who knows.

[Magnum_design]

perhaps the previous time when it worked the active applications were consuming less memory, who knows.

Yes ofcourse Also I think the resolution is way overkill here for the purpose. I got fooled by the numbers... The cellsize is about 1,5cm wich I thought was big. But in this scale it´s pretty small. I think I can increase the cellsize to 3cm and get almost the same look...