for the simple case above, the less you deal with scripts the faster/better you will get. at least in my experience i gotten lot better at eyeballing/accuracy and speed. i use scripts a lot, but not for simple things like that. i actually have fun doing simple things like that and dont want to script everything. sure the…
There are definitely things not worth the time to script, but I'll disagree because I think the above mentioned task of fixing topology on a particular type of layout is a PERFECT example that's worthy of scripting. I actually still use a few buggy ones I hacked together a long while ago to fix some of the typical…
well you are WRONG i would not "always" look for shortcuts i need to edit the ethic to: "dont always look for shortcuts" it is a judgment call. i would script something that would help in the long term and not just something i might need right now. things like the topology change above does not require a script. relying…
Yeah I was gonna say, I have no idea what Blaizer means by that. Are you saying it's somehow "more artistic" to make a character using sub-d poly-modelling instead of sculpting from a crappy base mesh or ZSpheres? Isn't the end result the only thing that's important, not how you got there? Does this mean that if you model…
What i've wanted to see for a while, and i dont know how realistic this would be, is a script that would run through a mesh and "smartly" quadify it, using intersections like pior shows.
I'm gonna go ahead and say you're doing it wrong - sure there are things that it doesn't make any sense to try and make a script for, but I have seen a huge amount of times when artists have been using painfully slow methods to do repetitive actions and just keep on doing it because they are used to it and refuse to…
that looks pretty scriptable so? it could work from just selecting the vertex in question, assuming you always have the 2 tris and 2 quads, the tris could be auto turned to quads like presented. or you work from the 2 edges selected as piors original gif. if you work on this on a single case basis, one could go so far and…
nice thread BUT, instead of posting exact work flow which can be a personal preference thing, i am going to post some work ethics which i follow daily: *don't be lazy *don't "always" look for shortcuts and try to make scripts for everything fucking task *don't try to over analyze art *when in doubt look up reference…
Hmm MM I would say there is even one more differentiation to be made. A technical guy can very well know all the tools of an app, but at the same time, not knowing how to use them properly in a modeling scenario. For instance I can go and ask a technical guy at work where to find the bevel tool of whatever app. He might be…