SJBMX

There's never been an issue with bombs dropped from the middle of the DLZ staple. The problem has been that bombs dropped from the top end of staple come up short (over a mile short at one point, but it was down to a few hundred yards, the last time I checked) and from the bottom end of the staple overshooting. Your test just shows that what already worked fine still works.

Need to do some more testing, but I didn't run into any issues with the GBU-54 coming up short or flying weird today (didn't test 38s or 31s), so they may have fixed the DLZ bug.

The bug report topic (https://forums.eagle.ru/topic/252217-reporteda-10c-ii-jdamljdam-range-staple-and-cep-issues-dcs-25657264/) I put in was marked as "reported" and locked several months ago. I've heard conflicting reports as to whether or not it was fixed: Some people say it's fixed, some people say it's fixed if you drop below an altitude of 20,000ft, and others say that it's simply not fixed. Now that I'm no longer working at home and don't have to clear desk space to play DCS, I'll have to hop on and run my test mission again (the test mission uses an invincible T-90 as the target, which has a steerpoint set at its centerpoint at the ground elevation). edit: Just noticed that this is for the original A-10C module, and not the A-10C II, but the issue should be the same between them. Another thing to test, I suppose. edit: Forgot to save the track, but the verdict is the same: GBU-38/54/31 all let you drop from too far away. When within the actual DLZ, though, they seem much more consistent than before.

Hrm. The other thing that comes to mind, that I'd honestly never really even thought about, is that the front wheel is offset to the right as a result of the GAU-8, so it could be that it naturally wants to drift left somewhat as a result?

Oh, I missed that. Hrm. Without watching the track (I'm not on my PC presently), what was your loadout? The first thing that comes to mind is that it could be a weight imbalance? On takeoff, I'm usually pulling *slightly* to the left when loaded up with my "typical" unbalanced loadout (ALQ-184 or GBU-12 and a rocket pod on the left, AIM-9 or empty and TGP on the right) but it's never been anything more than a slightest annoyance with the keyboard (but was very noticeable with the pedals).

When I had TFRP pedals, I had the exact same issue with both the Hog and the Hornet. I suspect that it's because the pedals had poor ergonomics (too narrow) and were very touchy (springs were too light), even with strong curves. Using the keyboard for controlling the rudder and brakes, this simply doesn't happen. For the record, I presently use Q/E for rudder, W for brakes, and control my throttle during taxi and takeoff using my forearm. Haven't had any issues at all.

I'm expecting (read: hoping) them to fix all this and add more preset options into the mission editor when they add the ARC-210.

The ILS actually works at some airbases? I had thought that it had been completely broken, because it never worked whenever I tried to use it. Last I checked (probably 9 months ago), it didn't even work in the tutorial mission...

I've had up to six simultaneously for GBU-38s, and used all of them. On the same pass, no less.

Terrain 100% does the trick, but, yes, trees don't. That's usually the problem that I run into on the (admittedly rare) occasion I run 82AIRs.

Low level, terrain following attacks on stationary targets. SAM sites, airbase parking/taxiways/runways, fuel depots, etc, etc. Without scripting magic, this can be real hard because SA-15, SA-19, and Mr. Shilka know exactly where you are, even when they shouldn't.

https://www.476vfightergroup.com/ would be my first thought.

Right Engine Set OFF and Left Engine Set OFF do exactly that. I use the same keybinds for both startup and shutdown.

I would kill for this.

The correct one to hit is the top button on the right side of the MFCD. If you're hitting that one, the only thing that I can think of is that you're typing in an invalid name.

Personally, I think it makes sense to leave it in the manual with a simple note that it's non-functional in DCS. Maybe with a comment that, as a result, a long press of the LTB gets treated as a short press.

Yes, I know. I got the track to load, got a whole bunch of error popups, and then the mission started playing but the player never spawned in.

Tried to watch the track, but got a ton of script errors trying to open it. The player aircraft never seemed to appear.

It's definitely more difficult using TIR than VR, but it's mostly a result of the "my actual head is pointed this way, my in-game head is pointed in exaggerated version of the way that my actual head is pointed, and my eyes are pointed in the opposite direction back at the screen" factor. It just takes some getting used to. Looks to me like you're more zoomed in and/or closer to the target in the second image. IIRC, the dashes and corner hashes are a consistent size, so you can't have any dashes if it's zoomed in too far.

Pro-Tip: Unless you're in a situation that doesn't afford you a chance to do so, always label your markpoints.

I've beaten it a couple times, but I've found it to be very frustrating, simply because (A) the SEAD F-16s are very inconsistent, (B) your AI wingman is, as usual, completely useless, and (C) you start off within the SAM envelope. If this mission started the player off even ten miles further back, it would probably play much better.

I can accept that. That being said, for DCS, wouldn't giving users a separate set of rendering options for TGP (or Mav/SLAM/etc views) be the "simple" fix? ie: User can set buildings/trees/etc to render at 20 miles in normal view, but at 40 miles in the TGP. Any performance hit would therefore be entirely up to the user?

We're talking about a PIP TGP display viewed from a first-person perspective, so... yes. It seems reasonably appropriate. As far as none of those games having non-PIP scopes, they all display clear, magnified images in the scope window with (at least in the case of EFT and RS2) clear, unmagnified images around the scopes bodies, and claim to be PIP, so I'm going off that.

Escape From Tarkov, Insurgency: Sandstorm, and Rising Storm 2 all pull off PIP scopes without major performance hits, at least for users with reasonably modern systems.

I have the settings maxed, and this drives me nuts. I especially like the way that buildings sprout out of the ground and grow. Which is really noticeable on Syria.