Page 1 of 1

Past 1.5 - A DS plugin for the OR Standalone?

Posted: Sat Mar 15, 2014 6:11 pm
by linvanchene
edited and removed by user

Re: Past 1.5 - A DS plugin for the OR Standalone?

Posted: Sat Mar 15, 2014 6:23 pm
by t_3
just a quick one: i'm going to answer this in-depth, just a little later; i know this carrying away what-ifs ;) usually when this reaches a point where coding starts, the what-if changes to sthg. like "what if i was just someone else somewhere on a beach on fiji" :lol:

ps: an example - you know i'm also digging photoshop; the situation there is, that larger parts of their api are 10, 15 or even more yrs old. never substantially changed. i can' get ps to do exactly what i want, only approximately; in return the outcome will be a good margin away from "ideal". is adobe going to change this for my needs? not until i buy the company, and even then it might last years...

Re: Past 1.5 - A DS plugin for the OR Standalone?

Posted: Mon Mar 17, 2014 11:51 am
by linvanchene
edited and removed by user

Re: Past 1.5 - A DS plugin for the OR Standalone?

Posted: Sun Mar 30, 2014 7:56 pm
by Spectralis
I think it would be a great idea to make the standalone DAZ compatible but what would be great in the meantime is to dispense with the standalone because the plugin doesn't need it. I still don't understand why we need to buy the standalone. I'm not looking forward to having to pay for v2 of the standalone when I just use the plugin. The whole licensing system seems silly to me.

Re: Past 1.5 - A DS plugin for the OR Standalone?

Posted: Sun Mar 30, 2014 8:17 pm
by t_3
Spectralis wrote:I think it would be a great idea to make the standalone DAZ compatible but what would be great in the meantime is to dispense with the standalone because the plugin doesn't need it. I still don't understand why we need to buy the standalone. I'm not looking forward to having to pay for v2 of the standalone when I just use the plugin. The whole licensing system seems silly to me.
it (currently) doesn't need it from a technical point of view - correct. from the cost pov any other solution would be probably worse, as a plugin alon would be not necessarily cheaper than standalone license + plugin license - bear in mind that plugin license costs mostly go into plugin development.

so for anybody using more than a single plugin it already saves money. ok, but you might say: what if otoy had decided to develop all plugins by themselves and just include them with octane - it would have made octane more costly, and i bet we would never have seen the range of plugins that is available now; at least not on this level of integration.

random control did manage to get live integration for max and rhino. so from the daz studio point of view: arion for ds? carrara? poser? or the same with vray, maxwell, ...? probably never, at least not until they follow the otoy way in doing it ;)