pokeraccio

Just a very simple tutorial on how to use the F18 ACLS on Super Carrier

may 18th OB changelog: DCS: F/A-18C Hornet by Eagle Dynamics Fixed crashes/freezes in avionics. Added ACLS Missing 10 SEC cue. Added Additional carrier data to the kneeboard - ATC frequency, TACAN and ILCS channel. Added ACL T/C available with simple carrier. Fixed: CMD CNT doesn't appear after coupling. Fixed: Stores diamond behaviour with BRU-55 with 2 * GBU-38. Fixed: JDAM TOO / PP behaviour when using QTY. also updated on Stable on friday

ciao @Bilico, senza avere altri dettagli ed in attesa di qualcuno più ferrato in robe tecniche mi sento di suggerire di controllare queste cose inizialmente: - Page File - hot plug - antivirus

Take a look also at this nice RedKite tutorial.

Nice, even if I think in real F18, you should be able to select CPL since the start of the approach. we have more than one bug going on with ACLS, one of them is about the wake turbulence option (when turned on) handling capabilities and sometimes with strong wind, ship speed >12 should work now with something around this: ship speed 11Kts and wind on axis 10Kts (also with wake turb on), tested also with no wake turb and ship speed 15kts and wind on axis up to 20kts.

Hi, @OLD CROW I've tested your mix and it was working good by my side, (the only difference from your video the mix it is day time). Something I notice from your video is that when I couple the system I have CPLD P/R on HUD and on UFC I have only :CPL the other windows "BALT" and "RALT" are blanked. Have you tried to engage autopilot ":CPL" just after you get ACL RDY on the left DDI? what I do, is after the LND checks (geardown, flaps full), I stabilize the AOA on speed when I'm on :BALT 1200, then engage ATC to maintain it, then when I have ACL RDY on the left DDI I engage the autopilot :CPL. Did that on your mix, and was working.

I got your point, and I agree with you that practicing during day time it is another kind of story. Let’s see if we can find a solution, we could also try with the wishlist section.

The problems about the default mission are because there are others “carrier able” AI with takeoff/landing waypoint as it seems interfering with acls, if you remove them, the acls will work as it should be. ED is investigating. If we want a little bit of life around and use the ACLS, now we are stuck with just let them spawn in flight and orbit… defenely a bug.

You have for sure some "carrier able" AI with takeoff/landing waypoint around in your Mix. try to delete them (at least their specific waypoint).

Hello, you just need to reset the system

Day would be better, for sure, but selecting a night time in ME is a Case III with a perfect CAVOK conditions, so in the mean time some guru finds a lua or mod solution, better then nothing I do Night CAVOK ACLS traps to see the carrier from the start of Case III approach.

this is an old mission I used to test things, then I've setup all the ACLS stuff and was working, keeping in mind all the current bugs about SC/F18 ACLS, so I removed all the "carrier able" AI take off/Landing waypoints... and also if using wake turbulence turn it off or lower the wind speed... https://www.digitalcombatsimulator.com/en/files/3322202/

In this video, I do not see the autopilot Coupled to the ACLS, just the ATC. Is that intended?

You're welcome, anyway I never test it, I'm still kind of basic with george interface, I'm using most of the time the FLT mode.

this make sense.

Hello This should be carried on by the George Interface. CMBT (COMBAT MANEUVERS) Right Short Commands George to fly a direct path to the current Navigation Direct-To Cue. If the point is part of a route, George will continue along that route in sequence. If the point is not part of a route, or is the final point in the route, George will come to a hover at that location reference: DCS AH64 Manual from pg. 325 (the specific text is on pg.331)

I think the MAX power application about all the videos we have access to, are due to this.

Normal Procedures states MIL (military thrust) power application. So it is reasonable to think that it is certified to be like that. I believe the use of MAX is not forbidden, but it is not advisable do to controllability issues in case of engine flame out, as it implies high asymmetric thrust management on a critical AOA/speed situation, seems that benefits are less than troubles.

hi IvanK, try to remove the Ai f18 flight aerial-2 form your mix or let it spawn already in air (no takeoff/landing waypoint), and test again, I see it's setup to take off from carrier in your mix. I never tested on stennis/multiplayer but just SC and single player, and I found some strange connection about the waypoint type (take-off/landing) of all the "carrier able" AI planes as I'm trying to track here:

CMD CNT and 10 SEC I believe are to be implemented yet. about the ACLS not working as expected when there are other AI flights in the mission, in this post I explain mine and others findings: so it's not just F18/F14 but I'm pretty much sure it's something related with all "Carrier able" AI (E2, S3, F18lot20, F14...) dealing with waypoints Takeoff/Landing... in the same mission.

never, maybe we'll see it in the next update also with "10 SEC"

Do you have CPLD HDG on final instead of CPLD P/R? Digging in this, I found the bug more complex than I thought, as the AI Flights group stuff is happening with waypoint logic based... so a lot of combination, then there is also the reported bug of ACLS not able to handle the new burble effect / strong wind that make the plane land too short.

For sure, now if we want to use ACLS, we have to turn off Wake Turbulence or lower the carrier speed

And as @Hinkey found, I confirm his statement, the AI F18 Flight group is not a problem if is not taking off/landing but just flying around, not messing with a waypoint "landing" on the carrier, as long as the player is performing ACLS approach/trap. (on carrier for sure, landing on a runway after an AI F18 air spawn I'm not sure as I did not test it yet)