Process always matters because the actual results usually happen after several iterations of other results. I love the ability to combine the quick sketch-like approach with a procedural one, so we can choose the level of "proceduralism".
Never used Modo but the interface looks well organised... and a good selection of intuitive tools. But being creatures of habit... changing apps is not something that comes easy. Regardless... seems like a great program.
I actually like that your boss didn't care about the process. Too often in the past, jobs asked for a certain process or program, even if the same result can be had with other processes or programs. For the boss not to care would hopefully open the door for your favorite process. I was able to bring my own copy to work and use it rather than use what they had.
I have a few questions regarding the procedural text part. You plugged the percentage user channel value into the 'integer' input of the string compose. Adding it to the 'float' input returns nothing. Why is that? Can percentages only be translated to integers? What if you wanted to express a decimal percentage? Why does the rig only return a value of 0 and 1? Why not who values between 0 and 100?
It seems like percentage is its own construct? It's something you just need to know about which makes it difficult to figure out your own rig via logical steps. You were aware of the percentage variable's construct and then used the math node to essentially clean it? I'm not sure if i'm making sense. I guess my angle is, why not just start with an integer user channel value?
Andy.... you never say how you got the number driver value slider to pop up in the text primitive example... that's where this tutorial ends for me :( Usually, you're pretty good about saying what you are doing.... Anyone know how to do this? Thanks for your help! Found it. It's the Channel Haul... keyboard: c
Curve Extrude is really cool, I was waiting for this tool since a long time. I saw that you can only apply this modifier to one curve index. Is there any way to make it apply to all the curves in an object. Is really time consuming to do it for each curve in the scene... Thanks
Thanks for the high-res version, much appreciated. A quick question, at 33:20 a "pattern" is entered into the String Compose node. This pattern is $[i:1] what does this mean? I can see the procedural system is very powerful, but if it relies on knowing such cryptic bits of code it is going to be quite difficult to use for non-programmers like myself.
Great video. I used the method in the train track section for duplicating the sleepers to create a necklace. That works great but now I am wondering if there is a way to change the scale of replicated meshes as they progress along the curve? In my case I want them to get bigger towards the middle of the curve and then return to the original size at the end. Thanks.
The super loud ear-piercing jarring sounds at the beginning of the video are a nice touch!
Process always matters because the actual results usually happen after several iterations of other results. I love the ability to combine the quick sketch-like approach with a procedural one, so we can choose the level of "proceduralism".
Never used Modo but the interface looks well organised... and a good selection of intuitive tools.
But being creatures of habit... changing apps is not something that comes easy. Regardless... seems like a great program.
Thanks Andy glad you found a hires version.
Ooh! I did some of the concept art for that shot at 0:55. Neat to see it in the opening montage.
portfolio link?
Hey, is there any way to check non manifold vertexes and zero area faces in modo? something like Cleanup tool in maya?
Excellent presentation, Andy. (as always!) :)
Love that roof-tile magic
Thanks.this is the only word that can i say.
I actually like that your boss didn't care about the process. Too often in the past, jobs asked for a certain process or program, even if the same result can be had with other processes or programs. For the boss not to care would hopefully open the door for your favorite process.
I was able to bring my own copy to work and use it rather than use what they had.
I wish he showed the Mesh Ops tab so we could see a breakdown of the roof.
I have a few questions regarding the procedural text part. You plugged the percentage user channel value into the 'integer' input of the string compose. Adding it to the 'float' input returns nothing. Why is that? Can percentages only be translated to integers? What if you wanted to express a decimal percentage? Why does the rig only return a value of 0 and 1? Why not who values between 0 and 100?
It seems like percentage is its own construct? It's something you just need to know about which makes it difficult to figure out your own rig via logical steps. You were aware of the percentage variable's construct and then used the math node to essentially clean it? I'm not sure if i'm making sense. I guess my angle is, why not just start with an integer user channel value?
Andy.... you never say how you got the number driver value slider to pop up in the text primitive example... that's where this tutorial ends for me :( Usually, you're pretty good about saying what you are doing....
Anyone know how to do this? Thanks for your help!
Found it. It's the Channel Haul... keyboard: c
Curve Extrude is really cool, I was waiting for this tool since a long time. I saw that you can only apply this modifier to one curve index. Is there any way to make it apply to all the curves in an object. Is really time consuming to do it for each curve in the scene... Thanks
Thanks for the high-res version, much appreciated. A quick question, at 33:20 a "pattern" is entered into the String Compose node. This pattern is $[i:1] what does this mean? I can see the procedural system is very powerful, but if it relies on knowing such cryptic bits of code it is going to be quite difficult to use for non-programmers like myself.
Great video. I used the method in the train track section for duplicating the sleepers to create a necklace. That works great but now I am wondering if there is a way to change the scale of replicated meshes as they progress along the curve? In my case I want them to get bigger towards the middle of the curve and then return to the original size at the end. Thanks.
how u move node text number to viewport? what command?
Is there an account for Andy brown on Tweeter or Facebook?
compared to houdini is this proceduralism from bronze age.
The author too likes to smack one's lips and publish not the most pleasant sounds during the demonstration, you are an Englishman? or I'm wrong?
what a fucking bad resolution. this is a fucking joke. foundry.