(Sorry about posting these things in the public forum. I forgot these are beta features.)
I got this message late on Friday. I needed to crank up the density of one Loader, so I checked the “Density->Mapping#” and put a output/vertex colors map in the opacity channel. I turned up the ‘output amount’. and rendered. It renders fine. Then i turn up the amount and render again and I get this error.
---------------------------
Krakatoa error in MAXScript function FranticParticleRenderMXS.InitRenderer()
---------------------------
– Runtime error: Attempted to set property “Density:DensityMethod”, which is not a valid property name.
---------------------------
OK
---------------------------
Any advice, I don’t want to lose the whole weekend’s rendering time.
Thanks.
Ben.
I stopped using the density override. But I am using the color Output/vertex colors to apply a lookup table to adjust the color channel.
I get about two renders, then I get an error.
The .ms file opens to the line
Max Quick Render
– Error occurred in btn_quickRender.pressed(); filename: C:\Program Files\autodesk\3ds Max 9\plugins\Krakatoa\Scripts\KrakatoaGUI.ms; position: 158679
– Frame:
– oldState: false
– oldTimeType: 3
– oldSaveFile: true
The weird part is the Max Render Panel stays open, and there is no way to close it. I can still work in the scene, i just lose all ablilty to render.
Again, the GUI just calls ‘max quick render’ which is equivalent to pressing the Render icon in the Main Toolbar. Then something bad happens in memory… I would expect the same to happen if you just press the teapot icon or the Render button in the Render Scene dialog. Would you be able to try to repro without using the scripted GUI’s RENDER button?
We should figure out what exactly it is that is happening, but I suspect that MAXScript is not the culprit in this case, it is just the last thing that reports a valid error before things go bad…
If you can figure out a repro case (possibly without using internal company data), it would be amazing. If we cannot reproduce the issue with our own test scenes, we wouldn’t be able to figure out what is going wrong…
I will try to get the same crash here by playing with Vertex Color / Output maps, let’s see if I can find a way to reproduce it myself.
max9 64bit 8GB ram.
I think I’m up to 112 million parts. using color and density channels only.
the ram used during a render is about 4.3gb
v1.0.104.30877
You might be right about the memory issue. But it does render. I have the caches turned off. It just doesn’t render after a few times. So maybe there is a memory leak?
I can check to see if a gc() lets me render more.
I also switched to using color correct now instead of outputmaps. I’ll try using them again to see if that was the problem.
it would be nice if krak could gracefully recover from these issues too.
I’m getting suspicious of the Output map. I can’t get any errors now.
I’m getting suspicious of the
Output map. I can’t get any
errors now.
Let’s hope it will stay that way, after all it is important to get the job done.
We will try to repro the crash using the Output map, let’s see if we can hit the same problem.
I have seen the crash you described once or twice, but could never reproduce it. I have never used the Output map in Krakatoa, so it must have been something else.
The strange thing is that “Density:DensityMethod” IS and forever will be a valid property name (this is the value of the “Volumetric”, “Additive”, “Constant Alpha” drop down list.
So the error does not really describe what happened, it is more a side effect of some bigger (memory-related?) thing going on.
Which means that unfortunately I cannot do much about it as it is not really on the scripted side of things.
Can you give me an idea how many particles you are rendering and whether you are using 32 or 64 bit Max?