Even I.....The KING of poor forum judgement, just spilled my coffee all over myself.

You got to love the net...reading that thread Radiance's FOUL language and attitude towards beta users...Oh well he just saved me some money and a lot of wasted time on testing his product :(

Wow, not good. I didnt buy a license, won it... but still.
Funny timing, this week in a course I am helping with,
we discussed the infinite memory of the internet and how things can come back and bite you.
A good example.

I installed the Demo today, because I was curious how fast an interior is rendered. The meshes from Rhino wasn't shown right and the scene navigation was difficult. I stoped my test. With mesh display problems the renderer is not useable.

Looks like Thea is the way to go with MoI... :-P

I'll give the demo a gander.

-Will

PS - Paq, that Car render (crinkles and all) with the wood attached at the back was hilarious!

Radiance should had understood that we're all just trying to make his product the best it can be - Michael was very helpful explaining how NURBS exports data, and how it should be properly used by a rendering app.

I hope Radiance takes a deep breath and reconsiders his stance on this - we're here to help him succeed not to stress him out as he seems to feel.

I agree that all other development should be put on hold until this issue is resolved however.

Taking the same model and rendering it in Thea and Octane should be proof enough, all personalities aside...

I think that these issues will be resolved eventually.

Please have patience and understand that it is on the radar and these example files will be a great help. I cannot confirm any timing with any further work in this area, but it is on the to do list (and it isn't the number 1 priority.)

Please sit tight, and by all means, try every demo of every render engine you can get your hands on. Then purchase the best one for your style and work flow. In the end, I hope that Octane will be every ones choice but understand that it will not be so.

Thanks for your patience and understanding in the issue.

Sincerely:

Phil Beauchamp

Maybe we can let this thread dwindle down now and get back to MoI discussions?

Otherwise poor Phil is going to be stuck in a loop having to apologize over and over again for something that he doesn't have direct control over.

- Michael

Yeah...like when can I fork over money for MOI3D Version 2.0!!!!

Pretty darn soon! :) This pesky documentation...

- Michael

How are those docs going, anyway? Have you begun the latin translations, or are you still working on the iambic pentameter? =)

I'm afraid I'm still stuck on the Aramaic at the moment... :)

One times more, Michael, you show us how serious you are.
You have a software almost bug free, but you don't start selling it just because of the documentation. I really admire your way of work. Thanks for that!

with so many new vis apps coming out i was about to invest in this even though i don't have a CUDA GPU. looks like i read this in time. Thea i'm testing atm and looks pretty good. i think in time it will become pretty powerfull, but somehow fryrender still feels the most professional renderer out there, with the best quality result, even though it lacks in areas.
hypershot and all the biased stuff out there just seems less and less enticing these days...
hey Michael, with all your spare time how about you make us an unbiased real-time renderer MOI style ;)

Hi all
Just to say the prob is solved. Radiance say:
<<we found the issue, it was a precision issue in the cuda kernel's normal interpolation/flipping.
fixed in upcoming 2.2.>>

That's good news. Maybe he'll put back the MoI logo on the home page :)

The new videos showing Octane ver 2.2 with dual GTX480 cards is impressive.

Ed

Hello,

He is just trying to cover himself now that the issue was cropping up with models generated in other applications. If Radiance is going to indicate true compatibility he needs to remove more logos, not add any at this point.

Looking good!

Here's a screenshot pf Micheal's previous "segmented cylinder"




Marc

That's a huge improvement Marc, that is now looking like it is supposed to!

So if that issue is fixed in Octane now, the only thing you should need to do when exporting from MoI is to uncheck the "Weld vertices along edges" option at export time.


Could you also try the single polygon file from here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=3472.40

What does that single polygon look like shaded in Octane now?

- Michael

Hi Michael,

This is a test image posted the developers on the octane forum, the beta will be out later this week.
Looking forward to test it!

Marc

Hi Marc, well it certainly looks promising!

- Michael