FOV value isn't accurate from what I can tell
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
I'm trying to do a comp match for something and trying to match the focal length. Octane shows an fov of 45° but Maya's focal length to match it is 25°. Is there some sort of camera back setting I need to change to get this to work at 45° or is Octane's value inaccurate?
FOV can be measured horisontally, vertically or diagonal... Don't know which one Maya or Octane uses, but my guess is that they're measuring different angles 
In 3ds max, the camera object has separate inputs for these three FOVs, maybe Maya has too?

In 3ds max, the camera object has separate inputs for these three FOVs, maybe Maya has too?
FOV and focal length are two differnt things.
Focal length is in Softimage a length in mm. The focus point where the camera see sharp. This should be used for e.g. DOF.
FOV are the angle who the scene is seen.
Focal length is in Softimage a length in mm. The focus point where the camera see sharp. This should be used for e.g. DOF.
FOV are the angle who the scene is seen.
Win10 Pro, Driver 378.78, Softimage 2015SP2 & Octane 3.05 RC1,
64GB Ram, i7-6950X, GTX1080TI 11GB
http://vimeo.com/user2509578
64GB Ram, i7-6950X, GTX1080TI 11GB
http://vimeo.com/user2509578
Another question i have, how can i use the focaldepth option?
I mean, give it a similar parameter in a 3d-package?
I mean, give it a similar parameter in a 3d-package?
Win10 Pro, Driver 378.78, Softimage 2015SP2 & Octane 3.05 RC1,
64GB Ram, i7-6950X, GTX1080TI 11GB
http://vimeo.com/user2509578
64GB Ram, i7-6950X, GTX1080TI 11GB
http://vimeo.com/user2509578
ya, sorry I said FOV when I meant angle. I was using the angle value and having to do 25° in Maya to get it to match the 45° value in Octane, even with the crop dimensions set the same.
This would be a lot easier to do with an FBX camera import/export - at least that way, I wouldn't have to reposition the camera, I could just tweak the angle value. As it is, it's a very finicky thing, trying to match them.
This would be a lot easier to do with an FBX camera import/export - at least that way, I wouldn't have to reposition the camera, I could just tweak the angle value. As it is, it's a very finicky thing, trying to match them.
we fixed a bug in RC1 that's now fixed in the new final i just posted,cgbeige wrote:ya, sorry I said FOV when I meant angle. I was using the angle value and having to do 25° in Maya to get it to match the 45° value in Octane, even with the crop dimensions set the same.
This would be a lot easier to do with an FBX camera import/export - at least that way, I wouldn't have to reposition the camera, I could just tweak the angle value. As it is, it's a very finicky thing, trying to match them.
that resolved the other issue, eg the camera being not correct horizontally.
Radiance
Win 7 x64 & ubuntu | 2x GTX480 | Quad 2.66GHz | 8GB
ok - it looks like it's sort of fixed. Default camera and angle is matched:
http://grab.by/41gT
But when I try and change the angle to 80 and do some simple translates, the offsets are completely different:
http://grab.by/41hl
http://grab.by/41gT
But when I try and change the angle to 80 and do some simple translates, the offsets are completely different:
http://grab.by/41hl