OctaneRender for Maya 4.02.1-13.36 [OBSOLETE]

[renmaxhb]

Not suport nparticle instancer?


why?

[calus]

Not suport nparticle instancer?

nparticle instancer is supported but with some bugs :

- support for instanced hierarchy is broken again :

Code: Select all

// Error: Octane: Error during translation of instancer "instancer1" (frame: 2) //

- Instanced objects needs to have octane materials applied BEFORE linking them to the instancer else they are invisible.

[Jolbertoquini]

Hi Jim,

Two question I'm asking for such a long time!

1. Why the demo is blocked now? why we can save the scenes anymore, when before we could.
2. Why is no support for Maya 2019 for Octane 4 Jules said we would still have support for Octane 4 why cut out Octane 4 and force the people to go to subscription?

Would be great to have the answer replied I have all company here to explain why that big change.

Cheers,
JO

[JimStar]

1. The DEMO versions are not intended to be used in commercial workflow. Their only purpose - to show "how it works" to newbies who is trying to decide whether to purchase it. And the "Project and render output cannot be saved" is stated on Otoy's DEMO-page. It has never been stated that Otoy offers the complex (and expensive in development) Octane project's nodegraph functionality for plugins' commercial workflow for free. If you need this functionality for the commercial workflow - it is fair to pay for all the development of it by buying the commercial license for this workplace. If you don't need it in some parts of your workflow - just uninstall the DEMO plugin there, and you are free to save any opened scene (with no support of Octane nodegraph of course).

2. Already answered https://render.otoy.com/forum/viewtopic.php?p=356122#p356122.
"Support" means fixing bugs, not continue the active development adding new big features making the stable production-suggested release completely broken again (and Maya 2019 has already brought a lot of issues into the 2018.1 branch, some of which are unsolvable currently 'cause these are Maya's brand-new internal bugs). So - yes, the support of version 4.X in regard of maintaining its stability will be continued.
Version 4.X branch has the feature-set you've paid for when you bought it, plus many free additions on top of that set. The development of any other new features is only happening in current new branches (with Bifrost support being the next big one). If you had a subscription - this would let you automatically get any new features implemented in upcoming major releases...

Thank you for understanding.

[calus]

Version 4.X branch has the feature-set you've paid for when you bought it

Version 4.X is still for sale now, so it would make sens to support the current Maya version.
Regardless of technical considerations you should be careful not to underestimate the impact of your decision to not support Maya 2019 with the V4 plugin,
as this may seem unfair and not in the Otoy spirit.

[nedan]

Version 4.X is still for sale now, so it would make sens to support the current Maya version.
Regardless of technical considerations you should be careful not to underestimate the impact of your decision to not support Maya 2019 with the V4 plugin,
as this may seem unfair and not in the Otoy spirit.

I definitely agree with Andre!

[Jolbertoquini]

Version 4.X branch has the feature-set you've paid for when you bought it

Version 4.X is still for sale now, so it would make sens to support the current Maya version.
Regardless of technical considerations you should be careful not to underestimate the impact of your decision to not support Maya 2019 with the V4 plugin,
as this may seem unfair and not in the Otoy spirit.

I agree to doesn't make sens.

[Jolbertoquini]

1. The DEMO versions are not intended to be used in commercial workflow. Their only purpose - to show "how it works" to newbies who is trying to decide whether to purchase it. And the "Project and render output cannot be saved" is stated on Otoy's DEMO-page. It has never been stated that Otoy offers the complex (and expensive in development) Octane project's nodegraph functionality for plugins' commercial workflow for free. If you need this functionality for the commercial workflow - it is fair to pay for all the development of it by buying the commercial license for this workplace. If you don't need it in some parts of your workflow - just uninstall the DEMO plugin there, and you are free to save any opened scene (with no support of Octane nodegraph of course).

2. Already answered https://render.otoy.com/forum/viewtopic.php?p=356122#p356122.
"Support" means fixing bugs, not continue the active development adding new big features making the stable production-suggested release completely broken again (and Maya 2019 has already brought a lot of issues into the 2018.1 branch, some of which are unsolvable currently 'cause these are Maya's brand-new internal bugs). So - yes, the support of version 4.X in regard of maintaining its stability will be continued.
Version 4.X branch has the feature-set you've paid for when you bought it, plus many free additions on top of that set. The development of any other new features is only happening in current new branches (with Bifrost support being the next big one). If you had a subscription - this would let you automatically get any new features implemented in upcoming major releases...

Thank you for understanding.

Hi Jim,

For the "demo" before was working we could save the scene.

We are not using commercial the demo because of the watermark and limitations. so why lock the demo plug to save scenes now! This is what I don't understand any render engine you can save the scene on demo version. I totally understand to block render resolution output and watermarks. Cause a lot workflow we have here on the studio for Animator who doesn't use octane plug for actually lighting or other thing is just to keep shaders save and be able to preview in case of problem with references.... To us is a waste of money to buy a entire license just for that, also is already complicate to change right now to subscription due the fact we will need to expend much more money then before to update the big amount of licenes we have from OTOY, to update farm, lighting artists, lookdev and now "apparently" Animators.

Hope you Guys understand our point of view here we are not trying to stealing licenses but to have a basic setup on the workflow we already have with Arnold and Redshift.

Cheers,
JO

[Vyoor]

Hi!

Some issues:

Particle instancers which are not on top of hierarchy are not visible in render.
Problems with render setup or legacy render layers - some objects are not visible in render. Sometimes removing from layer and assigning again works, sometimes not.
Animated parameters of shaders are crashing batch render randomly.

Cheers!

[JimStar]

Vyoor
Please attach the scene where you have the issue, with description of what exactly is wrong there...