(solved)

[linvanchene]

edited and removed by user

[asennov]

i said that already, and say it once again: if daz studio was such a great base for high-end render plugins - technically or because of user interest - why aren't you already able to choose between vray, arion, maxwell, indigo, thea, fry, ...?

You know the answer already - these companies have different busyness model. (I rememeber rumors about Thea for DS).

given the fact, that there was no single other developer ever asking to make an integrated daz studio plugin

I was (right before you've made this post ) and got answer from Otoy: "We are unable to provide access to the SDK"

i'm the only maniac that was willing to invest more than 9000 work hours into such a project...

Now count the hours your users invested into testing your software. Remember: testing is paid job. Some of them had to do HW upgrade just to be able to test it. Look from their POV.

counting features that are available in the standalone but not in the plugin is utterly useless.

Exactly. What counts is if software is doing what was declared it has to do. I would be happy if V1.2 of plugin just work as it was intended without me having to check EACH of thousands frame of animations for missed materials and misplaced models or after hours/days of rendering finding that half of frames are actually one repeated frame. After all, that's me who pays for electricity.

Features may be added when core functionality is stable, working other way will get us what we already have. What to add is up to you (I would be happy if only proper object-deformation MB was added, others have their prefs)

if i recall right there were 3 updates in the past 5 weeks, and the next one is coming friday. if that is not fast enough for you or you or you, just drop me a pm and we will talk about a license return.

Only last one has managed to start on my system, all others just crashed at DAZ Studio load (and I recall the reports on forums by others with the same behavior). 1.2 sorta works.

as you may have noticed, daz starts pushing 4.7 which means anybody who uses dzim to update, gets any 4.6 version completely wiped out, thus i _need_ to support it by now (actually around a third of the current plugin installs run on 4.7 already); in particular that means i had to spend quite some time to fix things that 4.7 did brake; in other words, even if the studio sdk is still unchanged since the 4.5(!) studio release, ds 4.7 again behaves different in some areas, and there are new features that collide with previous plugin methods; there is what i call a bug in all current 4.7 versions that affects geometry positioning (try it in 4.6 and you'll see it works) - of course i need to fix that on my side, as it is unclear if the behavior in studio will be reverted. there are even new features that are no longer accessible through the 4.5 api, that needed extra time to work around. note ahead: a particular feature - the "local dimension" in the daz camera isn't going to work, because octane doesn't support camera-specific render sizes (apart from the fact that the old api doesn't even allow to access these values).

I have 3 DS plugins written by yours truly back in 2013 for 4.5 - I even have no need to recompile them when the Studio changes versions. Needless to say that old scenes load in new studio flawlessly.

No need to blame DS team as they push Studio towards their goals (to help produce and sell more models of cute girls ) You made your decisions at the design stage (like having material data to save as base64 encoded binaries instead of JSON or using invisible node to save Octane settings instead of custom scene object) and it's you who have to live with all them (not limited to mentioned above )

btw, i'm perfectly fine with anybody currently not recommending the plugin - to participate in a beta and to take all the problems that come along is not for everybody. still, those who can accept it as is, have meanwhile rendered around 19.000 stills... during the last month only. apparently it's not that bad for everyone.

the plugin is in beta because the developer - me - is not going to pull off the beta label until most problems are sorted out. gmail was 5 years in beta, so what does that tell you? exactly - nothing. just that things need time; some more, some less.

Stop call it beta - it is only called so to let Otoy sell it under the Beta program. Beta quality means that software has all major features implemented AND tested with internal QA, major issues are known and listed and possible workarounds are suggested. Even V1.2 doesn't fall under this category (will not reiterate on counting it's bugs).

OK, will get my money back and try to take off with Carrara.

[enigmasi]

I think you miss old times when they release updates every two years or something like that instead of every month something new from Otoy

[Hubby72]

I miss just a stable running version to work with. Thats all.
None of the versions neither the official one from download section nor the testversion is able to run without bugs in the basics.
If you want read the DAZ forum part here feel free.
Randomcrashes when assigning materials. Wrong positioning of scene objects. Viewportrendering that does never stop when closing the viewport.
These are basics. No new features. That is all i expect from a render. There are objects in a scene, lights and materials and that can be rendered.
I checked the forums of other plugins and could not find an as long buglists as the ones in daz plugin forums.

As long as t_3 is not accepting the things users reporting or complaining it will not change.
From my perspective he needs help/support to find the things he is not seeing.
And he needs help in priorize all the topics on his list.
This is why i think Otoy should intervene. This is nothing program code related. It is planing. Just someone who is taking the load from his shoulders so that he can do his work and perhaps point him in the right direction.

[wendyluvscatz]

I have a lot of respect for those who code
have played with the standalone using Alembic import last week and realizing a LUA script needed for camera work I really appreciate the DAZ studio plugin
the one that renders alembic is static though there is a timeline and the only one that you can tween between points on does not use a timeline
a clever somebody could possibly combine the two scripts, I took one look in notepad and fainted.
I am just glad T-3 was keen enough to work on a plugin for DAZ studio, I am still weighing up if I want to buy the Poser or Carrara ones as well but though I have demos of both I have not been so far tempted as seem less user friendly than his is.

[larsmidnatt]

Whether it is a hobby project or a full time job really doesn't matter.

Many of us are happy that there is an Octane Render plugin for daz studio. But on the other end we want it to be stable and up to date for both Daz Studio and Octane versions. The people white knighting and telling us to be quiet are the ones that don't help the situation at all.

I still think better communication would help defuse some tension. Like I just found out we should be expecting an update in this thread in the general forums and not the Daz sub forum.