Gator762 opened this issue on Jan 15, 2016 ยท 199 posts
Male_M3dia posted Tue, 19 January 2016 at 10:30 AM
WandW posted at 11:25AM Tue, 19 January 2016 - #4250128
DreaminGirl posted at 11:07AM Tue, 19 January 2016 - #4250119
Prior to the release of P11, SM did in fact reach out to Daz about Genesis implementation, but Daz was not interested (I could look for the exact quote from Nerd, but I can't be arsed)
Sure you could say that is 'too little too late', but it says to me that Daz has no interest in ever supporting Poser again, so that is the end of that discussion. Time to move on.
Here's one instance, but recall a more detailed discussion somewhere... (EDIT:crosspost with Bruce)
_ "We don't control the DSON plugin, that's DAZ's property. All they have to do is update the plugin to support Genesis 3/Vicky 7. I'd love for all of you to have the power in poser to work with whatever figure you want to use." [Why don't Italics work anymore??] _
Considering the latest version of the DSON Importer doesn't work properly on Genesis 2, and hasn't been updated in nearly a year, (I use the previous Beta) I'm not expecting anything to happen soon.
One again, SM sidestepped the issue bringing in a false argument about the plugin when the full DSON spec is posted for them online to import like reading any other file format. Let not trot this false argument out because there's a major different between the "DSON Importer for Poser" and the "DSON specification". It's already been noted that DAZ has taken the importer as far as it can go because of the performance issues with python, that's why DAZ mentioned reading the specification natively, not trying to use some tool to hack the importer which would be a DCMA violation. It seems really uninformed that after all these years, SM doesn't know the difference. But I think we're getting away from the subject revolving everything around DAZ. The discussion really should be about what Poser should be doing to address customers' concerns.