Daz 4.7 with OcDS 1.2?

[DrHemulen]

How is the older version of the plugin working with DS 4.7?
I'm running 4.6, but like an idiot I updated my GoZ plugin, and now it doesn't work anymore as there's a version mismatch. Since I use that a lot, I'm wondering if I should try 4.7 :/

[sikotik13]

Seems to be (subjectively, of course), a little less prone to crashing. It still happens, but it's normally far easier to see it happening than the random CTD prevalent up through 4.6, for me. Basically, if it starts to hang on anything small, I save, and attempt to avoid too much futzing with the NGE when messing with materials, unless I save right beforehand. Often, whatever crashes it runs fine after a fresh start, so it's probably the memory leak Daz Studio is known for has improved a little, and actually empties the memory cache most of the time when a new scene is created, whereas 4.6 rarely did so. OcDS 1.2 works at least as well, and (for me, at least) often a little better in 4.7 than it did 4.6.

[Spectralis]

I'm having stable results with DS v4.7 and OR plugin v1.2. I can at least animate with it reliably now which isn't the case, so I'm told, with the v2 update so far. That's why I'm sticking with v1.2 until v2 is reliable.

[roro_sab]

I used Daz 4.7 with OcDS 1.2 for couple of days,
I noticed these 2 issues:
1- The camera animation is not rendered (as if the camera animation is ignored)
2- more stable than OcDS 2.x with Daz4.7 and less crashes....
(I removed OcDS 2.x and I re-installed OcDS 1.2)

[larsmidnatt]

(I removed OcDS 2.x and I re-installed OcDS 1.2)

I would suggest you make a copy of the daz directory so you can your "stable" version while testing new releases. So have two daz installs basically, one with 1.x and the other for 2.x. That way when the next release for 2.x shows up you can use it without impacting your 1.x install. Thats how I've been doing it this past year.

[DrHemulen]

Yeah that's the plan I'm still missing the GoZ plugin, but I hope I can get it from Daz supporot.
Thanks for the replies, I really misunderstood and thought it didn't work at all. I'm not using animations, so this sounds fine

[sikotik13]

Since I have hard drive space to burn, I technically have four Daz installs. One for 4.7 regular with OcDS 1.2, one for 4.7 Beta with OcDS 1.2 (some things just work better in one or the other, don't really know why), both on my ssd, then a backup of 4.7 with whatever 2.x release is out, to test it, and another 4.7 beta with 1.55 (just because I was curious if it would work better. It doesn't for me. Just a lot of extra options that either don't do anything or lock up Daz) on a secondary drive. Makes it easy to pinpoint which thing is causing a problem, more often than not. But yes, overall, I'd say 4.7 was a good step for Daz Studio, it seems much smoother for the things I do, just wish I could get rid of keyboard viewport navigation, since I'm apparently the one person who a.) never uses it, and b) used the keyboard to get to folders in my content library quicker, which no longer functions.

[larsmidnatt]

used the keyboard to get to folders in my content library quicker, which no longer functions.

ugh, that does suck. I use the keyboard for that as well. I am using 4.6 for my main Octane install and 4.7 for the 2.x prerelease. So I haven't used 4.7 enough to catch that yet.

[Hubby72]

I can agree here.
I very often use keyboard to navigate faster in content folders.
In 4.7 some keys are still working. But for some for example hitting P moves the cameraview.
But this is a DAZ Change / Issue. This time it is not a bug in octane plugin

Perhaps it can be deactivated somewhere in options. But i did not looked into that.

[sikotik13]

If you find the option, please share with the rest of us! I hate keyboard navigation, since it uses the most common keys for me, being w,a,s,d and i,j,k,l. Took me a few minutes the first time to figure out that's what was going on, and haven't been able to figure out how to make it stop.