Page 4 of 17

Re: Request for official statement concerning the OcDS plugin

Posted: Sun Sep 13, 2015 1:42 pm
by Notiusweb
Post by Goldorak » Fri Sep 11, 2015 5:15 am
We are in top of this and will update you all shortly. Thank you for your patience.
The plugin is listed on the home page as one of the "Fully Integrated Plugins", and also as a "BETA Product".

OctaneRender™ for DAZ Studio v2.x Beta + Standalone Combo v2.x License (379.00 €)
OctaneRender™ for DAZ Studio v2.x Beta License (99.00 €)
OctaneRender™ for DAZ Studio v2.x Beta License 3-pack (279.00 €)
OctaneRender™ for DAZ Studio v2.x Beta License 5-pack (459.00 €)
OctaneRender™ for DAZ Studio v2.x Beta License 10-pack (899.00 €)

Everyone who purchased is reasonably looking for the BETA Product to be Fully Integrated

The user base is super active in providing support to each other, and even has a running list of issue and request items in the forum started by developer t_3:
viewtopic.php?f=44&t=47686&start=330

Please consider that the user base is an asset OTOY has to develop its BETA Product further towards being Fully Integrated. Here is current list in its entirety:

FORUM LIST FOR OcDS V2.2FORUM LIST FOR OcDS V2.2

ISSUES:
(1) Materials Conversion - problems converting materials from Daz to OcDS (Iray materials not supported, materials not converting, mesh collision causing blotches, issues related to creation of 'Mix Material', etc.)
(2) Plugin Stall - upon repeated selection/use of materials in OcDS, or when selecting 'Reload'>'Rebuild Scene' tab, sometimes plugin no longer functions, grayed out...cannot create 'New' scene in Daz, can only load 'Recent' or close down
(3) Mouse sometimes maintains priority of focus, even when it shouldn't (such as when typing information in a text field), and may lose it when it shouldn't (not actively switching to whichever section of DS is currently being moused over while not entering text). This can lead to errant interactions with both OcDS plugin and Daz UI
(4) 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....)
(5) Camera Motion Blur
- HDR background has no camera motion blur at all
- When the camera is rotating no camera motion blur is created
(6) Object Motion Blur
(7) Export of Male Gens Hip Textures from plugin to full Octane not working.
(8) Network rendering does not work if the Master node has more than one network card present and active.
(9) Adding a keyframe to the White point element in the Rendersettings tab results in an instant CTD with no error message.
(10) Different Names for Projection Modes in OcDS and OR standalone.
What is called Mesh UV projection in OctaneRender standalone is called UVW projection in the OcDS plugin.
What is called XYZ to UVW Projection in OctaneRender standalone is called linear projection in the OcDS plugin.
(11) Plugin is missing the panoramic camera node
(12) Final Render Button issues - i.e. you let a render run not realizing the save button was disabled
(13) Scene Loading OcDS Data issue - if you load a scene that had OcDS data in it while the plugin was not enabled, saved it and opened later with OcDS enabled, scene does not retain the OcDS data

WORKAROUNDS:
(1) Unwanted Pixelated ‘Toonish’ Textures – Occurs because material parameter for Normal Map is set to "2" by auto-material. Set it to “0”
(2) Iray Eye Texture gives solid white eyes in OcDS - right click and select 'Eye Moisture' material, set Opacity for this material to "0"
(3) DOF - can change the settings in DAZ but there's no effect in Octane even after re-loading the scene - selecting a camera view should fix your problem.
(4) Octane doesn't save the applied materials, you have to load and apply them every time you open a scene - check your preferences in octane, make sure to read/save .duf. Also, you can save your octane mats as presets (and even templates) to save some time.
(5) Dr. Hemulen's Suggestion for material conversion problem:
Convert to a simple glossy material, but be sure to capture ALL of the textures. Include a bunch of templated materials - skin, eyes, fabric, leather and such with the release. Then just drag and drop them on the simple, auto-generated mats or use your own.

FEATURE REQUESTS:
(1) Highlight empty Image Fields in bright red, as well as the materials in the Octane Material List. If something got left out or lost in a scene would make it easier to see when something is missing. (i.e. - Recent Normal Map issues, and issues like when building a character skin with different face/lip maps ,the lips will have missing Spec or even Bump maps.)
(2) Add Out of Core support to network render Slave nodes.
(3) A button to resize all textures in the texture tab. It would be a real time save for us who render smallish images on smaller cards, instead of having to click each individual texture. A "Default texture size" drop down in Preferences/texture settings would also work
(4) Save texture size settings (i.e. 1/2,1/4 ...) with the file
(5) HDR Lightmaps - adding the functionality that the Poser version has for the HDR Lightmap Plugin.
(6) Use the "Render SubD level" setting in Paramers/Mesh Resolution.


Thanks OTOY! Regards!

Re: Request for official statement concerning the OcDS plugin

Posted: Wed Sep 16, 2015 2:58 am
by larsmidnatt
@Notiusweb, thanks for that post. I have more bugs, but have refrained, waiting for an update. Hard to post bugs when they may or may not be fixed already...

An update would be great!

Re: Request for official statement concerning the OcDS plugin

Posted: Wed Sep 16, 2015 8:04 pm
by Hubby72
I do not want to destroy any illusions , but i would not expect to much.

t_3 will or will not send a signal of life some day while blaming again the customers.
Goldarak will delete his weekly reminder to visit this forum in his lotus notes or whatever someday in october.

With luck we will receive an updated piece of software with a "final" button on it near xmas which will have same amount of bug - but different ones as now.
Nevertheless it will be usable in any way when you ship around the bugs - like the actual version do and we will live with like we do it now.
Because we were happy to have what we got even when it has lots of bugs and not working or promised features - and the alternatives are rare.

"You take the blue pill, the story ends. You wake up in your bed and believe whatever you want to believe. You take the red pill, you stay in wonderland, and I show you how deep the rabbit hole goes."
―Morpheus, to Neo

Re: Request for official statement concerning the OcDS plugin

Posted: Fri Sep 18, 2015 2:57 am
by Goldorak
Hubby72 wrote:I do not want to destroy any illusions , but i would not expect to much.

t_3 will or will not send a signal of life some day while blaming again the customers.
Goldarak will delete his weekly reminder to visit this forum in his lotus notes or whatever someday in october.

With luck we will receive an updated piece of software with a "final" button on it near xmas which will have same amount of bug - but different ones as now.
Nevertheless it will be usable in any way when you ship around the bugs - like the actual version do and we will live with like we do it now.
Because we were happy to have what we got even when it has lots of bugs and not working or promised features - and the alternatives are rare.

"You take the blue pill, the story ends. You wake up in your bed and believe whatever you want to believe. You take the red pill, you stay in wonderland, and I show you how deep the rabbit hole goes."
―Morpheus, to Neo
I agree that the process hasn't been working far as user communication. I did commit to you guys that we would ensure regular updates

We will make a formal announcement about how we are resolving this as soon as possible. Thank you guys for your patience.

Re: Request for official statement concerning the OcDS plugin

Posted: Fri Sep 25, 2015 2:00 pm
by Hubby72
Any informations about an estimate timeframe ?
I mean just for your "Announcements" - not for plugin.

Re: Request for official statement concerning the OcDS plugin

Posted: Fri Sep 25, 2015 4:02 pm
by Goldorak
Hubby72 wrote:Any informations about an estimate timeframe ?
I mean just for your "Announcements" - not for plugin.
Hoping we can share that next week.

Re: Request for official statement concerning the OcDS plugin

Posted: Sat Sep 26, 2015 1:37 pm
by larsmidnatt
i'll get the popcorn ready

Re: Request for official statement concerning the OcDS plugin

Posted: Tue Sep 29, 2015 5:39 pm
by Spectralis
This thread was posted over a month ago. The main request was pretty straight forward - could we please have an official update about the development of the OcDS plugin. I'm willing to be patient but a month is more than enough time for some level of information about the plugin to appear. This just feels like more stalling and I'm not very happy about it. Please update us this week or at least explain what is causing the hold up.

Re: Request for official statement concerning the OcDS plugin

Posted: Tue Sep 29, 2015 11:04 pm
by Hubby72
Taking so much time could only end up in a announcement we do not want to hear.
I personally expect an end of distribution of the plugin and some kind of pay-off for the remaining complaining customers.
That is why it takes the time. Otoy is checking the contracts with their legal office to calculate the payback and possible juristic acts.
Otoy as well as t_3 has already proven multiple times that they are no longer interested any more in DAZ customers.
The only thing whats left is the "promised included upgrade license" they have sold us long time ago with the purchase.

I mean t_3 has already offered it once to give license back and get back the money for the plugin - not for the standalone.
How many are we ? 20 ? 50 users ? honeypee for Otoy.

And whats left for the user at the end ?
Do not take that offer and work with the license and beta software as long as it remains active. So no change to situation now.
Or go back to Iray and 3DDelight.

I am personally an optimistic guy. But i am also a realistic guy.
I would be very lucky if Otoy and/or t_3 will prove me that i am wrong, because i really like the OCDS as it is so intuitiv to use.

Re: Request for official statement concerning the OcDS plugin

Posted: Wed Sep 30, 2015 12:29 am
by Nubblet
I wont be impressed If the plugin development stops. I only recently bought the plugin and spent time migrating all my content from poser to daz and buying a lot of genesis content and re-learning daz. It was becoming increasingly clear that poser was never going to get true genesis support, which is a deal breaker for me, because daz digures will always have the most content support. So i switched to daz studio.

I like octane. I see some nice results in iray, but the iray integration (from what i understand) does not allow much node editing/customisation. Another deal breaker for me.

Killing the plugin leaves me with 2 ugly choices, i really hope it doesnt come to that.

Who has the rights to the plugin? I would assume otoy would have them exclusively, so why cant they just give the project to another developer?