Octane 3 features release!

[darkline]

I completely agree, as per my post above I paid for V2 and it's pretty much been useless for me, even with all the new features. Not being able to open my scenes from V1 is something that should have been fix in V2 patches, and quickly. Even worse was we were never told about it before paying for the update.

There is just no excuse for charging for this in V3. Imagine if Vray's new version wouldn't open some old scenes anymore, they sat on it for 9 months with no news, ignored anyone's questions about it, then announced it was fixed in the next paid-for update.

[riggles]

My concern is not development time. My concern is if we have to wait till Octane 3 to get the V2 features working well. It means we are paying for an upgrade to get features we already paid for. Don't get me wrong, I will most like want to upgrade but want and 'be able to' are 2 different things

Understandable. I would like to think, though, that until v3 gets released, v2 will still be receiving updates and fixes. I get the impression that's the plan, as just last week I commented on a small feature request, gave some examples and feedback with one of the devs, and bam he said it was done and will be in the next point release (2.22). So that left me with a good impression. We'll see what happens to other bugs over the next few months.

IIRC, the devs said after v2 was released that generating rounded edges on the GPU was quite difficult and did need improvement. It's possible that getting this feature to the level they really wanted would have required much more resources than they originally thought and perhaps this is something more easily accomplished using OpenCL in v3. I don't know, of course, I'm just saying that's the kind of thing that can happen in software development, and sometimes you just have to draw a line, as unpopular as that might be.

I don't mean to excuse bugs, because I hate them, with a passion. And I'm not even a developer. And if I was on a project that needed rounded edges and motion blurred info passes, I'd be pissed of course. But I'm not, so I can stand back and talk with less irritation. But there have been times when the opposite has been the case.

[gordonrobb]

I know there were problems with the features. But rounded edges and displacement are two of the reasons I upgraded. They sold them as complete features and they kind of weren't.

As I say though, I love the software, and these are niggles.

[caffe3]

To be fair though, some of these glitches and bugs I mentioned are mostly just in the development version (2.21), I'm assuming, right?

[sethRichardson]

Kinda pisses me off when things like rounded edges dont even work right.... in my opinion thats far more important in a production environment. But lets go ahead and spend all the dev resources on vr and lightfields. makes sense. All aboard the hype train choo choo!

Want to meet big studio standards? Then stop developing for new crap that isn't even taken off in the industry yet and likely wont for quite some time. Instead focus on whats broken and not working in big pipelines or hell even in normal studios.

Working on new features while some existing ones don't work right? You should be used to this from MODO

Around the v2 release, I mentioned something similar and one of the devs said the Octane team operates pretty indecently of the other OTOY teams. So they focus on Octane, not the other light field, etc pursuits except for where it intersects with Octane. Not that certain features like rounded edges not being up to snuff aren't frustrating, but I don't believe their dev time is as divided as I originally speculated.

Well thats good to know at least.

And as for MODO.... preachin to the choir my friend haha.

Its funny when they say we went to big studios to make sure octane is up to snuff and they have what they need yet the features are totally broken... I open octane for real work in a real product dev work place and find myself going back to vray/modo because Octane just isn't there. It's not just rounded edges its a number of other things that are too limited or flat not there. Vram isn't a problem or anything like that its the basics that are not there and working right.

[itsallgoode9]

yeah, sometimes it's easy to get frustrated and think their resources are being used on the other products, but they always seem to be really receptive and on the ball when it comes to fixing bugs and adding feature reported by users. Magnitudes better than some of the other programs I've used.