OTOY Forums

10 days.
5 since replying to bepeg4d.

preciousillusion wrote:10 days.
5 since replying to bepeg4d.

I was out of the office last week. I will try reply to your earlier post in further detail once I have a chance to review it and see if I can add anything useful beyond what Bepe has posted.

Please keep this topic focused on Octane. Octane is not Cycles. Cycles' scaling/GPU usage metrics are not the same as Octane's. An arbitrary tax that is added to an otherwise free/OSS render slave node license isn't helpful in determining how we price commercial slave licenses (other than understanding that people would like this to be free if possible). Cycles is of course also free in Blender, but we still have to sell Octane -> Blender licenses at the the same pricing as our other plug-ins to justify development and support (it's in fact more work than any other plug-in). We continue to do well with this model, with the understanding that we need to be continuously addressing the cost/value of Octane as commercial software relative to free/built in options.

Have you had a chance to review the render job system we are working on in the core engine? That is designed to let the host app group multiple outputs into distributed workloads across multiple servers, which can be queued both on your local and cloud render jobs.

Goldorak wrote:

preciousillusion wrote:10 days.
5 since replying to bepeg4d.

I was out of the office last week. I will try reply to your earlier post in further detail once I have a chance to review it and see if I can add anything useful beyond what Bepe has posted.

Please keep this topic focused on Octane. Octane is not Cycles. Cycles' scaling/GPU usage metrics are not the same as Octane's. An arbitrary tax that is added to an otherwise free/OSS render slave node license isn't helpful in determining how we price commercial slave licenses (other than understanding that people would like this to be free if possible). Cycles is of course also free in Blender, but we still have to sell Octane -> Blender licenses at the the same pricing as our other plug-ins to justify development and support (it's in fact more work than any other plug-in). We continue to do well with this model, with the understanding that we need to be continuously addressing the cost/value of Octane as commercial software relative to free/built in options.

Have you had a chance to review the render job system we are working on in the core engine? That is designed to let the host app group multiple outputs into distributed workloads across multiple servers, which can be queued both on your local and cloud render jobs.

Cycles4D was one of several renderers mentioned and probably got most attention since it just got released.
I also mentioned Thea for example, which for my 30 clients example would actually be even cheaper than Cycles. By the way, Thea supports a total of 256 concurrent gpus.

You might think that comparing with Cycles isn't helpful but inevitably that's something you can't escape from.
I haven't tried Cycles but it looks like it supports roughly the same features as Octane. If speed and quality is comparable then users will see:
Two equal products, one of them at only a fraction of the price, includes free nodes and offers significantly better expansion options. Add to that Otoys withering reputation and increasingly big pile of problems.
Why would a potential customer choose Octane?

Regarding render jobs system; where's info on that?
But the main thing is that I already have a pipeline. I don't want a separate one for Octane and I absolutely don't want my main workstation to host, handle or have anything to with batch rendering except for acting as an extra slave when not used. I have a dedicated server for that with redundant power, disks, network and nothing but C4Ds Team Render Server and plugins installed.

Hi preciousillusion,
sorry but I have to find the time to recover a PC in another town to make a direct test with a mix of Team render and Octane Network rendering and mixed works c4d standard + c4d render jobs. I will back to you with a direct example test asap.
all the best,
ciao beppe

bepeg4d wrote:Hi preciousillusion,
sorry but I have to find the time to recover a PC in another town to make a direct test with a mix of Team render and Octane Network rendering and mixed works c4d standard + c4d render jobs. I will back to you with a direct example test asap.
all the best,
ciao beppe

None of the issues with your approach needs testing to confirm, Team Render Server does not have a way to specify clients used for specific job. And even if it did there's a risk of forgetting to specify or selecting wrong clients.

For render times you only need a calculator.

Hello,

1) 400$ for one slave I think is to much, I felt the needed to purchase one days ago.

2) "Render one frame per system" option is necessary, in order than Octane it would be affordable for render farms. I'have also tested Orc beta and right now is very confuse. Even if you push the button "send to orc" in Cinema 4D, you need to setup the whole render settings in the website... This integration is far behind of other options like rebus farm plugin, that analyze incompatibilities and errors and send the scene/start with one click, also is automatically downloaded.

I think right now Octane for C4D is a risk if you need to render long scenes in short deadlines. Buying one standalone per slave is expensive, but buy one standalone and one plugin per slave to enable one frame per system has no sense.

However, I think Octane is the best GPU solution for rendering still images or short scenes.

JavierVerdugo wrote:Hello,

1) 400$ for one slave I think is to much, I felt the needed to purchase one days ago.

2) "Render one frame per system" option is necessary, in order than Octane it would be affordable for render farms. I'have also tested Orc beta and right now is very confuse. Even if you push the button "send to orc" in Cinema 4D, you need to setup the whole render settings in the website... This integration is far behind of other options like rebus farm plugin, that analyze incompatibilities and errors and send the scene/start with one click, also is automatically downloaded.

I think right now Octane for C4D is a risk if you need to render long scenes in short deadlines. Buying one standalone per slave is expensive, but buy one standalone and one plugin per slave to enable one frame per system has no sense.

However, I think Octane is the best GPU solution for rendering still images or short scenes.

Your mistake is that not doing a test in Standalone for exported ORBX. Render results will be same on ORC vs C4D. But you should check some frames in Standalone before sending to ORC.

aoktar wrote:

JavierVerdugo wrote:Hello,

1) 400$ for one slave I think is to much, I felt the needed to purchase one days ago.

2) "Render one frame per system" option is necessary, in order than Octane it would be affordable for render farms. I'have also tested Orc beta and right now is very confuse. Even if you push the button "send to orc" in Cinema 4D, you need to setup the whole render settings in the website... This integration is far behind of other options like rebus farm plugin, that analyze incompatibilities and errors and send the scene/start with one click, also is automatically downloaded.

I think right now Octane for C4D is a risk if you need to render long scenes in short deadlines. Buying one standalone per slave is expensive, but buy one standalone and one plugin per slave to enable one frame per system has no sense.

However, I think Octane is the best GPU solution for rendering still images or short scenes.

Your mistake is that not doing a test in Standalone for exported ORBX. Render results will be same on ORC vs C4D. But you should check some frames in Standalone before sending to ORC.

So we have to test in a second application if a feature that's supposed to work in the first application, actually works in the second application, and if it does it should work in the first application?

Since this is going effectively nowhere I'm gonna repeat one of the countless questions Otoy has ignored.

If no news, or from the customer's perspective, bad news:

How do I transfer my credentials to someone else if I sell my copies of Octane? If I sell all of them I can just change the login email, but let's say I want to keep one?

That sounds interesting preciousillusion, I hope they can give you an answer soon