Modo 901 wish list ? :P
On 7 May 2014 00:08, Sergio Mucino <sergio.muc...@gmail.com> wrote: > I understand what you're saying Matt. My point is, though, that there may > be ways in Modo of accomplishing the same tasks that do not rely on the > existence of a modeling history I'm not undervaluing its presence, just > merely stating that there might be other ways of getting there. > After switching applications quite a few times, I've stopped thinking > about tools, and focusing mostly on tasks. Of course, I have come to > roadblocks from time to time, but you learn to drive (or sometimes, chew) > your way around/through them. > My $0.02... > > Sergio Muciño. > Sent from my iPad. > > > On May 6, 2014, at 6:07 PM, Matt Lind <ml...@carbinestudios.com> wrote: > > > > Under general modelling conditions, you're right in that most people > just freeze it anyway, but there are workflows that come into play where > you must have a construction history to employ. For example, primitive > retopology. > > > > You may need to do a primitive re-topologize. So you get a polygon mesh > grid and shrinkwrap it to the object you want to retopo. Although the > shrinkwrap operator has an option to use nearest vertices, you end up with > situations where the vertices on the grid collapse and target one or more > of the same vertices on the target mesh. No good. To fix the problem you > must move the shrinkwrap operator up the stack into the animation region > then use the movecomponent tool (or just translate subcomponent) to move > the points on the grid until they snap to a different vertex on the target > mesh. This works because your movecomponent operation evaluates first, > then the shrinkwrap evaluates with the vertex in its current location to > find the closest vertex on the target mesh. Simple example, but > illustrates the point. Also comes into play with enveloping and corrective > weighting. > > > > These are the kind of flexible workflows we lose by not having a > construction history. > > > > > > Matt > > > > > > > > -----Original Message----- > > From: softimage-boun...@listproc.autodesk.com [mailto: > softimage-boun...@listproc.autodesk.com] On Behalf Of Sergio Mucino > > Sent: Tuesday, May 06, 2014 2:57 PM > > To: softimage@listproc.autodesk.com > > Subject: Re: softimage to modo > > > > Honestly, I hasn't been a deal breaker for me. I found that I used the > history during modeling a lot less than I initially thought so (in > applications that have it), and always end up deleting it. > > For animation, I do think I'd need it, but if Modo has been capable of > delivering animations without it, it must just mean that it's done in a > different way. So far, I've just been rigging with it, but I'll jump into > more stuff soon, so I'll see how much I actually need it. > > I'm not closed to re-learning how to do things. It's just a matter of > seeing how difficult they actually become, I guess. > > > > Sergio Muciño. > > Sent from my iPad. > > > >> On May 6, 2014, at 5:23 PM, David Saber <davidsa...@sfr.fr> wrote: > >> > >> Ouch > >> Deal breaker. > >> No history in Modo, no history in C4D, that leaves us... > >> > >>> On 2014-05-06 21:16, Tim Crowson wrote: > >>> Nope, you're not doing anything wrong... there is no modeling history > of any kind in Modo. > >>> -Tim > > > > > >
