Deciding to learn a modeler...is it better to invest time in Hexagon or Blender?

Richard Haseltine

rsharp said:

kyoto kid said:

Modo was next that i really liked, but that began to become too expensive an option, particularly as it gravitated from primarily being modelling software to a full feature programme like 3DS.

I just couldn't get into modo.  I could get past the UI, but it has horrible bugs.   One was that I clearly had a single object selected, subdivided it, and it subdivided a different object.   When painting one object, it automatically applied that texture to most of the objects in the scene.  I couldn't figure out what it was doing.

As with most software trials, I put them away for a bit and come back in a few days.   In all cases though, I continued to have bad experiences in not only modo, but Blender.  They could be bugs, or they could be that their workflows are just not for me.    Complete opposite experiences have been Cinema4D.  Alas, the most expensive option though if I pursue it.

Back to modo... I was really hoping it would have worked out.  While expensive (up-front and yearly maintenance), it is 55% the cost of Cinema4D Studio.  While there are cheaper versions (e.g. C4D Broadcast), they don't have key features.   But, one also has to look at productivity (and ultimately throughput) of the software.  So even at a higher cost, if C4D allows me to crank out output at double-the-rate over modo, then it would pay for itself.

In modo a texture, or anything else, aplies to everything below it in the Shader Tree unless masked or grouped to apply to only certain things. Heer I added a new image and painted on it, the paint affected both models. Then I assigned a material to the sphere and dragged the map into a group set to apply to only that material.

wolf359

I have an old seat of modo 401 Love the modeling tools and the render engine. However the "shader tree" appears to have been designed to literally punish the user...I truly hate it.

kyoto kid

rsharp said:

kyoto kid said:

Modo was next that i really liked, but that began to become too expensive an option, particularly as it gravitated from primarily being modelling software to a full feature programme like 3DS.

I just couldn't get into modo.  I could get past the UI, but it has horrible bugs.   One was that I clearly had a single object selected, subdivided it, and it subdivided a different object.   When painting one object, it automatically applied that texture to most of the objects in the scene.  I couldn't figure out what it was doing.

As with most software trials, I put them away for a bit and come back in a few days.   In all cases though, I continued to have bad experiences in not only modo, but Blender.  They could be bugs, or they could be that their workflows are just not for me.    Complete opposite experiences have been Cinema4D.  Alas, the most expensive option though if I pursue it.

Back to modo... I was really hoping it would have worked out.  While expensive (up-front and yearly maintenance), it is 55% the cost of Cinema4D Studio.  While there are cheaper versions (e.g. C4D Broadcast), they don't have key features.   But, one also has to look at productivity (and ultimately throughput) of the software.  So even at a higher cost, if C4D allows me to crank out output at double-the-rate over modo, then it would pay for itself.

.what version fo Modo?  I was looking at 301 when it was still more of a modelling programme.