Since Krakatoa no longer works as a material editor renderer, should the Assign Krakatoa toolbar macroscript ensure that it isn’t assigned as such?
Good point.
I guess I have hoped deep down inside that the Material Editor rendering will be fixed some day.
I will make sure that the renderer is unlocked and set to Scanline when assigning Krakatoa via the MacroScript.
EDIT: Done.
this tripped me up when I first started working with krakatoa, and then was glad to see how easy of a workaround it was… but i’m sure to new
people that would just cause 1 less question to be asked over and over on the forums 