Krakatoa Log Window

#1

Is it possible to disable the open krakatoa log window on warnings permanently? Running 1.6.1 in Max 2010 keeps enabling it on startup but I’d like to have it disabled.

#2

Yes, it is possible to “hack” it, but unfortunately I never thought of making it editable via the UI (but I should have). I will try to fix this for the next release so you could specify it in the Preferences rollout whether you want it to be checked or unchecked on startup.

For now, do this:

*Go to your Krakatoa installation folder and find the Scripts folder, e.g. C:\Program Files (x86)\Thinkbox\Krakatoa\Scripts
*Locate the file “KrakatoaGUI.ms”
*Make sure you have Administrator rights to modify the file since it is in a Program Files folder and Windows Vista/7 would normally refuse to let you modify it. You could right-click the file, go to Properties > Security tab and Edit the Permissions to enable writing.
*Open the file in a text editor (or the MAXScript Editor) and locate the following line:

try(FranticParticles.PopupLogWindowOnMessage = true)catch()

*Change the ‘true’ to ‘false’ and save the file.
*Restart Max.

Hope this helps.

#3

Works great, thanks Bobo! You guys are doing an awesome job with krakatoa :thumbsup:

#4

Thanks!
FYI, I just fixed it for Krakatoa 2.0 so that it remembers the last state of the option in the INI file - if you turn it off, it will stay off until you turn it on again.

#5

Awesome!

One other thing, when you switch between krakatoa and the other renderers, does krakatoa create a new particle view each time? I was doing some testing in a scene not knowing I had 4 particle views which was killing productivity when I had the particle view open. Deleting the excess views made it function like normal again.

#6

No, Krakatoa is not doing anything, we are using the Max native Render Presets to store/restore renderers. It sounds like a bug/side effect of using RPS (which is half-broken since around Max 2010 anyway - if you enable file compression, it corrupts the RPS files). I will try to investigate, but it is most probably Autodesk’s bug. RPS files are like MAX files, but containing only the chunk responsible for the Renderer and its parameters. It is quite possible that new instances of Particle Views are made when an RPS file is “merged” into the current scene (since loading an RPS is like merging a MAX file).

#7

It does seem to be related to the RPS files. If I click no to load krakatoa with the default settings I don’t get any excess particle views. It’s only when I load the last saved settings or reverting to the previous renderer.

PS: it’s doing the same thing in 2009 too…

#8

THANK YOU!:scream:

#9

waa thanks! :bounce:

#10

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.