Greyman

When it is available, pressing the FINISH button will copy the command list to the clipboard, so you would be able to paste it into a document from there. Alternatively, the 'when I say' field, in the VA settings, for the VP profile, also contains the command list, so put your mouse cursor anywhere in that field and press Ctrl a and then Ctrl c to put the list onto the clipboard.

Airfield lights come on when you request landing, so maybe try that with the carrier

For the first time today, I've managed to stay connected, apart from a couple of those momentary separations, until my tanks were fully loaded. I think that the main reason is an improvement in my throttle control. I make very minor alternate movements, up or down, on each of the throttle levers and this makes it easier to close on the tanker under control and then to match its speed. Moving both levers together was a bit hit and miss for me, with the aforementioned lag and a tendency to over correct. I'm sure I've seen somewhere that this is how pilots control thrust in RL, but can't remember where.

It's good to hear that you got it sorted. i will probably need some help when i finally dive into the F14/AIRIO and you might be able to provide it. :)

so could it be something to do with the SRS PTT mapping option on the preferences tab. again, i don't use SRS myself, so possibly not going to be of much use, but i am trying to help.

Maybe try "approach to refuel"

That does sound like the radio is set to the wrong frequency, so either figure out how to do that or set easy comms to on. There is also an option that tunes the radio for you when you select an entity, even with easy comms off. For example "Batumi select" should tune the radio associated with the PTT button you pressed, to the Batumi tower. I'd go for option 1 though and learn how to tune the radio. I don't have the F14 yet, but I suspect that your RIO can be asked to do it.

"Approaching to refuel" should do the trick for the inbound equivalent and then "ready pre-contact when you are in position behind the tanker.

I've not used it for a while, but selecting the easy comms setting in DCS world might get somewhere towards what you are trying to do. Again, IIRC, you just use the Auto PTT button to select any radio

That sounds useful, particularly when I have accidentally left VA running and perhaps expectedly, given Murphy's Law, then gone on to potentially get my best ever recovery score. Also, it would appear that you can indeed move the comms menu and/or the message box, by editing a DCS lua file, so that might hold a potential solution.

it appears that the comms menu is getting called by something within VA/VP, possibly due to background noise, and whether you have the comms menu hidden or not in the options, it relocates the DCS text output box, or whatever the right name for it is, to the bottom right of the display and in a truncated form. I wonder if the DCS comms menu can be moved in the options??

is that just with VA/VP running or without it? I use VR too and when i fly that mission with VA/VP loaded, the apparently random acitvations of the comms menu, whether it's visible or not, causes Banklers summaries to be moved to the bottom right of the display to be truncated. that's why i don't fly that mission with VA/VP.

I also fly Banklers Case I mission, but I just close VA before I do. The landing summary, usually telling me what a crap recovery I have just flown, is fully visible in the top right of the screen.

Probably not helpful, but just to make sure that you have restarted both VA and DCS after elevating to run as admin. Also, does the PTT tab of the VP config screen correctly display the module you are using?

In an attempt to lighten the mood a little, I've attached a couple of tracks for your consideration and probable amusement. :smilewink: I saved a track of my first attempt at one of the VFR landing missions that comes with the Hornet. OK, i didn't fly the pattern, but that wasn't the point. The first track i recorded was with anti-skid on and i brought the aircraft to a complete stop, so that i could see where i ended up. I did use the airbrake and stood on both brake pedals as soon as i touched down and i pulled back on the stick at below 100knots. I then replayed the track and took control just before touchdown, turning off anti-skid and bringing the plane to a halt in the same way as above. This should ensure that the aircraft was in the same state at touchdown as the previous track and the point of touchdown appears to be just about spot on. The only thing that crossed my mind when taking control, was that i might not have got the position of the throttle levers right, so i replayed the anti-skid track again and took control just before touchdown, with the levers in the same position as the non-antiskid track, ie just above idle. It was the second antiskid track that i have attached. From the external views, although the non-antiskid rollout did appear to be more difficult to control, the two aircraft don't appear to be too far apart on the runway, when they came to a final halt, with perhaps the non-anti-skid aircraft stopping sooner. I might not have applied the controls at exactly the same time on both tracks, so please feel free to resume control yourselves or fly the whole thing, if you think you can get the timing of the inputs closer. Also, if you can provide some constructive advice on my flying, particularly around the transition to on-speed flight, i'd take that gratefully. anti skid landing.trk non-anti skid landing.trk

do we know for sure that runways of variable "slipperiness", for want of a better word, are modelled within DCS and if they aren't, could the standard friction factor be high enough so that the anti-skid system never kicks in? however, i guess that if that is the case, it would tend to make reports of poor braking performance unlikely. i just don't recall seeing anything about the attributes of runways changing as a result of the weather for example.

Try deleting the export.lua file and then restart DCS and VA. This probably needs to be done after every DCS update. Check out from around 12:00 onwards in the linked video

That's a good point. I have my WH HOTAS and MFG pedals attached to a wheelstand and use a powered USB hub to give me just one USB lead to plug in, before a flying session. I did once forget to plug the power lead into the hub and that caused a bit of odd behaviour on the controls, particularly with switch activations not being recognised. As all was well after powering the hub, i'd assume that the joystick, throttle and pedals simply pull too much power from the single USB port that i had plugged them into.

From a fairly basic test, using a Warthog HOTAS to land the F18, it would appear that if you pull the throttles back after touchdown, the Ground Idle setting is selected (thrust around 63-65%), whereas if you pull them back before touchdown, which i'm not sure is a good idea, the throttles remain at Flight Idle (around 70%) after touchdown and you need to apply a little throttle and drop it back again, to get to Ground idle. Given the apparently preferred procedure for landing, i would expect that most pilots would wait until touchdown before cutting throttle, but i was personally interested in checking this out, given that there is only one idle detente as standard on the WH, so thought i'd share.

No worries and it's good to hear that you have sorted it.

Maybe let me know which mission/campaign it was that holds the missing command(s) and i could load it and let you have a copy of the resulting string? You would then have to correctly identify the missing bit(s) of your string and copy/paste them from my version into yours. Not guaranteed to work, but it might be worth a try, as long as i have that mission of course.

it does sound like the sort of fault that a worn/dirty potentiometer would cause and, as you suggest, the Warthog doesn't use them, at least not for the main axes, so is less likely to suffer this type of issue..

Bankler's Case I landing mission, link below, should provide you with hours of fun and teach you how to land your hornet/tomcat on that bloody "moving runway thing" without causing a big bonfire. https://forums.eagle.ru/showthread.php?t=221412

that "lurch to the right", if you are not touching the stick or pedals, sounds like a dodgy roll or yaw axis. maybe load up the windows USB game controllers setup window and look at your joystick/rudder pedals properties. keep an eye on the stick's axes and make sure that it doesn't give any unintended deflections. if it does, that would probably explain your AP issue. If the deflection isn't that great, you might be able to fix it by introducing a deadzone on the associated axis, to dampen the effect of the unwanted inputs.

yup and if you are using the default axis mappings, it might be worth making sure that there aren't any odd ones in there.