Mmm, I don't see the connection... You can make everything you need for VR with Octane 2.xristoraven wrote:Yes, but, well, Q1 2016 is when there's a release of CV1 and Vive.
Without Octane content with V3 features, whole Virtual Reality will fail miserably.
Octane 3? what happened to June beta realease?
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
- Rikk The Gaijin

- Posts: 1528
- Joined: Tue Sep 20, 2011 2:28 pm
- Location: Japan
- ristoraven

- Posts: 390
- Joined: Wed Jan 08, 2014 5:47 am
TurbulenceFD - without it I can't blow the roof off.
More crucial than V3 are ORBX viewer 2 + authoring tools & tutorials and the cloud rendering.
More crucial than V3 are ORBX viewer 2 + authoring tools & tutorials and the cloud rendering.
So theoretically it should will be possible to do first render for ex. 1000 samples per frame and dump all frames render samples. Then later ... "over-render" starting each frame from 1000 samples and go up with samples countGoldorak wrote:Rikk The Gaijin wrote:DMAEuropa wrote:...pause/resume render to disk and not losing samples when network nodes disconnect are planned to be completed in that time frame.
MSI 83 VF 6RF 2x1080 SLI
Yes - we have to finalize a file storage format for the film buffer state (and it will be large), but we are working on this. This functionality will be a part of ORC down the line, so you can go back and render more samples for a previous cloud render, if you so choose.indi_80 wrote: So theoretically it should will be possible to do first render for ex. 1000 samples per frame and dump all frames render samples. Then later ... "over-render" starting each frame from 1000 samples and go up with samples count
Your right i would never plan my project over software that has not yet been released that is asking for trouble, i think i will stick with C4D built in renderer just for speed, i understand that allot better then octane at the momentGoldorak wrote:It is never a good idea to plan any project around a version of Octane that is not out of beta, even for 2.x releases.Rikk The Gaijin wrote:Everyone is waiting for v3, the release should be scheduled for the end of the year, but the Beta is already late, so I wouldn't be surprised if it slips to next year...DMAEuropa wrote:The demo is good, but only show case volumetric rendering and does not showcase any of the other features promised, i know this is an early alpha that was used at OCT 2015.
If this still in early development? do we have a long time to wait.
For your current or near future projects don't wait for v3, it's not gonna make it on time.
We are still planning to release 3.0 for the end of this year, assuming we get through alpha and beta without any major surprises during the next few months. Alpha is expected to be ready in the coming 3-4 weeks, with baking support, which opens the door to UE4 and other plug-ins that depend on this feature. Also pause/resume render to disk and not losing samples when network nodes disconnect are planned to be completed in that time frame.
as for as optimization goes anyway.
I guess we just for octane to give us more information
i am looking forward to v3 i think it will changed how people render, i cant see how Maxwell, vray will be able to compete with octanes speed
Last edited by DMAEuropa on Fri Nov 18, 2016 7:26 am, edited 1 time in total.
Not just for cloud, It is intended to work for local renders too.indi_80 wrote:So this feature will be available only for cloud render?
- sethRichardson

- Posts: 95
- Joined: Thu Feb 27, 2014 2:16 am
As long as rounded edges gets fixed ill be happy with a end of year release.
