Machalot

I'm glad to hear!

That's a brute force solution!

The lame suggestion, but sometimes works, is too do a repair of your installation. I don't have any better ideas.

We confirmed there's a new bug that doesn't let you cycle through the pylons.

My understanding is that they need to be disabled as part of the skin data. @MYSE1234?

Sounds like the first missile needs to spin up again. If you wait 3 minutes does it work? I think we used to be able to switch missiles using IR-RB Framstegn, but that doesn't seem to be working now.

A trivial mission with just the player Viggen should make a very small track file. If you need help with that I can post my test mission later tonight.

Can you point to docs for how the KURSKORR should function?

It should be a 3 minute spin up from liftoff. I haven't timed it carefully but I haven't noticed an obvious variation. If you do find one please post a track and I'll submit a report. Between Maverick shots, I haven't found it necessary to reset to T0, only to cycle the safety, then do T1 and TV to lock. Can you check this again? I agree with you on the "direct TV fix", and I plan to submit a request for that capability. I don't think it needs to be a special keybind, though. We just need the Mav to assume an implicit T1 any time it goes from T0 to TV.

Can you post a track file? This sounds very strange.

Check your keybinds for unexpected mappings that might activate that.

Have you switched the mode to REF/LOLA? That's the procedure for loading the cartridge. There is no valid Input in AKT POS mode.

I don't remember if you can blank the number in the rearm screen. Worth a try.

I have added this to the bug tracker. Thanks for the report!

When you report the CK37 estimates the wrong wind, how accurate should we expect it to be? Is 5° and 20% speed unreasonably bad for an airborne Doppler radar? In your test cases do you fly over water? If so, do you set the Doppler switch to SJÖ? This setting strongly influences nav drift. Are you generally aware how the TERNAV system works, and accounting for its function on your reports? For example, at 2000m it will not do anything, but below 500m you might get some nav fixes if there is some terrain variation below you.

I'll semi-defend this on the ground that the most straightforward version of the underlying math to create the wind in a sim uses the "blows to" direction, so a software dev writing the code would find it natural to do it this way, especially if unaware of the met convention. (Tbh I am an aerospace engineer and I find the met convention "backward" just like using negative charge for the electron or giving bodyweight in "kg" )

Where did you read this?

This similar issue with Mission 3 was supposedly fixed in early 2022. Can you check if it works for you?

This may be referring to the fact that the Phoenix has a nozzle exit area of 0.000001 m^2 (apparently at ED's direction), which effectively zeroes out the ambient pressure correction.

In general I think the text should refer to figures and tables by number, rather than phrases like "the figure above" as shown in your kneeboard example.

Make your own single player mission.

I can't figure out the difference between time error on target and timetable deviation. What does it mean when a Bx point is selected and it calculates time "for the previous waypoint in the polygon"? What is considered previous?

Can you list the steps you are following, just to make sure you're not forgetting something?

I think without a time on target set, it shows estimated time of flight to the next waypoint, not to the target.

I just searched for this thread because there is a manual update in work, and I wanted to suggest adding the label formats for TOT and ingress Mach to the manual. If there's anything else that you think should be added, go post it here: