Jagohu

When F-14s of the same group are late activated they open their wings to 16 degrees for a moment. When they are spawned next to each other (ie. on the carrier deck on the same elevator) the wings touch and they hit each other, eventually causing damage, which in turn means they won't depart from the carrier. Could this behavior be fixed somehow?

The official answer from ED is that it's not possible to package any models, like the civilian airliners in a campaign at the moment. They have to be installed manually. Too bad. I hope someday it'll change or at least they'll consider incorporating these nice models into DCS itself as AI models.

When the AI is done with the refueling, it always seems to go into a descend ~2500 feet, which is a strict no-no in AAR. When the formation is finished refueling, it should back up from the boom/basket, climb 1000' and then leave on its route. (ATF56)

Still there with 2.7. Could it be fixed at some point?

1. All the abovementioned objects (Oil rig, Gas platform, FARP, Helipad single frequencies) keep showing up in the ATC tab even when they're dead. 2. When calling "Inbound" to ie. an Oil rig with an F/A-18, the Marshal check-in pops up, but only the numbers are said. 3. Please remove the ATC tabs for these objects for airplanes - they only clutter the menu and make communications with ie. the carrier impossible if there're more than 10 oil rigs around. There is no point having them for fixed-wing aircraft, since they can't land there anyway. Trackfile attached. OIBA.trk

Anything on this?

Latter has to do with fuel levels and formation handling apparently, it's been checked before, this part is not a bug. Of course it's questionable once you "split formation".

Wingman is sent home via the Formation menu/Go to/RTB. Ship is in CASE3, therefore I could immediately hear "me" check in with Marshal - even without any of the radios being set to the Marshal freq(the radio frequencies didn't change even after the call, I could only hear my call). The main issue is, that this way the Player gets into the landing queue (it can be checked at the LSO platform) and as long as he doesn't say "Abort inbound", all the airplanes "behind him" in the queue will orbit instead of landing. It'd be better not to have this automatic Marshal-call if a wingman is sent home. It's a very easily reproducible bug, so I haven't made a tracklog. Thanks for checking!

Apparently this is the main issue of including mods as the CAM or MAM: Any suggestions are welcome as well as if anyone knows the creators of CAM/MAM so I could check it with them. Otherwise it'll have to be default DCS aircraft types - not that you'd see many of them visually anyways. The issue of installing the mods is another question to be addressed.

When the wingman is told to "Hold position" (COMMS/F1 Flight/F6 Hold position) it descends to ~13.000 ft and starts holding instead of keeping the altitude where the hold instruction was issued. By descending it might put itself in harm's way too, so I think it should always keep the present altitude. Tested with both F/A-18 and F-16, same behavior. F16_wingman_hold_here.trk

Perhaps, but it still should be counted as weight carried - if it was non-usable fuel it shouldn't show on the fuel gauge in the first place in my opinion 90 lbs is not a big thing, but it made me wonder if it's a bug or if it's like that IRL too.

ME says 100% fuel is 10803 lbs. IFEI shows 10890I when tank is full and CHKLIST page also calculates with 10890 lbs. Could you please have a look and align them somehow? Thank you!

Thanks, guys I'm happy that you like it so far I need to check with ED if including the CAM or any other mod which adds extra aircraft for the AI is allowed in payware campaigns at all, it all depends on that. If they are ok with it, it would increase realism very much and I'm all in favour of that

@makosch: thank you for the question. Presently I'm trying to finish this one, as this is part of a rather large campaign, which is planned to bring a complete CSG deployment alive in DCS with the everyday operations reconstructed throughout the 4 months as much as possible from the available materials during OIF. It's aimed to be more realistic and thus sometimes probably not as exciting like when ie. there's a full-blown (imagined) war, but this campaign is modelled based on historical data down to the details which I dare say you haven't seen in a DCS campaign before. There are no .miz templates, all you see is LUA scripted, generated traffic, it's not like they are inside the .miz file and wait for activation. There's more than 2000 hours of work in it already, and there's a lot more to go before it's released but I hope sometime during next year it'll be possible. Even restarting the same mission will generate a somewhat different air situation picture as it'd be IRL, so players will always have to be on their toes. Even the weather is going to be the same as it was on the same historical day (as much as DCS permits), based all on real meteorological reports - naturally this bit won't be random. In the future I guess it could be adapted to other maps, we'll see. I'm thinking more of Syria as a next stop, if there will be one, but who knows maybe the Caucasus could be done too, I haven't looked into that yet.

My single player campaign will contain all the major airways in the PG with the actual arrival/departure routes, airways, directions, navaids and traffic flying on them as white traffic with real callsigns, along with civilian ATC(including approach/departure/GCA/center+the default DCS tower) for both the white traffic and the player. The player will be able to set a performance value for his rig so for lower-end rigs we won't generate so many background traffic or they will only be generated near the player's predicted trajectory. It's one hell of a lot of work, but I'll get there at some point. Here's a screenshot from a test run in TacView. Same goes for marine traffic. Any comments are welcome.

OMAA(Abu Dhabi): TWR frequency: 119.2 MHz/270.0 MHz (DCS: 250.55) Source: https://www.airport-data.com/world-airports/OMAA-AUH/ OMAL(Al Ain) TWR frequency: only VHF 119.850 (DCS: 250.7) Source: https://www.airport-data.com/world-airports/OMAL-AAN/ OMAM(Al Dhafra) TWR frequency: 119.6 MHz/292.4 MHz (DCS: 250.1) Source: https://www.airport-data.com/world-airports/OMAM-DHF/ OMDB(Dubai) TWR frequency: only VHF 118.75MHz /119.05 MHz (DCS: 251.150) Source: https://www.airport-data.com/world-airports/OMDB-DXB/

The Oliver Hazard Perry class frigates only fly their flags/banners if they are marked as US[flag+banner] or Turkey[flag only]. If it's marked as ie. Australian, no matter what argument is given the ship won't fly neither the banner, nor the flag. On the picture there's a US(far) an Australian(middle) and a Turkish (close) OHP-FFG, all with the same(!) custom skin (HMAS Newcastle). Please fix this to allow ships with any nationalities to use any arguments or fly flags. Thank you!

Maybe it's carrier-dependent, on CVN-71 it worked fine for me.

This used to be a known bug. https://forums.eagle.ru/topic/259060-tacan-distance-error/?tab=comments#comment-4540862

The Tower frequency for OMDW is incorrectly set for 118.600 (OMSJ, Sarjah Tower frequency). In reality the frequency is 118.625. Source: UAE AIP, AD 3.2.18 OMDW AD 2.18 ATS COMMUNICATION FACILITIES

Push is time based AFAIK, if you miss your time at your push point (15+altitude nm) -> ie. if your assigned altitude is 8 then you need to be at 23 nm TACAN from the ship and commence as prescribed at your given approach time ie. 12:45:00+-10 seconds. At 12:46:00 the next guy in the stack at 24 nm distance will push.

In case of many inbounds during a CASE III recovery, Marshal assigns FL310+ for an E-2 aircraft which I cannot reach. It struggles up to FL316-ish, and keeps trying to get above to no avail correctly. Maybe the Marshal logic could be changed to behave as IRL, so that the E-2 would not be put on the top of the Marshal stack even if it's the last one arriving if the top is above FL280(?). Track attached. Thank you! E2D_FL320_assigned.trk

This is the first time it happened to me, but I thought I'd report it. Nearly 3 hours after launch, returning to the ship, calling in with "Inbound" to Marshal. My side number is 405, wingman's 402. As you can see on the screenshot, Player calls in as 402 holding hands with 405, while it should be 405 holding hands with 402. Marshal replies correctly. Reporting Established works fine (405). Abort inbound, continue mission works fine (405). Pressing "Inbound" again causes the same problem.

When checking in with Marshal / reporting "Established" in a CASE3 stack, the pilot reports the mentioned "theatre altitude", which is displayed in the F10 menu. Example: F10 menu altitude: 36169 HUD altitude: 34890 Altimeter setting: 29.92 "Marshal, 405 established, angels 36..." Not ideal.

FARP is scheduled to be destroyed after 10 seconds, just as additional info.