OcDS PROBLEMS RESULTING IN CRASHES - read & post here...

[kraken]

This is frustrating. I want to do a fly-through animation. I have all my object paths keyframed, and have set the camera flight in DS4.
I originally bought Daz Alembic Exporter. This worked as far as exporting object geometry but would not export the camera.

So now I've bought OcDS plugin.

A whole new can of worms. I'm unable to animate in the viewport so I exported the alembic file.
When the file is imported into OC stand-alone, I can see the camera node but I'm not getting all the translation. Instead of camera orbiting my object, It appears to compress the object along the y-axis instead of camera translation or rotating orientation.

How can I get camera movement? Sadly, I don't have time to learn blender or afford C4D, so I need a solution to finish this project. Can someone give me a code snippet that will get me started? Something that will make the camera orbit an object.

[sikotik13]

This technically is not a crashing problem, so should be somewhere else. That aside, I rarely use the standalone so could not offer you help in that regard.

As an alternative (assuming this is viable for you/your project), would it be possible to leave the camera stationary and just rotate the object(s) relative to that view? I'm pretty sure you can move the lighting too, if need be for your project. It might be easier if you are struggling with the camera.

[kraken]

Redacted. Not usable information to anyone.

[sikotik13]

Ah. You didn't mention the crash in the original post, so I had no way of knowing that there was one. Regarding moving the objects, I did say if applicable for your project. Clearly, it is not. My suggestion was based on the .abc you attached, which would be simple, judging by the name.

I understand you are frustrated, and truly hope someone with more expertise in the standalone (and/or with Alembics) can offer a suggestion to help you. If you haven't already, you might try asking in the general discussion thread, where it would get more visibility, especially among users of the standalone/Alembics.

In other threads, you posted very specific questions that were easier to address directly. It is no fault of anyone attempting to answer your question if you leave out important details. It was also recommended to you several times when you created your thread to wait until the plugin stabilized. You bought a semi-functional prototype of a "TV", after being told that is exactly what it was, by myself, Spectralis, and the creator on the first four posts of the release containing said "TV". It even clearly states specifically that many things are incorrectly or non-functioning at this time. If you are disappointed in your purchase, that would be your expectations being unreasonably high, despite being told what to actually expect.

[Spectralis]

Assuming you are using the 1.2 build, try animating from the second frame. I've found that certain animations won't start on the first frame for some unknown reason. Secondly, I assume you've keyframed your camera movement? If everything animates properly, including the keyframed cameras, in the DAZ Studio viewport then the DS/OR plugin should render each frame accurately. Despite the problems associated with the plugin I've managed to animate a number of scenes where the camera is moving through the scene so it is possible.

Many (including me) have testified on this forum that the 1.2 plugin is unreliable at rendering animations on their systems. There is as yet no solution to this unreliability. I and others have advised that the plugin in it's current state should not be relied upon especially for commercial work where a deadline has been agreed. Buying the plugin in it's current state is at the owners risk. Short of emailing OTOY or PMing the developer I doubt anyone here will be able to solve these fundamental problems associated with the current build.

The point of buying the DS/OR plugin for me was so that I could render from inside DS. For that reason I have never used the standalone or the Alembic exporter and it seems unlikely that there will be many in the DS plugin forum who will be able to advise about porting scenes to the standalone with or without the Alembic exporter. I would follow sikotik13's advice and ask those questions in the general forum.

[kraken]

That's a first. Selling beta software. Kudos for breaking the trend.

When I win the lottery I'll buy all the best software and equipment available so that I can do commercial work reliably.
I certainly would not want to go to Siggraph and claim I can do cinegraphic quality renderings like Transformers,
then have to explain why its limited, buggy, and totally cool to charge money for beta software that is unreliable.

Rendering inside DS4, yes that is the goal. Having a super fast rendering engine that only can render static geometry from one perspective, with one light source, and limited material manipulation...pointless.

In the meantime, for those of us trying to build a portfolio by offering services at an entry level cost using entry level software I have found a work-around by exporting the geometry through alembic files so that you can use all the great features that really work in Octane Stand-alone.

Its posted in the general discussion.

http://render.otoy.com/forum/viewtopic. ... 50#p205734

[Spectralis]

Having a super fast rendering engine that only can render static geometry from one perspective, with one light source, and limited material manipulation...pointless.

Despite problems with the viewport not updating I've not found the limitations you describe with v1.2 of the DS plugin. For example it's possible to create many light sources with the plugin using texture emissions.