Sky Cube sequance not matching up

[cyphyr]

HI guys, I've run into a bit of a conundrum.
I rendered out a cube map and I think the settings are right but it does not match up properly.

The camera is set to a 90 deg FOV
Each faces is rendered out at 3000 px sq
Motion blur is OFF
GI Cache is written and then read as "Equal blend within range"
Number of files to blend is 6
Ray detail region is set to "360 degree detail (highest)"

This should work

Have I missed something? I can't think what. The errors get worse as the camera progresses through its sequence.
This took all over 50 hours and my client is expecting it today

Any suggestions would be really helpful
The DEM's are obviously missing from this file (they are quite large)

[Hannes]

Without having tested your file - could it be that your stitching software didin't match the appropriate images together?

[Hannes]

Found something. I don't know if this is relevant, but as far as I know you have to switch off motion blur in your camera settings as well. In your file it's still set to 0.5.

[Hannes]

I tested your file. The only thing I did was disabling the motion blur in the camera settings. I rendered out a sequence of low quality images and stitched them together to a spherical map with an old german program called ReSPaM (I actually don't know how to create a sky cube).
Everything matched perfectly together.
As far as I remember Matt mentioned some time ago that the activated motion blur in the camera settings would offset the POV, even if it's disabled in the render settings.

[Hannes]

Confirmed! With motion blur on in camera blur the POV is different.

[Tangled-Universe]

You just beat me Hannes

This definitely needs to be filed as a bug or undesired behaviour at least.
The render node setting should override the camera setting.

[Kadri]

I found it confusing too and asked Matt here.

http://www.planetside.co.uk/forums/index.php/topic,17773.msg172179.html#msg172179

I think there should be a warning that the camera motion blur should be disabled too. Or a different solution i don't know.

[cyphyr]

Thanks guys.  Slaps fore head ...  Duh! 

I had assumed that with motion blur set to OFF in the camera settings it would simply ignore its effect.

So by "disable motion blur in Camera settings" you mean set it to "0"?

Ok then off to render again.

Will my GI Cache files still work do you think?

[Tangled-Universe]

Thanks guys.  Slaps fore head ...  Duh! 

I had assumed that with motion blur set to OFF in the camera settings it would simply ignore its effect.

Rightfully you did, in my opinion.

So by "disable motion blur in Camera settings" you mean set it to "0"?

Yes.

Will my GI Cache files still work do you think?

As the FOV has been offset my guess is that your GI files won't work anymore.
You can still test by rendering 2 or 3 sides of the cube map @ 300x300'ish.

[cyphyr]

Thankyou
yes I've re rendered the GI cache, didn't want to risk it.

[Oshyan]

Motion Blur is different than Camera Offset. The Camera Offset can still be useful to have enabled even when the actual *blur* is disabled. The Camera Offset is what I think you're seeing here. I agree it can be confusing, but the best way to handle it is not entirely clear to me...

- Oshyan

[Hannes]

The Camera Offset can still be useful to have enabled even when the actual *blur* is disabled.

I don't understand that. What could this offset be good for?

[Oshyan]

Well, Matt more or less explains why it is needed for here:
http://www.planetside.co.uk/forums/index.php/topic,17773.msg172181.html#msg172181

- Oshyan

[Hannes]

Thanks, Oshyan. That makes sense.