• Welcome to World Machine Community. Please login or sign up.
 
September 23, 2019, 04:04:56 am

News:

Read the Development Diary for an inside look at World Machine's progress!


Feature Request - Bundle Node, Collector, Pass through...

Started by hogjonny, November 19, 2008, 01:59:38 pm

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

hogjonny

So I've got some pretty complex node structures now, with 2-3 large "node clusters" to generate different texture passes for real-time game shader input maps.  I am finding that I am passing the final output heightfield of my terrain generation (ending in final erosion...) into like 10+ different nodes scattered across the file, a couple in each of the larger clusters, and a few loose ones.

It's now becoming more difficult to visually track some of the flow from node to node, lots of wires out of my terrain passing and crisscrossing the file.  This is fine for me as I created the file, but when I think about passing this on to another artist on the team to use or replicate it could appear confusing or even daunting (just as I felt the first time trying to wrap my head around building what I need.)  Like other tools and process in our pipeline for game content, I want to make our files as clean and easy to work with as possible.

What would be really useful to me is some kind of additional flow control, just a simple pass through or a multi-splitter with ALL outputs ON, which would do nothing more then allow me to simplify the visual routing of the node structure.  So for instance, I could split and route my primary heightfield to or around my larger clusters and forgo most of the crisscrossing.

I'm currently looking at doing this by building my own simple macro, but it would be nice if this was a simple tack-on to a future release?
skype: hogjonny

marmil

QuoteWhat would be really useful to me is some kind of additional flow control, just a simple pass through or a multi-splitter with ALL outputs ON, which would do nothing more then allow me to simplify the visual routing of the node structure.  So for instance, I could split and route my primary heightfield to or around my larger clusters and forgo most of the crisscrossing.

This sounds like what I would call a "no op" (no operation) node.  Something mostly just for routing purposes, but it could also be used to create a temporary visual place holder, or a point mid way between here and there where something could branch off of.  I would like this too.

Btw, you don't really need multi-splitters any more since the release of WM2.0.  You can hook as many things as you want to an output port on a node, but if you want you can bring a multi-splitter node from a pre WM2.0 network into your new network and it works fine.

Quick Reply

With Quick-Reply you can write a post when viewing a topic without loading a new page. You can still use bulletin board code and smileys as you would in a normal post.

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Note: this post will not display until it's been approved by a moderator.

Name:
Email:
Verification:
Please leave this box empty:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:

Shortcuts: ALT+S save/post or ALT+P preview