OcDS 1.2.120.34xx - BUG REPORTS

[linvanchene]

edited and removed by user

[birdovous]

I don't have to reload the whole scene. I just need to save the modified object as new prop and then just load that prop. Then the new material zone appears in Octane Plugin. But yes, basically a reload on DAZ side is required for the plugin to notice the change.

[larsmidnatt]

where are we are geo-graphs? Right now they seem totally broken and even worse than before. I read the 8 or so post in this thread about it and saw the reason for it not working but did we ever get any resolution to get it working now or are we waiting some more?

oh and I get that octane material duplication bug pretty regularly, hopefully that gets solved.

It seems like materials settings from last years version of the plugin won't get you the same results in the new plugin, I guess that is because of the differences in octane releases?

[Tofusan]

After the latest release of this plug-in, 3 months have already passed. Aren't these bugs fixed until OcDS 1.5 released? Is the next release after five months pass?

[Spectralis]

I'm having a recurring problem with the v1.2 plugin not updating the viewport. This occurs specifically with clothing and any objects fitted to genesis or any other figure. Sometimes the viewport will update after a few minutes, other times I have to actually move genesis forward, back or up to get the clothing to reset - then I can replace genesis back into position and the clothes will follow. There are times when none of this works and I have to restart DS. This is an ongoing problem that needs to be fixed because I spend at least a quarter of my time trying to get the viewport to update. It doesn't solve the problem if I close the viewport when adjusting figures - in fact that will actually causes the problem. I have this problem with small and large projects - it makes no difference. It doesn't happen all the time but enough to really cause me significant delays when creating a scene.

Another problem with the OR viewport is with a Genesis character that I have been using in other scenes without any problems. When I merged this character into this latest scene black lines appeared along the skin seams. The skin doesn't appear to fit any longer. This is a Genesis skin on a genesis figure so there are no compatibility issues. In the DAZ viewport there is NO problem at all but in the OR viewport these black seam lines appear. How do I fix this without reloading the skins on the figure? I've spent hours trying to fix these viewport problems - half a day trying to troubleshoot a plugin that should work properly. What a stupid xxxxxing waste of time!

I'm using the latest version of the plugin and DAZ Studio. I have a GTX 780 3GB card, 12GB RAM, Win 7 x64 and NVidia drivers which are both up to date.

[Spectralis]

UPDATE:

I tracked down the problem with the black seams appearing on Genesis to a t-shirt clothing the figure. I've merged this fully clothed character into numerous scenes (>10) without any problems before so I have no idea why the problem occurred in this scene. I fixed it by re-clothing the figure in a different t-shirt. Fortunately, I can get away with this change in continuity due to the development of the story I'm working on.

I still have no solution to the viewport updating problem apart from the ones I've already mentioned that includes restarting DS which is a PITA.

[kraken]

Hello,

Yes, its me again. I've been putting a lot of time into finding a work-around from the Daz Alembic Plugin (DAP) and OcDS plugin. I figured out a way to use both to give me the features I'm after, but I hit another wall that is going to need a fix.

When I open a .abc file created with OcDS it generates thousands of frames in Oc Stand-alone (OcSA). I have to drop frame slider to 1fps to match the actual frames exported. When I open an .abc file from DAP in the same scene the frame rate clashes and ultimately causes a crash in OcSA. If I open the .abc file from DAP first, the frame rate is roughly whatever it was in DAZ (24, or 30 fps). Of course opening the OcDS.abs file will cause a crash if you try to monkey around with the fps.

I think the problem is with OcDS. Check this screen shot.

What does "Seconds/Frame" refer to?

Notice the description says "Seconds / Frame". And the minimum setting is 15. If I wanted it to match 30fps, it should go to as low as 0.0333...3

What does spf refer to? Did it get transposed?
Is this what causes the OcDS.abc file to show thousands of frames when there should only be a few hundred?
Is this mismatch of fps causing the two alembic files to conflict and eventually crash?
What does "constant time" do? Is there is a time input that is converted to fps that is missing or on another tab?

Thanks
James

[t_3]

What does spf refer to? Did it get transposed?
Is this what causes the OcDS.abc file to show thousands of frames when there should only be a few hundred?
Is this mismatch of fps causing the two alembic files to conflict and eventually crash?
What does "constant time" do? Is there is a time input that is converted to fps that is missing or on another tab?

Thanks
James

first off: the alembic export ist - like other thingss - not yet completely ready.

the constant time option on the other hand has no effect on alembic export (and also not on fps) - it just tells the plugin, when rendering an animation, to render each frame for the given amount of seconds instead up to the maxsamples value of the render setting (maxsamples is in this case set to 256k)...

[linvanchene]

first off: the alembic export ist - like other thingss - not yet completely ready.

Quick summary:

- DAZ sells an alembic exporter for DAZ Studio in their store:

http://www.daz3d.com/alembic-exporter-for-daz-studio

Customers noted about one year ago at release that camera value export is not supported with that alembic exporter.

- The ORBX container file introduced by Otoy in OctaneRender 1.5 seems to use the alembic format to collect and export animation data.

- - -

Questions:

- Do OcDS users need to buy the Alembic exporter for DAZ Studio in order to export animated OcDS scenes and import them again in OctaneRender standalone?

or

- Will the OcDS plugin include a new and separate alembic exporter that also supports camera data export?

[t_3]

- Do OcDS users need to buy the Alembic exporter for DAZ Studio in order to export animated OcDS scenes and import them again in OctaneRender standalone?

no. the alembic exporter workes entirely from octane and exports everything that is part oft the converted octane scene,

- Will the OcDS plugin include a new and separate alembic exporter that also supports camera data export?

and this also includes cameras... once it is completed.