SetCameraInterest and general camera issues

[miscology 10]

Anyone been able to get this to do something useful? I thought it would add depth of field like you'd have with a real lens, but apparently not. I've been experimenting in my camera scripts and can't see any difference even with Post Processing set to Max. Even at high FPS the engine seems to blur things I'd prefer it didn't. Such a pity, because depth of field makes the world of difference with the look and feel of a scene.

Other camera issues I'm having:

- An inability to set FOV while camera is attached to an object and the camera's direction is set with SetDir, rather than CamSetTarget. Just won't work. Don't know why.

- CamSetTarget removes some of the "attached" qualities of an attached camera. For example, attach to the wing of a plane and you bank and pitch with the plane. CamSetTarget to some other position and only the camera's position remains. It's pitch and bank twists and turns at the whim of the engine.

VisiblePostion isn't working as a suitable replacement for GetPos. The 1.6 Beta introduced interpolation which introduced flickering into old camera scripts. VisiblePosition was supposed to be the fix, but it doesn't seem to make any difference in my experiments. I was using GetPos and SetPos but had horrible flickering, yet visiblePosition didn't really change that. Currently the only way I found to follow a moving target is to attach it to the object at some relative position.

I've found workarounds to most of my problems, but I'm enormously curious why they exist in the first place, and if my workarounds were unnecessary, and I've just done something wrong.

Any thoughts?