OctaneRender_for_Maya_4.0RC2_-_13.5-Beta [ OBSOLETE ]

[BK]

Hi Joss,

Thank you so much for reporting these issues. Here is the quick response outlined below.

1. Material attributes are getting 'stuck' at some point: user can change the values in AE,
but the next time you press 'load attributes' button or reselect the node - all changes are gone.

- This issue has been resolved in the Stable release [ viewtopic.php?f=109&t=68758 ]. We are currently working on V4-RC4 and will be available soon.

2. I hope current version of AE templates is a 'test version' or something, because right now AE layout is a mess,
can we use just Maya standard combination of 'color swatch - slider - texture plug' in AE?

All the AE controls are in log space, to create rubber material, diffuse's Value needs to be set to 0.001..

As I understand, textures are also affected by this, so, spec texture that can be used in VRay/Redshift/Arnold/Maya SW
has to be converted or reformatted somehow to fit the Octane pipe(not sure here, but had to fight with speculars today)

Didn't find the thin glass option on

- Changing the AE layout cannot be done at this stage as there are many restrictions with Maya API itself. The plugin uses the best that it can squeeze out of current Maya APIs.
We have plans to improve the Octane material converter sometime in the future releases.

3. I think some color spaces are off, had to set jpeg diffuse texture gamma to 4.84 to get normal look.
Dome lights using Image texture node that by default thinks that HDRs have 2.2 gamma.

- Check if Maya default color management is enabled? Try Turning off the blue button from the Render view.

4. Maya render view is meh, do we have any other option?

- We have a feature request ticket to implement Octane render view. It would take some time to do RnD to implement this.

5. Camera changes are not triggering the update: cam position, focus distance - have to press 'reload' button in render view to see the changes.

- Cannot reproduce this issue. can you please share a sample scene or steps to replicate?

6. Couple of times Maya got stuck in the 'render mode', when it was impossible to stop the render, and it was consuming the resources all the time.

- thank you!! Do you mean Maya's "Render Current Frame"? If yes, Maya has no API to stop the Render current frame, the only way is to set the Samples lower.

7. Is it possible to get/set Octane attributes with mel/python?
node.FilmWidth
# Result: Attribute(u'octaneGlossyMaterial2.FilmWidth') #
node.FilmWidth.get()
# Error: The data is not a numeric or string value, and cannot be displayed. #

- Try using

Code: Select all

octane -help

in SE MEL console. It shows the commands you need to get the internal value of Octane attribute. For example:

Code: Select all

octane -gpf octaneGlossyMaterial1.FilmWidth

But be aware that this only works for the texture plugs that have the default built-in value (not connected to anything). If your plug is connected to some Octane texture - then you already need to ask the values of plugs of this connected texture, not of the plug to which it is connected.

8. RenderView pop-up after each render asking if I "want to save renderState or not".
Can we go without popups after each render? Like with some checkbox somewhere or such.

- Try to increase the "State save threshold(min)" value to avoid the pop-ups.

PS: And is it just to me 'universal shader' looks not that universal?
I mean I would love to just have 1 shader with typical diffuse/reflection/refraction/ior/opacity/sss/coat/bump/displacement/illumination
parameters/textures in a compact slick UI.

- Thank you for the idea, we would forward this request and see if these can be implemented in future.

[Jolbertoquini]

Hi Bikram,

Can we have a update matching the dev for OC4 please we need RC4 and keep up with the dev, because then the all point to develop a beta is to be ready for the release not late which time there is a new standalone version.

Soon will be release a OC4 and we still have a plug not complete as Beta or Stable. Would be good to have more activity on the Maya Plug for that, I understand is a task who takes time but we need be more proactif to get some where this what I think.

Cheers,
JO

[BK]

Hi Bikram,

Can we have a update matching the dev for OC4 please we need RC4 and keep up with the dev, because then the all point to develop a beta is to be ready for the release not late which time there is a new standalone version.

Soon will be release a OC4 and we still have a plug not complete as Beta or Stable. Would be good to have more activity on the Maya Plug for that, I understand is a task who takes time but we need be more proactif to get some where this what I think.

Cheers,
JO

Hi Jo,

Thank you for your suggestion.

Please find the OC4 here [ viewtopic.php?f=109&t=68813 ]

cheers

[Joss]

1. >>- This issue has been resolved in the Stable release [ viewtopic.php?f=109&t=68758 ]. We are currently working on V4-RC4 and will be available soon.

There's still a problem, I'm not sure if that's related just to old scenes or to all of them:
when I'm opening the scene from 13.5, rubber material's diffuse set to 0.001(one I mentioned before),
but AE shows that color slider is set to the middle value (0.5 or so).
(see pic)


2. Changing the AE layout cannot be done at this stage as there are many restrictions with Maya API itself. The plugin uses the best that it can squeeze out of current Maya APIs. We have plans to improve the Octane material converter sometime in the future releases.

But it's done already by multiple other vendors? Arnold, Redshift, Mental Ray, etc.
See the pic, at the left there's standard Lambert UI, at the right - Octane shader.
Fence of empty useless fields doesn't make it easier to read all that stuff.


3. - Check if Maya default color management is enabled? Try Turning off the blue button from the Render view.
Yep, I had sRGB profile set. Guess there's some double conversion happening somewhere, or I'm doing something really wrong.


4. Camera changes are not triggering the update: cam position, focus distance - have to press 'reload' button in render view to see the changes.
>>- Cannot reproduce this issue. can you please share a sample scene or steps to replicate?

https://www.youtube.com/watch?v=7g6itVgYyFo

5. >>Do you mean Maya's "Render Current Frame"? If yes, Maya has no API to stop the Render current frame, the only way is to set the Samples lower.
Ehm, do you mean that after render is started, there's no way to stop it in current Maya session?


6. >> octane -help
>> octane -gpf octaneGlossyMaterial1.FilmWidth

.FilmWidth is a simple float value, any reason it's implemented that way?
It's basically making Octane Render completely incompatible with native Maya workflows.
I mean - I can't use standard ways to query Maya node values...

Same for RenderGlobals: imagine you need to set all these 'kernels', 'imagers' using script.
Now I'm not even sure how to do that.

PS: All of that still a problem in 13.7 btw.

[BK]

Hi Joss,

1. Could you please PM us a sample scene to investigate, we just need the Diffuse applied in any Maya primitives?

2. We would request if the UI can be redesigned and give you update.

3. My apology for the confusion, I should have said "Disable" Maya's Gamma correction like this

2018-09-25 18_09_31-Render View.png (1.77 KiB) Viewed 1812 times

Then create an Octane Imager node, set the Response curve to Linear/off and Gamma as 2.2 and see if it works.

4. Try clicking the "Go to start playback range" or the rewind button. This will be fixed in the next release.

6. We will check on this >> octane -gpf octaneGlossyMaterial1.FilmWidth further and get back to you ASAP.

cheers