FMBluecher

As of now, both issues are fixed, at least for me! Thanks!

Thanks--and sorry, I didn't write what I meant very clearly! Yes, I've been using that workaround, and that does reset the view to normal zoom. The issue is that I can't change what my default view is even after using that workaround (normally bound to RAlt+Num0). That's the thing that only works when I switch to a different seat and back again (if there's one available to switch to).

To add to this, I cannot reset my default view angles unless I'm in an aircraft that has multiple seats--I can do it only by swapping from one seat to another and then back to the original seat.

Bug still present with 16 November OB patch.

I would try altering this. Mine always looked awful until I increased this display setting, and now they look crisp and beautiful. Give it a shot and see if that fixes the issue.

I did just have that issue for the first time yesterday--switching from GBU-12 to CBU-97 did seem to cause a problem for me with the GBU-12. Perhaps the issue isn't weapon-specific, but maybe something else?

Can strongly recommend anything by Reflected, Baltic Dragon, or Ground Pounder. I don't know what you already have but IMO those three set the standards for DCS campaigns.

Ah, that might be the issue then. Got the ILS to work properly on other airfields at hot starts, so that would make sense; I've only been flying out of Nellis with cold starts.

Don't know if this is user error, early access, or bugs, or what, but ILS at Nellis doesn't seem to be working as it should going from the manual. 1. I enter the ILS frequency into the UFC, which seems to accept it (goes from ILS OFF to ILS 109.10) 2. I select ILSN from the HSI (HUD confirms I'm in ILSN mode to a waypoint on the runway) 3. I enter the course into the HSI I do get the glideslope indicator, but I never get the ILS localizer bars to appear on the HUD or the ADI. Am I doing something wrong? Or is Nellis's ILS broken and I should try a different airfield? AFAIK, Nellis's ILS works for other aircraft, but it's been a hot minute since I tried it. I briefly tried ILST with Nellis's TACAN as well, and that didn't work either.

Another relevant factor: do you play mostly multiplayer or single player? A lot of modules are released with very little single player content, but you should be OK for multiplayer.

Thanks for checking! I guess I must have fat-fingered the abort option, since I don't use voice attack or anything like that. I didn't think my fingers were close enough, but hey, I was pretty tired when I played it yesterday, so maybe I wasn't self-aware enough to consider that as an option! Thanks again!

Trying M12 today, I pulled off of the secondary target in order to get a bit of spacing from it before starting my run when I heard Steep just suddenly abort the attack without my selecting that via the F10 menu. I was then unable to order E-Boy to resume the attack, ask for SEAD, etc. I was a bit to the north of where E-Boy was orbiting, so maybe I wasn't 100% where I was supposed to be, but I figured attack heading didn't matter quite as much since this wasn't a CAS tasking. I was still quite close to the target (less than 9 NM from the Uragans I was targeting)! I can provide a Tacview replay if that would help.

nullThe map of the target points for Target Fox has Steep's target point (TGT POINT 2) in the upper-left corner of the map even though the briefing text says "the southeast tower." I am assuming that the target actually IS the southeast tower, but I initially thought it was the northwest one because of the map orientation. If it is the southeast tower, perhaps putting a North arrow on the map might help to orient the player? BTW, overall, amazing work! Took a bit of a break from playing this campaign for a few months and now I'm back at it--absolutely loving it and can't wait to get into Kerman once I'm done!

Correction--this issue still doesn't seem fixed for me, either. If I make a brand-new mission, the waypoints work properly. However, if I load a mission that existed previously, incrementing the waypoints via any manner other than the QA menu still doesn't work. Did the update break older missions?

Odd advice, but maybe try a second repair? I did one repair post-patch and then another after Ramsay posted. The first one didn't seem to fix it, but the second did. To clarify--the WP increment bind does work but pressing the arrows in the EHSD doesn't? Or do you have to do what I did pre-second repair and pull up the QA menu in order to select any different waypoint at all?

Thanks for looking into it--knowing that you couldn't reproduce it, I ran a repair and then opened a fresh new map, made some waypoints, and everything worked properly. Guess it was either a problem with my DCS install or something specific wrong with the mission, but everything seems to be OK!

Been a while since I flew the Harrier, thought I'd hop in yesterday. Lots to get back up to speed on, but one of the weirdest things I've encountered is that I can't seem to manually increment the waypoints. Pressing the waypoint increment button short does nothing, nor does pressing the up or down arrows on the EHSD. The only way I seem to be able to change my currently selected waypoint is to press either the waypoint increment button or up arrow on the EHSD long enough to bring up the QA menu and then input the desired WP number on the UFC. Now, I know RAZBAM have changed a bunch, but I didn't see anything about this changing. Is this a bug? User error? Am I the only one who's experiencing this? Thanks in advance! To be clear, I am not talking about changing the type of waypoint (waypoint vs. target vs. mark). I'm literally just talking about changing W1 to W2 to W3, etc.

There's been a recent series of videos by FlyAndWire on YouTube that have been very helpful for me. This is one of the most important ones: But Part II of this series is also useful. After watching these, I've launched (only a limited amount yet, but with good success) at 40-60nm.

Makes sense, I thought I was flying the pattern, but must not have been flying the heading precisely enough. I only ended up 17 nm away (on speed and on altitude) because I just kept hoping it would eventually trigger!

What exactly do you mean? Campaign designers are limited by what the DCS AI is capable of; they can only do so much. There are two types of AI wingmen: 1) The standard DCS AI wingman that you can control. Campaign designers can do very little with these. There are some things campaign designers can do to make them slightly more effective, but this is mostly impactful in A-G, not A-A, which is what you seem to be asking about. The best way to make these AI wingmen more effective is to learn how to get the most out of the AI from issuing the right commands to them at the right times. 2) Custom AI wingmen that you control through the F10 menu (or that operate completely independently, only by scripting). Only a couple campaign designers use these (Baltic Dragon, Ground Pounder, and Reflected are the ones I'm aware of), and the campaign designers are already pushing the limits of what the DCS AI can do with these. Which type are you talking about, and what specific problem are you having? Describe a precise situation where you wish the AI wingmen would have done something different.

After absolutely struggling through the rest of the syllabus, got my first Above Average on Mission 5! However, once we got to the strafing, it seemed like it took forever for both me and Paco to call "off safe." At one point, I was flying in circles, 17 nm away from the target, with time acceleration on waiting for Slick to call "off safe." I assume I did something wrong (even though one of these was where I got my Above Average), but I'm not sure what it was! OTOH, it didn't seem like Paco was any faster. For clarity, this isn't a mission-breaker, I was still able to finish it, but it was a bit of an immersion breaker! Edit: On another note, you may want to double-check the briefing pdf--it lists different altitudes for some of the setups than what Paco says in-game.

And IRL, wouldn't pilots already have a ton of formation flying under their belts at this point from previous training squadrons (just not in the Tomcat)? Not to say that I have no experience--I've done a fair bit before now, I just never tried flying such a tight formation on anything aside from an S-3! Truly terrifying, and that's just in the daylight!

Using my actual first attempts? I like to call this "World Record Speed & Angels Any% Glitchless Speedrun"

Hey, feel free! I'm glad I'm not the only one getting something out of it.

Yup, I think the issue I had is that I'm so inured to DCS missions where the trainer says "OK, that's 360 degrees, now level off" and I didn't even think about the possibility that I might actually know that I've done a 360-degree turn!