Biggus

To be fair, you've made quite a few of us a bit more educated and smarter.

I'm quite space-constrained, so no cockpit for me. I'm jealous of the quality of the work on display in this thread though! I am building switch panels that are more for quality of life than a true 1:1 reflection of reality, but I'm mostly using PCBs to do it. I print a basic enclosure and mount the PCB to it. They're not pretty, but they work well enough, are cheap, do not take up too much desk space and are fast to design. My Jester control board has been revised a few times now, as I've added features, taken away features, changed layouts, and finally changed from a Pro Micro running Mmjoy2 to a Raspberry Pi Pico running a modified sketch based on the Real Robots Configurator. If I was going to build a cockpit, I'd be inclined to stick with the Pro Micro due to the ease with which you can add shift registers, but being able to mount the Pico directly to the PCB via castellated holes (not to mention price and availability) inspired me to change hardware. I'm not quite finished building the display control panel, as I'm not happy with these particular switches. But I'm pretty happy with how the panels have turned out so far. Next panel is going to be for the AP panel (and I'll add an O2 switch and ejection seat arming switch because VR and lazy).

There are no guarantees that the switch symbology matches the actual limitations.

I'm absolutely not any kind of signals engineer at all, but I believe it's PRF eclipsing. The radar return is happening whilst the radar is in the transmit part of it's cycle rather than in the receiving part of the cycle. This is probably a grossly simplified explanation, but that's why the radar has limits on the closure it can work with. It is apparently less of an issue with pulse mode however that's not really particularly helpful when launching 54s.

Plenty of reactions. Most of us I think are content to leave it to HB to address this, with presumably the full unredacted report. I agree it's an excellent investigation.

Our current work around is for the idiot in the front to make a ker-chunk sound effect.

I find that the button inputs don't work for elevation, but having it on an axis certainly works for me.

Great bunch of skins. Thank you very much!

I can't see it until around .3-.4 on a flat 3440x1440 screen. I don't think it's just VR that this is a problem for.

Just to add to the comments so far, there are two things you should know that aren't often explicitly stated in tutorials: 1. Pay attention to the buffeting and creaking of the airframe and be gentle. Everyone rips the wings off at least once through overly violent maneuvers at high G. Learn the limits. 2. When you encounter radar issues, the problem is not Jester. It's your lack of understanding about what the AWG-9 can and can't do in nearly every instance. IMO the Tomcat and the Viper are a great pair. I find it easier to switch between them than I do switching between the either of them and the Hornet.

My RIO reports the same thing.

One thing that's really helped me is to watch the rate of change on the altimeter more than the VSI as you level out. There is a bit of lag in the VSI.

Ah ok, didn't realise it was specific to a land based campaign as I haven't played it. Nevermind.

I've had blackouts on launch pretty regularly over the last few years. I've also experienced redouts too. I've heard that head position is a large factor in whether it happens or not, but I don't know if this is true.

I think I experienced this or something similar a few nights ago. I had spawned on the SC, had made it not terribly far into the alignment and was head-down in the cockpit doing start up things. I heard a loud bang, looked up and saw that another player had spawned beside me. I didn't see any obvious damage and didn't give it another thought for a few minutes. I flipped the TID switch so I could follow the alignment process and noticed that instead of the "ASH" message, there was another acronym in it's place and the alignment did not seem to be progressing. It would appear that although my aircraft was otherwise physically fine, the gentle nudge given by another aircraft spawning next to me was enough to break the alignment process. I wonder whether you're having another aircraft damage you when you or they spawn?

That matches my experience. I wasn't sure if I was imagining it when I noticed it a year or so ago.

For what it's worth, I find it easier for some reason to switch between the Viper and the Tomcat than I do between the Hornet and the Tomcat. However, the Hornet does things that the 14 cannot do and that the Viper cannot do quite as well. So I treat flying the Hornet as a necessary chore, and the Tomcat as a reward for getting my chores done.

Vaguely recall a 100ms delay working for me a month or so ago. I didn't experiment much, though.

I'm not sure I am ready to agree yet, switchology notwithstanding. My interpretation of the passage I posted is that in a scenario where an F-4 has been vectored to a frontal intercept, a target traveling above 1800kn is going to be impossible to find in PD. Given the scenario, this means Vc of greater than 1800kn but quite a bit less than 2900kn. Maybe I'm misunderstanding something.

Look at the date. The AWG-10 still hadn't reached proper production by May '66 when the first J hit the fleet. The tactical manual I referenced was produced in 1972. I'll go and dig through the F-4J/S NATOPS book later and see if there's more information there, but I'd suspect that the FG.1 report might not have been completely accurate.

Just in reference to the AWG-10, the 2900 closing was in pulse only. PD was 1800. Source is the F-4B/N/J tactical manual. The 1964 document referenced earlier might have been a bit optimistic, but given the date I'm not surprised. I'd pay very little attention to the F-4X proposed performance otherwise. An on-paper-only variant of a radar that would never be produced, referencing a Sparrow variant that was still on the drawing board. Edit: I've attached a snippet from NAVAIR 01-245FDB-1T, page 1-219.

That's a really informative response. Thanks @Naquaii.

I know it's not going to be exactly the same (or perhaps even enough information about the inner workings), but the F-4B/N/J Tactical Manual has quite a bit of detail about how it appeared to work in the Phantom, if you'd find this useful (and don't already have a copy of it) @IronMike.

I think I'm gradually getting my head around it after a couple of dozen passes now, but I'd love someone to show us some technique with the input window on screen. I'd also really like to get a run-down on what we can do to make the burble stronger or weaker in the mission editor.

Well done, guys. Looking forward to angrily swearing at the carrier, the wires, the LSO, the deck crew and the poor unfortunate people who wander into my study over the coming days and weeks.