OctaneRender for DAZ Studio 3.02 [OBSOLETE]

[Elele]

Has the extreme lagging in the viewport after installing octane finally been fixed?

Has this issue been reported to me as a bug previously? I don't recall it.

Paul

I thought other people were discussing it, but I'm not sure. Moving something in DS lags about a second or so which is extremely annoying. It is easy to misinterpret as a DS issue since it also occurs when you don't actively use Octane. But the only fix I found, is having a second version of DS installed without Octane and use that to move stuff in the scene.
Am I the only one having this issue???

[ForceX]

@Elele :
When you experience lag in the Daz view window are you also rendering with Octane at the same time? If so try this.

Sorry I don't have octane available ATM so I may use the incorrect wording.

1. If you have a single GPU: Reduce the GPU rendering priority to around 80%. This will allow the GPU to keep using some processing power for Desktop rendering.
2. If you have multiple GPUs : Consider removing your primary GPU from the renderer or reducing its rendering priority so it can focus on Desktop rendering.

The lag I think you are experiencing is because the GPU is having to prioritize between Desktop and Octane rendering.

[Elele]

No, I have a GTX 670 for the viewport& OS and a gtx titan that handles all my octane rendering and only my octane rendering.

And it also happens when I haven't touched octane yet.

[ForceX]

That is strange. The only time I have experienced a delay in the Daz scene window is when rendering with 100% priority to octane, never when octane is shut down. I know Daz has some scene view quality settings like antialiasing, hardware acceleration shadows or something to that effect somewhere in the preferences tab. I never alter them from the default settings because I have had problems in the past. If they are on perhaps try and disable them? Sorry I can only speculate at this point.

Right now the issue I am having is the newest beta not rendering past 1 sample. It appears to be a object / material limit. I have not discovered the magic number yet but it's not many 10 objects 15-20 materials. Scene composition does not appear to matter so it's not any one particular asset. But once this magic number is reached removing one asset will allow octane to render again. I know it's not a video memory limit its only about 300mb vram usage. Was not an issue in the past.

[face_off]

I thought other people were discussing it, but I'm not sure. Moving something in DS lags about a second or so which is extremely annoying. It is easy to misinterpret as a DS issue since it also occurs when you don't actively use Octane. But the only fix I found, is having a second version of DS installed without Octane and use that to move stuff in the scene.
Am I the only one having this issue???

I'm sorry - I haven't seen anyone else having this issue. Have you trying unticking Don't Load Render Settings, Environments and Unused Materials in the Preferences tab?

Paul

[linvanchene]

- - -

Low priority. Hard to track down

Happens randomly. No pattern detected:

Switching from one IES preset to another does not seem to update the viewport even with forced reload.

Update / Edit: This only seems to happen with some scenes.

Example:

- Test scene with IES 19 selected.

- Switch to IES 34
- viewport does not update.

- save scene
- reload scene
- IES 19 is still saved as preset even though it was changed to IES 34

- - -

Update / Edit:

When I try to reload this saved scene this not updating behaviour is the same.

Nevertheless when I create a new scene switching IES lights seems to work.

No clue why this is not working in that specific scene and is working in others.

- - -

[face_off]

Switching from one IES preset to another does not seem to update the viewport even with forced reload.

It looks like either the plugin is either not sending a "reload" msg to Octane when loading the new IES distribution, or the IES light is being loaded into an unused material and not the actual material being rendered. I will add this to the list of things to investigate.

Paul

[wlebrun]

Daz is showing temp of 50 while precision x shows 37. It seems octane has a setback in that area. Im not sure what the problem is exactly but its a pretty small scene. I normally have to restart Daz to get the viewport to update as well sometimes. Its seeming like its collecting more and more information on the scene then it stops updating no matter what.

[face_off]

Daz is showing temp of 50 while precision x shows 37. It seems octane has a setback in that area. Im not sure what the problem is exactly but its a pretty small scene. I normally have to restart Daz to get the viewport to update as well sometimes. Its seeming like its collecting more and more information on the scene then it stops updating no matter what.

I am not sure what problem you are referring to here....

[wlebrun]

Daz is showing temp of 50 while precision x shows 37. It seems octane has a setback in that area. Im not sure what the problem is exactly but its a pretty small scene. I normally have to restart Daz to get the viewport to update as well sometimes. Its seeming like its collecting more and more information on the scene then it stops updating no matter what.

I am not sure what problem you are referring to here....

it seems to freeze