Jagohu

The ME only offers the "default" skin, while there is a desert one which can be accessed through ModelViewer2.

Please consider adding the possibility of GPS jamming in certain areas. It could be added in the mission editor/LUA script with a trigger zone defined for the jamming and simple triggers of GPS jamming ON, GPS jamming OFF. On the aircraft side it should affect the relevant systems, ie. GPS position lost/highly inaccurate and generated error messages, along with the inability to deliver GPS-guided munitions. A substantial part of ie. the airspace near Syria is GPS jammed area for years now.

When enabling the "Historical list of units" filter in the ME, the tab Ground Vehicles within "Add Static Object" completely disappears. Date set to 21/06/2016

Iran has purchased AGM-65A missiles, but for DCS purposes the AGM-65B should be ok. Alternatively AGM-65A could be created with lower accuracy and more sensitive to optimal launch conditions. Sources: AGM-65A: 1972. First TV-led contrast-based release. Requires optimal launch conditions which, if not met, will cause the missile to lose its target. Guidance system focal length: 200 mm AGM-65B: 1975. Improved version of the AGM-65A, with better TV guidance, updated electronics, and a 400mm focal length allowing the target to be captured from further away. http://www.iiaf.net/stories/warstories/s4.html

@Flappie Thanks for picking this up. 1. If it's destroyed with bombs it removes the F10 icons now, but not the object from the scenery. This bit should be fixed, thanks for reporting it! 2. Indeed that bit seems ok. 3. Types are OK indeed 4. It still has a radio transmitter on 127.5 OIBA fixed according to the F10 CALLSIGN field. It can't be modified through ME, but at least it's not showing up anymore even in Easy Comms which is good!

Static objects have been there since the beginning and there's hardly any addition to them which could be used by 3rd parties. Please consider either adding new static objects to allow for more variability, especially in buildings-trees, etc. which could improve the scenarios. Please consider allowing the usage of static objects which are present on the given map (or at least on the ED-developed maps if it's an issue). It'd be nice to be able to re-use items from airports, cities, etc. elsewhere. Please consider adding road/runway/taxiway surfaces as static objects - allowing the developers to make maps look nicer in some areas. Thank you!

It could be ONE simple animation played every time there's an event S_EVENT_REFUELING_STOP - it should be simple enough.

Please add the callsign option "SANDY" to be used for some SAR assets. Thanks!

It would be nice if mortars would also show up on the FLIR, standing out of the background right after firing - for a while at least. Thanks!

It'd be nice to have the heat or radar signatures for mortars, so the player would have a chance to find them somehow. Thank you!

It doesn't cover it 100%, but it's something - along with a ton of other stuff to be included in my campaign at some point. The focus is OIF though, so this is not THE most important area.

It looks like it's fixed now with DCS 2.7.15.26783 Open Beta.

It's still an issue. @NineLine?

I've put the Mi-24 there for a comparison, that it's not a general bug, it's specific to AH-64 and UH-1. It seems to work with Mi-24 or AH-1, probably others too. That's interesting, thanks! I didn't realize that this was already considered as map's border and I also didn't think it'd anyway influence the behavior. Thanks!

Towards the end of this year hopefully, as part of a semi-dynamic campaign with proper ATC and a lot of other stuff I'll post it here when it becomes available.

To me that didn't work either, but I'll test it again.

Simple, but it works

For some reason the UH-1, AH-64A, AH-64D, AH-64D Block 2 helicopters don't react to the Search then engage, Attack Group or Attack Unit commands, they just fly around the target and get themselves shot down. I have changed the helicopter to others (AH1W,Mi-24P,Sa342M) and they work properly with the exact same setup, so it's just the Apache. Tracks attached. helicopter_attack_Mi24.trk helicopter_attack_AH64Blk2.trk helicopter_attack_Gazelle.trk helicopter_attack_AH64A.trk helicopter_attack_AH64D.trk helicopter_attack_Cobra.trk helicopter_attack_UH1trk.trk

Just noticed: when the JTAC/FAC asks for a specific weapon to be used, both the text and the sound is missing in case of Maverick is requested[possibly others too, haven't tested them, but the request cannon works]. It only says/writes "use" or "request" without the weapon being specified. JTAC_missing_sounds.trk

In dcs.log now we can see the parameters given by the JTAC: I'm not sure if it's a bug or a feature, but does anyone know how could we plainly access this data through LUA or the ME? I'm particularly interested in the egress direction and the target location. Thanks!

Tested on the Hornet, I suppose it's the same all around: If a unit is given a frequency which is non-selectable by the radio (ie. FAC given 211 MHz while the range starts from 225 MHz+), although entering the frequency into the radio gives an "ERROR", selecting the frequency via the Easy Radio / JTAC / Axeman1 [221.0 MHz] works. Even though it's greyed out, the buttons (ie. checkin) are selectable and the transmission/dialogue starts as normal.

Not that I found unfortunately. What you can do is set the trigger in the ME to read something and execute a script with that. Cumbersome, but it works.

I have created the HMAS Newcastle which will be released as part of a campaign.null

I have removed the soldiers - for me it didn't work, then I removed both the soldiers and the HMMWVs and they still not go through. I'm not quite sure what is the difference between your version and mine. ground_unit_static_cross_wo_soldiers_and_hmmwv.trk

First vehicle of 3 drives through ok, other two goes into the static objects. ground_unit_static_cross.trk