Hi Calus,
Thank you for collecting the database.
Moderator: JimStar
BK wrote:Thank you for collecting the database.
dsyee wrote: (It's been a while since I've tried to render hair/fur with Octane.)
Sugarninja wrote:Thus far, the customer experience for Maya users is abysmal. The way (this) information is hidden, makes it very hard for customers to even find out that certain functions have even been implemented yet. If it weren't for dedicated users like Calus, the community would be even more in the dark. As long as the plugin is understaffed and underfunded, the competition is steadily gaining the upper hand. It's confusing when you read how successful Otoy is becoming with other ventures, but your personal experience feels like a crowdfunding swindle.
Goldorak wrote:We are in the process of recruiting more devs to the Maya team, and committed to completing this process as soon as possible.
There are new APIs coming soon in 3.07 that expose the full SA node graph system and UX inside of DCC plug-ins (already working in 2 apps so far with very good results). The intent is to enable access to Octane functionality not easily or fully mapped to the DCC host app UX. Well share more details once we have further testing done.
Sugarninja wrote:Goldorak wrote:We are in the process of recruiting more devs to the Maya team, and committed to completing this process as soon as possible.
There are new APIs coming soon in 3.07 that expose the full SA node graph system and UX inside of DCC plug-ins (already working in 2 apps so far with very good results). The intent is to enable access to Octane functionality not easily or fully mapped to the DCC host app UX. Well share more details once we have further testing done.
Thank you Goldorak, there just might be a light at the end of the tunnel. Since we're on this train, I guess all we can do is buckle up. Hopefully Otoy can allocate more resources to improve the features and potential that the plugin shows.
Users browsing this forum: No registered users and 14 guests