Machalot

Unfortunately there are videos online that incorrectly describe it as an IR Maverick, but it is the visible light version so night ops are not guaranteed.

A track would be very useful. Or provide the mission file so others can test it themselves.

I was not able to reproduce this bug. I started at Sukhumi and set a navigation waypoint near Gudauta, and an attack waypoint past Anapa, which would be like a 20 minute flight, and takeoff time was 10 minutes in the future. When I changed the Mach number for B1 to 0.80, the takeoff time changed to 25 minutes in the future. The best way to help you would be for you to provide a track file.

There's a mod for it: However, I would recommend just flying with tooltips on for a few weeks and you'll quickly learn what all the switch and knobs do in Swedish.

Glad you could get it working. I have run into a few issues where the frequency of my flight was different from what the briefing said.

What do you mean? Is this a new DCS feature?

Does an old stable platform system align in the same time as modern strapdown IMUs? Isn't it also driven by mission accuracy requirements?

I checked in the game. The keybind called Autopilot Quick Disengage will disable all autopilot and stability augmentation, including SPAK. This is only supposed to be used in emergencies, maybe when SPAK is malfunctioning. If you press the SPAK keybind (default E), it disables HOJD and ATT, and leaves SPAK active. This is probably when you want.

I don't have access to the game right now, but I have two suggestions to try. The SPAK button might disable both ATT and HÖJD, and just leave SPAK enabled. There is a button on the control stick called Autopilot Disconnect, which apparently is called SNURK in Swedish (item 50 on p. 22). See if there is a keybind for it.

I just ran your track and saw that. I see memory addresses 83 and 86 are not working. The rumor is that 81, 84, or 85 might work. I'm not in a good position to do testing until later this week.

I know we are now officially past the deadline. I'll still post this for your consideration. Today we had a discussion about how to handle the non-functional input codes for the BK90 and RB15. One suggestion was to keep them in the manual, but note that they are unimplemented in the game. For the BK90, the only codes that are implemented are 921, 922, and 923 to control the dispersion. I believe the 91XXX0 altitude codes described on p. 343 are not functional. For the RB15, the only codes that are implemented are 800000, 800001, 800002, 800003, and 800004. All the other custom settings in the tables on pp. 336-7 are not implemented.

Thanks, I see several of the recent updates. I noticed the title page image is very pixelated. Is that something you're still working on fixing?

I've heard of this before, but never tried to use them myself. Out of curiosity, do you have the STD-VALB switch set to VALB? I think in STD it will ignore any settings you enter.

I think that's a good point. Why not list both?

I have asked HB about an updated list. Do you have a latest and greatest draft posted somewhere? I still only have the Nov 11 version without all the updates you've made based on feedback in this thread.

What are your thoughts about updating the Credits section with the latest lists of devs and testers?

It would be helpful if the page headers included the section number, like 6. Aerodynamic Properties I also noticed an error in the headers of Section 6. On pages where the AERODYNAMIC PROPERTIES header appears on the left, it is correct, but on the alternating pages where it appears on the right, it says WEAPON EMPLOYMENT. This WEAPONS EMPLOYMENT chapter header error also appears on the Chapter 6 title page, even though it is hidden in the black background (shown as a green search highlight here). This suggestion about figure numbers might be more trouble than it's worth now, but may save trouble in the future. Numbering figures sequentially in the whole document (e.g. Figure 237) means any time you add or delete a figure, you have to renumber everything downstream of it, including all the cross-references to those figures. Instead, if you use chapter- and section-based figure numbers (e.g. Figure 6-14 or Figure 6.3-4), it minimizes this problem.

In Section 5, several of the subheadings in light blue font now have double quotes on them. This is unusual and I see no reason to do this. null There may be places where header and subheader styles were not applied properly, like here on TILS landing. There are several places that use plain prose to point to other content, such as this. I think these references should include chapter and section numbers where available, or at least include the section titles and subtitles.

The manual says it's not functional. This is part of Figure 87.

Can you elaborate? What switch settings and modes are you using, and what codes are not working? It would be best if you have track files.

Yes, already reported and tracked. Thanks.

I agree, that seems like the right solution. Unlimited ammo should respawn "hot start" RB-75s.

Thanks for these reports. The theory is that you could use the second missile if you fire it before the first missile is replaced by unlimited ammo. But once the first missile is replaced, it requires a 3 minute spin up before it can be used. Unfortunately the missile select feature (safe-unsafe, or IR-RB Framstegn button) has become bugged in the last update so you can't just select a different missile. This is already reported and tracked.

The unusable Mavs after rearm bug is fixed in the December 2022 patch. Now there is a 3 minute warmup time that starts at liftoff. I haven't seen the look angle issue though. I'll see if I can reproduce it.

Yep, this bug is already tracked. Thanks!