Welcome to od|forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Follyx

node color conventions

Are there any international standard node color conventions?

Share this post


Link to post
Share on other sites

Here is a good thread... color with a u because SideFX is Canadian...

Also Graham Thompson has a decent script on setting it up for pipelines for non-hda nodes. It's a bit old at this point, but still works pretty good.

https://github.com/captainhammy/Houdini-Toolbox

1 person likes this

Share this post


Link to post
Share on other sites

According to odforce scenes, no. The only common thing is an arbitrary color saying "attention/problem/fix there". H16 started to colorize many nodes. Now it's a bit confusing, since old nodes kept their colors. When you add op, new color differentiates it from similar node created before.

IMO, the better way is automatic coloring and shaping. Like syntax highlighting in code editors. Divide operators into classes, then users can customize colors and override classes to their own preferences.

2 people like this

Share this post


Link to post
Share on other sites

Nuke has an 'autocolor' preference which is sometimes good, sometimes not.

Share this post


Link to post
Share on other sites

COPs has a standard color scheme, which was implemented with the original design:

  • Generators are green
  • VEX operators are purple
  • Operators which don't affect image data are beige (timing operations, control flow, etc)
  • Collapsible Color Corrections (precursor of Compile SOP networks) are blue

The last three had special meanings with regards to cooking, which is why they were colored by default. VEX operators could bind planes named the same  as VEX function parameters, Timing operators didn't take long to cook because they didn't modify image data, and Color Correction nodes would be collapsed into a single operation if there were no other non-color correction operations between them, saving memory and improving performance.

But other than that, I don't believe there are any standard color schemes in Houdini.

1 person likes this

Share this post


Link to post
Share on other sites

Ok, thank you mates. Btw. I wasn't looking for an autocolering function. Instead a rule wich is most common in Studios arround.

Edited by Follyx

Share this post


Link to post
Share on other sites

not sure what the issue with autocolor nodes is- that's a common form of syntactic highlighting for all programming - which is what Houdini is, a visual programming language. i.e. TextWrangler ships with a ton of presets.

Screen Shot 2017-07-19 at 8.40.09 AM.png

Share this post


Link to post
Share on other sites

@marty:

sorrry dont understand your post in this context

 

@konstatin magnus:

Fantastic. Thats what I'm looking for. Diese Stutttgarter...^_^

Edited by Follyx

Share this post


Link to post
Share on other sites

sure, that link has essentially what you would call common-sense categorisation but it doesn't actually answer your original question

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now