OctaneRender 3 for DAZ Studio [TEST and STABLE] [OBSOLETE]

[vortex3d]

Any ideas why OCDS is hording deleted and unused texture file references?
I thought this issue was related to the cache, but it isn't. It continues to defy me and is getting annoying, I don't like junk.

1. DAZ Cache folder is empty.
2. Loading with "Don't load unused Materials", didn't fix it.
3. Saving as "Scene subset" and reloading, didn't fix it .
4. Delete button [x] is disabled.

Thoughts?

[face_off]

Any ideas why OCDS is hording deleted and unused texture file references?
I thought this issue was related to the cache, but it isn't. It continues to defy me and is getting annoying, I don't like junk.

I'm sorry, but I cannot reproduce this problem - so it's difficult to track down the cause. I have searched through the code, and can not find the reason those dead link are in the list.

Paul

[vortex3d]

Any ideas why OCDS is hording deleted and unused texture file references?
I thought this issue was related to the cache, but it isn't. It continues to defy me and is getting annoying, I don't like junk.

I'm sorry, but I cannot reproduce this problem - so it's difficult to track down the cause. I have searched through the code, and can not find the reason those dead link are in the list.

Paul

Thanks for taking the time to reproduce this. It appears to happen with every scene where I've changed materials from DS to LiveDB, then back to DS.

[face_off]

It appears to happen with every scene where I've changed materials from DS to LiveDB, then back to DS.

I tried this but still couldn't reproduce the problem. Can you give me an exact set of steps to follow pls?

Paul

[vortex3d]

It appears to happen with every scene where I've changed materials from DS to LiveDB, then back to DS.

I tried this but still couldn't reproduce the problem. Can you give me an exact set of steps to follow pls?

Paul

I will test typical scenarios and write detailed steps for you. Most of my scenes are imported from Poser, which shouldn't be an issue, but will see.

[vortex3d]

It appears to happen with every scene where I've changed materials from DS to LiveDB, then back to DS.

I tried this but still couldn't reproduce the problem. Can you give me an exact set of steps to follow pls?

Paul

I will test typical scenarios and write detailed steps for you. Most of my scenes are imported from Poser, which shouldn't be an issue, but will see.

I loaded an unmodified scene (https://www.daz3d.com/modern-serenity) with the same results.


So far, spec maps seem affected. Could this be happening during the material import/conversion into OCDS?
This is just one scene. I imagine if users import multiple scenes, sets and props, these rogue textures would accumulate.
What does the "X" mean? I thought it was to remove textures.

[face_off]

I loaded an unmodified scene ( https://www.daz3d.com/modern-serenity ) with the same results.

Can you provide an example with a freebie scene pls?

Paul

[vortex3d]

I loaded an unmodified scene ( https://www.daz3d.com/modern-serenity ) with the same results.

Can you provide an example with a freebie scene pls?

Paul

I'll try to find a freebie scene that's affected.
Meanwhile, here's another commercial scene heavily affected by this: (https://www.daz3d.com/the-washroom).



Again, these are off the line with all original materials. I'm leaning towards iRay mat conversion issue.

[vortex3d]

I loaded an unmodified scene ( https://www.daz3d.com/modern-serenity ) with the same results.

Can you provide an example with a freebie scene pls?

Paul

I'll try to find a freebie scene that's affected.
Meanwhile, here's another commercial scene heavily affected by this: (https://www.daz3d.com/the-washroom).



Again, these are off the line with all original materials. I'm leaning towards iRay mat conversion issue.

Okay, i found you a free prop that has iRay materials using RGB textures

1. Download & Install: https://www.sharecg.com/v/87623/browse/ ... Props-Iray
2. Switch to OCDS/Textures tab.
3. Load the paper straw from "/Props/AllenArt Props/Milkshakes/" and select.
4. Navigate to "/Props/AllenArt Props/Milkshakes/iRay Materials/Paper Straws/"
5. Change material to "Plain White".
6. Change material back to "Red White Stripe" (notice the rogue texture appears)
7. Save scene.
8. Clear and load the newly saved scene using "Don't load unused Materials" (this option does not affect the state of this texture).



Viola! There's the rogue texture reference permanently embedded into the file.

But wait, there's more!
After loading the saved file, switching to and back from "Plain White" generates more rogue textures (or whatever they're called )

That's all I have time to play with, I hope it helps.

[rajib]

Hi Paul,

I am having 2 consistent issues with the latest TEST build of 3.6.3.32.
1. Remember the issue I had reported that sometimes when opening scene files without doing a new to close the current open scene, the Octane Viewport will have a running bar going back and forth and will not load the new scene even after doing rebuild scene / force reload ? It seems to be back. Now I often get that when opening scene files without first doing a 'new' to close the current scene.
2. The sky texture in the environment tab doesn't change often even after selecting a texture. Most of the times I need to do a 'Clear Texture' and then load the other sky texture again to get it to change. This one is simple to create. - Save a scene with the environment set to daylight and a sky texture selected. Close it. Open it again and try to change the sky texture to something else. A lot of times it will not change. Do have the Octane viewport open as sometimes even if the file name updates in the environment tab, the render sky texture does not change.

I also have a feature request - something to do with making it easier to place the sun in the daylight environment exactly where we want without having to worry about east west north south and the orientation of the scene - as in facing where east, west, north, south or north east, north west.... etc, etc, etc.... It should be more like assuming the DAZ 'front' orientation is the front of the scene, I want to place the sun on the right of the scene or the left of the scene or behind the camera or in front of the camera, etc.... Basically any place in a circle or a half sphere. Will that be possible ? Btw. any way from the DAZ script to inform the octane plugin to pose the sun at a certain place ? If so, I can create by own mechanism to take the inputs and then pass to the octane plugin the data it needs to set the sun to that location.

Regards,
Rajib