Register Latest Topics
 
 
 


Reply
  Author   Comment  
p0las

First taste
Registered:
Posts: 14
Reply with quote  #1 
upresFluid when switched to full turbulence crashes maya 2017 (update 2). Example scenes crash maya too. noise advection seems to have no visual impact on upressed fluid

windows 10.

does the wavelet turbulence have some special dependencies?



0
pshipkov

SOuP Jedi
Registered:
Posts: 4,702
Reply with quote  #2 
Just tried Maya2017 on windows 10 and no problems.
If you think this may be something related to your scene - feel free to email it to me, or post it here and i can take a look.
0
p0las

First taste
Registered:
Posts: 14
Reply with quote  #3 
I don't think it is scene related. If i try to load soup example scene "upresFluid4.ma" it crashes maya instantly. In other upres examples the moment I turn the upres node on maya crashes.
Do I need some other plugins or dependencies installed? I'm running SOuP_2017_02_27, maya 2017 update2, windows 10 anniversary...
I have installed latest (update 3) of Microsoft Visual C++ 2015 Redistributable.

https://www.microsoft.com/en-us/download/details.aspx?id=53587

here are my steps to crash maya:
1. create 3d fluid with emitter
2. with the new fluid container I go to soup shelf and hit upresFluid
3. I tick on ''envelope" on the newly create upresFluid node. All good at this stage but the upressed fluid doesn't look any better than the source one and even massive values of strength, steps, octaves do not change it.snip_20170302094536.png 4. I switch to any turbulence and it kills maya after a second snip_20170302094646.png 
the crash is not a usual maya one that attempts to save a scene but complete windows one:
snip_20170302094748.png 

obviously, there is something wrong with my system and/or I'm missing something...
4x upres with huge strength (delta seems to work and move the fluid with the motion vectors but again without any noise added to it)
snip_20170302095632.png 

0
pshipkov

SOuP Jedi
Registered:
Posts: 4,702
Reply with quote  #4 
Strange.
Anyone else having this issue ?
Trying to determine if this is an isolated case, or something more widespread.
0
p0las

First taste
Registered:
Posts: 14
Reply with quote  #5 
I tried it on another box (similar setup) with the same results.

I also discovered that if my initial fluid resolution is small like 10x10x10 then it doesn't crash when I switch to turbulence (the result however, is nothing like in the examples in the documentation) and changing the "strength" has no effect on the look.
larger initial fluids like 40x40x40 crash maya.

it seems that there is a threshold of how many voxels can be processed by the turbulence.

I found that maya API's texture lookups (sampleShadingNetwork) can handle up to 512k samples. above that maya will crash the same way.
0
pshipkov

SOuP Jedi
Registered:
Posts: 4,702
Reply with quote  #6 
The only limitation to source fluid container resolution is the available memory on your computer.
Can this be the case ?

EDIT:
So if you have 100x100x100 and you upres 3 times you get 100x100x100 + 300x300x300. That's quite a bit. But apparently you are talking magnitudes less data.
Also, during the process memory spikes in order to hold the extra data. Once process finishes the data is stored in the fluidContainer.
But if you have at least 12 gigs of ram you should be able to run quite heavy data sets. Container with resolution with 40x40x40 leading to a crash tells me that there is something else going on.
0
p0las

First taste
Registered:
Posts: 14
Reply with quote  #7 
64GB of RAM. no way.

EDIT:
30x30x30 and upres of 2 results in a crash.

10x10x10 and upres of 6 was ok but second pass of 2 crashed maya.

what worries me the most is that most of the settings do not change the look of the fluid. magnitude of 10000 should completely mess up the fluid but it has no visible effect. Like the noise is not calculated at all.

I tried with other plugins on/off, vanilla maya etc. I also tried an older soup and maya 2016 with the same results. This indicates to me that some system DLL that the plugin relies on is incorrect but I don't know enough to track it down.
0
pshipkov

SOuP Jedi
Registered:
Posts: 4,702
Reply with quote  #8 

That part of the plugin does not rely on external dependencies other than the standard C++ library.
That's why it is so puzzling to me. Especially given that fact that the problem is persistent across different Maya versions.
I tried today (briefly, but still tried) on two different Windows computers (win 7 and win10) - everything seems to be fine.

Can you provide stack trace, if there is any ?

0
p0las

First taste
Registered:
Posts: 14
Reply with quote  #9 
visual studio gives me this:

Unhandled exception at 0x00000199B6DD5F2C (SOuP.mll) in maya.exe: Stack cookie instrumentation code detected a stack-based buffer overrun.

this is in vanilla maya 2016 extension1 + SP5 with SOUP plugin manually loaded (it is not copied to maya plugins or set in the environment).

Other tests in maya 2017 had the plugin in the environment.

I simply opened upresFluid4.ma scene to crash maya.

SOuP_2017_02_27.tar
windows 10 Pro (1607)
Intel i7-4930K 3.40
60GB RAM

0
pshipkov

SOuP Jedi
Registered:
Posts: 4,702
Reply with quote  #10 
No idea what could be the reason.
I checked on the exactly same Maya version and win10 and it worked as expected.
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation: