samsue wrote:One thing I have not realized until recently, is that you are "stuck" with what Octane has "originally", and that this connection through platforms does not make your work any easier.
I wouldn't say "worst" ... but it is the general "problem" of the SDK, it is overcomplicated. in AOV, you have layer on layer, aov imput. you can't understand the structure, is organized in a complicated way. ... This should be included in the Render Frame, with a better realtime visualization of what you are doing. Other engines have similar things in a very simple way, without naming names.
I know this may not help much, but unfortunately I don't have the time to do a review of the AOV, I would have to take screenshots, make a montage in Photoshop with explanations etc...
Sorry if I sound like the kind of person who always says everything is bad, but for me the whole SDK needs to be reorganized, optimized, made simpler.
A lot of good news this year from Otoy, but as I have already said several times, in the proportion that they improved the SDK technically, they got worse in usability.
Hi samsue,
Thank you for explaining your impressions.
I fully agree that the first time we see those new feature's interface (aov, ocio, scatter surface and volume, ..), it's very confusing !
As plugin developers, we have the same trouble at first, especially as it's still evolving..
As we get more familiar, we'll have more and more samples and tutorials for those features, and certainly the interface will be simplified and can be tailored for particular usages, like the 'light mixer' tool that I added.
All the new feature's parameters must be accessible, to take full advantage of the power they provide, but some could stay hidden in some cases..
I'll look into this, and the issues and crash you reported.
Thanks!