Public Voice Network
- FACE EATER 1616
- Prometheus 143143
- Pentagram: Forty Story 22
- Aging = Scary 1111
- Bilderberg 11
- alternatives to chrome?? 1111
- What are you listening to… 47024702
- Beeeees! 1212
- Minimum rate? 33
- blog 5626556265
- Chick of the Day 1538315383
- Outfit of the Day 33
- Coda 2 3636
- Show your latest Pics 32953295
- Vid of the Day 1203412034
- the gif animation thread 1283512835
- News of the day... 138138
- Battlefield 3 305305
- New York 88
- Pic of the Day 6330263302
- Music over 5.1 System 66
- Random Fascinations? 55
- What is THEIR work? 55
- Meme of the day 1414
3D App 1313 Responses
Last post: 2 years, 2 months ago | Thread started: Mar 15, 10, 8:39 a.m.
Out of context: Response #12 [Mar 15, 10, 8:39 a.m.]
- lukus_W
I like to think of each 3D application as a virtual workshop. You have a number of tools available to get the job done. The kind of basic tools that are available are the generally the same in most 3D applications.
In my opinion, mastering 3D is related to understanding and mastering a logical workflow. Getting the job done effectively, involves learning;
* which tools are available
* which methods are available to achieve your objective
* (and most importantly) which method is most appropriate in your individual circumstanceThis is the process you need to master, no matter which package you choose. I think it's beneficial to look behind the UI, and to try understand what you are trying to achieve - because this knowledge will allow you switch packages more readily if you need to.
The the main difference betweens applications is in the way the tools are _used_ and the way the tools are _laid out_.
Higher-end applications include tools which have been produced more recently -> as time goes by, these features are made available in the lower-end (cheaper) packages.


- View thread



