I've got a significant update for you. On a whim, I tried it on the latest release build, and it worked properly. Now it was time for my digital hording tendencies to shine through, as I still possess the knightly builds from that far back on my drive. After trial and error, I've narrowed it down to the knightly where things don't work properly in this mission... February 23rd. A quick check of the post for this build reveals a few changes regarding eyepoints. I'd bet that's the source of the problem.
[Edit]
So a bit of an oddity. Under the Feb 22nd build, although the eyepoint was properly situated, I couldn't fire my primary guns for some reason. It turned out that it wasn't assigned to a button for some reason, but the odd thing is that when I tried to bind it, it wouldn't recognize any button pressing. In game, every assigned button worked, but the control config menu wouldn't register when I pressed a button. Restarting with a newer build allowed me to assign it, but I still got the same wrong-viewpoint issue, so I had to switch back to Feb22 to play.
[Edit2]
Got it! I'm not sure about the issue I just mentioned with button assignment, but I figured out what the problem with the eyepoint in newer builds is, and it's a problem with BP. The Ainsarii fighter that you're flying pretty much exclusively in Tenebra, although it has an eyepoint, it doesn't have a normal assigned to it. I gave it one and then reloaded the game under a new Knightly, and the problem was rectified. I guess that the change in the Feb23 build no longer took 'look forward' as a given.
