I have experienced that behavior with PPG logic for custom plugins and
shaders. Usually happens when performing some illegal command and Softimage
ducks for cover to protect itself from crashing. Whatever internal data
Softimage was managing gets corrupted/deleted and you must restart the
application to rebuild it to continue work. Whatever the issue, the
internal data seems to be dynamically built. On the rare chance you have to
deal with .spdl and related bits, you might want to flush your .spdlindex
file in your user profile as a last resort, but don’t touch it if you don't
have to.
Matt
Date: Mon, 16 Feb 2015 14:39:35 -0000
From: "raff" <[email protected]>
Subject: ICE Node Database Invalid Error
To: <[email protected]>
Hey folks,
I'm getting some very weird behaviour with a node where XSI issues a warning
on reload that the database for ICE Nodes is invalid followed by the name of
the node I'm prototyping.
The node definition behaves erratically, with me having had to change things
such as the names of the callbacks or the port group ID for parameters to
actually reflect changes, otherwise they would do weird stuff like appearing
in the PPG as the right type (or not appear at all), but actually internally
be flagged as a different parameter (with related error about mis-matching
CDataArray type, such as a parameter that's clearly a float insisting it's a
matrix).
Anybody ever encountered anything like it and has an idea if and how this
database can be purged or what would lead to these issues? It's making for
dev hell.
Cheers,
Raff
