OctaneRender™ for Blender 2.24.1 - 9.5 Win [OBSOLETE]

Blender (Export script developed by yoyoz; Integrated Plugin developed by JimStar)
justavisitor
Licensed Customer
Posts: 242
Joined: Sat Oct 05, 2013 5:34 pm

JimStar wrote: If rendering 5 vertices per hair instead of 65 presented by current versions of Blender is "correctly" and "without any problems" - then you know anything better than me.
Your "bug" have appeared exactly due to the reason this was fixed in last version and now renders the correct amount of hairs, children and vertices-per-hair presented by Blender in F12 mode.
Bottom line: If I understand you correctly, you have 'fixed' Blender's hair rendering by changing it in a way so it doesn't work anymore.

This doesn't make sense. You can't just suddenly change the rules in the middle of the game. What I used to get in my final render is now destroyed - and for no reason at all.

This means that a huge project I've been working on for months, using your software, now is trashed because you fundamentally changed the basic way hair rendering works, without any warning.

I can't even begin to understand how you can have so little respect for your customers and their work, or how it can look like a 'fix' to you, when it makes Octane entirely worthless for rendering existing projects.

And who would want to use it for future projects? Nobody knows when you're going to fix it again. :evil:
Latest OctaneRender for Blender. Windows 10, i7 quad 3.7GHz, 16GB, 2xTitan.
User avatar
afecelis
Licensed Customer
Posts: 188
Joined: Sun Jan 17, 2010 4:26 pm
Location: Bucaramanga, Colombia
Contact:

justavisitor wrote:
JimStar wrote: If rendering 5 vertices per hair instead of 65 presented by current versions of Blender is "correctly" and "without any problems" - then you know anything better than me.
Your "bug" have appeared exactly due to the reason this was fixed in last version and now renders the correct amount of hairs, children and vertices-per-hair presented by Blender in F12 mode.
Bottom line: If I understand you correctly, you have 'fixed' Blender's hair rendering by changing it in a way so it doesn't work anymore.

This doesn't make sense. You can't just suddenly change the rules in the middle of the game. What I used to get in my final render is now destroyed - and for no reason at all.

This means that a huge project I've been working on for months, using your software, now is trashed because you fundamentally changed the basic way hair rendering works, without any warning.

I can't even begin to understand how you can have so little respect for your customers and their work, or how it can look like a 'fix' to you, when it makes Octane entirely worthless for rendering existing projects.

And who would want to use it for future projects? Nobody knows when you're going to fix it again. :evil:
I think we're all aware of how difficult it is to keep the Blender integration updated and functional, even more when they keep changing its API with each new release. It's a very delicate balance that can be broken with the tiniest change, and even though Octane Render is no longer a beta, we have learned to cope with the fact that things that were working fine in Octane Blender in certain version, they might get broken in another one, but will get fixed at some point in the near future. From all the 3d programs that work with Octane Render, Blender is the most complicated to get integrated with due to its license limitations. JimStar is doing a hell of a job with each new release he offers us, and I bet he sometimes feels he's shooting in the dark in order to get certain features to work properly due to the lack of constancy in the ever-changing nature of blender.
If you're in the middle of a project then don't "change the saddle of your horse in the middle of the river", do it when you've finished it (the project). If worse comes to worse, go to the previous version that was working fine for you and deliver your work. I don´t think this is the way to demand getting a change done, or to report a bug.
Win10 Pro | Geforce GTX1070 8gb Vram X2 (display/render) | Intel Core I7 4770K 3.5GHz | 32GB DDR3 1600 Ram |Nvidia 378.78 drivers | Cuda 8.0 | Blender/Modo/Sketchup
justavisitor
Licensed Customer
Posts: 242
Joined: Sat Oct 05, 2013 5:34 pm

afecelis wrote: I don´t think this is the way to demand getting a change done, or to report a bug.
Afecelis, I'm a patient guy.

I'm not reporting the hair bug - I did that when JimStar first created it back in May:
viewtopic.php?f=32&t=47241&p=236839#p236839

I repeated it when it got worse in July...
viewtopic.php?f=32&t=49348

Another user, Balvarez, reported it in August...
viewtopic.php?f=32&t=49945

I mentioned it again on September 16...
viewtopic.php?f=32&t=50280

And I mentioned it again in this thread because it's worse than ever in the latest release...
Latest OctaneRender for Blender. Windows 10, i7 quad 3.7GHz, 16GB, 2xTitan.
User avatar
afecelis
Licensed Customer
Posts: 188
Joined: Sun Jan 17, 2010 4:26 pm
Location: Bucaramanga, Colombia
Contact:

JS, one question. I animated the visibility state of objects in the outliner but when I render the scene all of the objects show up (including the ones that should be off), it's not taking into account the visibility parameter. How can you animate objects on/off then? I was reading about blender layers vs octane layers. Blender layers are no longer animatable, is it possible via octane layers?

thanks,

Alvaro
Win10 Pro | Geforce GTX1070 8gb Vram X2 (display/render) | Intel Core I7 4770K 3.5GHz | 32GB DDR3 1600 Ram |Nvidia 378.78 drivers | Cuda 8.0 | Blender/Modo/Sketchup
amadinam
Licensed Customer
Posts: 17
Joined: Tue Oct 23, 2012 7:54 am

0.9.png
amadinam
Licensed Customer
Posts: 17
Joined: Tue Oct 23, 2012 7:54 am

no priority
1bmoVLQcy1X4ry.png
amadinam
Licensed Customer
Posts: 17
Joined: Tue Oct 23, 2012 7:54 am

vopros4.png
amadinam
Licensed Customer
Posts: 17
Joined: Tue Oct 23, 2012 7:54 am

vopros7.png
Locked

Return to “Blender”