Viking_355th

I vaguely recall hearing that the Harrier would get the APKWS rockets if possible. Any word on whether or not that's possible?

It's about 98% complete. It still needs JDAMs, but those are already in internal testing, so we should have them shortly. It doesn't have a campaign yet. I think that's about it for things that are still missing. I'm sure there are a few bugs that still need squashing, but that's the case for almost every module. Edit: I forgot, the manual's badly out of date. They're working on a final version, but it isn't out yet. Use Chuck's guide and/or YT videos to learn how to use it, because the current manual's wrong or incomplete about many things.

You can actually see what happens to the switches by looking at them. They're on the left.

It's a one-way toggle. The paddle disengages autopilot (if enabled) and physically flips the pitch and roll SAS switches. You have to flip those two switches up again to un-toggle, and autopilot won't work until you do.

I have a TM Warthog, and I just stick my finger in the trench. YMMV, but my finger is precisely wide enough that when I feel pressure, the throttle's at full mil.

Everybody here seems pretty chill already. Did I miss a panicky comment?

Great news, and great attitude! This is what we love to see!

Slideshow I'm also having the slideshow bug in Mission 3. For most of the mission, I was between 30 and 75 fps. When I pause it, it's 75 fps from inside the cockpit and 130+ with an external F2 view. When I unpause it, it's somewhere between 4 frames per second and 2 seconds per frame. It happened just after I dropped my last Mk. 83 on a Tu-142. I was just about to quit out of frustration when an SA-10B Grumble blew my wingman to pieces and my frames came back. And then the MiG-23 following me shot me down, so I ended up failing. Tried it again, had the slideshow shortly *before* dropping my last two bombs (but I was lined up well, so I was able to get them off the rack and hit two targets), but again, things went back to normal the moment my wingman died. This time, there was a good 30 nm between me and the MiG, so I was able to light the cans and stay out of his WEZ for the trip home. That particular glitch notwithstanding, this has been a great campaign so far. Thanks Kaba/HB! Cheers! Note: I've attached the Tacview file, and I'm uploading a video of my perspective of the flight to YouTube. I'm posting this before it's done uploading, so give it a couple of hours (I have slow internet right now) from the time of this post for the video to become available. However, I didn't start recording the video until about 13.5 minutes into the flight, so you'll have to do a little math to match the timecodes. The framerate hit comes in at around 16:41 in the video and 30:30 in the Tacview Tacview-20190927-033820-DCS.zip

Do we know how many parking spots the Forrestal will have? As in, how many jets can be assigned to it without any spawning on top of each other and exploding?

Thanks Ragnar! Nothing does rocket attacks like the Viggen, so it's good to know it'll be able to do that again soon.

If you're creating BX8 on the fly, BX6 & BX7 will get created automatically, and if you pass either of them before firing, then they won't fire. So, when creating BX8, immediately switch to BX7 and adjust it as needed, then the same for BX6. Every time I follow that process, I get successful launches.

On the latest Open Beta?

I'm guessing it's a bug, but if they want to fix some more serious issues first (being able to repair the jet ever, that rocket salvo thing from the other thread) I'm fine with this one being low on the priority list. :)

@Svarthandske just put the video ID in the tags, not the whole URL. So, (YOUTUBE)MqIJswcpnrU(/YOUTUBE), except with square brackets instead of round ones. (I made this mistake, too.)

Basically, when you disengage HOJD mode, you have to use the HOJD button, not the ATT button. If you use the ATT button, re-engaging requires two presses.