Greyman

Forgive me for asking, but is it the ailerons that are moving and not the speed brakes, as they are the same control surfaces on the A10? Check that you have the toe brakes on your pedals assigned to their respective wheel brakes and not the speed brakes.

when DCS finds a new module it will often, if not always, assign multiple controller axes to the same command, so for example, your rudder, pitch, yaw and throttle controls will have the joystick, the throttle and the rudder pedals all assigned to them. Just go into the controller setup / axis commands and clear all of the assignments that you don't need, so that you just have, for example, only the pedals controlling the rudder and only the stick controlling the roll and pitch. The aircraft, whatever it is, should then become infinitely more easy to control :)

With my tendency to want to buy every module, including the choppers, I am really spoilt for choice, but the A10C, my first payware module, is the one that I keep coming back to. I probably shouldn't say this, but with this being my only real niggle, it would probably save me a lot of money, on future releases, if it were to be sorted. I like your suggested solution and I hope that ED do too.

i've had a play with those keyboard commands that change the pilot's viewpoint in the cockpit and all they appear to do is to reverse the change that ED applied, a few patches ago, to put the pilot in a more realistic position. Although that position does perhaps put your helmeted head a little too far back and too close to the headrest, to get to a position where you can see the whole of the HUD puts you way too far forward. So much so that it looks like you could get another pilot in there. I was hoping that changing the FOV or the two angle settings in the snapviews file might be of use, but editing those does not appear to make any difference at all to the scale of the HUD, at least not in VR. I'll stick to the default view i think. Thanks for the offer though @eaglecash867

That would be useful and appreciated

Here's a description of what i can see when i load the "Take Off and Basic Handling" training mission, recentre my headset and sit upright, which puts my head about where i would expect it to be, relative to the headrest. It also puts the controls to the extreme left and right of the cockpit within easy reach. The heading tape of the HUD sits right at the bottom of the display, with the -15 degree line and "STPT" only just visible in the bottom left, which is probably where it should be. At the top, however, all i can see is the 5 degree nose down pitch line. To see the zero degree pitch line, i need to lean forward quite a way and raise my eyes to see it, along with the flight vector. If you can see both the heading tape at the bottom of the HUD and at least the flight vector at the top, then i'd really appreciate it if you would share your settings. I have a Rift too and have set the standard VR settings, although i have tinkered a little with the forced IPD setting, that doesn't appear to make any difference to the amount of the HUD information that i can see.

and you can see the top of the HUD and the bottom of the HUD from the same position, without craning your neck? edit: and when you look round at your seat's headrest, it doesn't look about 3 feet away? Never mind, having read through this apparently identical thread, http://forums.eagle.ru:8080/showthread.php?t=190225, it would appear that it went the same way as this one appears to be going, with some being happy with the default pilot position and HUD scaling and others not so much so. In the absence of a view from a RL A10 pilot, i guess we will never know which camp is correct. Ergonomically however, something does seem wrong in expecting the pilot to either sit away from the back of his/her seat or to have to move his/her head significantly to gather all of the HUD information that would feed into split second decision making.

I can agree with your point about the headset not allowing a realistic flexibility of eye movement, but the pilots would need to have elbows that bend the wrong way and not have a problem with sitting on the joystick if that were a realistic flying position :)

The position for being able to see the full HUD puts the pilot too far forward to be realistic, hence ED's update to move it back. What they apparently didn't do when doing that was to rescale the HUD. If you move yourself forward again, in VR, as before the updated position, you have to turn your head a long way round to access the controls, for things like the ILS and intercom

Table-mount wasnt a good idea with my glass-topped desk, but my wheelstand pro is awesome.

Before I got my second sensor, looking over my shoulder, to check my six for example, could cause the odd stutter, but it has never let me down since.

In VR, the HUD has been off since they pushed the default pilot viewpoint back from the original "sat on top of the joystick position". When sat in that new position, the pilot cannot see the whole height of the HUD, without adjusting the seating position or craning their neck. This has been reported elsewhere on the forum, in a number of threads, but I guess that it has yet to reach the top of the list of priorities, if it ever will.

keep an eye, or two, open for the next generation of VR headsets. the current offerings are pretty good, but with the next gen not too far off, you might want to wait. If you have a good HOTAS, and the Warthog does me just fine, as with RL pilots, it will reduce if not remove the need to take your hands off it, to press keys etc, so tbe immersion will be almost total.

If you followed the instructions on page 33 of the manual, I've linked it a few posts up btw, then I have no other ideas. I'm sure that Hollywood will be on soon though. He will be able to help

@By-jokese, as your DCS installation isn't in the standard location, ie under Program Files(x86), have you done a manual install of the lua files? If not, give that a try and it might sort your problem.

For crew, I just open the canopy and say "request repair", "request rearm", "request refuel" etc , thus bypassing the radio. It works fine, as I guess the AI crew are always within earshot

No worries. The manual on the website should always be up to date, even if the one in the install hasn't been updated. Did you get the DCS module displaying on the PTT screen yet?

https://www.vaicompro.com/uploads/7/5/4/3/75436709/vaicom_pro_user_manual.pdf - Page 25 As for the second part of your question, if you read back on this thread for a couple of weeks, there have been a few posts about it and a solution.

I'd take Nineline's post as "official info". From elsewhere it looks like you need to submit a support ticket, to gift a mod to another user.

Or wait for the next day. I think it only asks you if you want to update once per day.

go with what it displays at the bottom of the PTT screen

You don't have Immortal, or any other switch that might block failures, in your gameplay options do you?

it was an attempt at humour, referring to Hollywood's lack of Spanish, that apparently failed, I won't do it again. honest :)

https://www.youtube.com/watch?v=Su3vDNYCgAU - Sergei will teach you :)