• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
trouble with wavelet sim
#21
Hello,

You've mentioned that "deleting user prefs did the trick" - did the problem came back at some point while still on SP5 ?

Thank you.

Regards,
Kresimir Tkalcec
  Reply
#22
I have just wanna confirm that i just faced the same problem with maya 16 sp2 and after deleting pref dir wavelet started working normally, and didnt freeze after, in my case, after 6th frame

i hope you guys will be able to find the problem with pref thing...

cheers
  Reply
#23
small update,

after saving pref, closing maya, and loading the scene again, wavelet stopped working again, after 6th frame!!!!???

i think this is a serious problem, and needs to be fixed asap

p.s.

also i notice that even after deleting the pref for 2nd time, wavelet is simulating 5x slower then im my previous post, when i test it. Scene is simple just a default container with simple emitter...

200f compare:

maya 2014:
default sim: ~1min
wavelet sim: ~3min

maya 2016 sp2:
default sim: ~1min
wavelet sim: 25% 10min (didnt had the time to wait for 100%)
  Reply
#24
I think i know whats the problem but i dont know how to solve it,

im uploading videos in few min
  Reply
#25
Here it is people

2014, left/right default/wavelet
https://vid.me/e/xPkF

2016, left/right default/wavelet
https://vid.me/e/haov

as you can notice, i think there is a problem with velocity, or something with reading the info from default sim...

i hope this can help you out guys to find whats wrong, now im off to my vacation Big Grin
  Reply
#26
Hello,

Thank you for the bug report.
We will try to reproduce it, but so far all attempts have failed.

Regards,
Kresimir Tkalcec
  Reply
#27
will it help if I upload wavelet cache file?
  Reply
#28
Hi guys,

i did few more tests trying to figure it out what could be a probl with wavelet in 2016 and here are the results of the log file compared with 2014

[Image: compare.jpg]

if you take a look Vmax and CFL are way way too high for some reason...

im attaching the log files just in case...

p.s.

fume cache files for 14/16

https://www.sendspace.com/file/4kf83j
https://www.sendspace.com/file/wfbmqb

also notice that 2016 wavelet files are smaller like they are not written ok...

sorry for being boring but, this is the only reason that holds us back from moving to 2016
  Reply
#29
any progress on this?
  Reply
#30
i hope you didnt forgot about this probl Smile
  Reply
#31
Hello,

Any chance that you can upload first 5 default caches and the scene so that we can run a wavelet on those ans see if we can reproduce this error?

Thank you.

Regards,
Kresimir Tkalcec
  Reply
#32
yes of course Wink

may take some time, im in a heavy production, but ill try to upload over the weekend

thx
  Reply
#33
here you go guys

http://we.tl/nYNqPZI3Jp

i tried everything, for a moment i thought it was problem with Parallel processing, since 2016 is fully multi threaded, and i notice that some plugins doesnt work properly, but even when i switch to DG processing nothing changed im still getting crazy Vmax/CFL vaules and wavelet looks very strange...
  Reply
#34
Hello,

This is an old thread, but I just want to drop a note that this issue has been solved in FumeFX 4.0.

Regards,
Kresimir Tkalcec
  Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)