Fishbreath

If you're dropping in AUTO mode, try using DSL and dropping from slightly further away. AUTO drops right at the very end of the allowable release range, so at 10,000 feet you're already pretty close to the target. If you bank away at 30 degrees, you might end up with the target behind you, and the TPOD as mounted on the Harrier doesn't have a very good field of view in that direction. If you stick with AUTO mode, maybe try a steeper bank to keep the target abeam of you. I've been dropping using DSL mode, however; GBU-12s will easily fly 5-6nm from the release point starting at 10,000 feet and 350+ knots TAS. That allows for a shallower bank, and it seems like an easier profile with respect to the TPOD limits.

Not yet. I believe RAZBAM is currently working on the INS and associated UFC functionality, so I would expect to see coordinate entry coming before too long.

1. I believe SLAVE mode is supposed to point the TGP at the A/C CMD LOS. It doesn't currently work; I think that's a known issue/not-yet-implemented feature. Note that the manual isn't super clear on this one. The section on SLAVE says: While the section on the default mode (TDC, non-underlined, on the PB 14 legend) says this, making no mention of SLAVE mode: It's not evident whether enabling SLAVE mode is required, or whether it just forces the TPOD to move if there's no designated target. 2. I just started a thread on this, as it turns out. The manual says that when the TPOD is loaded, SSS Down 'assigns the TDC to the TPOD'. I don't know if that means it brings up the page, toggles between TDC and TDC modes, or just sets the A/C CMD LOS to the TPOD's position. 3. See #1. 4. The NWS button will only fully and correctly reset the TPOD's position in TDC mode. Sometimes it works in HTS mode, but other times it jumps back toward caged without getting there all the way. Presumably this feature isn't finished yet.

The pocket guide says this: It sounds like SSS Down should change the TPOD control mode to TDC, but it doesn't do that. The LITENING II chapter doesn't seem to say anything about the TPOD TDC assignment besides the TDC/TDC toggle with the OSB pushbutton. I have noticed that, if you hold SSS Down for >0.8 seconds, it seems to toggle some kind of mode in which you can't double-click SSS Down to enter or exit HTS mode. If you do SSS Down long while already in HTS mode, it seems to enable a mode where the AC CMD LOS moves to the TPOD's current point whenever you move the TDC. (You can see the AC CMD LOS diamond on the EHSI moving around. Move the TDC, then tap the TDC in any direction, and the CMD LOS shows up at the pre-tap position.) That doesn't seem quite correct to me, but I figured it was worth mentioning in case it's useful to anyone in the interim.

Nope, waypoint entry is not currently implemented.

I think the ARBS target-from-nav is a planned feature but not released yet. The TPOD can be slaved to the ARBS target point.

I suspect it is at -2 degrees already, and the centerline of the texture just isn't the bottom of the witch hat.

Is the roll SAAHS channel enabled? It's impossible to comment on flight model characteristics when a stability augmentation system is in play.

I flew to Vaziani the other day on 22X without observing that behavior.

Yes. You need to designate a target with the DMT to calculate its altitude for CCIP modes. I believe the weapons delivery system uses sea level otherwise, which works for most of the Georgia theater but not a lot otherwise.

I'll share mine later tonight, when I get back to my gaming computer. Stick only? Do you want the throttle, too?

I believe it's 82.

That's my problem, too. I can correctly slew it, but I can't use the TDC switch to set a new aircraft designation, as the RL manaul suggests.on page 1-402.

Is it possible to use the TGP as the sensor to make an attack at present? I can slew the TGP separately from the DMT or have it track the DMT's viewpoint, but I can't work out how to designate a target with the TGP or use it to cue the DMT.

To expand slightly, random spread around a vehicle with a bias toward the boundaries between terrain types, or toward bodies of water, would probably get you 80% of the way there. Both of those seem fairly easy to detect, given that the Viggen's ground-mapping radar can display them with no dramatic loss in performance. You could even use it to display random target without a vehicle ahead, as long as you know the sensor's FOV—again, it's a close parallel to the ground-mapping radar we already know to be possible. It isn't quite as random as random-around-vehicles, so that a skilled pilot can more quickly evaluate target markers based on their location on the terrain, and mimics the real-world behavior a little better—there are false targets even when not looking at a vehicle, and it seems to me from the videos I've seen like they're often arranged in lines along thermoclines. Of course, ED might be cooking up something fancier, as far as querying scenery objects goes, for the Hornet. Who knows?

This appears to be an issue with CK37 input, rather than the TOT calculations per se. The Viggen dynamic campaign has reasonable ingress speeds as part of the mission plan.

I have a CH stuff across the board, fighterstick, pro throttle with frankenpotato mod, and pedals, with no special scripting. (I do run everything through the CH control manager for consistency, but nothing beyond that.) No idea what the causes might be, but it's always good to give more datapoints to the developers.

I didn't do a clean install, but wheel brake axes work for me in 1.5.7, and main power is correctly off on cold start.

Here's hoping indeed—at present, the BK90 can't be used in MBot's dynamic campaign, because targets destroyed with them aren't registered by the system. I get the sense that there are a lot of simulation engine improvements DCS really needs, like more flexible weapon modeling and better simulation of jamming effects, that are on hold while they finish cranking out the new graphics engine and 2.5. I hope they find the time to focus on systems after 2.5—at present, it's the only part of DCS which feels below-par to me in terms of fidelity.

In my opinion, the Viggen is much easier to learn than, say, the A-10C or even the Ka-50. Those aircraft feature a lot of data entry and/or pilot skill requirements, whereas the Viggen is relatively easy to fly and only drops one kind of weapon at a time (in most cases). It's straightforward to write down checklists out of the manual, run through the one you need for a given mission before takeoff, and execute the attack without too much drama. I would recommend using the mission editor to create a mission with a Viggen over the Kobuleti airbase and some targets on the old X airport near Kobuleti proper. Set a waypoint on the center of the X, and you can use that mission to practice weapons delivery. Set the loadout how you want, and you don't have to worry about startup or ingress. You're already aimed at the target, all you have to do is the weapons procedure. That's how I learned.

Aha, I've been trying to click it. I'll give it a try with keys and report back. Thanks. Sent from my Nexus 5X using Tapatalk

Out of curiosity, how much of the campaign engine is random? Given the same starting conditions and mission results, will the same missions be generated? Does any simulation of sorties occur outside of the sim engine?

And a daylight mission, so you can see what's going on:

When flying with the countermeasures pod, the quick release works for me (the one with the switch on the throttle), but none of the fancier modes seem to. I.e., setting the pod mode selector to 3 and the KB release switch on the canopy to continuous neither releases chaff in external view, nor sets off the MOTVERK light on the right-side indicator panel. Is this expected behavior for now, or am I doing something wrong?

I've finally had a few missions in which I don't die, so here's a video of a night strike on the Tuapse railway station.