Moderator: BK
This look to be the one in error. However I cannot produce it....Live Button OFF
- Moving objects updates the scene and restarts the render
- Rotating and bending limbs that do not have objects parented to them DOES NOT update the scene or restart the render
I think I have reproduced. Not saying this isn't behaving as designed, just posting results:face_off wrote:This look to be the one in error. However I cannot produce it....Live Button OFF
- Moving objects updates the scene and restarts the render
- Rotating and bending limbs that do not have objects parented to them DOES NOT update the scene or restart the render
1) Start DS
2) Load Genesis 2 base
3) Open OctaneRender Viewport (Live is OFF)
4) Bend an arm - render does not re-start - which is the expected behavior
Paul
I think this is a terminology issue. The "Live" button turns on/off "geometry" updates. When you move the cube, the geometry is not updating - the entire props transform is changing - so the plugin is updating the Octane Placement node to reflect the new position. So I believe this is working as expected.I think I have reproduced. Not saying this isn't behaving as designed, just posting results:
In that case, is it possible to add a feature that pauses the updates to the Octane Placement node while rendering is paused?face_off wrote:I think this is a terminology issue. The "Live" button turns on/off "geometry" updates. When you move the cube, the geometry is not updating - the entire props transform is changing - so the plugin is updating the Octane Placement node to reflect the new position. So I believe this is working as expected.I think I have reproduced. Not saying this isn't behaving as designed, just posting results:
Paul
To all those people having issues with "lag":Right now I've given up on working with complex scenes because the lag I experience while doing so makes it incredibly frustrating.
Thanks for your advice, but...linvanchene wrote:To all those people having issues with "lag":Right now I've given up on working with complex scenes because the lag I experience while doing so makes it incredibly frustrating.
Yes, I've made sure I've deactivated my display GPU.linvanchene wrote:Did you make sure to deactivate the GPU that is assigned to your monitor?
On windows one GPU will always also handle your monitor AND all the other applications.
DAZ Studio will also need the GPU assigned to the monitor to display the interface.
Especially with high load scenes it is extremely important that the GPU who is handling the monitor and all other applications is NOT assigned as a render GPU in Octane.
Yes, I know I have deactivated the correct GPU. For one, I'm pretty sure I wouldn't be able to game while running renders in the background if I was rendering on my display GPU, fairly certain I'd notice the performance hit.linvanchene wrote:The GPU number in OsDS may not be the same number as displayed in the windows display selection or the Nvidia panel!
You can find out which GPU is assigned to your monitor and general application handling by opening up a lot of different software like photoshop with huge files and let videos run.
Then check in the OcDS tab each GPU separately which has the least VRAM available.
Disconnect that GPU in OctaneRender and use the other GPUs while working on your scene.
Nope, never opened it, ever.linvanchene wrote:Other things to check and try out:
Make sure not to use the Iray live preview viewport at the same time as the OctaneRender viewport is open.
I've disabled all OpenGL options in Daz, and as I previously mentioned the stuttering lag does not happen until I start rendering with the Octane plugin, until then I can move objects around without any issue. Further to this the stuttering matches the exact timing when the plugin updates the Octane Placement node while running a render.linvanchene wrote:In general DAZ Studio OpenGL texture shaded viewport mode is not handling large scenes well.
Nope, already tested that, doesn't do anything, as I mentioned the stuttering lag does not happen until I start rendering with the Octane plugin, until then I can move objects around without any issue.linvanchene wrote:Use the wireframe mode for the OpenGL viewport with high count geometry scenes.
so my "solution" for the moment is to get the posing correct in first try
Retested with Prerelease 0 OcDS 2_24_2_3.@ 09 Exporting Animated Cameras to standalone Only still cameras seem to be exported from OcDS to OR standalone
compare:
viewtopic.php?f=44&t=49315
This should be fixed in the current 2.24.2.1 release if you export to ABC.
Retested with Prerelease 0 OcDS 2_24_2_3 to check if the status is accurate.08 Camera & Object Motion Blur
- Object Motion Blur not working
- HDR background has no camera motion blur at all
- When the camera is rotating no camera motion blur is created
compare:
viewtopic.php?f=44&t=49118&p=244278
The camera motion blur limitations are probably OR standalone related issues.- HDR background has no camera motion blur at all
- When the camera is rotating no camera motion blur is created
I notice the plugin keeps rendering even after to close the Viewport. What about if the plugin STOPPED Octane rendering when the Viewport was closed. Then you could simply close the viewport and remove the lag.Right now I've given up on working with complex scenes because the lag I experience while doing so makes it incredibly frustrating.
So apps snaffle your rendering card for their OpenGL viewing without you knowing (Rhino does this for example). To test, run GPU-Z and double check that your Octane rendering card is not being used for DAZStudio's OpenGL processing. OR, click Edit->Preferences->OpenGL->Hardware Features, and it will tell you which card DAZStudio is using.Yes, I know I have deactivated the correct GPU. For one, I'm pretty sure I wouldn't be able to game while running renders in the background if I was rendering on my display GPU, fairly certain I'd notice the performance hit.
This solution sounds fine by me, it would certainly be faster than having to close and reload the scene to remove the lag.face_off wrote:I notice the plugin keeps rendering even after to close the Viewport. What about if the plugin STOPPED Octane rendering when the Viewport was closed. Then you could simply close the viewport and remove the lag.Right now I've given up on working with complex scenes because the lag I experience while doing so makes it incredibly frustrating.
NVIDIa IRay was selected, however I have changed to both Basic and Intermediate OpenGL and this did not resolve the issue. I've also disabled all devices for NVIDIA Iray under the advanced render settings just to be sure.face_off wrote:Also - I'm unsure why I do not get lag on the test scene you sent me. What Render->Render Settings->Engine are you using?
I couldn't tell using "Edit->Preferences->OpenGL->Hardware Features" as both my cards are identical. I ran GPU-Z and turned on all the OPenGL features, which I have disabled by default, doing so ramped up the memory usage and load on my primary display GPU. I then started an Octane plugin render, and confirmed that this ramped up memory usage and CPU load on my rendering GPU.face_off wrote:Updating an Octane Placement node (ie. moving a prop, or moving an entire figure) should be almost instant. Updating a pose (when Live is enabled) will require all the geometry for that figure to be reloaded (so take a sec or too).
So apps snaffle your rendering card for their OpenGL viewing without you knowing (Rhino does this for example). To test, run GPU-Z and double check that your Octane rendering card is not being used for DAZStudio's OpenGL processing. OR, click Edit->Preferences->OpenGL->Hardware Features, and it will tell you which card DAZStudio is using.Yes, I know I have deactivated the correct GPU. For one, I'm pretty sure I wouldn't be able to game while running renders in the background if I was rendering on my display GPU, fairly certain I'd notice the performance hit.
Paul
