Greyman

i'm certain it was there earlier, but it does look like something has gone wrong somewhere since. I'm sure it will be back soon.

It's all relative i know, but the Rift is at a pretty friendly price brand new already. As for the F14, the OP of this thread, https://forums.eagle.ru/showthread.php?t=219346, might be of interest.

If you don't mind me asking, how long is your extension?

snap!!. oh wait :)

Having visited that realm a few times, having made a cock-up of F18 carrier landings, it doesn't currently look deep enough, so i'd expect the maps to have to be changed a little before submarine warfare could become a thing. it might be interesting though

it depends how long it is going to take you to put all of that sparkling new kit together, as of October 7th, the F-14 might also be an option :)

Maybe you could read the post immediately above yours, for a clue?

Maybe check that any dead zones/curves that you might have had on your control axes have not been somehow reverted to default.

Thanks for correcting my incorrect phraseology, but as the point of my post was to try to help someone with their unexplained apparent yaw, maybe you could suggest an alternative explanation and provide some help for someone that was asking for it?

My point was that the ai plane would correct for a crosswind to remain on the course that the mission designer had set. To also retain that heading, the player pilot would also need to correct and if they didn't an unwanted heading relative to the tanker would result. It was just a suggestion that might have explained the issue. If it doesn't then fine, but maybe you can suggest an alternative?

...and stick VAICOM PRO into Voice Attack too and you have full voice control of all of the comms as well. In VR especially that is a very useful immersion enhancing addon.

it's the two that are watching that concern me ;)

and the AI pilot would presumably be applying some opposite rudder to keep on course

have you got a cross wind maybe?

not unless you want to spend about 5 minutes editing the mission file, which is where the problem appears to be and not in the code. It's a very simple change and appears to work perfectly thereafter Edit: To save you doing the edit, i've attached a fixed version, where the S3 should stay at 15,000ft and i've also stuck an ICLS on the carrier, at channel 1, so that you can combine the refueling session with a bit of ICLS carrier landing practice. I'm sure that ED will fix it, but in the meantime, this should suffice. Amended Caucasus FA-18C Aerial Refueling.miz

As you are in the UK, you should actually get a 2 year warranty, at least until we leave the European Community and then, who knows?

So is there no sign of the "Kamikaze" S3 tanker AI pilots being fixed in the Instant Access A2A refueling missions, in PG and Caucusus maps? Whatever has been changed in one of the recent patches has apparently caused an issue with these missions. Edit: never mind. it looks like someone goofed on the orbit altitude for the S3 in the .miz file, for the Caucusus mission at least. On waypoint 1 or 2, there is an orbit command with 8000ft as its parameter, when it looked like it should be 15,000ft, to match the starting altitude. The dive into the ocean rather than it sticking at 8,000ft is probably just the AI getting very confused. either way, a quick edit, to change the altitude to 15,000, followed by a quick test flight and it appears to sort the issue.

Which is why you press the button I spoke of, as that combines all of those commands into one. When you edit that command, as per the instructions in the manual, delete the current contents of the 'when I say' field, by first selecting the field, press Ctrl+a to select all of the content, and then press delete. Then paste the contents of the clipboard, that were put there by the FINISH command. Please note however, that when you have pasted the commands into that field, due to a bug in VA, you might not be able to see the. They are there though, so just think of it as magic. :)

Take a look at post #893 and there is a post, from Hollywood, later in the thread, that contains a screenshot of the VA profile edit screen, showing exactly where the combine commands button is.

I looked more closely at the throttle controller in the A10c cockpit yesterday and it looks like TM might have either misunderstood how the slew controller moves or, perhaps more likely, have decided that it would be easier to implement with a very small "nipple joystick" inside the concave bit of the control, rather than have that concave bit just being the head of a larger joystick. If you think about it, a pilot, probably with gloves on, would struggle to adjust the smaller of the two and it would make more sense if that concave shape were just there to provide better purchase for the pilot's middle finger. In short, this mod is probably more realistic than the TM implementation. Any RL A10 Pilots out there to confirm if it is the whole of the slew control that moves?

I wonder if it is random or whether it is something about the carrier moving, for example when it moves a certain distance or into another grid square?

Yup, amend the 'A10C Sim' profile to be like the second screenshot above and you should be good.

It is starting to look like it might be a hardware/driver issue, but as @eaglecash867 suggests, a screenshot(s) might help to exhaust the DCS settings possibilities, before trying to diagnose that.

and you can map it to a HOTAS button too. look for the info bar commands in the controller setup screen.

Two more suggestions. Unlikely as it may seem, they are still worth excluding as possibilities 1. there are two sets of controls for the A10c, one for Sim and one for Game. It is worth checking that the switch in the gameplay options is set to use the profile that you are setting up. 2. check the aircraft bank left and aircraft bank right commands, to make sure that they don't have anything in them apart from keyboard commands. These are presumably provided for peeps that don't have a joystick/HOTAS and want to fly using the keyboard, but it will let you map the commands to buttons, as well, so worth checking that your rudder toe brake controls haven't somehow got in there. this would rely on there being a switch on each of your toe brakes, as well as an axis, so possibly not that likely. My rudder pedals don't have any switches on the toe brakes, but i suppose that it is possible that yours do. One suggestion is that you select the 'All' option in the drop down box, and select the first cell in the column for your rudder pedals. Then clear the whole column with 'clear category'. your rudder pedals should only have 3 assignments, for yaw and each of the left and right wheel brakes, so it won't take long to set those up again and at least you will know that your pedals haven't been assigned to anything else. Also do that for the axis commands section, before remapping.