Fishbreath

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.

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.

Little bit hairy there on landing! I had a mission in Cristofer's dynamic campaign which had similar visibility, but unfortunately, I got shot down before I was able to give the landing a try.

The delay parameter in that function doesn't delay the respawn, it delays assignment of the group's original task. The group will respawn instantly, then, after the delay has passed, will begin to follow its original task again. Edit: wow, this thread moves fast.

No worries. I get the sense that the continued 1.5/2.x split is making a lot of extra work, and my comms needs aren't that complex. (I can certainly get by with three preset channels and a fourth frequency set on the dash.)

It's always nice when you figure out things on your own. So, I have the top row down, at least. Special 1-3 are the middle three buttons, between H (guard) and the - button (manual setting). I also understand that the next row down is presets for airbases if the window next to the right-side dial is showing a number, or the same channel as the backup radio if it's showing ALLM. Beyond that I'm still baffled.

I've read the manual, done some searching here, and read some threads on the subject, but I'm still entirely confused as to how the Viggen's radio is supposed to work. I'm playing Cristofer's dynamic campaign as a way to really dig into the Viggen and its systems. I have a home airbase, whose frequency (254 Mhz) is listed in the briefing as 'channel 1', and a package whose frequency (120.65 Mhz) is listed as 'channel 2'. The radio frequencies page in the mission planner has Special 1 as the package frequency and Special 2 (as well as E) as the airbase frequency. What do those correspond to in the cockpit? How do I select them? More broadly, what do all of the buttons on the top section of the panel do, and what do they correspond to in the mission editor? How do I use the bottom section of the panel (with the knobs and 0-9), if I want to do that?

I got it working. Thanks for the pointer. For anyone at home, the list of files which require changes: 1. Nordic Battle.cmp (change the path in all four places) 2. Nordic Battle/FirstMission.bat (change the path to correctly point at DCS/bin/luae.exe) 3. Nordic Battle/SkipMission.bat (change the path to correctly point at DCS/bin/luae.exe) 4. Nordic Battle/Init/camp_init.lua (change the path at the top) 5. Nordic Battle/Status/camp_status.lua (change the path at the top) Thanks also for putting this together! All I have to do now is figure out how the radio works.

I'm having the same problem as SirBunker. I've made the changes to allow LUA os and io functions, and I'm using the version which isn't missing any folders. Note that my DCS OpenBeta install doesn't have an AJS37/Missions/EN directory, and doesn't load campaigns placed in Missions/EN/Campaigns. Putting it in Missions/Campaigns shows it as a campaign option, but gives that error popup when leaving a mission.

Cobra et al., do you guys have a copy of Norman Friedman's US Aircraft Carriers? It's a great reference for internal detail and e.g. typical radar fits, and it also has some highly detailed line drawings of Forrestals, both plan and profile.

RagnarDa says it's fixed internally, so hopefully it'll make the next DCS release.

It's the heading from the pop-up point to the target point. I.e. 180070 (if non-10km distances were working right now) would be a pop-up point 7km north of the target.

I believe it's currently bugged, and only works with kilometer quantities which are multiples of 10.