shagrat

IRL the Apaches definitely marked targets with laser for fast jets in a CAS stack. Not necessarily guiding the bombs, but pointing the Jet's TGP/Eyes onto the right spot via LSS. Nevertheless the TADS should also be able to guide any LGB, as well as APKWS or LJDAM.

With the new option to restrict weapons in the ME it would be the best solution to manage it like a TGP on other platforms. This way a mission designer could easily restrict its use when necessary, but it could be added in MP as the user or group wants. For example have two teams of 2 Longbow with one FCR each, or a flight of 4 with one FCR...

Virpil has a black curved 20cm extension, that's supposed to be compatible with the Warthog. Here is a link: https://virpil-controls.eu/vpc-flightstick-extension-200mm.html Ah, read the comments about the spring centering forces!

Der Witz bei der Mi-24 ist, dass tatsächlich die NVA-Begriffe korrekter aus dem russischen übernommen sind, als die "englischen" Begriffe, die versuchen quasi die Avionics eines US-Helikopters zu nutzen und wo nicht möglich kreativ werden... So wie deutsche Begriffe zum Betrieb eines Flugzeugträgers schwierig sind, wenn es keine Begriffe für z.B. den "Ball" oder "Paddles", "PriFly" etc. gibt. Lino hat sich da wieder extrem viel Mühe gegeben und das super aus den NVA-Unterlagen erarbeitet. Möchte gar nicht wissen wie lange er da dran gesessen hat.

Scale is set in the ME, IIRC.

^this

CCD is too "clean" at larger distance, FLIR is more dependent on the environment temperatures. The thing is we need more/better temperature representation.

Au contraire, it does suffer especially on the FLIR video. Simply switch from CCD to FLIR on the A-10C's Litening II. The resolution difference on the ATFLIR vs Litening is definitely modeled. What we don't have is blooming/background noise (ground being hot/cold) that influences how "sharp"/detailed the picture is, in real life.

By the way, another big factor is the environmental conditions. That's currently not modeled,but a huge influence on the real life images/Video.

Depends if it is a modern FLIR like the ones that you can buy on Amazon that have a digital circuit measuring the input and automatically adjusting/dimming/filtering the signal, before it reaches the sensor. Then postprocessing software may compensate to optimize the actual video you see on the screen... Just saying. Depends on a lot of factors.

"Videos" with unknown resolution, contrast, brightness, filmed from screen or from the system, post processed or a capture from direct feed... That's a lot of guesswork, to state "this is how it should look". I prefer the ED approach instead of trying to imitate obscure videos we don't know what version, Software, upgrades etc. we are watching... Mentioning the F-14 LANTIRN is a good basis, as it faithfully represents the oldest, low resolution analogue system with a low resolution IR sensor. The Lightening pods and AT-FLIR are round about 10 to 20 years more advanced and upgraded from those first analogue systems developed in the 80ies and early 90ies. My guess is EDs SMEs that actually looked at the real things are possibly a good source, that can provide better input than assumption. Just my 2 cents.

Depends, if the Hornet uses a Gen 4 Litening, or an older one. There is a lot of upgrading optimization that took place over the last decades since the Litening was introduced.

Genau das hatte ich geschrieben... Tracks sind KEIN Video, sondern enthalten jede Menge Details. ED kann Tracks auch noch deutlich tiefer analysieren... Aber auch für normale DCS piloten die helfen möchten, sind jede Menge Infos drin, die ein Video nie aufzeigen kann.

The WWII airfields don't have any beacons, so you need to improvise by setting up a "beacon", manually. ILS like directional transmission isn't possible, so you can only emulate an NDB/location beacon. Together with a "know" runway heading and dead reckoning, this should get you on a good enough approach at night, or with a bit of weather... In full IFR conditions where you can't see beyond your wipers, well you get a realistic WWII heartbeat skipping experience.

If "Approach Beacon" means ILS than you need ILS at the airfield, so a modern airfield/map is required. If you mean a beacon as in location beacon for an airfield, you can add it at the runway threshold as explained and set your approach to known runway heading and keep the beacon centered... Not a perfect VFR ILS approach, but should get you close to the runway and on approach course.

You're right of course.

Ja, man unterschätzt die Tracks. Ideal ist kurz rein und nur das Problem "provozieren". Man kann dir dann quasi "über die Schulter schauen". Tracks sind nicht eine perfekte Aufzeichnung (kein Video-Ersatz) aber ein gutes Hilfsmittel, um z.B. zu sehen welche Steuereingaben, Schalter, Hebel etc.bedient werden und welche Settings du gesetzt hast. Asymmetrische Loads (Sogenannte Dirty oder Ugly Loadouts) mit unterschiedlichem Gewicht, aber auch Drag (Luftwiderstand), sind nicht ohne. Es gibt extra Tabellen und Listen um Trimmung, insbesondere beim Trägerstart zu errechnen und es gibt Grenzen, wo ein asymmetrisches Loadout aus guten Gründen nicht geladen werden soll/darf. Fly-by-wire hilft zwar, ist aber keine Zauberei und hat auch seine Grenzen.

Just put a unit like a truck (OpelBlitz?) or some antenna or even a single soldier adjacent to any building in the mission editor. Then create an advance task top "set frequency" (it's MHz so 240 kHz is 0.24) and below add a "Transmission" task with any way or ogg file you want to transmit. Check the loop option, power to 100W. That's it you created a "beacon" transmitting from that unit.

Wenn du den Funkschalter am HOTAS gemapped hast, kannst du eines der beiden Funkgeräte anwählen und es sollte das Funkmenü oben rechts erscheinen. Dieses lässt sich auch per Maus anklicken oder in VR mit dem Punkt und dem Mausemulationstasten.

A quick video from Casmo: https://youtu.be/3w-OWojSjtY

When AV-8B spawns on the deck (aft of the island) on the LHA-1 Tarawa the aircrafts nose points towards the bow of the ship. It should in fact point towards the stern of the ship (angled of course, but switch the direction from front to back), to allow the aircraft to roll to the stern, turn on the tramline and line up for take off, without requiring a 270° turn. If you look at basically any picture, showing AV-8B on the deck of LHA or LHD and they are preparing to launch or parked after recovery they all point aft to the stern of the boat. The rare photograph where they don't, shows either port visit line ups, or crowded decks to store the aircraft/optimization of storage space, so they can't launch anyway. This should just need a simple tweak to the spawn position and plane direction on spawn.

Without having looked at the Miz file, a common issue is that the Waypoint with the attack is too close to the target, so when the "order" comes they turn around to get the necessary distance for the attack run, first. Try setting the waypoint at least 10-15 NM away from the target and verify the attack task does not specify a specific attack heading etc.

Ok, so I checked today. Disclaimer: no real life F/A-18C pilot here, so can not tell if this is true to life or not. I have realistic TDC enabled in the special options. Set up a similar scene. Oil rig with a T-55 some 60m away. WP1 is at the base of the Oil rig. Ingress, make sure Master arm is on, A/G mode selected, TGP on RMFD, stores on LMFD, center MFD HSI. Box WAYP on center MFD, select WP1, then WPDESG. This slaves TGP and MAV to the designation. TGP should now look at the oil rig. On LMFD box MAVF and press OSB again to call the MAV video feed. Sensor Select left to get the diamond on the MAV screen, this should uncage the MAV, as well and commands it to look at the oil rig(WP1). It should lock the oil rig. As long as there is a ground designation, everything is slaved to it! Now, there are to options. 1) change the designation and Cage/uncage the MAV to slave to the new point (useful if you switch between Markpoints or prearranged waypoints with different targets) or 2) with focus still on the MAV screen, press NoseWheelSteering/undesignate once to remove the INS designation and then depress and hold(!) the TDC while slewing the MAV seeker over the T-55. Releasing TDC depress will command the MAV seeker to attempt a lock. Again, I can't say if this is the correct implementation, but like this I can operate the MAVF manually. Please check, if this works the same, for you.

The right MFD with the TGP is selected for control with the TDC. Indicated, by the diamond symbol in the upper right corner. Switch to the left MFD with the MAV, with SensorSelectSwitch left (check diamond is on the MAV screen) then you control the MAV seeker with the TDC. It may be necessary to depress TDC to actually command a lock, if it can't lock the tank immediately on slew.

After one year, the update with Cyprus released and me currently testing a mission in northern Syria, again, I'd like to bump this thread and kindly ask, if it's possible to add a couple generic city blocks and streets where the city of Afrin should be? It was very popular in the news when contested and sieged... also it is one of the cities actually present by name on the F10 flight map and thus an important landmark for VFR navigation.