OTOY Forums

Anyone else had this issue?

I'm using Octane VR 3.06-TEST4 and trying to queue some renders in the queue.

All three of these renders have camera motion in them and some focus pulls.

It's rendered the focus pulls but they camera remains static in all three renders.

If I use the picture viewer it works normally.

Any ideas?

Any scene to show it?

Unfortunately I can't share the scene as it's a job for a client.

Any suggestions of thing I could test or maybe I should install the non-test version of Octane?

I just tried installing the latest stable version of Octane VR 3.06.2 and the problem is still there unfortunately.

I just tested rendering with the picture viewer and that's still rendering fine.

For some bizarre reason the render queue isn't recognising the camera movement in the scene, just the focus pulls.

It's a problem as I can't manually start all of my renders as I'm doing them overnight.

Hi Teddi,
I have recently tested Render Queue and PV with latest version, and I can confirm that they work at the same here.
I cannot think at a reason why it does not work for you.
Probably something strange with your camera animation
As a workaround, you shoud export all your scenes to Standalone, and do a Batch Render Job with all the .orbx files at once.

Wait, one question, maybe stupid, but, are you sure to have chosen the correct camera in the Render Queue interface?
ciao beppe

Thanks Beppe,

Yes I've double checked the right camera is being used.

Not sure what's causing this.

I'm going to do a few tests with different scenes and see if I can isolate the problem.

Exporting to the standalone is a good idea, will try that too.

Thanks a lot for looking into this.

create a new - clean - project, copy only camera there.
Check if the issue is prestent.
If so, post it here. You wan't have to worry about your client and we'll have oportunity to find the issue.

slepy8 wrote:create a new - clean - project, copy only camera there.
Check if the issue is prestent.
If so, post it here. You wan't have to worry about your client and we'll have oportunity to find the issue.

Thanks slepy8.

Good idea and I would have done that, but I've done the renders I needed now. (I had to wake up in the middle of the night to set off a render :-/ )

Although I did create clean camera in that scene and the problem was still there.

I've now moved on to close-ups where I've got a simpler scene without the Kino Flo models and the table, I'm using a circular/tubular cyc, invisible area lights and a metal floor.

I've just done some test renders with the render queue and the camera movement is working now.

The scene is identical in terms of the cameras and materials and the main model.

This was the base scene that I imported the model of the table and Kino Flos into to create a few wide, establishing shots.

I don't have time investigate what went wrong with the table/Kino Flo scene right now but I'd be interested to know what it was because everything else is identical to the basic scene I'm using now.

Could it have been the Kino Flo models perhaps?

They were DAE files that were converted from Sketchup.

I made the table from basic, native cubes so I can't see how that was an issue.

Weird anyway, hopefully the scene I'm using now won't cause me another problem.

Thanks again to both of you for taking the time to offer potential solutions

I just wanted to pop in and say that I also have been having the same problem.
One thing that stuck out that you said, is that you were working with CAD files -- because I am too, and that's not something you see on every post. I am almost curious if importing a .dwg is breaking something.
I've tried to reduce the file down as far as I can, and reset everything -- the next step is of course to start with a new scene and import that all in, but... this almost doesn't seem like a true fix... that's a pain-in-the-butt work around.
Even with EVERYTHING baked to keyframes (every frame), camera and all... what happens is each computer pulling a 20 frame sequence leaves the camera in the same position as the frame it starts on. This leaves me with a sequence where the camera stair-steps to its new location every 20 frames.
What a strange, strange problem to have.

edit: my current work-around is to submit one-frame tasks for the farm.