Page 2 of 38
Re: OcDS Setup v2.2 (last Beta)
Posted: Wed Jun 10, 2015 1:35 am
by larsmidnatt
Protip: if you notice anything weird with the plugin, save a new copy of the file and close daz and reload everything. This helps with old files you may be opening for the first time in the new plugin, as well as if you do something crazy like below.
Proof that there is some success with geografts now. I notice some quirks, but I think its usable now...I expected this extreme example to fail actually. 3 geografts at once...
UPDATE: Tested both Genesis and Genesis 2 female. Both my catgirls now work! I suggest you create the figure with geografts. Save, close. Reopen then create materials for the best success.
I'm not done testing, but thanks t_3, this update seems solid so far.
Re: OcDS Setup v2.2 (last Beta)
Posted: Wed Jun 10, 2015 2:38 am
by thongology
Anyone else having trouble typing exact values into the NGE? Or the LDB when searching for a material? More often than not I am unable to type exact values; only the sliders work.
Re: OcDS Setup v2.2 (last Beta)
Posted: Wed Jun 10, 2015 3:07 am
by swipswap
This release is making squeaky wheels like myself shut up. Very solid and professional plugin. Finally being able to ditch 4.7 is a huge relief. Looking forward to hearing about the roadmap.
Only issue I've had so far is the viewport resizing when you show/hide the side tabs, especially annoying if you have the viewport maximized on another monitor. Seems like an obvious bug that t_3 is probably already aware of but I submitted a report anyway.
If anyone is having an issue not being able to upgrade the plugin from v2.1 to v2.2 like I did, deleting
plordazs.dll from
C:\Program Files\DAZ 3D\DAZStudio4\plugins\OctaneRender prior to upgrading did the trick for me.
thongology wrote:Anyone else having trouble typing exact values into the NGE? Or the LDB when searching for a material? More often than not I am unable to type exact values; only the sliders work.
How precise are you trying to be? The manual doesn't say how precise float values are but the standalone interface shows 7 digit precision (1000.000). Haven't had an issue yet with typing in values or filtering the Live DB.
Re: OcDS Setup v2.2 (last Beta)
Posted: Wed Jun 10, 2015 3:42 am
by Veneris
The animation works wonderfully, T_3 I invite you to eat some Tacos. Here in México.
Re: OcDS Setup v2.2 (last Beta)
Posted: Wed Jun 10, 2015 4:26 am
by birdovous
I would say that this release was timed very well as today I should receive a package containing two new Titan X cards to replace my old Titan and 780 Ti. So I'm really looking forward to give the new plugin a spin and burn in those Titans!
btw what is the recommended DAZ version for the 2.2? Should I use it with the 4.7 I use now for the v1.2 of the plugin or should I go with DAZ 4.8?
Re: OcDS Setup v2.2 (last Beta)
Posted: Wed Jun 10, 2015 5:04 am
by TRRazor
Thanks for the update t_3 - looks nice so far and seems to run very stable.
Good work!
PS: Seems to run well in DS 4.8
Re: OcDS Setup v2.2 (last Beta)
Posted: Wed Jun 10, 2015 5:17 am
by Laticis
Thank you very much t_3

Re: OcDS Setup v2.2 (last Beta)
Posted: Wed Jun 10, 2015 5:41 am
by voto1979
I really like the overall look and how you structure the plugin ... its very accessable (even better as the standalone version but I guess it's personal preference)
Everything's in place clean an quick to access. The only thing is that we could dock the render viewport in application itself.
However I am very happy with the UI.
Re: OcDS Setup v2.2 (last Beta)
Posted: Wed Jun 10, 2015 7:07 am
by asennov
Thanks for update, shall test it this evening.
(Ho-ho, spells still work

)
Re: OcDS Setup v2.2 (last Beta)
Posted: Wed Jun 10, 2015 10:09 am
by t_3
thongology wrote:Anyone else having trouble typing exact values into the NGE? Or the LDB when searching for a material? More often than not I am unable to type exact values; only the sliders work.
what happens? does the input field go out of focus, so that the value is reverted?
this could happen when the mouse is moved away, and another ui-element captures the mouse focus - this would trigger esc/input-undo on the last active input field.
i was able to force such a behavior by moving the mouse around a bit (after clicking into an input field), and at some point it went inactive - what it actually shouldn't do. if it's that, there should be a fix - once i found out what other element(s) may steal mouse focus but should not.