OTOY Forums

I agree. There is always management to blame. I've sent them an email asking (ok...begging) them to allocate more developers to finish this project. I've got a couple of paying gigs I would like to accomplish using Ds4.7 and OCDs. I just don't see how this current state of any version is acceptable.

I attached a vid...the first part is OCDs, the second is just Daz (3Delight). OCDs is totally unacceptable results.
My only suggestion is to start contacting Otoy direct and urge them anyway you see fit to get this back on track.

...? Genesis characters have bones?

No animation.. just camera movement.. :-\

Exactly.

I added bones for my project, but it couldn't handle it. Even if I pull it down to the most basic V4 model the hair is offset and still no body movement only camera. Totally useless. I about fell out of my chair when I say how it butchered up the model. Looks like a shark got a hold of her.

Super bummed I have to use 3Delight after spending all this money on Octane.

I see the writing on the wall.

I basically mothballed Daz, Octane, and the forums for the last few months out of shear frustration. Someone was mentioning iRay, which is the same technology that Octane is using provided by NVidia.
Personally, I think OCSA is faster ( with the compiling) and has more options. Daz has problems with iRay so I'm still not able to make an animation that doesn't crash after 40 frames.
Anyhow, from all these pieces of the puzzle, here's what I have concluded: Octane got word that Daz was
going to integrate iRay and basically walked away. I'm sure the developers at Daz were stonewalling Octane because they don't want any competition. Since Octane doesn't want to refund any money, they string everyone along with false promises and misdirection.

I predict... There will NEVER be another version of OcDS released.

If this is indeed the truth, how hard would that be to admit? Life is full of risk. Had I known they were planning on cutting their losses, I could have done the same...instead they left me (and the rest of us) to go down on the sinking ship. Poor form IMHO.

I think we'll see a full v2 release but doubt that we'll get a v3 version. Noticing the website has been given another update and advertises all these ventures OTOY are now involved in but it appears as if everything, apart from the standalone, is in permanent development rather than fully realised releases. I think they're spreading themselves too thin and a lot of these ventures will end up as vapourware. The OR standalone is a solid base to build from but trying to compete with the likes of NVidia to attract business partners might lead to the dilution of the brand and end up repelling rather than attracting customers.

Displaying material parameters on drag-and-drop hover.

Is this feature really necessary, because I'm being forced to use it but don't see its usefulness, so please enlighten me.
All it does is lag my system according to the material's complexity. Eventually it will crash DS and corrupt OcDS 2.x.
I've had to re install the plugin so many times while setting up RedSpec, which is already being sold and requiring OcDS 2.x and above.

I think if the feature is left in, please give us a way to disable it, otherwise It'll be self mutilating and just bloatware IMHO.

I keep getting material replacement and duplication after saving and reloading. The more I save the more it duplicates into UNUSED.

Anyone else getting this?

vortex3d wrote:I keep getting material replacement and duplication after saving and reloading. The more I save the more it duplicates into UNUSED.

Anyone else getting this?

I have the same.
When loading a saved scene i have lots of "unused" Materials. Sometimes is has an effect on the scene sometime not.
If nto to complex a delete the unused materials and reload mats new. But if you have done lots of material changes this is not a good option - you have to redo everything
I have some characters where i changed the skin materials just the gamma slider and this always end up that this characters materials are "unused" after loading and the character is untextured.
No matter if i save as a subscene or a scene.

When i am not able to finish my scene at once i note down my materials setup either on a paper or via screenshot or keep the daz session open for days - hoping it is not crashing.

Hubby72 wrote:

vortex3d wrote:I keep getting material replacement and duplication after saving and reloading. The more I save the more it duplicates into UNUSED.

Anyone else getting this?

I have the same.
When loading a saved scene i have lots of "unused" Materials. Sometimes is has an effect on the scene sometime not.
If nto to complex a delete the unused materials and reload mats new. But if you have done lots of material changes this is not a good option - you have to redo everything
I have some characters where i changed the skin materials just the gamma slider and this always end up that this characters materials are "unused" after loading and the character is untextured.
No matter if i save as a subscene or a scene.

When i am not able to finish my scene at once i note down my materials setup either on a paper or via screenshot or keep the daz session open for days - hoping it is not crashing.

This happens in OcDS 1.55 as well. I'm thinking it was introduced then. So... I loaded OcDS 2.15 and spent some time trying to figure this out.

These are the steps to replicate the bug:

1. Load a figure (I used a Genesis 2 Female).
2. Apply any OcDS material to any body part.
3. Save as Scene.
4. Use File/Open Recent to load the scene.

The OcDS material has been duplicated and the initial copy sent to the 'Unused' drop-down.

Now..

5. File / New to clear the scene
6. File / Open or Merge to load or append to the scene.

No material duplication.

Avoid the Open Recent option!

However, I keep getting the following JSON errors in the DS log file:

JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: OctaneRender

Same number of instances every time I load or merge scenes and only if the scene contains OcDS materials.

vortex3d wrote:

Hubby72 wrote:

vortex3d wrote:I keep getting material replacement and duplication after saving and reloading. The more I save the more it duplicates into UNUSED.

Anyone else getting this?

I have the same.
When loading a saved scene i have lots of "unused" Materials. Sometimes is has an effect on the scene sometime not.
If nto to complex a delete the unused materials and reload mats new. But if you have done lots of material changes this is not a good option - you have to redo everything
I have some characters where i changed the skin materials just the gamma slider and this always end up that this characters materials are "unused" after loading and the character is untextured.
No matter if i save as a subscene or a scene.

When i am not able to finish my scene at once i note down my materials setup either on a paper or via screenshot or keep the daz session open for days - hoping it is not crashing.

This happens in OcDS 1.55 as well. I'm thinking it was introduced then. So... I loaded OcDS 2.15 and spent some time trying to figure this out.

These are the steps to replicate the bug:

1. Load a figure (I used a Genesis 2 Female).
2. Apply any OcDS material to any body part.
3. Save as Scene.
4. Use File/Open Recent to load the scene.

The OcDS material has been duplicated and the initial copy sent to the 'Unused' drop-down.

Now..

5. File / New to clear the scene
6. File / Open or Merge to load or append to the scene.

No material duplication.

Avoid the Open Recent option!

However, I keep getting the following JSON errors in the DS log file:

JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: PLORDAZS
JSON interpreter warning: Unexpected string member: OctaneRender

Same number of instances every time I load or merge scenes and only if the scene contains OcDS materials.

Thanks for the steps, will check with current version.