pokeraccio

Hi, as some folks asked me to share an ACLS mix, I'd like to share just a quick practice mission I use to test stuff. with some kneeboards page from DCS SC manual Case III. cheers Practice Mission. ACLS, AAR, Ground Strike, Night OPS F18 HOT START CVN F18 COLD START CVN F14 HOT START CVN F14 COLD START CVN F18 HOT 50nm APP FLIGHT: 305.0 COMM 1 BUTTON 1 TOWER: 127.5 COMM 2 BUTTON 1 CVN: Wind over deck: 21 kts BRC: 285 TCN: 71 ICLS: 11 LINK4=225.0 ACLS=ON AAR= 1X - 251.0 COMMS 1/2 BUTTON 18 AWACS= 256.0 COMMS 1/2 BUTTON 4 Ground Strike with voice feedback if good hit 2 Ground Targets at WPT 3 and WPT 4 2x AAA 2 Moving Target same location 2x Tank (T72) https://www.digitalcombatsimulator.com/en/files/3322202/ copy the miz file in: \Saved Games\DCS.openbeta\Missions created and tested with F18 on DCS Open Beta: 2.7.12.23362 V1.2 -temporary version due to current bugs -AI flights just orbit around V1.1 -trigger fix -added F14 COLD -removed wingman -added F18 AI CAP (will recover after player)

do you have wake turbulence option ON? if yes, try to lower the carrier speed from 25 to 11kts in this mission.

There is also another WIP situation, that seems ACLS is not able to handle well the burble effect, so if you have wake turbulence active may cause trouble to the system, try to disable WT if you have it on. try also to setup in mission editor carrier speed to 11 and wind no more than 10

Hi, I'm opening this dedicated post as I did some troubleshooting on some old mix, I believe the problem is other units (F18/F14) not in your flight group. For example, I got a mix with 3 F18 flights, the ACLS was not working and got strange behaviour, then I deleted all the flights not in my group (F18x4), and the ACLS was working as expected. I tested and it's happening with F18 AI (even if F18 Flight are on a Airport to Airport route so not dealing with Carrier at all) and F14 AI flights. On the same testing mission but changing F18 AI flt with F16 AI flt on the same Airport to Airport route, ACLS on Carrier works perfect as expected. Tracks attached (F14AI CVN OPS ACLS no good, F18AI LAND OPS ACLS no good, F16AI LAND OPS ACLS ok), but it's easy to reproduce. latest OB. - New test: This bug seems related to the AI ("carrier able" so not just F18 or F14) Flight groups waypoint logic (takeoff/landing). As in a new test I've setup Awacs and AAR to take off from CVN from Ramp Hot and then at a specific subsequent waypoint "orbit", I was able to use ACLS with no problems, but just when the 2 AI where orbiting. If in the mix editor I set them to follow their route with normal waypoint, even with no landing wpt at the end, after Takeoff from runway/Takeoff from ramp/Takeoff from parking hot, I've got bad ACSL behaviour like CPLD HDG (once TILT) with autopilot disconnected instead of CPLD P/R. Bad ACLS behaviour also when there is just an only Landing waypoint and they do not have any orbit to "isolate" them from that waypoint type. If you set the "carrier able" AI to spawn already flying with only Fly over point/Turning point, ACLS works as expected (burble Bug excluded). - Added some more tracks, sorry for the Case III app not by the book, but it's just to keep the tracks file small. hope that helps you out to fix it. cheers Pokeraccio_ACLS_5_F18_F14AI_noACLS.trk Pokeraccio_ACLS_6_F18_F18AInoCVNLND_noACLS.trk Pokeraccio_ACLS_7_F18_F16AI_OKACLS.trk Pokeraccio_ACLS_17_F18_F18andF14AIairNoTakeoffLnd_E2TakeoffRunwayNoLnd_bad_ACLS.trk Pokeraccio_ACLS_16_F18_F18andF14AIairNoTakeoffLnd_E2TakeoffHotNoLnd_bad_ACLS.trk Pokeraccio_ACLS_15_F18_F18andF14AIairNoTakeoffLnd_E2TakeofframpNoLnd_bad_ACLS.trk

I'm able to trap with ACLS every time, except if some other F18/F14 AI Flights are in the same mission. Is your trap weight around or under 33.000? (I did some flights and I was able to trap with ACLS up to 36.000 I believe, but I'll test again on that)

Nor F14s AI active flight group.

In mission editor try to delete the other F18/F14 AI Flights (not your wingman or element) save as another mission and test, let me know.

Do you have any other F18 AI o F14 AI flights in your mission? maybe I found a possible bug on that read my post here:

Hello, try to do not add other F18 flight to your mission, but just your flight group (your F18 + the ones you want) then test.

Hi, I did some troubleshooting on some old mix, I believe the problem is other units not in your flight group, try to see if in your test mix there is this situation, and if it is like that, try to delete the other F18/flights not in your flight group. For example, I got a mix with 3 F18 flights, the ACLS was not working and got strange behaviour, then I deleted all the flights not in my group (F18x4), and the ACLS was working as expected. (just check the carrier is setup correctly in ME, something like my pic attached and test) I think ED @BIGNEWY is aware of this, I tested and it's happening just with F18 AI (even if F18 Flight are on a Airport to Airport route so not dealing with Carrier at all) and F14 AI flights. On the same testing mission but changing F18 AI flt with F16 AI flt on the same Airport to Airport route, ACLS on Carrier works perfect as expected. If you need I can open a new bug report. got also some tracks, but it's easy to reproduce. ciao Hi, try to follow my post and check the mission. Let me know, the carrier is set ok in your pic. Hi, do you have other flights than your flight group in your old mission? try just to delete them in case and save as a new mission, test.

Tested 345.0 on a quick mix, SP, SuperCarrier, everything works ok be sure you set it up correctly in Mission Editor and do all the comms

https://www.fighterpilotpodcast.com/episodes/135-carrier-air-traffic-control/ a very nice episode, but if you want to have reference for the professional answer you can find it from 41:10... cheers

AFAIK, in DCS not implemented yet, in real life I heard the radar vectors you to enter in a straight in approach between 2 traffic approaching as they manage with separation some "holes" to handle bolters in CASEIII

Hi, as per title, CASE III situation when you command RTB to your Flight, triggers "marking moms" behaviour and logic also for player, I don't know if it's should be like that.

Hi, try to reset the system after ACLS trap, on the DDI exit with -> "menu" pushbutton ->HSI ->ACLS, it will test again it, you should be able to get rid of TILT adv.

Night time it is enough to trigger case 3 recovery. ref. Supercarrier manual Case II Recovery Case II recovery occurs during daylight hours when conditions may be poor on the approach but adequate for landing under visual flight rules. The cloud ceiling must be above 1,000 feet and visibility more than 5 nm. This can be thought of as a combination of Case I and Case III. The Case III procedures are used outside 10 nm and Case I procedures are used inside 10 nm. For a CASE II recovery, you will radio “see you at 10” when the aircraft is 10 nm from the carrier just as on a Case I recovery. Radio control is transferred from the approach controller to the tower controller. At this point, the pilot performs an overhead break and landing. No Case I holding stack is required. Case III Recovery Case III recovery occurs when any cloud celling is below 1,000 feet or when visibility is less than 5 nm regardless of cloud ceiling. All night operations are conducted in Case III

Hello, on F18, after an ACLS approach and trap I'm unable to switch off the ICLS. I don't know if it's intended with the new system logic or just a little bug. I'm pretty sure I was able to do that before the last OB patch. Cheers Pokeraccio_ACLS_2.trk

That's true, files in kneeboard must have extension in lowercase.

prego, figurati Se ti interessa l'AH-64, ti consiglio i video di Casmo, un pilota che ha operato realmente con il mezzo, in questo in particolare, dal min 10:40 circa, spiega nel dettaglio il meccanismo del ruotino.

Ciao, per essere bloccato, una volta reingaggiato il comando, il ruotino deve essere in posizione neutra (dritto/allineato), così che il blocco possa sistemarsi nella sede.

hi, try this \Program Files\Eagle Dynamics\DCS World OpenBeta\MissionEditor\MissionEditor.lua Change the OPTIONS_ADD_COMMAND_CODES_TO_TOOLTIP so that its value is TRUE

To be clear, to setup in Mission Editor a typical SA6 SAM system: group units (you can try add/sub units if you like) all in the same group 1 x SAM SA6 KUB (STR) 4 x SAM SA6 (TEL) 2 x Ural 375 1 x GPU APA 80 ZIL 131 1 x URAL 375 Mobile C2

I believe you need to setup the sam site with all the vehicle needed a Search/Track Radar for example, the sa6 launcher DCS version alone is not enough.

Copy that, sorry guys, I misread the troubles you were facing