Weekly Dev update [12/5/2016]

[BK]

Hi everyone,


Thank you, for your inputs/feedback in our test builds.

Just a quick update...

Now, we are prioritizing smaller issues as all the major bugs have been fixed.

We have also been very busy to make this version stable.

The following is the changes since the 28th of November.

• ~Improved the virtual material consistency when rendered on different machines. This will work OK only in Maya versions starting from 2016, 'cause it uses some new functionality of it (the scenes must be saved from these versions too)~
  
  ~Reworked a way Octane UI is registered for AE, to eliminate conflicts sometimes with mentalRay etc.~
  ~Made Octane virtual materials to be consistent when rendered on different machines.~
  
  ~Improved material converter to support imported FBX case.~
  ~Minor fixes and improvements...~
  
  ~Implemented support of Maya's fluid "Auto-resize" feature. For those who uses it - the volume's wrong offset in some cases must be gone now.~
  ~Minor fixes and improvements...~
  
  
  ~New 3.04.5 rendering core integrated.~
  ~Fixed batch render bug.~
  ~Minor fixes and improvements...~

[calus]

Now, we are prioritizing smaller issues as all the major bugs have been fixed.

So issues in the internal converter/ORBX exporter won't be tackled soon ?
Or are they considered "smaller issues" ?

I can understand if reworking this part of the code is planned for later,
(for example planned for when ORC and Resuming will be implemented).
just let us know

[BK]

So issues in the internal converter/ORBX exporter won't be tackled soon ?
Or are they considered "smaller issues" ?

I can understand if reworking this part of the code is planned for later,
(for example planned for when ORC and Resuming will be implemented).
just let us know

hey calus,


ATM, our major goal is to focus on making Octane for Maya stable for everyone.
ORC and Resuming will be implemented as soon as we are done with few smaller bugs ##one step at a time.

[calus]

Oh I was not asking for ORC and Resuming, I'm all for stabilizing the plugin before implementing new feature.

But the ORBX exporter have a lot of major issues, and for some reasons fixing them doesn't seem a priority.
Too bad, because exporting to standalone is the only workaround we have when the plugin fail or doesn't support a feature.

So that's why I was asking when it was planned to begin to fix the exporter.*
And I was speculating that maybe a refactoring of the exporter is already planned for later, that could explain why it is not fixed now.



*one exporter issue have been fixed: particle "trail" bug.

[haze]

Sending you a PM, calus

[Jolbertoquini]

Hi Guys,

I have some comments about this...

~Improved the virtual material consistency when rendered on different machines. This will work OK only in Maya versions starting from 2016, 'cause it uses some new functionality of it (the scenes must be saved from these versions too)~

No doesn't work they maybe improved but still not working with Maya 2017 and higher. Still the same issue every time we save the scene as a new version the colour are changing.
Also rendered on Farm on different machines still not working gave us different result.
Is not a big deal we stop using this option because is no utility on production if they change for each version saved ex: scenes_v01.mb, or scene_v02.mb the colour should stay the same.
We use as before in house scripts to apply randomly shaders.

~Implemented support of Maya's fluid "Auto-resize" feature. For those who uses it - the volume's wrong offset in some cases must be gone now.~
~Minor fixes and improvements...~

Still a big problems with Scale special settings with fluids settings we can't use right if we use scene scale 0.01 to have the scene as "cm" on maya pretty standard on the industry every studio I worked before use this scale 1 maya unit = 1cm.
After changed this setting many option on the scenes doesn't respond correct as displacement, sss and we don't have enough range to be able to set the settings.
Same problem with export we have retouch many times this setting after export for the Standalone

~New 3.04.5 rendering core integrated.~
~Fixed batch render bug.~
~Minor fixes and improvements...~[/list]

[/quote]

Some people still have issues with batch render after some renders complete. I have to check my self but I had a little bug to.

For "ORC" I do not understand, we try to use also with Standalone and we are not aloud to connect and we try many times I wrote on the forum many times without any answer Otoy guys.
To be activated for us I did "call" and "mails". And still any answer about it.


So i think still a lot work on Maya to re-check on this features aswell fix old issues.
Best,
JO