Maya can be fine, (despite being ~3x as
memory hungry and still way more cumbersome comparatively )
with these steps indeed maybe indeed in a few years would it be a closer alternative. (if overhauling render layers, it's non-destructive framework? shapes workflow and other workflow-s-, and a still pretty big 'etc'.. ) But regardless, if already "forced" to use Maya, wait until rental-only kicks-in. Then prices could double again (or quadruple or whatever), and purchases couldn't be withheld without also losing the ability to function in the same move. What were you saying about inside the mouth of a crocodile? On 04/14/15 14:48, Sebastien Sterling wrote:
|
- Re: OT: Hypershade changes in Maya 2016 Andres Stephens
- Re: OT: Hypershade changes in Maya 2016 Ed Manning
- Re: OT: Hypershade changes in Maya 2016 Eric Thivierge
- Re: OT: Hypershade changes in Maya 2016 Leendert A. Hartog
- Re: OT: Hypershade changes in Maya 201... Eric Thivierge
- Re: OT: Hypershade changes in Maya 201... Raffaele Fragapane
- Re: OT: Hypershade changes in Maya 2016 Christoph Muetze
- Re: OT: Hypershade changes in Maya 201... Francois Lord
- Re: OT: Hypershade changes in Maya 2016 Leendert A. Hartog
- Re: OT: Hypershade changes in Maya 2016 Sebastien Sterling
- Re: OT: Hypershade changes in Maya 2016 Jason S