Yurgon

@BIGNEWY @NineLine I've reported a few issues here in June and haven't seen the devs respond to a single post here since then, even after pinging 6s.duke. Can you get in touch and let them know people are looking for support?

Indeed, thanks for sharing! The sub skipper was also featured in a German documentary where he almost busted his check ride. Nice to see him firmly in the saddle now.

Interesting; as far as the jet is concerned, I'd have thought it would detect a LAU-131 or a LAU-68 (IIRC), but should be entirely unable to tell which rockets are in there. So just to be clear, you had the DSMS fully loaded with APKWS on at least one station, then you went into DSMS -> INV and changed that station to another type of rocket with the same launcher, and then it showed an error? Which was the indication next to the station?

Der Hypetrain nimmt Fahrt auf! Das Interview mit Matt von ASC fand ich auch sehr interessant (hätte mir als Podcast besser gefallen, weil es dort nur Schnipsel aus dem Pre-Purchase-Trailer zu sehen gibt):

Sinai is one of the few maps I don't currently have installed. Like Eric said, if you can recreate that issue in the Caucasus map, that'll make it much easier for people to take a look.

Bei der F-14 hatte ich da 0 Probleme. Hatte dort das Bundle mit einem T-Shirt gekauft und wegen eines Fehldrucks habe ich sogar zwei T-Shirts bekommen; das mit dem Fehldruck ist tatsächlich nicht so cool wie das richtige, aber trotzdem nice. Das Einlösen des Codes bei ED hat für mich reibungsfrei funktioniert, und seitdem habe ich die F-14 halt bei ED freigeschaltet und kann sie sofort installieren, wenn ich DCS zu neu installiere, ohne dass ich nochmal bei Heatblur irgendwas klicken muss. Kurz und gut, aus meiner Sicht erwarte ich da keine Probleme.

Die C-130J kann ab sofort vorbestellt werden. Hier findet ihr die Ankündigung von ED: Direkt bei ASC kostet die C-130J, wenn ich es richtig sehe, im Moment 5 Euro weniger; wer dort kauft, bekommt einen Code, den man dann auf digitalcombatsimulator.com einlösen kann (so wie beispielsweise auch bei Heatblur mit Tomcat und Phantom), wenn das Modul released wird. https://www.airplanesimulations.com

Yes indeed. All presets were updated across all missions across all radios. Most presets will be persistent, so let's say in Mission 01 you have Nellis ATIS on Channel 2 on both ARC-210 and ARC-164, then it'll be on preset 2 in every mission so that players get a more intuitive feeling for what preset to use at what stage in every mission. There was also a report about a preset mismatch in one of the later missions that has been fixed. In turn, any preset issues in the current campaign version should be fixed with that future update. But since working the radios and frequencies is such an integral part of the campaign, there needs to be more testing first. Anything to do with transmitters and weak or missing radio calls, please keep reporting those! (And of course anything else that doesn't work )

An update of all radio presets is now in internal testing. Just a bit more consistency across all missions, a fix for this issue from M01 plus named presets in the ARC-210. Yeah, I saw the exact same thing. The unit used as transmitter was trying to sneak behind a mountain. Gave him a jolt to gain good Line Of Sight, should be good now. Yup, another case of the actual transmitter unit being in the wrong place, good catch! All fixed internally and now in internal testing. I can't give an ETA for an update, hopefully soon.

https://www.airplanesimulations.com Da scheint sich was zu tun...

Und was genau fehlt dir an den Antworten in deinem fast gleichlautenden Thread von Anfang des Monats? Sollen wir alle den gleichen Sermon nochmal aufschreiben, damit du Mitte August wieder fragst?

I'm not sure how closely the devs monitor this part of the forum, so just in case I've also filed an internal report. That should hopefully get that house removed.

Another great report, thanks! This one is correct as is; Guard 1 is in the VHF AM frequency range and the ARC-164 can't go that low. So this preset is only available on the ARC-210. Not sure if there's a good way to signify this in the kneeboard without making it a good deal more complicated. But as far as I remember, there's no need to tune into the Emergency freq anyway. Thanks, will take a look at that as well.

https://www.tagesschau.de/inland/gesellschaft/hubschrauber-absturz-grimma-102.html

Excellent report, thanks! The ARC-210 isn't used a whole lot in the campaign; the presets come from the legacy A-10C version where only the ARC-164 would have been able to dial in those freqs, and these presets should all be correct for it; but you're right of course that the ARC-210 presets should also be set. Shouldn't be too much hassle to also name them. Will take a look at that!

Wenn ich nichts übersehe, haben wir hier im deutschen Teil des Forums noch keinen Thread für allgemein wissenswerte Schnipsel, die nicht direkt mit DCS oder Luftfahrt zu tun haben, dabei zu interessant sind, um gänzlich unerwähnt zu bleiben, aber nicht interessant genug für einen eigenen Thread. Zum Auftakt gibt es die Empfehlung, die Nvidia-Treiber zu aktualisieren. https://www.heise.de/news/Sicherheitsupdates-Schadcode-Luecken-in-GPU-Treibern-von-Nvidia-geschlossen-10501190.html Nvidia hat in den neuesten Treibern teils kritische Sicherheitslücken geschlossen. Falls ihr eure Treiber von Hand aktualisiert, wäre jetzt ein guter Zeitpunkt für ein Update.

Errr, okay. Well if you intend to purchase another module based on deficiencies of one you already own, feel free to ask ahead of time if it offers the features you desire. Better yet, if you installed DCS via digitalcombatsimulator.com (not via Steam), you can Trial most products for free for 2 weeks. Just check out the big fat TRIAL button on the E-Shop.

The A-10A did not have any autopilot at all. Pilots crossing the Atlantic en route to the middle East in 1990 for Operation Desert Shield had to hand-fly many hours in lose formation with tankers. What fun that must have been! The Low Altitude Autopilot with its fairly basic modes is thus a big step forward and allows pilots to spend more time heads down and focus on the mission. While I'm not sure if it actually played a role, USAF leadership was never a fan of the A-10 and has tried many times to get rid of it. The request for additional funds might not have gone down well with them. Plus there are probably technical reasons. None that I know of. Just to clarify, are you mad at Fairchild Republic or at DCS? Because DCS is a simulation, and adding an autopilot that doesn't exist on the real aircraft would put it in fairy tale land. And criticism towards the aircraft's manufacturer is a bit ill-placed in a forum about its simulation.

This may sound stupid, but... did you by any chance forget to retract the gear? With the gear down, weapons can't be fired (unless you set the ground safety override switch on the rear left console to override - but it's generally advised to retract the gear instead). IIRC Mavericks won't come off the rails with the flaps in the MVR or DOWN position, but that should put a big FLAPS indication or similar on your MFCDs. Also, flaps auto-retract at around 190 knots to protect themselves from overspeeding, so unless you were fairly slow (even for an A-10, that is ), that probably wasn't the issue. Otherwise, might have been a one-off DCS glitch with an incomplete repair, though I'm not actually aware of any problems with the repair option. If you can recreate the issue, ideally in a short mission, a track would be very helpful to figure it out.

With the recent 2.9.18.12722 patch, the Iron Flag Campaign received a bit of an overhaul. It wasn't mentioned in the patch notes, so let me give you an overview. Subtitles Last year I tested some Iron Flag missions and noticed a few discrepancies between what the voice actors said and what was shown in the subtitles. With Baltic Dragon's permission, I thought "Let's quickly correct that". Well. Iron Flag has a lot of voice-overs. I mean a lot. Clicking through the Mission Editor turned out to be unfeasible, so I extracted the dictionary file from each mission archive. But that has everything in seemingly random order, so for every voice-over sound file I listened to, I then had to find the correct line in a file of 2000+ lines, which made the process unnecessarily slow. With a bit of bodging a couple of scripts together, I got all the lines ordered by their index so from DCS's point of view, everything was correctly identified, while for me it was in the proper order, making the process a lot smoother. Along the way, some common typos showed up, and for the most part it turns out that the voice actors just loved to go off script and change a little "We'll go ahead and" into "We're gonna", and a lot of stuff like that. Same meaning, different words. The campaign's instructors, BIFF and LOTUS, have particularly long lines of dialog, reaching from a simple "Two" or "Gotcha" up to around 40 seconds of dialog in a single transmission. For improved readability, these were split into paragraphs where applicable. In a lot of cases, these long lines of dialog were then repeated in the so called "action text" that prompts players to take a certain action. These are now split into much shorter chunks, omitting a lot of the free text around the actionable items, and were formatted as lists that, I hope, will be easier for players to follow than those super long lines. At this stage, if you find any typos, spelling or grammar mistakes in the subtitles, they're 100% mine (if I didn't introduce them myself, then I missed them. Well, except for some freestyle English that the voice actors spoke - the subtitles only reflect what they say ). BIFF's datalink For a long while, the instructor's aircraft (BIFF in most missions, and LOTUS in mission 9) have been AWOL from the datalink. Somewhere along changes to the whole datalink system and the introduction of new Advanced Waypoint Actions, it just stopped working. Adding new AI controlled aircraft worked fine, but with dozens or hundreds of triggers bound to the existing jets, replacing them with fresh ones just wasn't an option. The issue had been reported to ED, but with a fix still not in sight, I decided to dig into it, trying every Advanced Waypoint Action I could think of, but it just wouldn't work - BIFF and LOTUS just never showed up on TAD and HMCS. Well, if new aircraft do and some old aircraft don't, there's got to be some difference, right? And if the Mission Editor doesn't allow to edit the difference out, then maybe looking at the raw mission file might? So, long story short, I just copied the entire Advanced (Waypoint Actions) block from a fresh A-10C aircraft over to BIFF's and LOTUS' jets respectively in each of the 12 missions (10 regular ones, plus two shortened versions of the otherwise very long Mission 06), and voila: they're back! Additional fixes In some missions, the position of radio transmitters was changed to improve the quality of radio transmissions. There may still be a few cases where the radio quality of other transmitters degrades a lot and makes them much harder to understand. If you come across any of those, please let us know! In a few cases, changes and upgrades to the A-10C II module invalidated some voice-overs for what was a completed and finished A-10C campaign before the A-10C II was released. Where this makes an actual difference, NOTEs were added to subtitles and/or action texts. Small QoL improvements A bunch of smaller Quality of Life improvements were snuck in as well. The briefing images showing the flight plan have been slightly changed to make the waypoint numbers a bit easier to read in all missions. The datalink, now that it's working again, was updated and both player and instructor aircraft should have the correct GRP ID and OWN ID data from the briefing already set, as well as a sensible CALL sign, which is now the first and last letter of the flight call sign plus number in flight, so Tusk 1-1 would have TK11 preset for instance. A dialog about radio presets that appeared twice (once in M01, once in M06) was removed from the second occurrence. The weather in one of the missions was changed and should now be within legal limits for the assigned approach while still offering a challenging flight through thick clouds, with Nellis Runway 21L only becoming visible roughly 300 feet above minimums. The short versions of Mission 06 were updated to have plausible fuel values (these airstart missions used to begin with 100% fuel). There used to be kneeboard images showing the entire HOTAS tables for throttle and stick. These are now part of the module's default kneeboard, so they were removed from the missions. Credit where credit is due I want to thank Baltic Dragon for trusting me not to break these missions. Of course a huge shout-out goes out to Doughboy - I learned so much from this campaign! New members in the tester team who ran many of the missions countless times are Jakes, MadDog and Nexonix01, thanks for all the help! tl;dr Datalink is working again for the Instructor Pilot jet; a few kinks were ironed out; most subtitles were updated. Thanks for reading.

Yeah, DCS AI certainly has its issues, and understanding what it does, and why, is certainly not self-explanatory. I feel for all mission designers who put so much time and effort in their missions only to find that the AI does something it shouldn't (and never did in testing) and then breaks the mission. I think I had spent some 30 to 40 minutes in the mission already. The briefed task was complete and I was rerouted to another one, which I was looking forward to because it sounded interesting. When the mission failed, I had passed roughly half the distance to the next tasking. So roughly 5 minutes startup, 20+ minutes in total in transit and around 10 minutes for directing the first tasking. Maybe I'll replay it and check that my wingman takes off, then hit AI Cruise and fast forward.

A bit of a problem with Mission 7 - Steel Rain: Enroute to a midflight tasking, it says "Mission failed. Your wingman died. Retry the mission" Looks like my wingman didn't die. He just never took off, shut down his engine right after I had taken off, and pretty exactly 30 minutes later was despawned, which seems to count as "killed". Until that point, I didn't even realize that he wasn't somewhere on my tail, because his voice overs played without a hitch. As a general rule, failing a mission for a wingman getting killed can be pretty annoying, DCS wingmen being what they are, unless their aircraft are crucial for triggers (didn't seem to be the case here, at least not yet). Also, please for the love of whatever is holy to you, do NOT end missions for players. I can find the "Quit" button just fine on my own. At this stage, I don't want to fly the exact same mission again, so I'm going to skip it, but maybe I could have seen what was in store at the next tasking if the rug hadn't been pulled from under my feet. Otherwise, I'm really enjoying the campaign, which just makes it more annoying to fail a mission for no fault of my own, and not getting to see where it would have led.

Nachdem du das im ED-Discord geschrieben hattest, wollte ich das gleich ausprobieren und habe es erstmal nicht hinbekommen. Wie es dann letztlich für mich klappt ist in der CDU: IDX <-START COORD REF : MGRS Dann kann ich beispielsweise in der FPLN Page MGRS-Koordinaten eingeben; die Anzeige der Koordinaten wird dann aber direkt in Lat/Long geändert. Bei der Eingabe scheint der Grid Zone Designator im Moment eine Pflichteingabe zu sein, aber bei den Ziffern geht von 2 bis 10 Stellen alles, das ist ganz nice (ja Hornet, dich gucke ich schief an, mit deinem "6 Stellen. Immer. Außer du hast PRECISE geboxt. Dann 10. Immer." Unsinn). Also das alles sind erlaubte Eingaben bzw. Formate: 38TLM16 38TLM1267 38TLM123678 38TLM12346789 38TLM1234567890 Diese hier ist (jedenfalls aktuell) NICHT gültig: LM123678 (GZD fehlt) Sehr nice! Und Bignewy meinte vorhin im Discord, er will mal nachhaken, ob die Eingabe des Luftdrucks (BARO SET) vielleicht auch mal angegangen werden kann.

Nah dran. Ganz rechts bei Labels musst du deine Auswahl treffen.