OctaneRender™ Standalone 1.53.1

[kavorka]

I checked turning off the shutter speed and there was no change. I havent checked frame 1034-1035 yet.

I did render out a couple of frames using the script to try and do some comp and it worked perfectly

[blobbybarack]

add or remove group into a alembic file can make crash octane when reloading the .abc scene file.

[kavorka]

Ok, so our animation we are working on has 4 sequences.
In our previz animatics, there was no shaky alembic camera, 1.53.1 fixed it.

However, in 2 of the sequences, the shaky camera returned! After everything was setup, after we rendered it out (we thought the camera was good because of our early test), we found a lot of shaking.
I read the release note that fixed the camera shake problem "Fixed precision problem if camera focal distance is set to a very low value." and checked my camera in Blender. Sure enough, the focal depth is set to zero. I increased it to 10 feet and exported it again and the shake was gone.
I wasn't using any aperture, so the depth shouldn't have any other effects, but if anyone else still gets the shakes, check your focal depth.

[roeland]

Ok, so our animation we are working on has 4 sequences.
In our previz animatics, there was no shaky alembic camera, 1.53.1 fixed it.

However, in 2 of the sequences, the shaky camera returned! After everything was setup, after we rendered it out (we thought the camera was good because of our early test), we found a lot of shaking.
I read the release note that fixed the camera shake problem "Fixed precision problem if camera focal distance is set to a very low value." and checked my camera in Blender. Sure enough, the focal depth is set to zero. I increased it to 10 feet and exported it again and the shake was gone.
I wasn't using any aperture, so the depth shouldn't have any other effects, but if anyone else still gets the shakes, check your focal depth.

Can you post an example file which still gives a shaky camera after import?

--
Roeland

[blobbybarack]

About Alembic bugs again :
Objects from an imported Alembic how do not have at least 1 poly at frame 1 is not imported by Octane.
The group pin is not available and the object not visible.

[kavorka]

Ok, so our animation we are working on has 4 sequences.
In our previz animatics, there was no shaky alembic camera, 1.53.1 fixed it.

However, in 2 of the sequences, the shaky camera returned! After everything was setup, after we rendered it out (we thought the camera was good because of our early test), we found a lot of shaking.
I read the release note that fixed the camera shake problem "Fixed precision problem if camera focal distance is set to a very low value." and checked my camera in Blender. Sure enough, the focal depth is set to zero. I increased it to 10 feet and exported it again and the shake was gone.
I wasn't using any aperture, so the depth shouldn't have any other effects, but if anyone else still gets the shakes, check your focal depth.

Can you post an example file which still gives a shaky camera after import?

--
Roeland

I just sent you a PM with the .orbx file

[kavorka]

We were just rendering an animation and got this error. This is a completely separate animation from the previous thing I posted.

It ran for 7 frames and then this came up.
We are running it again now to see if another error comes up.

[kavorka]

We started running the animation again and got 14 more frames till the error happened again.
I opened the log and this is the error message:


Started logging on 21.05.14 08:33:16

OctaneRender version 1.53.1 (1530001)

CUDA error 719 on device 0: Error code unknown.
-> Kernel execution failed (dl)
CUDA device 0: Direct lighting failed



I just started running it on another computer that has the same hardware (a 780ti and 690) to see if that comes up with an error as well.

[roeland]

We were just rendering an animation and got this error. This is a completely separate animation from the previous thing I posted.

Is this the only scene where you get these errors?

--
Roeland

[kavorka]

So far.
However, I have rendered out almost 30 frames of this animation on another computer with the same hardware and no problems so far. We will see what happens overnight.

The computer that had this error is running another animation that is very similar and has had no errors so far, once again, we will see in the morning.