3000 Black Jets of Allah

Coolie Switch Up will also switch to the next waypoint, only problem is that it only increments up so you need to type the waypoint like MagicSlave said to go down in the order. i.e. from WP2 back to WP1.

Still present here as well. It's incredibly frustrating as an Australian player given that most servers are hosted in the EU or NA. I basically can't play on any server that enforces ping based kicking.

I've always wondered this, it seems to give a number that is much much lower than what can actually be landed with.

It's not tied to a mission, it's tied to a skin. So unless they make copies of all skins for ground and water operations, and then have mission makers use only the carrier skins it's a little bit too much effort. Much easier to just let mission makers add the grey bomb skins to their missions if they want that realism.

The 54C will in DCS, the 54A in DCS will not.

It shouldn't trash it.

I thought so, thanks

After reading through the 1993 TO 1F-15E-1 I found the section about taking command of MPDs via the castle switch interesting. In the manual it says to take command you must depress the castle switch and then move the switch within 2 seconds in the direction of the MPD you want to take control of (like how you take control of the HUD in DCS). Can a dev confirm if the long press castle left/right/down we have in DCS correct for the version of the F-15 we have or should it be like how we do the HUD for all directions as per the -1? I understand we are not supposed to post links to any real world manuals in the forums so please don't post anything like that here

Happens to me as well in MT Multiplayer. It's really quite annoying.

I got the Forrestal to transit fine, I stuck to the realistic speed of 8 knots and it takes 11 hours to fully transit which is also realistic. I've attached the .miz as well. Forrestal Suez.miz

What unit is the tape in? Seems too high to be time of flight in seconds.

He did say he tried on the ground. When you're on the ground the points SHOULD be auto assigned as a T#, and if you do it in the air then you have to use the CAS page to assign them a T#. The other thing I noticed that is slightly wrong from the Chuck's guide is that you don't need to name it #TP01, you can just do #TP1. No need to add a 0 to pad out the single digit points.

My apologies, I just tested it and you're right, what I was thinking about was that the rectangle that goes around a locked ground unit shakes like crazy.

It shakes at every zoom level, its just when you're zoomed in more it's more noticable. And it does shake when you lock a unit.

I hate everything Restarting my pc for the 10th time got it working again, I don't know how but it did. Has anyone run into an issue recently where the script stops working in game and out? ID Lookup and DCS Comms are both blank and if I click a button I've already created it flashes up a yellow warning symbol on that button and nothing happens. I'm assuming something has gone wrong and the script isn't communicating with the streamdeck and vice versa but I'm not sure what to do, I've tried uninstalling and reinstalling but no dice. I noticed it happening yesterday but I haven't done an PC updates or even installed/uninstalled any programs in the past few days so it can't be something like that interfering with it. I've also tried removing everything in my Export.lua except the ExportScript.lua line but nothing happened.