[Modo]modo 301 trial is available

[jbshorty]

Originally Posted by behzad

I could be wrong, but maybe most of the work in their gallery can be done with c6. DAZ needs to be more selective about their gallary.

They just display anything like caligari. You have got to show the best to attract new customers.

You could render the same scene in numerous render engines, all using equivalent settings. But they will all render differently. The fact is some render engines just have higher quality output than others do... Carrara's texture room is not an accurate depiction of how the object will render in the the final. But Modo's real-time preview is pretty damn close. It makes material/lighting setup incredibly fast. This has a big impact in achieveing the deired render quality. Certainly for me, it does. I never quite got along with C5. But Modo and I are pretty tight...

[behzad]

So i better start saving?

Maybe not, i came across this.

http://forums.luxology.com/discussio...20546&show=301

I think i stick to carrara. at least they are doing fixes.

[Wася]

They mostly talk about 203, it was really buggy indeed. 301 is more stable, but still misbehaves.

[jbshorty]

Originally Posted by Wася

They mostly talk about 203, it was really buggy indeed. 301 is more stable, but still misbehaves.

I've been using 301 (mostly for rendering) on average 40-50 hours per week for the last month or so. Crashes have been very few for me. Maybe i am just lucky...

[Wася]

I think, you and modo just well supplement each other. I'm not so lucky.

For example, I put two backdrop images, ajust transparency, put one(!) cube(!!) to a scene, go to "model quad view", en voilà - modo eats 50% of my CPU (2.66 Core 2 Duo) on every click. Of course, it does not happen when I use other backdrop images in other scenes. Even whith the same scene while I am in a "model" view, everything is okay.

[jbshorty]

Originally Posted by Wася

I think, you and modo just well supplement each other. I'm not so lucky.

For example, I put two backdrop images, ajust transparency, put one(!) cube(!!) to a scene, go to "model quad view", en voilà - modo eats 50% of my CPU (2.66 Core 2 Duo) on every click. Of course, it does not happen when I use other backdrop images in other scenes. Even whith the same scene while I am in a "model" view, everything is okay.

I always work in single model view. So i've never had such a problem. But i just tried your example, and Modo was fine. CPU usage was at 4% (on a dual core P4 3.6 Ghz). I had some problems in 203 caused by the VBO's. When i turned them off, everything ran fine. But now in 301 i can leave VBO's on and i have no problems. Have you tried turning them off?

[Wася]

No, I had not. And nothing changes after I did. In any case thank for advice, shorty.

However, as I said before, I have not this problem with similar scenes, so I did not expect you would reproduce this bug. I just demonstrated an example of strange modo 301 behaviour even in simple situations.

[isdnmodem]

The Demo charge is strange, but they sure have their reasons.

C6 render is good but I don't think it comes close to Modo's.

[Wася]

ok
They gave me $100 discount on uprade, and I did it
I hate myself. I hate them. I hate Christmas. I hate Father Frost. I hate you, shorty!

But, at least, they'd return me $50 for both the trial and seahorse tutor I bought earlier.

[jbshorty]

Originally Posted by Wася

...I hate you, shorty!...

Being hated is better than being ignored...

shorty

[Wася]

[mayito7777]

Merry Christmas and I don't charge for wishing you all Merry Christmas, it is free!!!

[jbshorty]

Originally Posted by mayito7777

Merry Christmas and I don't charge for wishing you all Merry Christmas, it is free!!!

It is official American policy to charge money for everything relating to Christmas...

[mayito7777]

Except saying it, hmmmm, got to double check that, maybe Wal-Mart is charging...