I'm jumping in here again to offer one last "plea" for you fine Corona devs to please roll this fix out into a final 1.7 hotfix.
2.0 is still a way off, it seems, and even when it is released we, like most others, are unlikely to jump on it until at least 1 hotfix is out, so we're stuck with a broken CoronaCamera for quite some time. This bug is super annoying and causing regular issues with every viewpoint on every project. Plugging in 24mm into your camera settings and then shifting quickly turns that camera into more like a 17mm or similar, making it very hard to quickly nail down views at the classic focal lengths. It also makes it impossible to quickly extend previous renders, which was dead easy previously, when shift was completely reliable.
It's pretty frustrating knowing that you've already fixed this long ago and you're sitting on the fix, refusing to roll it out. Is it really likely to break something else if literally only that fix is included in the update? With a simple "legacy" checkbox included, so that coronacameras already using tilt/shift aren't then affected unexpectedly, of course, as would be necessary.
You've already said no to this multiple times, so I'm not expecting a sudden "yeh ok" but I felt it worthwhile harassing you one last time.
For what it's worth also, I really strongly encourage you not to release a super useful amazing new feature that's not fully tested and working solidly, if you're at the end of a major release product cycle and not going to be supporting it any more. This wouldn't have been an issue at all if it had been saved for a 2.0 daily build.
And no, it's not possible for us to go back to using the PhysCam. The constant IR refreshes were a massive time-sink, and having tone mapping/exp built right into the coronacamera is not something we're willing to drop again, just so we can get reliable shift back into our workflow.
Cheers,