Machalot

I haven't had a chance to watch you track. Are you cycling the trigger safety between shots? That's how you select the next missile.

Question submitted. Let's see what they say.

Your nav drift will also be better over water if you put the Doppler mode switch in SJÖ.

Looking at that chart, I really wonder about some of those complex curves that wiggle back and forth, especially in the TIPPVAXEL and SERVOMOMENT regions. They must have either a ton of test data, or done a huge amount of analysis, to have enough confidence in all those little wiggles to put them in the manual.

When the F-86 is transonic, above Mach 0.85 or 0.9, the roll authority drops off severely.

This is good advice. When I started exploring SPA mode a while back, it was easy to make fixes, but it took me a long time to figure out how to select my SPA targets for attack. - In SPA mode, press the keypad number of the fix you took. For example, if you took 3 fixes, you created recon points M1, M2, and M3, and you can select them by pressing 1, 2, or 3 while in SPA mode -- not B1, B2, B3. - Then you can switch to NAV or ANF and the destination will remain the same.

I can add it, but before I do, what is the best way to reproduce the issue?

I have added these to the bug tracker as two separate issues: LG door clipping and fuel tank clipping. Thanks for documenting this.

It's not publicly accessible. You can try searching the forums for previous reports, but that's not necessarily easy to do and will only find the bugs reported by the general public. There's no problem with submitting things that are already tracked. Better to be thorough and let the HB staff or testers sort it out.

This is already reported in the bug tracker. This I have noticed before but never thought it was worth reporting. I can add it to the tracker. This is new to me, I didn't know there should be lights in the airbrake. I'll add it to the tracker.

I had a conversation with a HB dev who explained how it is implemented in the code as an effect on the doppler measurement error. Here's the Google translation of the text:

Need @MYSE1234's help! Here's the excerpt he provided at the time: I reposted it here: https://discord.com/channels/1071433028045377637/1071578053584638093/1077408862862311535

Are you still making updates? There's an issue with the description of the LAND/SJÖ switch. It changes the mode of the Doppler radar, not the radar altimeter. It appears on pages 114, 115, and 234, at a minimum. There may be other places.

Are you able to see the HUD symbols against direct glare from the sun the off snow, clouds, and water in other modules?

You can't make an accurate model based on qualitative descriptions. The kind of documents and data that is classified or otherwise held from the public is also, not coincidentally, the kind of data you need to make an accurate model. You, the general public, not knowing what's classified about a program might just be by design

I have found the breakers are not fully and robustly implemented. Haven't checked this specific one though, mainly I tested the trim.

Is the first stage considered active when you pull to second stage? I don't have a two stage trigger, but I assumed it would close the trigger safety before you reach the second detent and prevent a weapon release.

(I see @LazyBoot beat me to the solution by a few minutes while I was typing my long-winded answer :D)

If you are using A/A radar lock with T1, you need to clear it to T0 when you exit A/A mode. This has bit me a few times. Basically pressing the "T1 Fix" keybind [not "T1 Fix (Two-stage trigger middle position)"] sets and holds the T1 state as if the pilot is holding the radar trigger at the first detent. What this means is that when you exit A/A mode, he is still holding that trigger and it initiates whatever action T1 does in the new mode, usually a NAV fix. This is probably what's happening. Make sure to clear the T1 state back to T0 (so the pilot releases the radar trigger) before or immediately after exiting A/A mode. I'll also add that when you have an accidental NAV fix like you're seeing, you should be able to revert it by using the RENSA button once on the CK37. Don't press it a second time or you'll clear all the past fixes too.

If you already have a two-position trigger, take the suggestion above and use a modifier button on your throttle. When you hold the modifier, the trigger is T1-TV, and when you don't hold the modifier, the trigger is (no-op)-Weapon Release. Something like that.

I wold not recommend binding T1 like that. It can put the radar and flight computer in unintended modes. For example in NAV mode (which is the mode for HD bombs, btw), initiating a radar or visual nav fix, unlocking the RB75 crosshairs, or toggling the RUTA polygon in SPA mode. In Attack mode, T1 starts a radar fix for the BK90 or RB15, and uncages the RB75 seeker. I think you should only press T1 with intent.

In the real jet, T1 is the first trigger detent and TV is the second. So there is an implied momentary T1 any time you press TV.

Are you doing a nav fix intentionally or by accident when these big jumps in the waypoint locations happen?

Why don't you think that applies?

It's likely something specific about your situation. I can usually place BK90s on target. So l they are useless. Did you check the accuracy of your target waypoint relative to the target radar returns?