OcDS Setup v2.2 (last Beta)

[linvanchene]

Okay, let's start by listing generic issue points. We can expand on them as we get our list going... I can compile after reading your posts. And this would be with goal of not requiring a workaround in the future.

From my own experience, so far I know of:
(1) Materials Conversion - problems converting materials (including IRay materials) from Daz to OcDS
(2) Delete Key - while using in OcDS deletes character in Daz scene
(3) Plugin Stall - plugin no longer functions, grayed out...cannot create 'New' scene in Daz, can only load 'Recent'
(4) Non-responsive node to keyboard - sometimes you can't type a numeric figure for a node parameter, you have to use a mouse on the slider, then it works
(5) Drop-Down Defaults to 'None' - sometimes when using a node drop-down, and you select something other than 'None", it sets itself as 'None" requiring a second drop-down entry (then it works....)

Others? Let's get our list

Camera Motion Blur
Object Motion Blur
There is mixed information which of those are working.
My workstation is offline... cant test right now...

- - -

I got worried if the next plugin update will take longer.
I wrote t_3 a pm to ask what the plan is.

t_3 got several other requests for a quick fix to how the autoconversion works.
The unwanted interaction with the DS UI are also a priority.

The plan seems to be to release an update for those most pressing issues at the beginning of July.

[Notiusweb]

This is from the OcDS 'OctaneLive' tab:

These users put in time and effort into testing. You mean to tell me they all cumulatively overlooked this:

(1) Materials Conversion - problems converting materials (including IRay materials) from Daz to OcDS
(2) Delete Key - while using in OcDS deletes character in Daz scene
(3) Plugin Stall - plugin no longer functions, grayed out...cannot create 'New' scene in Daz, can only load 'Recent'
(4) Non-responsive node to keyboard - sometimes you can't type a numeric figure for a node parameter, you have to use a mouse on the slider, then it works
(5) Drop-Down Defaults to 'None' - sometimes when using a node drop-down, and you select something other than 'None", it sets itself as 'None" requiring a second drop-down entry (then it works....)
(6) Camera Motion Blur
(7) Object Motion Blur

Okay, this is my and linvanchene's list, and maybe not everyone will experience the same things, but come on, what the heck...

However, when all is said and done, I think at minimum we don't really have to see OcDS outdo Iray, but rather work well with it on a continuing basis.
I remember in other posts where t_3 asked why no one had PM'd him or something, I think a clear list would be a great thing to PM. It's a good metric gauge for any Octane professional to see where their product stands with its users.
I would encourage everyone to list, or expand, correct, etc., on what we have listed already. I won't ever expect a single update to have all fixes, but we can track it and help make OcDS better, while making it easier and more organized for t_3.

[Notiusweb]

Postby itou31 » Mon Jun 29, 2015 2:34 pm

Hi Notiusweb.

I agree with you on that some tweak should be made to obtain a good quality.
And also, Iray straight from shader and iray light looks good.
Here are my speedy comparison of V7 (Iray version use different makeup)
Iray/OcDs Mat/OcDs tgx G3F (notice the hair has not the same color !?)

Hi itou31!
I don't know how to get the color to match when it doesn't auto-convert.
But as a workaround, on right clicked on the hair, clicked "Select Surface Strands" to bring up the hair materials pane. Then where the default images are listed in Diffuse > RGB Image (.jpg), I clicked on it and selected "Browse From Disk" , and it opened a Windows folder that had the other colors, which allowed me to load the other color I wanted. Don't pick the hair shape, pick the straight line strand shape. With this technique you can load other same shaped strand images from any folder BTW.

Genesis 3 Toulouse Hair

Regards!

[linvanchene]

These users put in time and effort into testing. You mean to tell me they all cumulatively overlooked .

Daz released Iray.
The plugin needed to be updated based on each iray update.
Ocds user wanted a quick update for everyone.
It was deceided not to add another round of closed testing but to release public for all.
Remember?

- - -
So what do you want?

1) Quick public updates with some bugs?
Or
2) Closed testing and no updates for months?

---
I prefer 1.

[asennov]

But it still doesn't have a set of skin shaders that can compare to RedSpec for OcDS. But give it time and that will change.

You cannot find two artists that will agree on skin shader settings Latest skins for G3F come with separate SSS maps, those what I've seen (V7 and Adaline) are not physically correct and that's a problem, but at some point in time some PA will make it right. Or you can adjust them for your liking (as I did, not pretending to ultimate truth too ).

I think t_3 should reconsider whether this release is the last beta.

This is not beta, he can call this whatever he wants. Currently there are only two betas exist: 1.0 beta and 1.2 beta

[sikotik13]

This is from the OcDS 'OctaneLive' tab:

Photo Jun 29, 10 35 58 AM.jpg

These users put in time and effort into testing. You mean to tell me they all cumulatively overlooked this:

In addition, this list includes the username of almost everyone who's been active in this subforum for over a year. In fact, the only names I don't see on it that I know off the top of my head are my own and Spectralis. This includes people who have posted wondering about the status of the plugin repeatedly, so one shouldn't necessarily assume they were all involved in closed testing anyway.

[asennov]

These users put in time and effort into testing. You mean to tell me they all cumulatively overlooked this:

First reports of bugs in this version were within hours from the release, material conversion being one of them. All people on this forum have put their time and effort into testing. So what? I'm at the very same state with this plugin as I was 10 months ago - it's useless for me (even after I managed to produce something complete with 1.2).

I doubt there were any testers besides t_3 and tugspx at all. They tested something in their own workflow using their lovely characters and forgot that the whole 'public beta' thing is to gather info from real use cases and use it to improve the product, not just to get users' money upfront.

[Spectralis]

These users put in time and effort into testing. You mean to tell me they all cumulatively overlooked .

Daz released Iray.
The plugin needed to be updated based on each iray update.
Ocds user wanted a quick update for everyone.
It was deceided not to add another round of closed testing but to release public for all.
Remember?

- - -
So what do you want?

1) Quick public updates with some bugs?
Or
2) Closed testing and no updates for months?

---
I prefer 1.

That is besides the point. Surely a closed beta should be picking up these problems and when a quick release is made a note explaining what is overlooked or not fixed could also be released rather than leaving it up to those of us not in the beta to find out the auto-conversion doesn't work properly? The issue is, once again, poor communication that is entirely unnecessary. It doesn't have to be t_3 conveying this information - those involved in the closed beta can step in and explain what still needs to be fixed with each quick release. Also, there is no systematic way of reporting bugs apart from randomly PMing t_3. How do we know if a bug has already been reported without risking complaints that we're repeatedly reporting the same bugs or that the beta team are already dealing with them? We're damned if we do and damned if we don't! Please take these constructive criticisms seriously instead of acting defensively and posing irelevant ultimatums.

[linvanchene]

These users put in time and effort into testing. You mean to tell me they all cumulatively overlooked .

Daz released Iray.
The plugin needed to be updated based on each iray update.
Ocds user wanted a quick update for everyone.
It was deceided not to add another round of closed testing but to release public for all.
Remember?

- - -
So what do you want?

1) Quick public updates with some bugs?
Or
2) Closed testing and no updates for months?

---
I prefer 1.

That is besides the point. Surely a closed beta should be picking up these problems and when a quick release is made a note explaining what is overlooked or not fixed could also be released rather than leaving it up to those of us not in the beta to find out the auto-conversion doesn't work properly? s.

There was no closed beta as far as I am aware of for the latest plugin version put together after all those changes for Iray.

It was deceided to release what is available to everyone so everyone could help testing.

- - -

Does it make sense to you that when no one was testing it is simply impossible to

- pick up on anything
- make a note explaining what was overlooked

- - -

But yes some kind of transparent bug report system would help to know what is reported.

[Notiusweb]

Running with the list again...
I think it is helpful for our cumulative knowledge base to come together and work together in an efficient format. Likewise, maybe we could ask t_3 to view our list on this forum and make quick comments as to what is happening with the items, and that could help inform us what the status is on some of the things we have found. It could be a quick 2-way communique, because he could see what we have discovered in a single instance. If done on a regular basis you can imagine how functional that could be.