OTOY Forums

gaazsi wrote:the worst and most stupid problem since SEVEN years are the horrible loading times if you open some/most duf files for whatever reason. i am so fed up with this crap now and it is JUST the octane addon and nothing else

Hi,

Sorry you are experiencing issues.
Would you be able to share the steps or a sample scene or a video?
The scene loading speed also depends on you hardware configuration.

Octane would run better if the scene setup is optimized.

Cheers

BK wrote:

gaazsi wrote:the worst and most stupid problem since SEVEN years are the horrible loading times if you open some/most duf files for whatever reason. i am so fed up with this crap now and it is JUST the octane addon and nothing else

Hi,

Sorry you are experiencing issues.
Would you be able to share the steps or a sample scene or a video?
The scene loading speed also depends on you hardware configuration.

Octane would run better if the scene setup is optimized.

Cheers

dont know how useful it could be to record a clip where daz almost crashes and needs minutes to revive itself before you can start working its definitely not a hardware problem, whenever i deactivate plugin it is loaded and ready to go within a few seconds. most time problems start when you start merging other duf files into the scene, save it and try to load it again later... no matter how small they may be. so i guess its the "optimized scene setup" whatever that means

This Radio silence and no update no info whats going on is starting to get irritating

Hun73rdk_1 wrote:This Radio silence and no update no info whats going on is starting to get irritating

Hi Hun73rdk,

Thank you for the post.
We would try to release another build with the latest Octane engine ASAP.

cheers

What i hope getting fixed in the new version is

1. Live material database

2. using the right subd in daz for rendering



3. Better support for HDRI that fits Daz scale

4. denoise working in animations without having to render a frame manually and then apply denoise to make it work in animation

Hi BK

I've been using the Octane plugin for DAZ for a while now and remain really impressed by your render engine - but have been largely disappointed by the DAZ Octane plugin maintenance/support. I now have just over a week left to decide whether to purchase an OctaneRender Enterprise Maintenance Upgrade - or else just stick with the current version of the plugin.

As I have already purchased a perpetual licence to use the current version of the DAZ Octane plugin, I can't see any material benefit to spending another €199 on a 12 month 'upgrade extension' unless the Octane team is actually going to fix at least some of the major software defects for that money.

The major defects in the Octane plugin for me are (aside from general instability):
- Instancing doesn't work
- 'Strand-Based Hair' doesn't work
- Importing ORBX files doesn't work (unless only a single material is used)
- Templating doesn't work (for specular or roughness maps)

Which, if any, of these defects will be fixed within the next 12 months?

(It was great to hear from you back in January that you were going to "update the DAZStudio plugin while simultaneously working to refactor and improve the plugin". However, it doesn't seem like there's been much progress at all in the 9 months that have followed that announcement. I'm sure I'm not alone in having concerns about the apparent lack of progress. It would, accordingly, be really helpful if you'd please provide some commitments regarding timescales for fixing the existing software defects so that I can make my purchase decision.)

Many thanks
IAIN.

IainW wrote:- 'Strand-Based Hair' doesn't work

If we could get this working with octane's hair primitive or even just an approximate translation, that'd be great. Converting to a mesh would seem not worth it to me, since it would easily eat up all the VRAM.

Hi IainW & swipswap,

Thank you so much for your feedback.

We are already planing to work on these issues one by one.
Right now, the highest priority is set to Octane Plug-In Slowing Down Daz Studio due to Rigid Follow node which is an extremely critical one.

Once this is fixed we would pick one of these or please feel free to suggest!
or we could prioritize the hair strand/Dforce support!

cheers

Hi BK,

For me, the priorities would be

1. Strand based hair with or without dforce
The inability to use many latest hair products or LAMH for animals is really annoying
2. Templating
This is the most time consuming task, particularly with complex shaders. I would also add to this feature the ability to select a specific texture of the DAZ shader, and to be able to use colors in templates too.
3. ORBX import with multiple materials
4. Instancing

Of course the performance and usability issues remain the highest priority.

Thank you for reading.

sudisk wrote:Hi BK,

For me, the priorities would be

1. Strand based hair with or without dforce
The inability to use many latest hair products or LAMH for animals is really annoying
2. Templating
This is the most time consuming task, particularly with complex shaders. I would also add to this feature the ability to select a specific texture of the DAZ shader, and to be able to use colors in templates too.
3. ORBX import with multiple materials
4. Instancing

Of course the performance and usability issues remain the highest priority.

Thank you for reading.

Hi Sudisk,

Thank for the suggestions.
We have created tickets on our internal development system and will pick them up after the rigid follow node issue!

cheers

cheers