OTOY Forums

face_off wrote:

Can we please add the issue, reported by myself and vortex3d on multiple occasions, where high object count scenes results in massive lag in Daz when you attempt to move an object?

Can you provide a sample scene which demonstrates this issue pls.

Thanks

Paul

Sure, I'm fairly certain it would be illegal for me to send you the scenes I've experienced it in, due to the licensed content in them, but I've done my best to duplicate it in a basic scene.

The scene I've attached has 90 x 100 segment 400 sided spheres and a single untextured G2m model with a primitive cube parented to his left hand. The lag isn't as bad as some of the scene I've experienced it in, but it's still noticeable. You should notice that it doesn't start happening until after you start an octane render.

One thing I've also just noticed, is that if I initiate a Final Render, I not longer experience any lag moving objects around in the scene, until I end the final render.

face_off wrote:

02 Materials Conversion - problems converting materials from Daz to OcDS (Iray materials not supported, materials not converting, mesh-plain collision causing artifacts and blotches, issues related to creation of 'Mix Material' (such as Normals Map defaulting to 2, which causes Toon textures in Daylight Environment), etc.)

Can you pls provide sample scene which demonstrate the material conversion issues.

Thanks

Paul

I created a new thread to give an overview of the different issues related to Material Conversion.

viewtopic.php?f=44&t=51418

- - -

since that last quick patch i hadnt any more problems with modified material settings that arent saved... just lucky at the moment or is that already fixed?

Where does textures not updating correctly when rendering animation fit into the poll? I'm been having consistent problems with the textures in a scene becoming corrupted for a single or consecutive frames when rendering animation. Maybe 10% of the entire render is corrupted at different points in the animation which is incredibly frustrating as I only discover this when compositing the animation and then have to hunt down the corrupted frames and try to re-render them which also often doesn't work and the frames repeatedly render corrupted.

I'm also having textures becoming corrupted or crashing DS if I try out different octane materials on an object. This is a consistent problem but is not simply reproducible because it occurs at random.

OcDS doesn't remember when certain materials have been changed and repeatedly reloads the same wrong material. This seems to occur when one of the textures have become corrupted in the textures tab. By corrupted I mean that the material appears in the texture tab but is uneditable. This also occurs at random and doesn't appear to have any consistent cause.

I believe that something is still wrong with the way OcDS updates textures and this needs to be rock solid. I had the same problems on another less powerful system using v1 of the plugin that didn't happen on my newer PC so I put it own to the older system but now it's happening on my newer, more powerful system using v2.23.2 while rendering animation.

- - -

Update / Edit:

I will add issues mentioned in this thread that did not make it on version v1003 of the list and the poll to a special section on the first page.
New issues mentioned after the poll started can not be added to the poll without reseting the already submitted votes.

- - -

From my point of view:

The point of this thread and the poll was to give face_off a first impression over the issues we had in the past BEFORE the OctaneRender DAZ Studio 2.24.2 release and how important they are to different users.

Users are able to vote on the allready known issues and requests to share what they think is most important to address first.


Now the next challenge is how to move forward:

What kind of bug reporting system does face_off want to implement for the future?

- Will there be a special thread to officially report new bugs found in OctaneRender for DAZ Studio 2.24.2 [TEST] ?

- Will there be an online form that users can use to submit bugs?

- Will there be a shared online document that all users can edit to add their bugs?

- Will there be a public online bug report database so users can check which issues and requests have been submitted?


For now it seems important to give face_off some time to assess the situation and then let him tell us how he wants to proceed moving forward.

- - -

since that last quick patch i hadnt any more problems with modified material settings that arent saved... just lucky at the moment or is that already fixed?

Just lucky.

I'm been having consistent problems with the textures in a scene becoming corrupted for a single or consecutive frames when rendering animation.

Can you send me a scene to me which demonstrates this problem, together with the exact set of steps I needs to do to reproduce the problem.

- Will there be a special thread to officially report new bugs found in OctaneRender for DAZ Studio 2.24.2 [TEST] ?

No - post bugs to the "TEST" release thread.

- Will there be an online form that users can use to submit bugs?

No.

- Will there be a shared online document that all users can edit to add their bugs?

No - use the "TEST" release thread.

- Will there be a public online bug report database so users can check which issues and requests have been submitted?

Not unless you want to start a Mantis system for this. My intent is to methodically work through the prioritised list as quickly as possible so that the bug small is small enough to not need a bug management system.

Paul

i have another two issues, workarounds possible BUT i guess its a problem for more people than just me

ok... i try to explain it as good as possible in english

nr1:

i am producing an ongoing comic series, using always the same main characters. whenever i merged them into a scene... or objects into that scene... or generally using the merge function there seems to pile some kind of data crap, just happens when plugin is installed and used. means the problem is caused by octane. so some filesizes grew and grew and grew... what ended up in for example those character .duf file had around 30mb size. even when i deleted for all of the stuff around it, clothing, props and so on again... filesize remained that huge. which results in annoying loading times, around 5-10 minutes. imagine what happens when i merged two of those main characters files and so on... or better dont

my workaround for this issue is... save the figure as character preset and merge it in with a fresh new figure (gen2 female in that case)... after i did that, filesize was again around 500kb again. so its not THAT high priority thing, but still its annoying... maybe have a look for it. i could provide files if needed, the clean and the big one for comparison just let me know


nr2:

whenever you save a scene enviroment settings have been saved. maybe thats also a PART of the problem nr1. whenever you merged files, aaaall those preferences have been merged together as well, and so on... after some weeks and months i had hundreds and hundreds of those presets saved for nothing in some duf files... maybe possible to deactivate this "auto save" function?

r1:

i am producing an ongoing comic series, using always the same main characters. whenever i merged them into a scene... or objects into that scene... or generally using the merge function there seems to pile some kind of data crap, just happens when plugin is installed and used. means the problem is caused by octane. so some filesizes grew and grew and grew... what ended up in for example those character .duf file had around 30mb size. even when i deleted for all of the stuff around it, clothing, props and so on again... filesize remained that huge. which results in annoying loading times, around 5-10 minutes. imagine what happens when i merged two of those main characters files and so on... or better dont

my workaround for this issue is... save the figure as character preset and merge it in with a fresh new figure (gen2 female in that case)... after i did that, filesize was again around 500kb again. so its not THAT high priority thing, but still its annoying... maybe have a look for it. i could provide files if needed, the clean and the big one for comparison just let me know


nr2:

whenever you save a scene enviroment settings have been saved. maybe thats also a PART of the problem nr1. whenever you merged files, aaaall those preferences have been merged together as well, and so on... after some weeks and months i had hundreds and hundreds of those presets saved for nothing in some duf files... maybe possible to deactivate this "auto save" function?

At a guess, without looking at the code, I would say the plugin is not deleting Octane data with is no longer used in the scene - so it is growing and growing. I doubt there is a quick fix for this - but it needs to be addressed at some point. I will had it to my list - but it might take a while to get to.

Paul

face_off wrote:At a guess, without looking at the code, I would say the plugin is not deleting Octane data with is no longer used in the scene - so it is growing and growing. I doubt there is a quick fix for this - but it needs to be addressed at some point. I will had it to my list - but it might take a while to get to.

Paul

Out of curiosity, given the way this problem is described (and the logical conclusion you drew from it), could it maybe have something to do with Spectralis' problem with animations reloading incorrect materials? If it's not getting rid of info, that could certainly lead to issues where it's referencing things it shouldn't be keeping any more on accident, I would think. Just popped into my head as a possible relation, feel free to ignore it as the blathering of a fool

could it maybe have something to do with Spectralis' problem with animations reloading incorrect materials? If it's not getting rid of info, that could certainly lead to issues where it's referencing things it shouldn't be keeping any more on accident, I would think.

I doubt it. I would need to see Spectralis' scene in order to speculate the cause of the issue.

Paul