Weekly Dev Update [04/04/17] Tweet

[BK]

Hi guys


Thank you all for the bug reports in the forums and on skype group. We really appreciate your contribution and help.
Here is our quick weekly development progress overview.


OctaneRender for Maya 3.06 (test 3) - 10.11 [OBSOLETE]

CHANGES SINCE THE PREVIOUS VERSION

Implemented volumes support in Octane animated scene export ("alembic inside" mode).
Animated visibility support in the ORBX exporter
Other fixes and improvements...


OctaneRender for Maya 3.06 (test 4) - 10.12 [OBSOLETE]

CHANGES SINCE THE PREVIOUS VERSION

Implemented 3.06 TEST 4 engine support.
Minor fixes and improvements...


OctaneRender for Maya 3.06 (test 4) - 10.13 [OBSOLETE]

CHANGES SINCE THE PREVIOUS VERSION

Lowered the min. value for adaptive exposure setting.


OctaneRender for Maya 3.06 (test 4) - 10.14 [OBSOLETE]

CHANGES SINCE THE PREVIOUS VERSION

Implemented motion blur step setting for detalisation tuning of internal motion blur.
Implemented "mapped camera name" parameter for image textures to be able to map them to cameras different from the view camera.
Minor fixes and improvements...


OctaneRender for Maya 3.06 (test 4) - 10.15 [OBSOLETE]

CHANGES SINCE THE PREVIOUS VERSION

Postponed new internal MB features implementations to later feature-releases.
Minor fixes..


OctaneRender for Maya 3.06 (test 4) - 10.18 [TEST]


CHANGES SINCE THE PREVIOUS VERSION


Lost material bug fixes using alembic and MB on...
And minor improvements





Bug Fixed -

Reported from OctaneMaya skype -> V2 material swatch in v3 bug
Reported by Calus's -> viewtopic.php?p=308181#p308181
Reported by Jolbertoquini-> viewtopic.php?p=308662#p308662
Reported by Calus -> viewtopic.php?p=308818#p308818
Reported by Renmaxhb - > viewtopic.php?p=309483#p309483

[calus]

I thought that since 3 weeks of silence JimStar was working on implementing MB geometry subsampling,
or implementing the ORBX PROXY feature, or XGEN support, or BIFROST support,
or fixing bugs like this one for example : viewtopic.php?f=110&t=52976#p300696

But I'm afraid he is wasting his time on the awful unneeded unusable useless broken Virtual Material feature.

Please, don't forget to prioritize the real user's needs !



PS: Sorry in advance if I'm guessing wrong here

[Goldorak]

I'll follow up with haze on your feedback tomorrow.

[calus]

I'll follow up with haze on your feedback tomorrow.

Did this really happen ?

[pixerati2]

Have to agree with Calus on the state of things. Given all the assurances of new team members several months back Maya development seems to have ground to a standstill again. I would have expected progress to be well into XGen implementation by now. Not sure where all the new blood went. Seems from the outside like all that happened was Jim Star was sent back in to patch up his old code to work with 3.0. I'm trusting that's not the case but I'm also eyeing Houdini as a viable alternative (working) host for Octane rendering at this point.

[calus]

To be honest the situation is a lot improved compared to 9 nine months ago,
but we were starting from so far that well the plugin is still in a bad shape globally, because the big flaws of the plugin were never tackled.

The promised additional developer that never arrived was really needed,
the truth is that JimStar alone despite all of his efforts is just not enough to catch-up the enormous Maya plugin delay.
Ironically Octane Core development alone is still too fast for the Maya plugin to just to follow its rate ...

And on top of that, there is so much development time loosed because of bad decision and absurd priorities,
this could be avoided by just asking users's input BEFORE implementing features, not once its done.
And this situation is not going to be improved as JimStar is not even reading user's feedback anymore (as he is not doing the release posts anymore).

[calus]

Maya plugin users are the only plugin users to get absolutely zero information from their plugin developer,
So we depend entirely on other Otoy people to get any information,
but it's been 12 days since my first post in this topic and we still didn't get any information from Otoy about why Maya plugin development is frozen.

So frustating to be ignored ...

So I ask again:

1 month ago there was a failed attempt to fix Motion-blur in the Maya plugin, since then nothing has been changed at all in the plugin except updating the Octane SDK.
Questions :

- What is JimStar doing since 1 month ?

- Why JimStar don't post release Topics anymore ?

- What are the plans for the Maya plugin development in the near future, and why not involve some experienced users in these plans ?