Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Well Octane by itself is good, however the bottleneck right now is the DS plugin. I would rather switch my license over to either modo or cinema4d since I have those apps, and I take advantage of all the 2.0 features... if I could. However the Iray integration and stability has octane beat for DS users right now.
Agreed. And I did just paint the entire situation with the same brush stroke. But then I consider their lack of resolution / involvement to the OCDS issue to be part of the support.
All true but somewhat besides my point. Being included as a "free" option in a £3100 package isn't the same as being the default in a free package.
Iray within DAZ Studio means render fans and pros can acquire an unbiased global illumination solution for nowt. This isn't just a game changer for DAZ's established customer base.
Otoy, Autodesk and others could not be blamed for re-examining their relationship with NVidia.
Now, as a Bryce user, I've suddenly developed a keen interest in Octane. Slide 49 of this OTOY Presentation - 2015 NVIDIA GPU Technology Conference - March 17 2015:
http://www.slideshare.net/otoyinc/otoy-presentation-2015-nvidia-gpu-technology-conference-march-17-2015
(hat tip Rashad)
Any comments from the DAZ crew?You want a comment on a third party developer that does not sell at DAZ 3D? You know as much about it as we do, possibly more.
I saw that claim by one person, and yet not a single word of it on the actual Lux Render site. One would think if there is that much speed up it would be all over the site, and plastered across the front page of the Lux Render site.
In fact on the Lux Render site, in the release thread the author is claiming that 1.5 is slower than 1.4. In the change log the only speedup I see is more efficient use of the processor. (In other words using the entire processor, or pegging the processor.)
I guess we'll have to wait and see.
Just a quick note for clarification. I own the Octane plugin for DAZ Studio (DS) and the plugin for Carrara. I'm guessing that when blanket statements about "DAZ users" are made, the posters are refering specifically to DS users, and not users of DAZ 3D products in general. Many Carrara users (my prefered application) could be refered to as DAZ users, because we do use "DAZ" content.
IMHO this is a very important distinction because the Carrara plugin for Octane is outstanding, and a very good value for the price. In fact, after spending many hours using Iray in DS, and posting several of the early renders from DS and Iray (until my computer deid), I can honestly say in comparison I've been more than a bit spoiled by the Carrara plugin. As it stands right now, the workflow, IPR responsiveness, feature set, and the speed of using the OR4C (Octane Render for Carrara) is much better than Iray in DS. Now I'm not saying that Iray isn't a fantastic addition to DS, because IMHO it is an awesome addition to DS. It's just that compared to using OR4C, it's a bit of a step backwards. As noted by others though, I would agree that compared to the current state of the DS plugin for Octane, the implementation of Iray in DS is a huge step forward.
If the DS plugin ever catches up to the current developement state of Octane, and is stable (i.e. doesn't crash every few minutes), then it would be a great GPU rendering upgrade for those who wanted to compose larger scenes, or get better performance for rendering animations (but animation rendering could improve with Iray), and some of the other features of 2, and the new features coming with Octane 3. I'm very glad to have Iray in DS, because I now have fast unbiased rendering in both DS and Carrara ( I haven't really used the Octane plugin in DS in over a year).
I saw that claim by one person, and yet not a single word of it on the actual Lux Render site. One would think if there is that much speed up it would be all over the site, and plastered across the front page of the Lux Render site.
In fact on the Lux Render site, in the release thread the author is claiming that 1.5 is slower than 1.4. In the change log the only speedup I see is more efficient use of the processor. (In other words using the entire processor, or pegging the processor.)
I guess we'll have to wait and see.
If 1.5 performs anything like the LuxusCore beta/preview for Carrara by SphericLabs, then the claims of a 10x increase in speed are quite believable. In my tests with LuxusCore for Carrara, CPU only rendering has been consistantly 8x-10x faster than Lux 1.4. But with my Fermi based card, the GPU (OCL) only render speed on more complex scenes is actually slower than CPU only.
The ORC2 plugin is very good and well supported so not all "DAZ users" are having a bad experience with OTOY. Which makes it all the more annoying that if they can get the Carrara plugin so right why not the DS one? It stands alone by a mile as the longest beta plugin in OTOY history. It's the 'Heaven's Gate' of the software development world (I'm referring to the film not the cult - although being picked up by aliens seems more likely than a working plugin at this point!)
It really comes down to the individual developers. They are not employees of Otoy, and as I understand it, in many cases they have full time jobs and are doing plugin development/support "on the side". The success of the Carrara plugin is definitely due to the developer, he is quite fast at squashing bugs and pushing out updates quickly with each new Octane release. It may also be that the Carrara SDK is a bit easier to use than the DS SDK, but I really don't know. I'm just very glad that the Carrara plugin development has been so outstanding, and that we have Iray for DS (I still hope/wish for a good stable version of the DS plugin for Octane 2x with out of core texture support, but won't be upgrading from 1.x until it actually happens, and we get a stable final version for 1.5).
source: http://home.otoy.com/otoy-unveils-octanevr/
I cannot predict if holographic computing in this form will catch on with the masses.
After windows 10 is released and support for Microsoft HoloLens and HTML5 WebVR is introduced in Q4 2015 there may even be more potential interest around.
compare:
Microsoft HoloLens - Transform your world with holograms
https://www.youtube.com/watch?v=aThCr0PsyuA
But for anyone working in 3d to be able to look at or even work on a 3d scene you created with a HMD may be something worth trying out.
- - -
You can watch a low quality recording of the presentation here:
OTOY Presentation at NVIDIA GPU Technology Conference 2015
https://www.youtube.com/watch?v=mHKmqWwEGxQ
A high quality recording may be added later so check the Otoy youtube channel for the other GTC videos and future updates.
- - -
source: http://home.otoy.com/otoy-unveils-octanevr/
I cannot predict if holographic computing in this form will catch on with the masses.
After windows 10 is released and support for Microsoft HoloLens and HTML5 WebVR is introduced in Q4 2015 there may even be more potential interest around.
compare:
Microsoft HoloLens - Transform your world with holograms
https://www.youtube.com/watch?v=aThCr0PsyuA
But for anyone working in 3d to be able to look at or even work on a 3d scene you created with a HMD may be something worth trying out.
- - -
You can watch a low quality recording of the presentation here:
OTOY Presentation at NVIDIA GPU Technology Conference 2015
https://www.youtube.com/watch?v=mHKmqWwEGxQ
A high quality recording may be added later so check the Otoy youtube channel for the other GTC videos and future updates.
- - -
That's nice, but you're talking about the future. Constantly exporting to the standalone when I can do it all in Iray now is not a workable solution or something I recommend. I didn't pay hundreds for a plugin to export, nor can I recommend it to others. It needed to work last year.
Next being able to use the same materials in other apps sound nice on paper, but ultimately I use zbrush and the other tools to render them in DAZ studio. Ultimately Iray will get more native support for my content than the other apps, so it's not something most DS users will use and I will be trying to support Iray in my products, not Octane. I can certainly use my Octane license to play, but it's going to take a backseat to Iray. I don't see recommending something based on features that most likely I won't be able to use for months or a year. Remember the official Octane plugin version is 1.2... not version 2.
Phantom scatter costs that EVERY year, it is a subscription software
and a one pony show, all it does is scatternodes on terrains
carrara replicators create scatternodes exported to standalone and carrara if in PC is the same price and a full robust software
and of course owned by DAZ, just saying :lol:
And as gathered from my post Octane render 4 Carrara exports full scenes to the standalone and Alembic camera
If 1.5 performs anything like the LuxusCore beta/preview for Carrara by SphericLabs, then the claims of a 10x increase in speed are quite believable. In my tests with LuxusCore for Carrara, CPU only rendering has been consistantly 8x-10x faster than Lux 1.4. But with my Fermi based card, the GPU (OCL) only render speed on more complex scenes is actually slower than CPU only.
I think the 10x speed boost claim comes from the integration of Embree's acceleration structure in Luxrender. However Luxrender's dev didn't state about such a gain.
You will need a processor with AVX Features to get the boost and that is only with CPU. Right now, I think you need to compile a version yourself to test the gain (may be the Carrara Luxcore is a compiled version of that development branch). I don't think they already pushed that in the main branch as I didn't see tremendous speed up with the 1.5 dev builds
The Luxcore branch is not really about speed up but rather a change of the Luxrender API which aims at "dynamic scene editing and iteractive rendering" (source http://www.luxrender.net/wiki/LuxCore). And that is not a sudden push as it apperead in the 1.4 dev builds (got that in blender last year already). It's equivalent to DAZ aux viewport interactive render
The embree integration can really speed things up for CPU rendering on the other side. I've tested Embree and Corona and I must say I was impressed by the speed of the renders. Embree is really efficient and that's why it was integrated in many renderers.
...OK that makes it moot for me as I have an LGA 1366 CPU (i7 930) which is not on the list.
Right now a memory boost to 24 GB is a higher priority, then hopefully by this fall I'll have the resources for one of the upgraded GTX 970s with 8 GB.
So much for reinstalling Reality4.
Keep in mind that the developer of the Phantom Scatter plugin has a huge risk.
Otoy may deceide to include some Scattering features in OR as well and then the Phantom Scatter guys are basically out of business.
I truely appreciate all the work the Phantom Scatter team is doing.
So if you think some features are missing just write the Phantom Scatter team some feedback to help out and make it even better!
They reply to all PM and mails and add possible features the community asks for very quickly.
Just a few weeks ago profbetis described on the Otoy forum how procedural clouds can be created with OctaneRender and now the Phantom Scatter plugin has a CLOUD scatter option.
I do not expect everyone to first try out things before forming an opinion but please at least have a quick look at the web page first before stating things that are not true at all.
- AREA-scatter
- PER TRIANGLE-scatter
- RAY-scatter
- CURVE-scatter
- BRUSH-scatter
- CLOUD-scatter
please compare:
http://guusthissen.nl/scatter/
A manual is available for download also for non registered users.
- - -
Some images to illustrate how you can even use the existing features like RAY scatter for different purposes.
Instead of creating rain and calculating on which surfaces rain splatters are created I used roses as drop objects and some other roses as impact objects on the ground.
- OctaneRender plugin for DAZ Studio was used to create OctaneRender materials for the DAZ Rose and Bridge of Cheirocrates.
- export the DAZ Rose object and the Bridge of Cheirocrates scene as separate .ocs files.
When exporting as .ocs instead of .ORBX separate .obj files are created that can be used by Phantom Scatter.
- In Phantom Scatter I created one .csv file for the falling roses and one .csv file for the "impact" roses on the ground.
- In OctaneRender standalone I imported all .ocs files and combined them with scatter nodes and the .csv files.
- - -
I can understand that some people are not happy with the current situation.
But please stick to the facts.
Please if you see someone spreading false or missleading information about other render engines and add on products jump in to correct it.
Sorry if I offended. For reasons that might not be permissible to discuss in open forum, I had thought that any developer must be working in conjunction with DAZ.
My enquiry was motivated purely by enthusiasm at the possibility of active development of Bryce. I have no knowledge at all about what the Otoy chap was referring to.
Thanks for your response. For us end users, it looks like Bryce remains shrouded in the silky veils of ardor.
.
If 1.5 performs anything like the LuxusCore beta/preview for Carrara by SphericLabs, then the claims of a 10x increase in speed are quite believable. In my tests with LuxusCore for Carrara, CPU only rendering has been consistantly 8x-10x faster than Lux 1.4. But with my Fermi based card, the GPU (OCL) only render speed on more complex scenes is actually slower than CPU only. The claim was actually a 10x speed up in CPU mode.
Sorry if I offended. For reasons that might not be permissible to discuss in open forum, I had thought that any developer must be working in conjunction with DAZ.
My enquiry was motivated purely by enthusiasm at the possibility of active development of Bryce. I have no knowledge at all about what the Otoy chap was referring to.
Thanks for your response. For us end users, it looks like Bryce remains shrouded in the silky veils of ardor.
.No offense was taken. I apologize if my response came off that way. It was not intended. I was just trying to point out that 3rd party vendors that don't sell here, rarely talk to us.
I am really unsure how a Hex plug-in could be developed as Hex has no accessible SDK or API.
I don't recall Bryce having one either, though I could be wrong on this one.
I am really unsure how a Hex plug-in could be developed as Hex has no accessible SDK or API.
I don't recall Bryce having one either, though I could be wrong on this one.
both have a bridge to DAZ studio though which does have an SDK
I am not a geek and know zilch about coding but presume you could use this to send to Octane
Adding a bit of clarification to my posts...
All of my experiences were restricted to the Octane for DAZ Studio and Octane Stand Alone. That was my "gateway" platform. The website has since been changed, but a year ago there was no mention of the beta state of things.
Also, I doubt that it's possible to export animation to the standalone in any meaningful way. Animation was the sole reason I bought into ORDS. For all intents and purposes v1.2 is the most reliable beta atm and that's not saying much. Based on what I've read about v2 in the ORDS forum there are problems with reloading the correct materials and, of course, animation rendering is still completely unusable.
The possibility that this plugin will one day offer great advantages over iRAY is an unfounded exaggeration atm. It feels as if users who claim this are somehow in denial. The reality is nothing like the promise which is what matters when you've paid over $600 for a unbiased renderer that doesn't work. And it's not just the cost of the plugin that counts - we bought into the beta years ago because we planned eventually to use the plugin for professional work. Such long delays cost in many other ways, creatively and financially. Maybe those who can afford the high-end gear can cut their losses and move on (or side-grade to one of the other non-beta plugins that actually work) but many of us DS users can't afford to do that after laying out $600.
IMO, the OR standalone is a pointless waste of cash that's being enforced for no discernible advantage to plugin users. At best it serves as a benchmark for OR development that is not necessary for plugin customers to own. At worse it's a cash cow for OTOY and a millstone round our necks. OTOY claim that the cost of the plugins would increase if the price of the standalone was not included but does the standalone development really cost two-three times more than the plugin development? Even if/when OR has plugin cross-compatibility I see no reason for owning the standalone unless it figures as an intermediary step between exchanging scenes from one app to another. The plugins work completely independently of the standalone so why this step would be necessary apart from filling the OTOY coffers is anyone's guess and if they have any hope of attracting future DS customers then they'll need to drop the cost of the standalone from the plugin price.
As it stands, iRAY already has a huge advantage over OTOY's plugin - it actually works! Not only that, but when DS v5 materialises so will a fully compatible iRAY but, based on speculation informed by the current state of development, the ORDS plugin will probably need to go through another round of testing before it's DS v5 compatible. I shudder to think how long that will take!
If the ORDS beta had taken twice as long as the Carrara plugin I would have no complaints but it's been nothing like as quick as that so I have no faith in promises of its future advantages over iRAY. This pie in the sky, if pigs could fly, thinking is no longer tenable because I suspect, based on current development, that in 6 months time ORDS will still be in beta while iRAY will be fully functional. Some might claim that this is schadenfreude for all we've been put through but I still try to remain charitable. After all, I've invested $600!
I know that I am beating a dead horse, but you just articulated why my experience with OCDS was so short.
I get extremely, extremely nervous when a developer makes claims of this nature. I am not claiming that this is occurring now, but my experience in the past with these situations has not ended well. I will just leave it at that.
I know that I am beating a dead horse, but you just articulated why my experience with OCDS was so short.
I get extremely, extremely nervous when a developer makes claims of this nature. I am not claiming that this is occurring now, but my experience in the past with these situations has not ended well. I will just leave it at that.
Right now I think you were right to get out when you did. Wish I'd made the same wise decision long ago. Though I don't think any of us when we bought the plugin over a year ago could have predicted that v1 would still be in beta today.
You never could have. Hindsight is always 20 / 20. Hopefully the course will right itself.
I grabbed the alembic exporter on sale and that does indeed export an animated mesh with timeline into the standalone
is bit limited though and you need to re-add texture maps, no camera movement either.
You can add it with several geometry groups to a group node and render target to build up a scene.
By the way, that's per year as the license expires after 365 days... which is pretty lame.
Phantom Scatter is impressive software, but that's a really crappy business model.
By the way, that's per year as the license expires after 365 days... which is pretty lame.
Phantom Scatter is impressive software, but that's a really crappy business model.
LOL, I think you quoted the wrong person. I don't have that plug in.
Male, you're right... my bad.
As I mentioned on the Otoy forum and the Phantom scatter bloke prolly hates me
there is a better plugin
its called Carrara
the Carrara plugin will export Carrara replicators as scatter nodes to the standalone
and you do not have to pay for it every year
I was not impressed by that sort of money grab at all.
I am really unsure how a Hex plug-in could be developed as Hex has no accessible SDK or API.
I don't recall Bryce having one either, though I could be wrong on this one.
both have a bridge to DAZ studio though which does have an SDK
I am not a geek and know zilch about coding but presume you could use this to send to OctaneLacking an SDK or accessible API means that DAZ 3D would have to write it.