Jump to content

shagrat

ED Translators
  • Posts

    13113
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by shagrat

  1. That's exactly how they operate in real life. Most GBU have a set of dials on the bomb, that are used to adjust the laser code by the ground crew. It cannot be changed in the air. That's also the reason, why most aircraft can deliver LGBs as a bomb truck, simply drop the bomb and let the JTAC lase. The pilot will tell the JTAC the bombs laser code. JTAC sets the code on his designator (it's actually implemented this way in Combined Arms, where a human JTAC has the option to adjust the laser code. The AI JTAC is currently limited to the default laser code of 1688. In some SP missions/campaigns, the mission creators go through a lot of scripting to basically build their own JTAC...
  2. On the bombs, but not the JTAC. IRL the code is fixed on GBU-12/10/16 etc. It is dialed in at the bomb and can't be changed from inside the cockpit. More and more modules simulate this real life limitation, by allowing adjustments to laser codes on loadout only on the ground. Now, if you have multiple aircraft armed with LGBs they will deconflict the laser codes between aircraft or flight according to the mission. Now in DCS the AI JTAC will always use 1688 as his laser code, whereas IRL he will get the code from the aircraft he is working and adjust his laser code accordingly. The only way to do this, currently, is to either script a "laser point" with a frequency with out using the AI JTAC or manually with Combined Arms and have a player do the JTAC role. If we could get an F-menu-option to tell the JTAC our bombs' laser codes, it would be fine. It could simply read the available codes from the loadout and let us select the appropriate one for the JTAC, just as an idea.
  3. The Laser Code implementation is a real problem in Multiplayer, as it more or less makes it impossible to use more than one AI JTAC in an area, or actually use the laser codes on bombs, as ALL bombs and TGP are required to set 1688. I know we have lua scripts using different codes, but that doesn't solve the basic issue, that you have a code set on the individual GBU-12/10/16 etc. and the aircraft tells the JTAC what code to lase, IRL.
  4. Yep, totally! I think I pointed out that I am making assumptions from the obvious (omission of Bahrain), but not "knowing". I am really stoked for Afghanistan, after all. Happy to getting closer to release.
  5. They don't. And as I pointed out, I have a pretty good idea why they, at that point in time decided against an Iraq area, removed Bahrain and omitted certain key infrastructure... Edit: also, I am not "angry". I just think it would have been the more versatile map after NTTR.
  6. Thanks! This is a very useful brevity code. If I've seen it somewhere, before, it definitely slipped my mind. Great conversation, by the way, I am learning a lot.
  7. Not only for helos! Lots of current DCS fixed wing jets will benefit from a real life scenario, as well. The AV-8B Harrier, the F-15E, the F/A-18C, the F-16C, the A-10C Warthog(!) and even the Mirage2000C with a bit of leeway saw action in the war on terror and OEF.
  8. Does not change the decision to make the wrong part of that area... Any place of the earth had its couple of days "conflict", but Iraq/Iran border down to Kuwait, with the 80ies Iran-Iraq war, Operation Desert Shield, Operation Desert Storm, Operation Southern Watch/Northern Watch, Operation Iraqi Freedom and the recent war on ISIL in Iraq, that saw engagements with a lot of available DCS' aircraft is definitely(!) more interesting than Operation Praying Mantis, a one day long naval engagement sinking some rusty Iranian boats in the Strait of Hormuz with the upcoming AI version of the A-6E Intruder... Just saying. P.S.: I personally think the reason to NOT create an Iraq map is connected to the fact, that the Persian Gulf map has the whole island of Bahrain missing, as well as the key locations of Kharg island and Busheer in southern Iran... but I might be wrong on that one.
  9. You can actually use the old .diff.lua files and load them into the "new" device ID, like you would with a backup. Fastest way I know, apart from command line script magic, with the benefit, that anyone can do this. Only if Keybinds changed drastically, you may need to sort some orange lines.
  10. The majority of Afghanistan is not remotely(!) a Desert. Eastern provinces are lush mountain valleys with timber industry as a major income, northern areas are a mix of mountains, hill and uzbekian steppe. The only desert is the Dasht'e Margo South of Kandahar and the region west of the Helmand valley. I personally am mostly interested in real life locations with well documented conflicts, which both Afghanistan and Iraq maps would provide. The decision to create a map in the Persian Gulf and deliberately omit Kuwait, Iraq, Iran's western border to Iraq was "interesting". I think I have a pretty good idea about the reasons, but as DCS maps can't really be used to plan a specific target run, I would have preferred the whole Persian Gulf Map moved some 500km to the west. My guess for the "other map" is strongly in the Pakistan/India Border region, though, as it would make a lot of sense.
  11. As Nick hinted at some more News in the upcoming "2024 and beyond" video in his interview at VIAF, I am stoked to see what we can expect. The map technology has made incredible progress over the last years, with the graphics engine tackling performance way better and handling quite large and detailed maps. Fingers crossed, we see a large low detail area down to the Arabian Sea and the Eastern parts of Pakistan... It would be a dream come true.
  12. You can see it identifying and prioritizing Anti-Air, tracked and wheeled armor on the whole screen, already, in Wags' FCR videos. It can classify those just fine and prioritize them.
  13. Not really, as the targeting computer is capable of identifying individual differences between tracked and wheeled armor, can identify Anti-Air as primary threats, etc. and sure as capable of identifying the "moving thingy" is a radar dish of a stationary SAM and not(!) a moving target.
  14. The limit comes from the computed targets, not the radar itself. It doesn't matter how big a radar dish is rotating on top of the chassis. The targeting computer will identify up to 256 targets, 16 are prioritized in the engagement range (that is 6km for stationary, or 8km if the computer classified it as moving). If the targeting computer is capable of identifying and distinguishing AA, tracked or wheeled MBT/IFV/APC, I guess it will recognize a stationary SA-6 radar as a "stationary SA-6"... that's because the AH-64D is an armed recon and attack helicopter designed to support ground forces against armor, not a dedicated SEAD/DEAD platform.
  15. No, you want to accomplish mission goals, with the least possible risk. If you encounter a situation where you would basically just sacrifice a trained crew and a million dollar worth of equipment for little to no gain, then you need to consider the option to turn around, adjust and/or fight another day
  16. That's because you are in a place, you shouldn't be. If you have attack helicopters flying in an environment where they are lit up by multiple SAM batteries, SHORAD and airplanes some SEAD/DEAD and CAP assets did a bad job and the best advice is, evade and get the hell out of Dodge. Frontal assault on a SAM/SHORAD infested enemy position seems a bit ambitious for a scout, light attack/support platform. Tanks, IFVs, APC and infantry is your game, preferable in an area already cleaned of anything but the occasional AAA or MANPAD and even those are usually a major concern to helicopters...
  17. If the blinky lights go on be evasive or dead... Should work for AI and players, alike.
  18. We don't have the Augusta Westland Apache AH-1 in DCS, only some british skins. No RR engines, not the defensive aids system...
  19. Bereinigt worden... Wie Yurgon sehr gut erklärt hat, fehlt uns im Deutschen ein Wort für "Missile" (hier hat sich Lenkflugkörper oder Lenkrakete) eingebürgert, weil es auch dem in der Luftwaffe für "Missiles" wie die AIM-120, oder AGM-65 verwendeten Sprachgebrauch entspricht. Raketen sind halt die Dinger die aus den Rocket pods verschossen werden. Das US Militär hat sich dazu entschieden, rockets mit einem LaserSeeker und einem Steuerset auszustatten und sie den FFARs (Folding FinAerialRockets) zuzuordnen. Damit tauchen sie in der Kategorie der Munition für die Rocket Pods auf. Es ist nicht möglich im Deutschen eine separates Bewaffnungsmenü anzulegen. Wir können nur die Begriffe übersetzen. Das Feld heißt halt im englischen "Rockets" und im Deutschen übersetzen wir es zur Unterscheidung von den Lenkraketen als "Ungelenkte Raketen". Die in der Kategorie tatsächlich hinterlegte Hierarchie der Waffen kommt aus der DCS internen Datenbank. Man könnte es so versuchen zu erklären: Da die AGR-20 keine Verbindung zum MissionComputer im Flugzeug hat (kein Datenkabel) und nicht auf ein Ziel aufgeschaltet wird, sondern ohne jegliche Ziel-Information, ungelenkt aus dem Launcher gefeuert wird und erst nach dem Abschuss den Laser erfasst und mit dem korrigieren beginnt, ist sie strenggenommen schon etwas anderes, als eine typische AGM.
  20. Or the bang for the bucks is considerable better, than for other aircraft. Or other aircraft are too expensive for the available budget, as a minimum of X aircraft is required, so you chose cheap over perfect... IIRC the MiG-21 and its licensed builds or copies were very popular, despite its shortcomings outside a very specific role. The original concept for the F-16 wasn't really a ground attack plane for Close Air Support, BAI or Air Strikes.
  21. You had to actively deselect the FCR for each AH-64D in every mission, as the default is FCR selected. So I am sure you need to revert every AH-64D you edited by hand. Though realistically the ratio of FCR equipped AH-64D should be around 1 out of 4.
  22. On the contrary, it would flood your target list with 100+ buildings and map objects to sort through in addition to vehicles, Infantry and aircraft. Even without that, as George "finds" targets by a factor of size, LOS and obstruction, he tends to always find the big "neutral coalition outpost" I put for decorations, instead of the enemy infantry near it. Not sure about the recent updates, but a while ago, static objects would be recognized and clutter the list. A typical workaround for targeting buildings, or bridges is to place a single infantry unit on the bridge or in front of the building. But you can try if a small container, tire or flag from the red coalition may show as a target on the list, as well.
  23. Gerade gesehen, Mikhail (K-51), macht auch wieder Kollektive. Da kommt zwar noch die Steuer drauf, weil außerhalb EU (Moskau), aber das Ding war sehr robust und preislich halt insgesamt bei 2/3 von den Virpil Collectives. Er macht jetzt auch ein "Zwei-Griff-viele-Hats-Kollektiv". Bestellung per PM und Zahlung war via Banküberweisung (privat zu privat da Mikhail kein Geschäft/Händler ist sondern die in Freizeit privat macht). PayPal geht wohl nicht mehr, wegen US-Sanktionen. https://forum.dcs.world/topic/222296-sollective-pitch-control-lever/?do=findComment&comment=5294568
  24. Kommt absolut auf den Helicopter an. Den Huey kannst du vermutlich komplett ohne Tasten am Kollektiv fliegen, eine Gazelle wohl auch, aber einen Apache definitiv eher nicht.
  25. Btw. it has been added in DCS 2.9 Thanks ED.
×
×
  • Create New...