All right guys - I split off all the Octane posts to a separate thread here and please lets just let it die off instead of continuing into a flame war. The Octane forum would probably be a better place to have this discussion.

- Michael

Well, if anything, it put Thea Render at the top of my renderer consideration list. ;-)

Hello,

Yhwh, someone interested in coming to the root of a problem would gather as much information about the settings as possible, not throw up an image using a different material and mesh density to deflect criticism, that's hardly a "solution". So yes, whether intentional or not your example was not honest, and your response to being called out confirms your true intent. Your thoughts on me being a troll are immaterial to the discussion, background noise, and do not explain the problem that Octane Render has, it's just another attempt at deflection.

You seem to keep forgetting Octane is still a beta product, and as I have said before these problems are expected in beta software. An Octane developer did request the test file, it was provided promptly and there was no response either publicly or privately afterward from the developer. It makes sense from a development and commercial point of view that an explanation be given if it was a problem with the model. I did not receive any statement from the developer to that effect. The "response" from the developer was a request for further information to investigate the matter, I think anyone would agree that is not a solution explanation.

By the way, creating the same scene in modo 501 sp4 gives a similar faceted result in Octane. I created a cylinder primitive, created a plane for the floor and and a plane for the backdrop, and export to OBJ. The problem is repeatable and consistent. If you choose to ignore it I have no problem with it, but others might. I typically like to give my impressions of products, whether good or bad, especially when those products involve someone parting with their hard earned money.

While you think it is insane to pay $2K for a renderer, $140 may be just as serious to those without many funds. I don't think someone would be too happy with this result if they encountered the same result, with no explanation from the developers and an unsatisfactory "solution" from users that masks, rather than fixes the problem.

On a different note, I apologize for the thread hijack Magic and MG.

Hi OSTexo,

I feel your pain about Octane, I was having some really hard time to resolve basic vertex normal trouble last year.
Taking one week to proove that :

- No my model is not wrong (as it render right in many other renderer)
- Yes I know what I'm doing
- No MoI is not doing anything wrong.

Then, only, they slowly accept the idea that something was wrong in Octane.
They tried to fix it the wrong way first (using smoothing group), and claim everything was ok now.

At that time I was really upset :P so they manage to kick my ass from the forum,
and my licence was refund. So pay attention how far you are ready to go when complaining, as they
are not always open, and emotive like a teenager.

About the product itself, Octane is really great for product shot ...

but ...

- it's buggy and easy to crash (beta beta)
- not that fast if you are after a clean final image (grain, aliasing)
- so many features missing compared to a 'cpu' renderer
- you need a second gfx card if you expect to use your computer while rendering
- you need an active internet connection to use the software.

Hello,

PaQ, I'm sorry to hear that, hopefully you found a renderer that would fit your workflow more appropriately. I invested in both Thea and Octane, they were inexpensive enough for my budget and I thought there might be room for both of them in the toolbox. I have to say I am really happy with Thea, and although it is slower I have a much higher degree of confidence that it will continue to deliver the great results.

I think I got my answer by not getting one from the Octane developers. In a broader sense, people usually invest in perceived value more than actual value, and I believe it is absolutely critical to know this when releasing a product into the market. Certain companies are acutely aware of this, and others are not, and the ones that aren't usually end up in a worse spot than those that do. I never understood the thinking behind not responding to these sort of support requests corporately, rather allowing end users with no involvement in development or vested interest in the financial well being of the corporation speak for the company. It certainly is cheaper to do it this way, but it leads to a highly distorted view of what the real market is looking for and doesn't end well.

Hi

OSTexo,
You send to Octane a CAD obj made in MoI converted to poly .obj
and as in 99% of cases (!) the prob appear when converted to poly

In the case of "vase.obj", I showed you the prob after conversion: duplicate vertices (not some but hundreds!), edges weld,...
I showed you with screenshots made from Thea that prob appear in Thea too, and how Thea (try to) solve it transforming itself the object

The most important for all is not only to criticize an application (here Octane)
when/if a prob appear but to understand how and why and solve it.
Im sure you can solve your problem only by different export setup
just send us the MoI file and we try to help you.

Its just to understand, not against you or your work or Octane

all the rest depend of mood (or testosterone rate, or day time, or...)

ps: hope my english is good enough to calm you all

Hello,

Ycarry, a logical step in this troubleshooting process is to investigate as many possibilities as reasonable and then come to a conclusion based upon the data available.

I didn't see a problem in Thea or modo with the vases or the cylinder, even on close inspection, I'm not tweaking anything in those applications to compensate. The fact that I simplified the object indicates that I wanted to see if the problem was with a complex model. The teapot example that was given on the Octane forum had horrible distortions when rendered in Octane. Increasing subdivision does not solve the problem, the distortion is still there when you zoom in. It is ironic that the teapot image was given to counter the assertion that there was something wrong with Octane in processing the geometry. If you think MoI does bad exports then you must also think modo exports bad geometry as well, since that geometry has the same faceting problem. You do realize companies buy MoI on the quality of the export alone, and I think the Luxology would have some real big problems if they didn't export OBJ correctly given their pure modeling foundation.

I took the time to go through a logical measured process to eliminate problem sources. It is an Octane problem, not MoI, not Thea, not modo. The only one that doesn't play nice is Octane, it is a repeatable and consistent issue, It is acknowledged by a set of licensed users of Octane even on the Octane forums. You can see evidence of it in transparent images on the Octane forum. I guess the real issue here is being able to acknowledge that Octane is a beta product with bugs. I'm not knocking the software, I'm knocking the denial on the part of the developers and some of the users, by not acknowledging the problem you end up hurting it.

Lastly, I don't take offense at what your saying, some people get highly emotional about products, I'm not one of those people.

> ...some people get highly emotional about products, I'm not one of those people.

No, you are getting highly emotional about people not seeing the world like you do. You care a f*ck about the product, but you can't stand that not everybody is like you.

Go seeing a doctor.

Please ...
Let's don't use this forum for personal stuff ... particularly attacks on others.
take a deep breath and enjoy the moment.
eric

Thread closed - please take any further discussion on this to the Octane forums.

- Michael