Paul, the graph is not creating infinite loops. When I got started with Modo, I also got confused about these weird loops. They are actually not circular dependencies. Modo will not allow this to happen (if you ever accidentally create one, Modo will warn you and undo the action automatically). They're just a visual consequence of how certain tools work. I've actually never created one. All my rigging just goes through what you'd maybe call a more linear flow. I've learned to just accept them as part of Modo's internal referencing system, and let them be (as I said, they are created by some tools, so I just let those tools do what they have to do). No need to panic. Modo's schematic is actually one of the best node-based environments I've had to work with. It doesn't have the depth of ICE (yet), but everything related to dynamics, particles, rigging (Kinematics) and shading is available there.
Sergio Muciño. Sent from my iPad. > On May 7, 2014, at 10:39 AM, Paul Griswold > <pgrisw...@fusiondigitalproductions.com> wrote: > > I wasn't really talking about the example, but instead the way they've > decided to set up their connections. It often ends up a spaghetti mess of > wires that make circular connections with the wires running behind nodes. I > don't see the logic in it. Maybe I just like clean layouts. :-) > > I'm open to new ideas and ways of doing things, but it just seemed weird that > no other node-based system creates these looped connections because infinite > loops are bad (I understand they're not really infinite loops, but they > visually appear to be) and again, it makes for a very sloppy graph. > > -Paul > > > ᐧ > > >> On Wed, May 7, 2014 at 10:29 AM, Angus Davidson <angus.david...@wits.ac.za> >> wrote: >> Ones mans circular is another mans intuitive. ;) To me I found the example >> easy to follow and to duplicate and understand what was going on. That >> begin said a lot of it is down to putting what you are used to on the shelf >> for a bit and really diving in. It was only once I did that did I understand >> just how flexible it is. Your never going to innovate if your always trying >> to put everything in the same container, or doing things the same way. >> >> From: Paul Griswold <pgrisw...@fusiondigitalproductions.com> >> Reply-To: "softimage@listproc.autodesk.com" <softimage@listproc.autodesk.com> >> Date: Wednesday 07 May 2014 at 4:22 PM >> >> To: "softimage@listproc.autodesk.com" <softimage@listproc.autodesk.com> >> Subject: Re: softimage to modo >> >> What do you guys think of Modo's nodal deformer layout? I just looked at >> that growing vine tutorial page and the splash page for the video shows >> exactly what I personally dislike. Their node connections seem to be really >> sloppy and IMHO could lead to a confusing mess pretty quickly. They've got >> connections that make circular loops, so there's no left to right or top to >> bottom flow like you'd have in pretty much every other node-based system >> I've used. >> >> I mentioned it during Brad's webinar and he kind-of brushed it off, but I >> find it really distracting. >> >> -Paul >> >> ᐧ >> This communication is intended for the addressee only. It is confidential. >> If you have received this communication in error, please notify us >> immediately and destroy the original message. You may not copy or >> disseminate this communication without the permission of the University. >> Only authorised signatories are competent to enter into agreements on behalf >> of the University and recipients are thus advised that the content of this >> message may not be legally binding on the University and may contain the >> personal views and opinions of the author, which are not necessarily the >> views and opinions of The University of the Witwatersrand, Johannesburg. All >> agreements between the University and outsiders are subject to South African >> Law unless the University agrees in writing to the contrary. >
