
Here’s something useful I’ve learnt from my short time fumbling around ICE. Keeping thing organised is key.
As your compound grows so does the complexity, and if you’re building it with lots of user inputs in mind then you can get some pretty messy node spaghetti.
Just like writing scripts, defining globals at the start is common practise, so do this with your compound. At the top level store all your UI inputs as custom channels.
You can then call these custom channels back with a get data node where ever you need them. Rather than trailing inputs right across the compound and into nested elements, it helps visual clarity, bug hunting, and speeds up duplicating nodes etc.
Here are a few examples of before and after clean up.
Before:

After:

Happy re-organising, even though it’s a pain, it’s well worth it! Oh and remember to execute your global values first, to make sure they propagate though the ICE tree correctly.
Read More
































