Page 35 of 38
Re: OcDS Setup v2.2 (last Beta)
Posted: Thu Sep 24, 2015 9:30 am
by kibbycabbit
Me "tarzan kitty" wants update. *beat chest*
Re: OcDS Setup v2.2 (last Beta)
Posted: Mon Oct 05, 2015 12:51 pm
by sixb0nes
Didn't see this bug posted:
- If you move/delete the HDR folder you had previously selected a file from, as soon as you choose the ellipses to open the Image Browser, the application crashes. It appears to be trying to reference a folder/file that no longer exists. This may apply to the Image Browser in general - not sure.
Re: OcDS Setup v2.2 (last Beta)
Posted: Wed Oct 14, 2015 3:59 am
by LuvMultimedia
awesome--was wondering if there is a way to create panoramic 360 images using Octane....?
Re: OcDS Setup v2.2 (last Beta)
Posted: Wed Oct 14, 2015 12:40 pm
by larsmidnatt
LuvMultimedia wrote:awesome--was wondering if there is a way to create panoramic 360 images using Octane....?
Octane yes, in the standalone. Not with the plugin currently. There is a more complete answer in the thread you opened.
Re: OcDS Setup v2.2 (last Beta)
Posted: Thu Oct 22, 2015 5:00 pm
by vortex3d
Soooooooo. I guess we're all castaways waiting to be rescued by a final OCDS release, again.
My BIGGEST issue is lag while the viewport is open and I try to pose cameras or characters (w/o LIVE on).
It appears to be permanently updating the scene's geometry, no matter what. Sometimes i seems to be random, only because I don't know the source or how to reproduce it consistently.
Closing the viewport doesn't stop the symptom once I go down this road.
I can't even reset the plugin to get rid of it, and actually screws DS to the point I have to restart it.
I tried re-installing OCDS from scratch, same problem.
I loaded different scenes with G2 characters, no change. Every complex, multi character scene behaves like this now. Camera and joint movements are the worst at 1-2 fps.
I know the plugin is the culprit since it only lags forever after rendering a preview.
Characters or cameras don't behave this way by themselves in an empty scene.
I'm using GROUPS to organize everything in my scenes, could this be bugging something in OCDS?
I haven't found ANY workaround but I know some of you have experienced this, have you found any fixes yet?
Re: OcDS Setup v2.2 (last Beta)
Posted: Fri Oct 23, 2015 1:57 am
by abayliss
vortex3d wrote:Soooooooo. I guess we're all castaways waiting to be rescued by a final OCDS release, again.
My BIGGEST issue is lag while the viewport is open and I try to pose cameras or characters (w/o LIVE on).
It appears to be permanently updating the scene's geometry, no matter what. Sometimes i seems to be random, only because I don't know the source or how to reproduce it consistently.
Closing the viewport doesn't stop the symptom once I go down this road.
I can't even reset the plugin to get rid of it, and actually screws DS to the point I have to restart it.
I tried re-installing OCDS from scratch, same problem.
I loaded different scenes with G2 characters, no change. Every complex, multi character scene behaves like this now. Camera and joint movements are the worst at 1-2 fps.
I know the plugin is the culprit since it only lags forever after rendering a preview.
Characters or cameras don't behave this way by themselves in an empty scene.
I'm using GROUPS to organize everything in my scenes, could this be bugging something in OCDS?
I haven't found ANY workaround but I know some of you have experienced this, have you found any fixes yet?
I have the exact same issue as you, however I don't have it with joint movement, only when moving an object/whole figure. I originally thought the issue happened with any figure posing adjustments as well as object movement, but this was only because the figures had objects parented to the limb, or a child of the limb I was attempting to move. So when I adjusted the pose of the figure, it would then move the parented object, causing the freeze. If a limb does not have a parented object, then it can be bent and twisted without any problems. I think if you hide the parented object it may also fix the freezing, but it's been a while since I did my testing, so I can't confirm.
I also found that hiding multiple figures/objects in the scene can reduce the length of the freeze. So I would start assigning figures to groups, and then hiding those groups to hide multiple figures and all there parented/worn objects with a single click to reduce the lag while adjusting another figure.
Re: OcDS Setup v2.2 (last Beta)
Posted: Wed Nov 04, 2015 11:47 am
by sixb0nes
sixb0nes wrote:Didn't see this bug posted:
- If you move/delete the HDR folder you had previously selected a file from, as soon as you choose the ellipses to open the Image Browser, the application crashes. It appears to be trying to reference a folder/file that no longer exists. This may apply to the Image Browser in general - not sure.
Anyone know a way around this? Clearing this cache somehow? REALLY annoying.
Re: OcDS Setup v2.2 (last Beta)
Posted: Thu Nov 05, 2015 8:18 pm
by wlebrun
I really wish they would put the ability to use HDR Light Studio with this plugin so i can update.
Re: OcDS Setup v2.2 (last Beta)
Posted: Fri Nov 06, 2015 2:31 pm
by bepeg4d
Hi,
what is missing is the connection between DAZ and HDRI Light Studio, not with Octane, as you can see from the lightmap site:
https://www.lightmap.co.uk/hdrlightstudio/connections/
If the host application has a connection with it, then Octane can render it, this is how it works in c4d for example

ciao beppe
Re: OcDS Setup v2.2 (last Beta)
Posted: Sat Nov 07, 2015 11:58 am
by sixb0nes
sixb0nes wrote:sixb0nes wrote:Didn't see this bug posted:
- If you move/delete the HDR folder you had previously selected a file from, as soon as you choose the ellipses to open the Image Browser, the application crashes. It appears to be trying to reference a folder/file that no longer exists. This may apply to the Image Browser in general - not sure.
Anyone know a way around this? Clearing this cache somehow? REALLY annoying.
Okay, figured it out on my own.
Delete:
Regedit->HKEY_CURRENT_USER\Software\DAZ\Studio4\OctaneRender
You could probably just remove the ImageBrowser* entries. Someone needs to add this one to the bug list. I don't always keep the HDRs I reference in the same spot, or at all if they are crappy
Cheers