Come on, the poly limit in v2 is a cock-up from 1-2, not a new bloody feature.
NEW IN V3 - NOW IT WORKS AGAIN!!!
It's clear why no developer ever responded to me, because it was never intended to be fixed in V2.
Since I paid for it I've not been able to open any of my scenes. Nowhere in the features list did it say :
"NEW in V2 'POLY LIMIT', saving you hours of rendering (by not being able to!!)"
So you expect me to upgrade to V3 to fix something that should have been patched in V2?? Ohhhhkayyyyy, that sounds really fair.
Any limitations we should be aware of in v3? Does it no longer work with the colour blue? Or only works with 2 lights in a scene (as long as they are off)? Don't worry you'll fix that when we pay for V4 obviously, but I'd like to know before I get mugged again.
yes, I'm being sarcastic, but you deserve it.
Octane 3 features release!
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Here are the slides Otoy showed during their GTC presentation (contains Imagery!):
http://de.slideshare.net/otoyinc/otoy-p ... ch-17-2015
http://de.slideshare.net/otoyinc/otoy-p ... ch-17-2015
W10 64 bit | i7 3770K | MSI Geforce RTX 2080 (8GB) + GTX Titan Black (6GB) | 32 GB DDR3 RAM
While I would never refuse more features to the version I already have, I realize that new features take time and resources to develop that companies naturally charge for. I purchase software knowing that's how this works, just like I expect clients to pay me for the work I do.Elonius wrote:While all these features are awesome and I am really excited about the ZBrush integration. Why can't they be added to version 2? How did we get from version 2.21 to 3? What happened to versions 2.3 - 2.9?
Spot on! Besides, it's only natural we spend money on stuff that makes our lives easier.riggles wrote:While I would never refuse more features to the version I already have, I realize that new features take time and resources to develop that companies naturally charge for. I purchase software knowing that's how this works, just like I expect clients to pay me for the work I do.Elonius wrote:While all these features are awesome and I am really excited about the ZBrush integration. Why can't they be added to version 2? How did we get from version 2.21 to 3? What happened to versions 2.3 - 2.9?
Also you should know 3.x is coming in Q3, so I'd expect we'll get a lot of updates until then with various bug fixes which octane desperately needs in order to be called a functional renderer. Maybe even some minor new features if they're feeling generous, though at this point I'd much rather have something I can use in production rather than an engine with lots of features but no real stability. Hopefully some of the more urgent fixes will come really soon! Cause it's getting a bit ridiculous adding motionblur and DOF to info passes in compositing. And having to re-render a scene multiple times just to get some object buffers/black and white mattes for isolating in post.
- sethRichardson
- Posts: 95
- Joined: Thu Feb 27, 2014 2:16 am
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.
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.
- gordonrobb
- Posts: 1247
- Joined: Sat Mar 16, 2013 9:08 am
Yup, we have some nice features already that aren't quite there yet.
Windows 8 Pro | i7 3770 OC | 32 GB Ram | Single Titan (plus Black Edition on Order) | Octane Lightwave |
Working on new features while some existing ones don't work right? You should be used to this from MODOsethRichardson wrote: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.

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.
- gordonrobb
- Posts: 1247
- Joined: Sat Mar 16, 2013 9:08 am
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 

Windows 8 Pro | i7 3770 OC | 32 GB Ram | Single Titan (plus Black Edition on Order) | Octane Lightwave |