It looks like you're new here. If you want to get involved, click one of these buttons!
putting together those tutorials I created eats up an enormous amount of time (no matter how I turn things, it takes me roughly about 1 hour per final minute of video).
I love doing it, because I am learning a lot along the way and I feel like I am getting closer to how I, personally, like tutorials to be. Which, obviously, is not what most people prefer - but without feedback on what you want to see (or hear?), I am lost to my own devices ...
So I would love to hear from you: Do you want me to record more tutorials, concentrate on specific areas? Do you want me to change something - in general or some detail (which may well be "use another narrator, different content, change editing, pace, length and resolution")?
I have a few ideas for further "introductory" videos, but the lack of feedback makes me think this is not what people want to see. I am using Fabric for some development experiments (avoiding the need to constantly compile/debug) as well - if there's considerate interest in following such experiments, I could record some of that (like using the "mesh painting" tool and improving it further, maybe integrating physics or whatever).
To me, Fabric already has proven to be a very valuable tool, given its stability and reliability when "pushing limits", allowing me to try things out, experiment without the environment crashing down on me. One of my current projects is creating a "destructive paint tool" for the Trollbridge movie - my vector math definitely isn't up to par for that yet, but Fabric provides the kind of "comfort zone" to learn what I need to learn.
This is what I would like to transport with my videos: Fabric is not a dumb "plug-in and get results-out" (though it can be used as such), but can adopt to the user's needs, it is flexible, yet consistent. I do think that modo can benefit greatly from integrating Fabric (not just to build KITs for procedural geometry creation, but for actual pipeline tools), yet, I just as well think that "the community" needs to see what can be done with this integration (in terms of different approaches/use cases) as well as how easy and straight forward it is.
Or not is: Could we, please, maybe discuss areas where people are seeing road blocks? Having issues with understanding how to solve a certain problem? Could we, maybe, share ideas for what Fabric could be used for?
Here's one: I am laboring with a modelling job right now, where I have to create a room based on CAD drawings. I do have a postscript file of the drawing, so I can extract lines/curves and convert those to 3d-ish geometry. For a single job creating a complex tool does not make much sense, but if this is a "typical job", why not create a "turn a CAD drawing into a 3d-scene" tool? By tagging lines with their required extrusion size, it should be quite easy to build such a tool in Fabric - maybe not providing 100% of the work, but if it can shave off 75% of the tedious "draw line to given length, extrude to given size, connect vertices" - this could be a perfect "use case".
What would you like me to tackle in tutorials - or would you prefer me to, finally, shut up? What are you using Fabric for (in modo or outside)? What are your reasons for getting on the beta-test-ship, as you must have had some ideas about what to use Fabric for? Are those expectations met or do you feel like Fabric is a dead-end (for modo)?
Marc Albrecht - marc-albrecht.de - does things.
©Copyright 2017 Fabric Software Inc. All rights reserved. | Privacy