Feature requests

[face_off]

In Poser I can just do 50 scenes in one document by key framing each figure in each fram. Tried that in Daz and didn't work. Any ideas?

If you want assistance with an issue, can you pls provide a complete description of the specific issue you are having, and include the workflow to reproduce the problem, and screenshots and/or a sample scene.

Paul

[morphious2013]

you are the one who told me how do it in Poser. How can I do the same in Daz?

[sikotik13]

you are the one who told me how do it in Poser. How can I do the same in Daz?

Pretty sure what he's getting at is you are in no way clarifying where exactly your issue is. You just say doesn't work in Daz, with no other details given. Is it that the timeline in Daz doesn't update correctly? The timeline does, but the plugin doesn't keep up? Does the plugin update something incorrectly somehow? What specifically is it that doesn't work in your workflow? It's impossible to assist you based on a description that vague, regardless of how many times you repeat it. AFAIK timeline key-framing works fine in Daz studio (or did in 4.7 at least), but I haven't tried it with the Octane plugin, as I've had no need. If it just didn't work at all, I would assume the people doing animation would be pointing out that animation is broken. Anyone would need more info than you are giving, which is why he asked for actual information if you want help. Odds are pretty good someone here could help you troubleshoot it, even if face_off can't (for some reason), but we need information to help you.

[face_off]

Pretty sure what he's getting at is you are in no way clarifying where exactly your issue is.

Yes.

[linvanchene]

Update/Edit:
It seems that I have taken a statement of another post out of its original context.

In order not to go completely off topic I create a new thread separate thread to give some examples what issues remain when animating OcDS specific values:

viewtopic.php?f=44&t=52768

edited:
removed some information that would be duplicate.

1. It would be nice to have Octane keyframes appear on the DS timeline, and to add the option to 'auto-key' everytime we make a change.

This would be a highly complex change - and I doubt it's something I could implement - sorry.

I did not make any post about this when I read it the first time.
But maybe not commenting on this gave the wrong impression.

If it just didn't work at all, I would assume the people doing animation would be pointing out that animation is broken..

The reason I was not going on a rampage over the broken and half finished animation features is

- I thought that it would make sense to give face_off time to address all those issues that affect rendering of single images first
I do realize that for those people who are mainly interested in animations sitting around another six months or a year waiting for solutions may not be that easy to accept. But then again it probably is not the best use of time of face_off to find solutions for issues that may be better solved on a different level.

But NO I am not at all happy about the state of animation rendering in OctaneRender standalone and the OcDS plugin and hope in the long run this situation can be improved.

- - -

Option 1:

- in general it seems there may be some upcoming changes to the animate, keymate, graphmate plugins for G3F and maybe even Iray.
Maybe some of those changes will open up new solutions for the OcDS plugin.

Maybe face_off could work together with GoFigure to find a way to bring OcDS animated values to GoFigure plugins?

http://www.gofigure3d.com/site/

- - -

Option 2:

I still hope that the OctaneRender standalone team will find some time to finally provide an "official" timeline solution that then can be picked up and supported by the plugin developers.

- - -

[sikotik13]

For the record, I wasn't attempting to speak on the Octane specific feataturesPrimarily why I mentioned I haven't attempted to use them. Cheating batch render with the basic timeline has long been a thing for Daz Studio itself, and never required any advanced plugin. It just requires keyframing anything you change on the timeline, by node. As long as you don't change what is in the scene, you can re-pose those things any way you wish. It's just skipping the animation part and moving things far more drastically per frame. Like doing a storyboard or comic strip, which were typical use cases. Going off of that method, based on the assumption it was what was referenced as being done in Poser (where the method originated, to my knowledge), sort of illustrates the underlying point. Without clarification on what is not animating, it's impossible to say what the specific issue is.

I also assumed there were still issues with the Octane soecific features, which was why I specified "if animation didn't work at all." To me, that was intended as "if Octane broke what native functionality that already exists in Daz somehow, someone should have mentioned it by now." If that was conveyed poorly, I apologize.

[morphious2013]

Ok. I appolagize. I need to address Daz directly. Nothing to do with plugin itself, but rather Daz studio key framing. It's just that faceoff told me how to do it in poser. Creating 50 scenes, each one on 1 frame, key framing each character so down the line everything stays posed separately in each frame. Thus bypassing the need for batch render. I apologize for my hasty efforts.

[face_off]

But NO I am not at all happy about the state of animation rendering in OctaneRender standalone and the OcDS plugin and hope in the long run this situation can be improved.

I'm still unclear if there is something specific in the plugin with is not working with animated scenes. If there is an issue where you can provide me a sample scene which reproduces it - I can take a look.

Paul

[sikotik13]

If I understood linvanchene's post correctly, the issue is that there is no representation anywhere of what is keyframed how from Octane, with the exception of the Octane Camera, as that is keyframed on the Daz Studio timeline. Meaning, there is no way of figuring out what values one had for anything done in the plugin, nor a way to be sure one is editing it correctly. The lack of ability to see/verify/check any of that would probably make it hard to accurately report/reproduce it, since there's almost no feedback at all to give, other than smatterings of guesses. That lack of feedback appearing to be at least a large part of the problem.

Please correct me if I screwed any of that up, linvanchene. I am only trying to reword for possible ease of understanding, and hope I actually understood what the issue is.

[face_off]

If I understood linvanchene's post correctly, the issue is that there is no representation anywhere of what is keyframed how from Octane, with the exception of the Octane Camera, as that is keyframed on the Daz Studio timeline. Meaning, there is no way of figuring out what values one had for anything done in the plugin, nor a way to be sure one is editing it correctly. The lack of ability to see/verify/check any of that would probably make it hard to accurately report/reproduce it, since there's almost no feedback at all to give, other than smatterings of guesses. That lack of feedback appearing to be at least a large part of the problem.

This sounds to me more like a "design limitation" to me than a "bug". DAZStudio does not seem to natively support plugin properties being animated - so the plugin has it's own keyframe system. You can edit the graph of a property (for example the Kernel->Specular Depth), but you cannot easily identify if a property has keyframes. DAZStudio is a free app. You get what you pay for. If you are wanting to animate Octane parameters in a production environment, so probably need to move to a 3d app which has better support for keyframing properties (like Modo, c4d, 3ds max, Maya).

Paul