Despayre

We definitely agree on that part. I decided to look into this further, and found a post that explains why codes are what they are, (btw, I was thinking 1688, "1655" was a mental typo ) More details on that, here:

I understand your point, but I just can't get myself all the way around to agreeing with it. This movie is one of the highest grossing movies ever, and you're suggesting that somehow the "Hollywood-ness" of it, is "counter productive"? I don't see that. I can also tell you that I went to the movie with someone that knows nothing about planes, and as non-technical as the movie was, he had dozens of questions about it later, realism would have made that so much more confusing.... not to mention the 8 minutes we'd all have sat there staring at the screen doing nothing else while the Tomcat INS warmed up.... and then stumbled into the various potholes, before crashing into those poorly placed grain silos (or whatever they were supposed to be). More realism means that SU-57 hits him with IFF, followed by a Fox1 from about 50 miles out, which doesn't even trigger a launch warning, and Cruise & Co, fall down go boom. But instead we get, "His partner just moved into his weapons envelope...." uhm, what? The SU-57 has off-boresight helmet mounted missiles, it's weapons envelope is pretty much a complete globe around the aircraft, moving outwards for at least 50 miles, it has no reason at all to move in behind the Tomcat. However, based on that, for ppl that thought the movie was too long, realism would definitely solve that problem.... this mission is over in about 5 minutes. To be fair, I did like the realism that was in the movie, such as knowing that the Tomcat needed ground power and oxygen to start up, that's not common knowledge, and I thought that was one of several pretty cool realistic touches, so it's not that I just don't like "realism", but this is a Hollywood action movie not a documentary, both are good, but when's the last time you saw a documentary that made 3/4 of a billion dollars in the first 3 weeks of release? $747,044,000.00USD worldwide gross so far says Hollywood might have got this one right, just the way it is. Complete with flaws and everything. (source: https://www.boxofficemojo.com/release/rl2500036097/) Sidenote, I also noticed in the movie that the code for the laser guidance was 1655, the same as the default code in DCS, which I assume coincides to something realistic cuz I can't assume that's a coincidence.

Aha, there's where you went wrong. Maverick is a film about human emotional growth and closure, and new relationships. The cool plane stuff is there so that guys will go see it too.

They have said they will be populating the map with more airbases when they turn their attention to the mainland, their first priority was getting the Falklands look right before anything else.

I did skim through all the pages, and did not see this livery shown. This plane was on display at the Air Museum in Palm Springs when I took this picture. According to Wikipedia, it was an important squadron in the 60's, 70's, and 80's. https://en.wikipedia.org/wiki/VFA-161

Really enjoying your campaigns btw, nice work! Two minor items from Mission 3, both have to do with radio chatter. 1. The text onscreen says to tune your radio to Coyote, but the voiceover says to tune your radio to Caliente. (I believe Coyote is the correct one) 2. Shortly after that, Coyote is referenced again, but it's got a spelling error, "Coyotte". This happens right before he talks about what "restricted airspace" means. I know, super-minor and doesn't really affect gameplay, I'm just reporting what I see.

I played mission 1, three times, each time, I had a complete HUD failure just as I got to WP2, and had to guide myself into Nellis with other methods each time. (Grabbed a heading from F10, and used my emergency compass to stay on that bearing to Nellis). I do NOT have random failures enabled in options. Not a big issue since I was able to complete the mission anyway, but just confirming that the issue exists (I thought it was intentional, some kind of "test" for us! ).

It is pretty simple to setup, so it seems likely that it's a config issue where the devices can't see each other, assuming you've set things up correctly, but let's start with the basics... What are the systems you're trying to connect? and what are the IP addresses of each device? On your Windows PC (I'm assuming that's what you have), Do you have any firewalls turned on? Either the Windows Defender, or any of the 3rd party ones (McAfee, Norton, AVG, BitDefender, Malwarebytes, Avast, Kaspersky, etc)? What IP address did you put in the PC, and what address did you put in the tablet/phone? Do you have any firewall type apps on the tablet/phone?

They'd have to be for realism, that's how the flat earthers tell us that they keep everyone away from the ice wall!

Sorry, that was ambiguous. By "this plane", I meant the F-18. not the MiG/F-5. I know the F-5 doesn't get a lot of love in DCS, but how can anyone say that's not one of the sexiest looking planes ever?! Everything about it's shape oozes awesomeness. (and I say that as an F-14 fanboi! )

Why do you think those silhouettes should be F-5's? Are you referring to the planes shot down in the first Top Gun? Because this plane wasn't in that movie... or, if this is a reference to something in the new movie, don't tell me yet, I'm seeing it tomorrow. I will also add that while I agree those do look like F-18's to me too, it's a pretty close comparison from those angles, and seems borderline nit-picky. F-5 image attached.

Mission 13: Cavalry Has Arrived. When you are approaching the mountains, you hear an AWACS (?) alert msg that you are too high, can be seen, and to get lower, except, it's addressed to your escort's callsign, and then your player replies anyway, and the escort doesn't. (I think the original msg just has the wrong call-sign, and it's supposed to be directed at the player, not the escort, who is not trying to be low in the first place).

Mission 13: Cavalry Has Arrived. Kneeboard and briefing notes both refer to the laser code as 1688, but in-game dialog with Ghost still says 1668 (until you get to the comms lasing dialogs, then it's correct again).

Loving the app, but on the M2000, I don't seem to be able to open the jettison toggle cover, nor can I use the toggle once I open it, is this functional and I'm just doing something wrong, or is this still on the wishlist?

I haven't been playing very long, but already I've found that I actively seek out servers that have the Overlord bot installed, it's so much better than using keyboard shortcuts, and it seems to work really well. +1 for anything, such as this specific topic, that makes the Overlord bot even better. Great job so far!