FMBluecher

Can confirm user error for Direct as well! Every other aircraft I learned to use Direct mode (or its equivalent) used IAS, not TAS, for their bombing tables, so I was accustomed to looking at the wrong airspeed indicator. That's why I was always dropping long (because KTAS is almost always higher than KIAS). When I started using the TAS indicator instead, I was much closer to what I'd expect.

OK, can confirm that the issue with DT was me not understanding what the Dive Angle was! Still having issues with Direct, though, and hoping you can point me toward what I'm doing wrong: 1st Track: doing a low-drag run with Mk. 82s. Again, not a perfect run, but, according to Tacview, I released pretty darn near on-altitude. I was also pretty close to on-angle, and a bit slow--so I was surprised to have significantly overshot the target. 2nd Track: doing a high-drag run with Mk. 82SE. Delivered on-altitude according to Tacview and on-angle, while about 25 knots fast. I would expect to overshoot, but not by anywhere near as much as I did (especially with high-drag bombs). Manual Bombing Issue 2.trkManual Bombing Issue.trk

Sorry about that! I don't have a lot of experience working with trackfiles, and didn't realize that would be an issue. I think that was in fact the issue with the DT drop! I've been more successful with that since. Still working the Direct issue, and I won't have time to test this for a bit so I'll post again, with a new file that you can work with, if I encounter the issue again.

The good news is that I think I figured out what I was doing wrong in DT! When I did a test run with DT, I nailed the target on my first attempt. (I think I had the aircraft out of trim on my previous attempts, so I kept fighting the controls and at the moment Jester locked on to the ground return, my reticle was oscillating far up from the target.) The bad news is that Direct mode still seems wildly off. I've attached a quick track, as well as a screenshot of the bombing profile I set up. (I do realize that I failed to say "bomb on target: 2," but since I dropped in pairs anyway, I'm not sure this would have made a massive difference anyway.) I flew a pretty garbage run, to be frank, but, as far as I can tell, these were my mistakes: 1. slightly slow 2. slightly low 3. significantly too steep of a dive angle But all of these should, according to my understanding, mean that I drop the bombs short--instead, they fall way over the target. Manual Bombing Issue.trk

Would you want a track, or me recording the in-cockpit footage? I assume the former but just wanted to check.

Fair question! Yes, as far as I am aware, I did everything correctly using the bombing table, in both DT and Direct modes: Set delivery mode, set bomb type, set airspeed, set dive angle, set target altitude, set release altitude. And for DT, I did say "Tell Jester" and heard him verbally acknowledge my input. (Please, keep checking if I did anything dumb...I 100% would not rule anything out!)

I picked up the F-4E on launch but haven't had much of a chance to play with it until now. Over the last few evenings I've been trying to learn unguided bombing in this Mostly Bomber, and I noticed something very weird: every single bomb I dropped fell long, and not by a small amount (about 500 feet). To be clear: I'm not God's gift to piloting. I was expecting to be inaccurate, especially for someone who just started phlying the Phantom. But the weird thing is that the inaccuracy is consistent across every bomb type I have tried so far (CBU-52B, Mk83, and Mk82 LD). And it's consistent across modes: using the DT mode to designate the target, and using the Direct profile calculated in the Bomb Planner. Now, while I'm new to the Phantom, I'm not new to unguided manual bombing. I've flown a fair bit in the F-5E, the Mirage F1, and the A-4E mod, and manual bombing in all of them was about as accurate as I was expecting: If I flew the profile on parameters, I was pretty accurate; if I flew the profile off parameters, I was pretty inaccurate, and in a predictable way. If I was fast, the bomb fell long, by an amount proportional to how much faster than the profile called for. But that's not what I was seeing in the Phantom: the bombs always fell ~500 feet long, even if I flew the profile nearly exactly. I would only miss by that much in the other aircraft I mentioned if I made extremely serious errors, like accidentally setting the wrong reticle depression by a large margin. If I compensate for the issue, I get bang on target. In DT, if I designate the ground about 300-400 feet short of the target, the bombs land exactly where I'd expect--even when I'm not flying the profile properly. In Direct, if I reduce the reticle depression by about 50 mils from what the Bomb Planner calls for (as an example, the Bomb Planner said 140 mils; I set it to 90) and fly the profile well, again, I hit almost exactly where I'm aiming. I am playing with the CPU: Lower Simulation Update Rate and CPU: Lower HB UI Refresh Rate options enabled. Might that be causing this? This seems weird, but I'm at a loss as to what's causing this. Also, for what it's worth, I did a DCS repair and that didn't fix things.

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.