i had to face some private family issues during the last year, which did increasingly affect my productive capacity up to a point last july, when i was no longer able to commit any time or energy into plugin development. although these issues were outside of my control, i still feel the need to apologize for delaying your experience on the next version of the plugin.
the reasons for these issues are behind me for a few weeks now, thus it is possible to give some info about how i want to and will proceed further; a number of decisions were made in coordination with OTOY, which focus on giving OcDS users something at hand as soon as possible and a clear outlook.
also, i'd like to note here, regarding the general future of plugin development: OTOY is at any time ready and willing to take over development in-house if i cannot continue for some reason; so there is no need to worry that the plugin might be abandoned. as i'm now getting back in shape, and haven't ever given up on the project (which i have invested so much time and passion), there is fortunately also no need to go that route.
steps to recovery:
1. get you the work i've done over the past months as soon as possible: on sunday, september 14, 8pm cest, i will release a "PREVIEW" 1.5/2.0 version. this will be a snapshot of the last developer build so far completed - "as is". with more details about it to accompany the release.
2. get you the well-tested release version: on october 31, 8pm cest, i will upload the qualified 1.5/2.0 "RELEASE" build.
in addition i may also release a few more previews in between, if you are open to it.
there will still be limited communication beforehand; i'll need to be relatively quiet on the forums in order to focus on these deliveries. if you feel it's important, i can always be reached by pm on particular problems or specific questions. i ask for your understanding during this time.
last but not least, thank you for your support, which allows me to continue work on the plugin, and also to the people at OTOY for the amazing stuff they are constantly building. i hope this post answers recent questions and clarifies further development. i'm happy that i can go back to work now and i believe you will be happy too, once you receive the outcome.
ps: i'll read your replies while i immediately focus on the preview release...
about the state of development
Moderator: BK
Forum rules
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
Welcome back t_3!!
Glad to see you've survived another one of life's many trials.
I hope your recovery continues and I think most here are thankful for the excellent work you do.

Glad to see you've survived another one of life's many trials.
I hope your recovery continues and I think most here are thankful for the excellent work you do.

Win 8.1 Pro 64bit | GTX 660Ti, GTX TITAN, 6GB GDDR5 | Intel Core i7 3970x, 3.5 GHz | ASUS P9X79WS | 64GB RAM
- linvanchene
- Posts: 783
- Joined: Mon Mar 25, 2013 10:58 pm
- Location: Switzerland
edited and removed by user
Last edited by linvanchene on Mon Oct 20, 2014 3:36 pm, edited 5 times in total.
- Laticis
- Posts: 154
- Joined: Sun May 02, 2010 2:23 pm
- Location: Darwin, Northern Territory, Australia
- Contact:
Looking forward to testing and playing with any developments 
More previews would be great.
Besides the few issues - I would just like to add that I love working DAZ / Octane via this Plugin I also have the Lightwave Version and I prefer this one.
Thank you.

More previews would be great.
Besides the few issues - I would just like to add that I love working DAZ / Octane via this Plugin I also have the Lightwave Version and I prefer this one.
Thank you.
- swordkensia
- Posts: 19
- Joined: Sun May 30, 2010 7:11 pm
t_3,
Sorry to hear about your personal issues. I hope everything works out for you..
This is encouraging news on the state of the Studio plugin..
I can assure you that once you have a stable V2.0 of the plugin available I shall be purchasing a copy of it.
Looking forward to future developments.
S.K.
Sorry to hear about your personal issues. I hope everything works out for you..
This is encouraging news on the state of the Studio plugin..
I can assure you that once you have a stable V2.0 of the plugin available I shall be purchasing a copy of it.
Looking forward to future developments.
S.K.
AMD Pile Driver FX 8350 @ 4ghz / 16GB Ram / Titan Black / Titan Z / Win 7 64bit.
t_3: you have my support. Thanks for the very specific dates.
linvanchene:
I work in software development - and I've done a little work in the DAZ api for my own projects. For another team - or person - to jump into an unfamiliar api, especially the landmine-filled rarely-updated one that is DAZ, within the timeframe you suggest (even for chunks) *and learn the plug-in codebase and design (which is as different per project as are people who created it)* is at least one order of magnitude longer than what t_3 suggested. One and a half weeks for the first one, using the new tools, is a quick start. And if he adds previews throughout - you may get another or two by the time you suggested, on the way to one with less bugs. This may be what you are asking anyway.
But, if software were as easy as asking unfamiliar chefs to help out with a meal - that would be great. In this case, each chef has their own spoken language and regional ingredients.
Sounds like t_3 is taking an Agile approach on releasing along-the-way to his dates (thanks).
linvanchene:
I work in software development - and I've done a little work in the DAZ api for my own projects. For another team - or person - to jump into an unfamiliar api, especially the landmine-filled rarely-updated one that is DAZ, within the timeframe you suggest (even for chunks) *and learn the plug-in codebase and design (which is as different per project as are people who created it)* is at least one order of magnitude longer than what t_3 suggested. One and a half weeks for the first one, using the new tools, is a quick start. And if he adds previews throughout - you may get another or two by the time you suggested, on the way to one with less bugs. This may be what you are asking anyway.
But, if software were as easy as asking unfamiliar chefs to help out with a meal - that would be great. In this case, each chef has their own spoken language and regional ingredients.
Sounds like t_3 is taking an Agile approach on releasing along-the-way to his dates (thanks).
- Spectralis
- Posts: 561
- Joined: Thu Jun 06, 2013 10:21 pm
Thanks t_3 for the update. I've been very concerned about the development of the plugin due to problems with v1.2 that haven't been resolved. I'm pleased to know that you now have a schedule and look forward to the final release in October.
I share linvanchene's frustration with the reliance on one person development and agree that this is not ideal, especially considering the pressure this can cause for developers but I'm willing to wait until October if this is a realistic deadline. I think it's important for OTOY to review how the plugins are now developed because it's unfair and unreliable to leave the whole development with one person. While I agree that the DS API and the plugin require specialist knowledge, a system where this information is shared just in case the main developer is unable to carry on should be implemented from now on if this hasn't happened already. I know of no other company that does not use the team approach to software development.
If a team approach had been implemented then we would not now be in this situation because someone else could have continued developing while t_3 coped with personal matters.
I share linvanchene's frustration with the reliance on one person development and agree that this is not ideal, especially considering the pressure this can cause for developers but I'm willing to wait until October if this is a realistic deadline. I think it's important for OTOY to review how the plugins are now developed because it's unfair and unreliable to leave the whole development with one person. While I agree that the DS API and the plugin require specialist knowledge, a system where this information is shared just in case the main developer is unable to carry on should be implemented from now on if this hasn't happened already. I know of no other company that does not use the team approach to software development.
If a team approach had been implemented then we would not now be in this situation because someone else could have continued developing while t_3 coped with personal matters.
ASUS Maximus VI Extreme, i7 3770k, 32GB RAM, 4 x GTX760 4GB, Win 8.1 x64.

- Attachments
-
- 2.png (15.64 KiB) Viewed 5306 times
-
- 3.PNG (3.57 KiB) Viewed 5306 times
-
- 4.jpg (3.84 KiB) Viewed 5306 times
http://www.Neil-Isted.com
Intel i7 870/2.93 GHz
RAM 16GB
1x Titan (6GB)
2x GTX 660Ti 2GB
Win10 Pro 64-bit
Carrara 8.5 Pro
Carrara - OR4C
OctaneRender™ for Blender
Ds pro
OR Standalone V4
Poser Plugin
Intel i7 870/2.93 GHz
RAM 16GB
1x Titan (6GB)
2x GTX 660Ti 2GB
Win10 Pro 64-bit
Carrara 8.5 Pro
Carrara - OR4C
OctaneRender™ for Blender
Ds pro
OR Standalone V4
Poser Plugin