OTOY Forums

aLeXXtoR wrote:

alien wrote:But people invest time in a product as well & have to keep up with time / technology.
If that is the case V2 is slower then V1.5 then price should be decreased not increased.
THE WHOLE POINT OF OCTANCE RENDER WAS SPEED.

Man, truly they owe you nothing — it was our choice (yours, mine, all others) to invest our time and money to this product. We're not stockholders, OTOY investors etc. We're just buying it as is (and hope that it will get better — and it gets for me). Or we not. That simple. Peace.

I agree they otoy owe me nothing But logically they are producing octane for customers like us. If we have concerns, we should let them know & they should try to address them. For example Autodesk Flame was amazing piece of software but now even with huge price cuts they are struggling to get new customers as most of them switch to nuke. So I personally think customers are more important then stockholders

Seekerfinder wrote:

alien wrote:If that is the case V2 is slower then V1.5 then price should be decreased not increased.

Perhaps you're not aware that Octane is one of the most reasonably priced renderers out there - still.

Seeker

I am fully aware of that fact. because I am planning to buy it. I have to choose between Redshift 3 (500$) or Octane+C4D (621$) ... Octane have benefit of having C4D plugin But Redshift plugins for DCC will be free.

So been trying to use hair and fur in v 2.0 but I'm guessing it
does not work yet as I cannot find any information on how to do this,
can a developer shed any light on this,

I'm using blender and have the plugin,

regards

daveyt wrote:So been trying to use hair and fur in v 2.0 but I'm guessing it
does not work yet as I cannot find any information on how to do this,
can a developer shed any light on this,

I'm using blender and have the plugin,

regards

The integrated plugin doesnt use 2.0 yet, so you have to wait. Also, I don't think you can use the alembic export yet to get it to standalone because I don't think the current alembic exporter exports that data. I don't know though.
It seems to be one of those features that exists, but you can't really use yet.

Yep, the Blender plugin users need to wait a bit for the 2.0 enabled plugin, I'm looking forward to it as well. Jimstar said that he is working on the Maya plugin right now and will direct his attention to Blender after it's done. He did say as well that the Maya plugin should not take very long.

kavorka wrote:

daveyt wrote:So been trying to use hair and fur in v 2.0 but I'm guessing it
does not work yet as I cannot find any information on how to do this,
can a developer shed any light on this,

I'm using blender and have the plugin,

regards

The integrated plugin doesnt use 2.0 yet, so you have to wait. Also, I don't think you can use the alembic export yet to get it to standalone because I don't think the current alembic exporter exports that data. I don't know though.
It seems to be one of those features that exists, but you can't really use yet.

Thanks for the information, Wish this was made more clear!!

To everybody who tried out the demo version and was disappointed by the speed: One thing I totally forgot is that in the demo version by default the "use priority" option is enabled for all GPUs and I think the render priority default is set to "low".

-> Make sure that you either disable the "use priority" option in the CUDA device settings or set the render priority to "high".

This will probably not make up all speed loss, but improve things. I also would like to note that we found one problem in the geometry compilation, which we are currently trying to fix. We found this problem with a scene Dom74 sent to us. -> If you have some scenes with dramatic speed losses, please send them to us. There is a chance that there are more issues hiding.

abstrax wrote:To everybody who tried out the demo version and was disappointed by the speed: One thing I totally forgot is that in the demo version by default the "use priority" option is enabled for all GPUs and I think the render priority default is set to "low".

-> Make sure that you either disable the "use priority" option in the CUDA device settings or set the render priority to "high".

This will probably not make up all speed loss, but improve things. I also would like to note that we found one problem in the geometry compilation, which we are currently trying to fix. We found this problem with a scene Dom74 sent to us. -> If you have some scenes with dramatic speed losses, please send them to us. There is a chance that there are more issues hiding.

Thanks for your continual efforts Octane Team - there's a lot of appreciation for your work!

Dear Otoy, now that a lot of people are talking about speed, I was wondering if you have more feedback on when we will be able to use the Cloud Edition?

Goldorak mentioned that it will (later on) be part of the 2.0 version (http://render.otoy.com/forum/viewtopic.php?f=7&t=29544&start=100#p177383).

Maybe there's a small speed decrease of 15% here and there, but with the Cloud Edition as demonstrated in one of your video sessions huge speed increases are to be expected. Which would be impossible I guess with renderers as corona or the likes (1 minute vs 90 minutes).

Btw, I have bought an additional nvidia card to celebrate your 2.0, so for me this version actually has an overall speed increase of about 33%! #differentperspective