ACLS - F14B

[Goliathus]

Hey guys,

this is meant to be a general question, this is why I don´t attach any files. If it will be necessary, I´ll add them later.

I play solely SP and I like to play the Liberation dynamic campaign. I have everything up to date (DCS Open beta, latest DCS Liberation release). I fly mostly the F/A-18C and am fully aware, that the ACLS is not functioning at all it there are more aircraft in the mission involved and is pretty useless until this will get fixed.

But is this the very same with the F-14B if you use the DCS Liberation? I tripple checked missions in mission editor and there is everything setted up correctly, so there are only two possible conclusions. First is, that the problem rests somewhere between my monitor and my seat (me) or it is messed up in DCS.

To make myself clear, I know how to use ACLS in the F-14B and am able to land with it in the missions that I created for this purpose (yes all the settings are very same as in DCS Liberation created missions, so they should be "ACLS" identical). But obviously, if I fly a DCS Liberation created mission, I get only the VOICE message and never anything other (LANDING CHCK etc.) and am forced to land by myself.

So I´ll try to ask a simple question - is there anyone who plays the DCS with DCS Liberation, is using the Supercarrier, fly the F-14B (singleplayer) and is able to land the CASE III landing via ACLS?

If yes, then I can try to post my trackfile, mission file etc. to see if it´s me, but I´m strongly convinced that this is ACLS not working properly not even it F-14B at the moment. I´m relativly new to the F-14B and I was learning to fly it manually, so I didn´t try the ACLS in the past until now, so I can´t say if this was happening from the very beginning.

But as I said, in a sterile enviroment created in my own mission I am able to use the ACLS and it is working there - if I´m the only aircraft in the mission. 

Thx and Happy New Year to everyone.

Goliathus

 

[WinOrLose]

I dont have Liberation but did some practice in the F14B and did obtain the ACLS lock on but the landing resulted in a bolter.

Probably doesnt help your question but does yours relate to the lock on or the landing itself?

[Goliathus]

Thank you for your response. 

The issue I´m experiencing is that I get no response from the ACLS at all. Not even the "landing check" light. It behaves like if my plane isn´t communicating with the carrier at all. 

TBH I was able to connect recently once and use the ACLS and I did only one thing differently than any other time - I switched to the RIO seat and set everything manually instead of using the Vaicom Pro plugin (to connect to the link of the mothership). I´m pretty sure I did everything correctly even when using he Vaicom Pro plugin and it does work in my test mission with this plugin. Unfortunatelly I didn´t have enough time recently to test this more, it is possible, that the Vaicom Pro stopped working after some update and is not able to set the link despite the fact I get the correct response from the AI RIO (we have this very same issue with removing the wheelchocks etc.).

So I will test this more once I´ll have more time and check if the AI RIO is able set the link correctly when I give him the order via Vaicom Pro and if I don´t get any proper response from the carrier, I´ll switch to the RIO seat and check it manually. If there is enything wrong, I´ll set the link manually and see if it makes the ACLS to work properly. If yes, then it is clearly not DCS related.