Page 7 of 17
Re: Request for official statement concerning the OcDS plugin
Posted: Wed Oct 07, 2015 10:30 pm
by Spectralis
Messaging OTOY directly has been done a number of times but the situation seems to return the current state of no communication. There are only so many attempts you can make before it becomes groundhog day.
Re: Request for official statement concerning the OcDS plugin
Posted: Wed Oct 07, 2015 10:44 pm
by Goldorak
leblancd wrote:larsmidnatt wrote:I'd give Goldorak some slack...
He can only say so much. Don't shoot the messenger. And Otoy isn't the only group involved in this process...
...until we hear otherwise the plugin is a third party one. So while that remains true things are complicated. For all we know there may be negotiations going on, and researching logistics and all that. They can't speak about the future until things are solidified, otherwise things would just be worse if things fell through.
If this is actually the case, why has it not been said by someone in an official capacity?
In fact, someone representative of Otoy could, at the very least, explain what it taking so long to give us a status, other than "we're working on it".
Saying you're working on it -- for weeks/months -- with nothing to show for it, only makes you look like you're not working on it.
An official statement is not a solution to a problem. We're past solutions, because most people have given up (long ago).
We're merely asking for a STATUS. A statement of where we are. That is all.
If things are changing, that should be reflected in a statement: "things might be changing soon, and here is why __ ".
It's really pretty simple.
It is not easy to give someone slack, when they have been given slack for over a month with no real response other than "hold on, we're working on it". Exactly how long should we wait? <-- THAT would be helpful information too!
Over the past several weeks, we have begun the necessary steps to ensure that development and support going forward for this product will match user expectations (and our own) for 3rd party software sold on the store - definitively and consistently. This is not a trivial intervention, nor one we are undertaking lightly. We are committed to a successful and timely outcome for users.
Once the details are sorted out (we are about halfway through the process), we will be able to share exactly what changes are being made.
Thank you all for supporting Octane. We are here to support you too, and are doing everything we can to get this wrapped up as quickly as possible.
Re: Request for official statement concerning the OcDS plugin
Posted: Thu Oct 08, 2015 12:48 am
by Sorel
Goldorak wrote:Over the past several weeks, we have begun the necessary steps to ensure that development and support going forward for this product will match user expectations (and our own) for 3rd party software sold on the store - definitively and consistently. This is not a trivial intervention, nor one we are undertaking lightly. We are committed to a successful and timely outcome for users.
Once the details are sorted out (we are about halfway through the process), we will be able to share what exactly what changes are being made.
Thank you all for supporting Octane. We are here to support you too, and are doing everything we can to get this wrapped up as quickly as possible.
Thank you Goldorak, I really love Octane and am glad steps are being made so the plugin has a future.
Re: Request for official statement concerning the OcDS plugin
Posted: Thu Oct 08, 2015 2:35 am
by larsmidnatt
Goldorak wrote:
Over the past several weeks, we have begun the necessary steps to ensure that development and support going forward for this product will match user expectations (and our own) for 3rd party software sold on the store - definitively and consistently. This is not a trivial intervention, nor one we are undertaking lightly. We are committed to a successful and timely outcome for users.
Once the details are sorted out (we are about halfway through the process), we will be able to share what exactly what changes are being made.
Thank you all for supporting Octane. We are here to support you too, and are doing everything we can to get this wrapped up as quickly as possible.
Thanks for the info, I knew it was nothing small, but glad to know Otoy is working on something.
@leblancd I've already stated asking for info is a legitimate thing to do. I've done so myself. However there are some things that are just rude and don't help the situation at all. I don't recall commenting on your posts however so not sure what the issue is.
Re: Request for official statement concerning the OcDS plugin
Posted: Thu Oct 08, 2015 2:45 am
by leblancd
larsmidnatt wrote:
@leblancd I've already stated asking for info is a legitimate thing to do. I've done so myself. However there are some things that are just rude and don't help the situation at all. I don't recall commenting on your posts however so not sure what the issue is.
I have usually went out of my way to be as logical and factual as I can.
If I was rude, I would appreciate you referencing where I have done so.
Re: Request for official statement concerning the OcDS plugin
Posted: Thu Oct 08, 2015 3:25 am
by Laticis
Goldorak wrote:
Over the past several weeks, we have begun the necessary steps to ensure that development and support going forward for this product will match user expectations (and our own) for 3rd party software sold on the store - definitively and consistently. This is not a trivial intervention, nor one we are undertaking lightly. We are committed to a successful and timely outcome for users.
Once the details are sorted out (we are about halfway through the process), we will be able to share what exactly what changes are being made.
Thank you all for supporting Octane. We are here to support you too, and are doing everything we can to get this wrapped up as quickly as possible.
This is great news, I have been a huge Octane DS Plugin Fan for sometime now but found my frustrations just like most have.
Really looking forward to seeing this moving forward again.
Re: Request for official statement concerning the OcDS plugin
Posted: Thu Oct 08, 2015 4:04 pm
by leblancd
Goldorak wrote:leblancd wrote:
In fact, someone representative of Otoy could, at the very least, explain what it taking so long to give us a status, other than "we're working on it".
Saying you're working on it -- for weeks/months -- with nothing to show for it, only makes you look like you're not working on it.
An official statement is not a solution to a problem. We're past solutions, because most people have given up (long ago).
We're merely asking for a STATUS. A statement of where we are. That is all.
If things are changing, that should be reflected in a statement: "things might be changing soon, and here is why __ ".
It's really pretty simple.
It is not easy to give someone slack, when they have been given slack for over a month with no real response other than "hold on, we're working on it". Exactly how long should we wait? <-- THAT would be helpful information too!
Over the past several weeks, we have begun the necessary steps to ensure that development and support going forward for this product will match user expectations (and our own) for 3rd party software sold on the store - definitively and consistently. This is not a trivial intervention, nor one we are undertaking lightly. We are committed to a successful and timely outcome for users.
Once the details are sorted out (we are about halfway through the process), we will be able to share exactly what changes are being made.
Thank you all for supporting Octane. We are here to support you too, and are doing everything we can to get this wrapped up as quickly as possible.
Thank you for the response.
By "about halfway through the process", I take it to mean about a month, since that is the timeframe of the original post for this thread. I'll check back then to learn the details of the situation.
Thank you.
Re: Request for official statement concerning the OcDS plugin
Posted: Mon Oct 12, 2015 9:31 am
by bramsy
It is the first time I write . I waited , like many , the final update of this plugin . I'm not going to tell the enormous difficulties I faced with my clients , I think at this point the roads are two :
1. the team give a release date
2. the team give a release date
We have to organize at least the work in time , we do not ask , for now , a refund , but at least give us a timeline .
Thanks a lot.
Re: Request for official statement concerning the OcDS plugin
Posted: Mon Oct 12, 2015 11:39 am
by larsmidnatt
bramsy wrote:It is the first time I write . I waited , like many , the final update of this plugin . I'm not going to tell the enormous difficulties I faced with my clients , I think at this point the roads are two :
1. the team give a release date
2. the team give a release date
We have to organize at least the work in time , we do not ask , for now , a refund , but at least give us a timeline .
Thanks a lot.
I agree, but they need a team first. Then the team can figure out what it will take to move forward. Then figure out what they will and won't support, fix, etc. Then dates. The problem we have had for a long time is there is no team. Up until now It has been a one man project.
So even after they figure out the business end of this all, will still take time I bet for dates. First thing is them announcing the solution to our current problem. So we just need to keep gently pinging this thread for a few more weeks (I'm guessing) and we will at least have the first step(the solution).
It's good to know they intend to fix all this, because for a bit I expected them to simply stop supporting Daz completely. I'm anxious for a feature or two in OR3 and figured I would have to go standalone to ever use it. Maybe now that won't be the case.
Re: Request for official statement concerning the OcDS plugin
Posted: Mon Oct 12, 2015 5:26 pm
by Spectralis
I'm willing to wait a little longer for an update if, when it arrives, it answers the questions we've been asking such as:
1. What is the current state of the plugin?
2. When can we expect a stable non-beta release?
3. Will there be a v3 of the plugin?
4. What is the timeline for fixing the current bugs?
Please, OTOY, ensure that your response addresses the questions we've been asking for so long. Customers of this plugin have contributed a lot of information about bugs and workarounds to this forum so we've been committed to this plugin's success since its inception. Speaking on my own behalf, if these questions are addressed it will go a long way to rebuilding the trust and goodwill I once had.