I am well aware someone has probably done this already, but I'm posting this "thing" anyways.

So, we've all been there. We want to have a HUD, which is easy. Then we want an HMD. Easy as well. Having one that locks onto targets? Not easy, but it can be done.

What about one that not only locks onto targets but also can fire missiles from said lock? That's a different story. At least until now (from my knowledge).

I was up to my usual tomfoolery, trying to find a way to lock onto targets from any angle when I realized something: what if instead of two cockpit parts, I had a cockpit and camera setup for locking? Here's what I thought:

Camera's Job: Lock onto targets using the "missileLocking = true" value
Cockpit's Job: record flight information so the gauges don't follow the pilot's vision.

So I set it up as per what you see on this aircraft design, and I had good news and bad news:

The good news is it worked! I could technically look any direction and lock onto targets from that vision without disrupting the flight information, allowing for true HMD combat.

The bad news is why I said technically.

So basically, when you view through a camera part, you can drag your mouse around to view the world you're in. Duh.

In order to lock onto targets, the literal camera part must move on the rotators that move when you drag your mouse to look around.

When both your view and the literal camera attempt to look around, the amount that you look around and how fast you look around both multiply. This begs the question: if the literal camera has to move, why not just look around in another camera? Well, there's another problem.

Say we have those two cameras, one mounted to the fuselage and doesn't move, called Cam1, and the other mounted to the rotators, Cam2.

Cam1: missleLocking = false
Cam2: missileLocking = true

The problem is you must be looking in Cam2 in order for the missileLocking feature to work. Therefore, we're stuck with the first problem mentioned either. At least, from my knowledge.

What's the solution, then?

The problem in short is we can't lock onto targets from another camera, like Cam1. If we can enable Cam2's "missileLocking" feature to use while in Cam1, then this system will work. That's where my smooth brain doesn't work, just like the design I've given you here.

I'm posting this just so everyone has access to it, in hopes that someone with more than 13.8 IQ unlike me can find a way to fix it. I'm stuck in college, so I don't exactly have too much free time. The "less than 14 IQ" part also plays into that.

So, if anyone knows how to fix the issue, by all means.