Yurgon

Betrifft vermutlich nur eine recht kleine Zahl an Benutzern, aber manchmal ist eine Accountsperre komplett willkürlich oder basiert auf automatisierten Kriterien, und dann kann der Schaden schon ziemlich groß sein, wenn man nicht darauf vorbereitet ist, auch andere Dienste nutzen zu können, und wenn die sperrenden Dienste außerdem erstaunlich schwer zu erreichen sind, um das Problem zu klären. https://www.heise.de/hintergrund/Automatisierte-Scans-Microsoft-sperrt-Kunden-unangekuendigt-fuer-immer-aus-7324608.html https://www.rnd.de/panorama/google-account-von-vater-gesperrt-missbrauchsverdacht-wegen-intimfotos-des-sohns-fuer-arzt-DWWNWFUAH5G5LNQVO5BJPCRQG4.html https://www.heise.de/news/Proteste-gegen-Sperrung-von-Fotos-stillender-Muetter-auf-Facebook-192904.html Betreibt man seinen PC ohne Microsoft-Account, dann kann man zumindest noch DCS spielen, auch wenn andere Dienste vielleicht aus welchen Gründen auch immer gerade gesperrt sind.

@BIGNEWY @NineLine can you move this thread? Thanks.

A short track would go a long way to figure this thing out.

What's your SRS version? Support for the ARC-210 was added when the A-10C II module came out. The A-10C II ARC-210 works fine here; it should be "Radio 1" in SRS, just like the old ARC-186 used to be.

Ich werd's wieder so halten wie beim Umstieg von Windows 7 auf Windows 10: Wenn ich mir einen neuen Rechner einrichte, käme jetzt ganz sicher Windows 11 drauf. Auf dem aktuellen Rechner bleibe ich bei Windows 10, bis Windows 11 entweder wichtige Features bekommt, die ich brauche/haben will (beispielsweise ein neues DirectX, das in Spielen einen Vorteil bringt) oder bis der Support für Windows 10 endet.

Passend zum Thread nochmal in aller gebotenen Kürze, bezogen auf die A-10C (beide Versionen in DCS): Es gibt immer nur einen Sensor of Interest (SOI). Den kann man mit dem Slew-Cursor manipulieren. Es gibt immer nur einen Sensor Point of Interest (SPI). Das HOTAS-Kommando "Make SPI" (TMS Forward Long) setzt den SOI als SPI-Generator. Das heißt, von diesem Zeitpunkt an generiert dieser Sensor den SPI. Manipuliert man diesen Sensor, der gerade SPI-Generator ist (TGP slewen, HUD Cursor slewen, TAD-Objekt hooken, HMCS-Objekt hooken, anderen Steuerpunkt auswählen, ...), dann aktualisiert das Flugzeug direkt und sofort den SPI. Wenn man einen anderen Sensor zum SOI macht, ändert das nicht den SPI. In der unteren linken Ecke vom HUD wird immer angezeigt, welcher Sensor gerade den SPI generiert. Für CCRP-Angriffe und beim Übertragen von Kontakten per Datalink wird immer der SPI genutzt. Hat man dieses Konzept einmal verinnerlicht, ist es super mächtig und es wird klar, dass fast immer unterschiedliche Wege zum gleichen Ziel führen.

Reading the question again, it sounds like you are right. In that case, option select buttons in the A-10C are the rows and lines of buttons around the 2 multifunction color displays (5 buttons on every side of each display). Keeping any of these pressed for too long will lead to the RIGHT/LEFT MFCD STUCK KEY message popping up. That should hopefully answer the question fully.

So to double-check: at certain angles, the TGP doesn't track targets, correct? And are those moving targets, or is it also unable to track stationary objects? In those cases, does it show "M" for "masked"? icemaker asked this question already and it seems it's pretty important. Can you at least post a screenshot of the TGP screen when this happens, and can you please also post a screenshot showing the HUD after you used the "Make SPI" HOTAS command on the TGP? Even when the TGP is masked and shows the "M" indication, that doesn't (shouldn't, at least) prevent it from generating the SPI, and using the HOTAS command "Make SPI" on the TGP should still place the SPI where the TGP line of sight intersects the ground, and the HUD indication in the lower left corner should still switch over to "SPI", and the TAD and HMCS should show the SPI symbol (the 3-layered wedding cake symbol) right where the TGP is looking (and the HMCS should also show the TGP field of view box around the SPI symbol, if my memory doesn't fail me). I'm trying to figure out if there's something broken with DCS, or in your specific DCS installation, or if it's user error. Right now it sounds like you might not fully understand what the SPI is, how sensors generate it, and what the difference is between tracking an object and creating a SPI. So, once again, if you can provide us with a complete and detailed description of the actions you take regarding HOTAS commands and the SOI, and if you can illustrate this with screenshots or a (short!) track, we can probably give you very specific advice within one response. Right now, though, we have to ask tons of questions and do a lot of guesswork, meaning this could drag on for another week.

Option Select Button

In einem deutsch lokalisierten Windows ist es genaugenommen C:\Benutzer\{Benutzername}\DCS Aber stimmt, C:\Users oder C:\Benutzer ist der richtige Pfad - normalerweise schaue ich sowas um sicherzugehen extra nochmal nach, hab aber gerade nur ein Ubuntu-Notebook am Start.

"Make SPI" doesn't do much to the other sensors. Can you confirm that the HUD shows "TGP" in the lower left corner after you've pressed "Make SPI" with TGP as SOI? Can you confirm that the TGP retains POINT or AREA track (as commanded) and that the TGP keeps looking at the proper object? Can you confirm that the HUD keeps showing "TGP" in the lower left corner throughout these issues that the thread is about? And do I understand correctly that after the steps you described above you then follow it up with the "Slave All to SPI" HOTAS command, but now the Maverick (as opposed to the TGP) isn't always able to track the SPI? If the answer to all of the above is yes, then this sounds like a simple case of Maverick gimbal limits. If the answer to any of the above is not "yes", I can only reiterate that we need more information and preferably a track.

Das wäre ganz besonders: C:\{Dein Windows Benutzername}\Gespeicherte Spiele\DCS oder C:\{Dein Windows Benutzername}\Gespeicherte Spiele\DCS.openbeta Es kann sein, dass deine USB-Geräte neue IDs bekommen; das kann man in DCS mit Speichern und Laden von Profilen lösen oder indem man die Dateien in Gespeicherte Spiele\DCS\Cinfig\Input (wenn ich mich gerade richtig erinnere) umbenennt.

Let me rephrase then: As far as I'm aware, masking does not prevent generating a valid Sensor Point of Interest. So with the "M" indication for masking, the SPI Generator as indicated in the lower left corner of the HUD should not change away from "TGP" to, say, "STPT". Sure, the TGP may no longer track a moving target, but that's not the problem OP described.

Ah, super! Das ist völlig an mir vorbeigegangen, aber so kann Peterik das Problem ja sehr gezielt angehen.

Not sure if there is a maximum range, but once the TGP (not TPOD, this ain't no Hornet) is slewed to the horizon and above it, it's obviously impossible to calculate a point on planet earth where the TGP line of sight intersects the ground, making it impossible to designate the TGP as SPI Generator. Otherwise, I'm not quite sure what you mean. I'm not aware of any lateral or longitudinal angle limit that would prevent the TGP from generating a SPI. So when you try to make the TGP SPI Generator with the Make SPI HOTAS command, does the lower left corner of the HUD not switch to "TGP"? If you could post a track and describe exactly what you expect to happen and what happens instead, that would be a big help to clear things up.

Die DCS-Reparatur wäre mein erster Tipp gewesen. Tipp #2: benenne deinen Ordner Gespeicherte Spiele\DCS.openbeta um, nimm beim nächsten DCS-Start nur die nötigsten Einstellungen vor und schau ob das Problem weiterhin auftritt. So oder so kannst du danach Gespeicherte Spiele\DCS.openbeta löschen und deinen umbenannten Ordner wieder zurückbenennen. Tendenziell würde ich aber auch mal einen Blick in den Windows Task Manager werfen, vielleicht ist es ja etwas außerhalb von DCS, das dir dazwischenfunkt. Vielleicht dein Antivirus?

That's an interesting thought, and it actually sounds quite plausible. On the other hand, from a low altitude release the weapon would carry the kinetic energy it was given by the launch platform, and an optimal release profile should pretty much allow it to reach the target with this energy. With a short bomb fall time from a low altitude drop, I assume there's a chance the bomb will run itself out of energy before reaching the target - then again, low altitude LGB releases aren't usually recommended anyway. I have a much easier time imagining a high altitude release where the bomb runs out of energy because its flight path deviates too much from a ballistic path. But from a level release, the seeker wouldn't even see the designation until the bomb is already quite a bit nose down on its ballistic path - so maybe the issue is indeed more manifest in a low altitude level release, where the seeker can pick up the designation right away. So even with a relatively small difference between a ballistic flight path and a direct flight path, this might be enough to run the bomb into the ground short of the target. I'm now more confused than ever.

IIRC the resident SMEs have said for ages that LASTE does a great job of collecting and updating wind information and that pilots basically don't touch the manual wind entry, unless there are very specific circumstances. There was also the question if manually entered wind data does anything at all in the jet; I recall a video (or was it a forum discussion...?) years ago where active pause was used and it was shown that the CCIP pipper does indeed move depending on the manually entered wind data, and in essence manually entered data can and does have an effect on targeting. But as I recall it, the difference between the generally suggested method of calculating wind data from whatever was entered in the ME and the automatically gathered data by LASTE was so minimal that it's just not worth calculating and entering this stuff for every flight.

I think I understand what you're describing, but I'm not 100 % sure. Could you post a track showing the problem and point out exactly where the briefing differs from the values measured in flight? Does this affect wind speed, wind direction, or both? Is this purely a problem with the data displayed, or do your weapons miss as a result of bad wind info? Do you manually enter wind data into the CDU, and if so, how do you retrieve and calculate this data in the first place? Which version of DCS are you running?

That shouldn't be the case. When properly set up and by default, Paveway-II-LGBs use the Optimal Release Profile (ORP) in the A-10C which drops them right into the "basket" where the seeker can pick up the laser cone. I've seen recommendations for lasing from between 8 to 15 seconds before calculated impact, and all of these values have consistently worked for me in the past. If autolase at 10 seconds before impact doesn't work for you, you could simply set it to 20 seconds and that should do the trick. On the contrary, older generation Paveways can run themselves out of energy when they pick up the laser designation too soon and try to fly toward the designated spot in a straight line with no flight control logic beyond "go straight there". I don't think that's an issue in DCS, and it's more likely to happen for high altitude releases which we can hardly do in the A-10 anyway, but I'd argue there's good reason to lase the target within roughly 8 to 15 seconds before impact, and with 10 to 12 seconds being a very good baseline. Long story short, manual lasing vs. automatic lasing shouldn't make any difference whatsoever regarding the probability of a direct hit. If this does make a difference, we should explore the reasons, because that could indicate a possible error in DCS. All that said, personally I never set up autolase profiles and quite often we do buddy-lasing in a split-element-attack or a lead-trail-attack, allowing the shooter to egress right after pickle, which is kind of a big bonus in MP vs. SP.

Jap, genau. Wobei gerade der Apache einem da ja eine riesige Hilfe bietet: Die Endurance, also die Ausdauer, die ganz einfach in Stunden und Minuten ausgedrückt wird und die sich immer der aktuellen Fluglage (oder besser gesagt: dem aktuellen Treibstoffverbrauch) anpasst. END 1:30 hieße halt, dass man mit den aktuellen Parametern eine Stunde und 30 Minuten fliegen kann. Naja, und wenn ich dann mit 100 Knoten fliege (ein Glück, dass das so eine Runde Zahl ist ) schaffe ich 150 nautische Meilen, bis mir der Sprit ausgeht. Die Endurance auf dem TSD habe ich auch viel öfter im Blick als den Treibstoffverbrauch, den man auf der Engine- oder der Performance-Page findet, wenn ich mich recht erinnere. Kleine Ergänzung noch zur razo+r: Fuel LB ist natürlich das Treibstoffgewicht in Pfund, und das Treibstoffgewicht in Pfund entspricht dem Gesamttreibstoff an Bord. Fuel LB/HR hingegen ist der Treibstoffverbrauch in Pfund pro Stunde, und damit kann man dann ausrechnen, wie lange bzw. wie weit man noch fliegen kann. Aber wie oben gesagt, die Endurance zeigt einem das eh im TSD (wenn man es nicht wegkonfiguriert), und das macht den Rest der Überschlagsrechnungen viel leichter.

Oha. Als der ganz neu war, hab ich das schon als Kritikpunkt gelesen. Hat Saitek/Madcatz/Logitech das bis heute nicht hinbekommen? Ist eventuell ein Montagsmodell, andere User sind glaube ich ganz zufrieden und schildern dieses Problem nicht. Wenn dein Portemonnaie nicht spontan implodiert: Warthog. Es gibt am TM Warthog auch ein paar Kritikpunkte, etwa den labberigen Slewcursor, der aber bei neueren Modellen durch einen vernünftigen Ministick ersetzt wurde (für die älteren Modelle kann man für circa 50 Euro ein Slew-Cursor-Upgrade aus England bestellen und selbst einbauen) oder den Umstand, dass es manchen Usern nach ein paar Jahren die Elektronik frittiert und man dann für circa 50 Euro eine neue Platine von TM ordern muss (ist mir in 8 Jahren nun schon 2 Mal passiert). Die zitternde Achse des Friction-Sliders, die man frei belegen kann, wäre auch ein gerne auftretendes Problem (ganz toll, wenn beispielsweise der Zoom immer hin- und herzittert). Aber: Der Warthog ist alles in allem ein ziemlich gutes und solides Stück Hardware. Meiner Meinung nach sollte man wegen der Probleme mit dem Preis runtergehen, stattdessen finde ich ihn aktuell für über 400 Euro. Angesichts der Inflation muss man das wohl hinnehmen, aber wenn man ein Angebot für um die 300 Euro findet, wäre das meiner Meinung nach deutlich angemessener. Alternativen wie Virpil, VKB und WinWing, die BoFrost ja auch anspricht, liegen preislich ein gutes Stück drüber, wobei es mindestens bei Virpil ab und zu ganz nette Rabatte gibt, z.B. 10% auf alles und nochmal 10%, wenn man Grip + Base zusammen kauft. Bin mit meiner Virpil T50CM2-Base sehr zufrieden und nutze mit einer 10cm-Verlängerung den TM Warthog-Grip, weil mir dessen Haptik deutlich besser gefällt als beim T50CM2-Grip von Virpil (und weil ich eh am meisten die A-10C fliege ). Also, es gibt besseres als den TM Warthog, aber es gibt auch viel schlechteres. Wenn dein X56 noch ganz neu ist, kannst du ihn ja direkt zurückgehen lassen und verlierst nichts. Aus meiner Sicht ist der Warthog sicherlich besser als der X56, wobei ich letzteren nie selbst genutzt habe. Und falls du irgendwann auf was besseres aktualisierst, sollte der Warthog bei guter Pflege noch einen ganz okayen Wiederverkaufspreis erzielen.

Affirm. I just checked, and all of these campaigns are only available for the legacy A-10C module, but not for the A-10C II module. Oh wow, that's awesome! I checked the filter in the module manager and assumed that I had no "A-10C II" entry because there were no more campaigns available for me, but it seems the filter "A-10C" in the module manager includes both the A-10C and the A-10C II modules. Either way, cool that the campaigns are available for both versions of the A-10C!

Let's check the campaigns: A-10C - Georgian Hammer Georgian Hammer with CA A-10C - Sturmovik Of these, the 2 Georgian Hammer campaigns are mostly the same with the exception that in the Combined Armes (CA) version, some vehicles can be controlled by the player (while flying the aircraft). This version was mostly a showcase for Combined Arms, but as far as I can tell has received very little feedback from players. The Sturmovik campaign, TBH, I didn't even know it existed. Then there are payware-campaigns like Piercing Fury that are no longer supported by the author. Operation Agile Spear by Combat King Simulations has been released for both A-10C modules right off the bat, and the Persian Freedom campaign is also available for both modules. The Training Campaigns by Maple Flag work just as well in the old module - yes, they lack the new toys, but what players learn in these campaigns translates almost 1:1 into the A-10C II module. When we look at the single player missions, to be honest, these missions were never really good to begin with. With community generated content (7 campaigns and 52 single player missions at the time of writing this post) and several payware campaigns available, these missions that come with the game are pretty substandard by now, and it isn't a big loss not having them available for the new A-10C II module. That leaves what I would consider important content: Training Missions and Instant Action Missions - both of these are available for both modules. I mean, yes, you guys are right that it should be an easy fix, changing the A-10C to an A-10C II and adding the old missions and campaigns to the new module. It's just that you guys aren't missing out on anything great without them.

I'm not sure I understand your question. So you found the chapters in the manual for Control Stick and Throttles, you've looked at the images showing all the buttons and what they're called, you've looked at the big tables describing what short and long presses do on every single button, but now you're wondering what the heck any of that means. Did I get that right? In that case, I would recommend reading the manual in much more detail, because it does explain and describe most of these functions. However, the information is spread around the manual, because using the HOTAS functions touches on many different aspects of flying and controlling the aircraft. For a good primer, I would recommend the in-game mission TRAINING -> A-10C II -> HOTAS Fundamentals You can also go on Youtube and look for video explanations. Some are really fantastic, others get stuff wrong and teach bad habits. You'll have to figure out what to embrace and what to ignore. Some of these HOTAS functions are indeed quite complicated and require a deeper understanding of the associated systems. These forums are full of questions and answers regarding those functions - the search function is your friend. For specific questions, just let us know what you're interested to know.