You simply are not on glide slope.
Now let me explain... The way the IFLOLS works is it is tied to your view, not necessarily your aircraft. For instance you can go to an external view and zoom out to the back of the deck and you can get to the proper positioning to watch the "ball" rise and fall based entirely on moving your view up and down.
So your buddies that were watching you would not see "your" ball unless they were in your cockpit. Chances are they were in an external view of your aircraft thus their "view" would be outside of a glide slope.
So, again, you are not on glide slope.
You need to provide a track file.
Second I would run the repair utility and see if that resolves the issue. I'd also make sure you are in Sim mode and not game mode.
Yes
This is to force the throttles into afterburner. Usually there is a simple "push through" but when you are on the carrier I believe you have to lift them to get them into afterburner.
Yes
You can, though it is not optimal. For instance when TWS is implemented you will be able to designate once to have a "soft lock" and designate a second time to hard lock a target. You will want to have an un-designate configured.
Yes, it will come in handy later on.
Glad to read that some of my previous points helped. In regards to this scenario...
Without knowing exactly the situation; one must keep in mind that the radar extends as a cone from the nose. Small at the A/C and gets bigger as it extends out. So it is possible to be close enough that the aircraft in front of you is not within that radar cone.
One thing to look at is how far you are scanning, i.e 40NM or so; pay attention to the "space" that is scanned - low versus high altitude. Then pan your cursor down to the bottom of the radar page. Take a look again at what altitudes are "visible" in this part of the "cone."
I've vaguely recall seeing a good 29k foot separation at roughly 35NM and only about 2k when at the bottom of the page. In your situation the "target" may have fallen within that cone or it may have just been outside of it.
Part of the problem is trying to figure out what is a limitation of the current radar implementation and what is a limitation of our understanding of how the radar works.
One thing to remember is that you have no direct control over any control surface. You have traditional flight controls to tell the flight computer what you want the aircraft to do and then it moves whatever surfaces it determines will accomplish your goal.
Post a trackfile, there are many things you could be doing wrong, unknowingly, that is leading to the issue you are seeing.
Also reference my previous post, I do not experience the issues you are seeing when operating the radar.