Max 8 sp3, xp 64, krak .10.
during local particle generation I keep getting a max script error, this then causes
“unknown system error”
then Max crashes.
I have included a max file and screen shot.
Sam,
I have seen this in the past but I could not repro it in the latest build which uses completely reworked Local Partitioning code.
I will ask you to test with 0.9.11 (when we post it later tonight) and see if it still crashes.
In short, Unknown System Exception means (nomen est omen) that nobody knows what happens. It crashes at the line “max quick render” which is equivalent to pressing the Render button. So there is not really a bug we can fix, only hope that MAXScript will not run out of memory or something similar.
Can you tell me what the result of
heapSize
is in the Listener? Just type it in and post the number.
Thanks,
Borislav “Bobo” Petrov
Technical Director 3D VFX
Frantic Films Winnipeg
ok cool,
heapsize result
30720000
this was done from a fresh open of the file.
cant do it after it crashes
cheers
Ok, cool, that is enough Heap memory for most scripts.
It would be interesting to see if 0.9.12 will crash with that scene, as it does not call “max quick render” anymore…
Cheers,
Borislav “Bobo” Petrov
Technical Director 3D VFX
Frantic Films Winnipeg
got the same error with .12 installed.
I have deadline installed, but did not update due to not wanting to screw with our entire render submit system.
but I also got errors just opening the Krak ui, but this may be due to the deadline thing
here is a screen of the open error
this is the script that poped up during the partion error.
not sure if its any help, but hey, cant hurt!
Sam, you are missing the point.
The new error you are getting is logical. You are running Deadline 2.6 and Krakatoa cannot work with it. Period.
The update that I posted YESTERDAY fixed that. It was just one file which you can back up first, then replace and then Krakatoa starts correctly AND submits to Deadline (see confirmation post in thread “Kraka 0.9.12 installation BUG” that shows the fix worked.)
The update I posted today installed ok on my home machine (and runs on the whole Frantic network anyway), but if you don’t want to install it, you can use the minimal patch that I posted yesterday.
You won’t be able to run Krakatoa 0.9.12 AT ALL without applying either fix.
Cheers,
Borislav “Bobo” Petrov
Technical Director 3D VFX
Frantic Films Winnipeg
ah ok, figured it was something like that, did not want to mess with Deadline till the techs got back in to work.
I will test at home and see how it goes
cheers
ah ok, figured it was
something like that, did not
want to mess with Deadline
till the techs got back in to
work.
I will test at home and see
how it goes
cheers
Actually I am about to post an updated GUI file which will hopefully work with 2.6 without the patch (but will disable the Tasks Per Machine and Limit to CPU options that require 2.7). It would be great if you would test that and see if it helps…
Cheers,
Borislav “Bobo” Petrov
Technical Director 3D VFX
Frantic Films Winnipeg
I posted the update in the Builds forum, in the same thread as the 0.9.12 build.
This should allow you to run Krakatoa without updating Deadline and hopefully fix the memory problems when saving partitions locally.
Cheers,
Borislav “Bobo” Petrov
Technical Director 3D VFX
Frantic Films Winnipeg
cool, I will test on Monday!
Took today off, first day since New Years!
yay.
cheers
hello,
I installed the Gui fix for .12 still using old version of deadline.
Everything work s as expected!
but…
the scrip error is still occuring
I manged to get it partioned by lowering the total # of parts from 10 mill to 5 mill.
but still kinda strange.
cheers
the script error is still
occuring
I manged to get it partioned
by lowering the total # of
parts from 10 mill to 5 mill.
but still kinda strange.
Sounds like you were running out of memory. Not strange at all. Use whatever particle count works, or switch to 64 bit Max to get more particles per partition.
the odd bit about this,
seems to be that each version of Krak seems to handle less parts per partion.
not a complaint, I love krak (heh) just an observation.
the odd bit about this,
seems to be that each version
of Krak seems to handle less
parts per partion.
not a complaint, I love krak
(heh) just an observation.
The really odd thing is that Krakatoa should not care how many particles you are processing since the saving to PRT is using streaming and not in-memory loading.
Thus, each version of Krakatoa should handle the SAVING of as many particles as the previous version. (This is not true for rendering, there were changes that made Krakatoa render slightly less particles on 32 bit Max versions).
Thus I would assume that SOMETHING ELSE is eating more memory on your machine (like Max itself, your PFlow or something you installed) as Krakatoa could save as many particles as PFLow can fit in memory without crashing.
Or it could be a MAXScript thing that we have no control over… Have you tried saving the same high count using MANUAL paritioning? (Press the one button to increment seeds and update the name, then press the Render button in the Main Toolbar of Max to save, if it does not crash, repeat for the next partition).
If it does not crash when doing that, we would have to investigate to see what is causing MAXScript to throw Unknown System Exceptions…
Thanks.