Seapiglet

Had seemingly the exact same issue in the Apache. Someone flying with George in the same session had no problems.

P137 of the manual describes the FFD display option, which is marked as N/I. Not clear whether this will ever be implemented, but if would make the digital map much more useful. It wouldn't even need to show all of the features the real aircraft is capable of - even just water, roads, urban areas, forests and ideally political boundaries would be awesome. I guess it might be quite a lot of work to construct this for each map, but actually I'd be delighted if we could have the F10 map on the TSD somehow, even if it isn't realistic. Using the charts are fine, but if you zoom in much it disappears, and while you can set the map scale independently of the zoom scale it is immediately lost as soon as you change the zoom so is a faff.

I am very glad EA wasn’t delayed further to finish the hold modes, but am also very much looking forward to their implementation. They are far from essential, but they will still be helpful.

Yes, hit-or-miss seems accurate. Not sure I have isolated the exact set of circumstances yet, if there is even one consistent pattern. The only thing I know for sure is that every time Ibhave actually tried to do it for real in the front seat (rather than just testing) it has not worked. TSD updates for PLT but not the IHADDS. Will see if the next patch somehow helps! Thanks.

Hi, Tracks here from PLT and CPG: https://1drv.ms/u/s!AvTMMMW6RxzwjVBX41oObsKhycGA?e=QGVY9G It seemed to be slightly different from what I reported - what we found was that if the CPG set points created by either player as Direct To, the symbology would only update on the CPG's IHADDS, though the TSD line would update to the correct waypoint. However, if the point was part of a route, it would work as expected regardless of whether the PLT or CPG generated the point to begin with. Didn't get a chance over lunchtime to try all the possible permutations, but hopefully this shows something funny going on. Let me know if the link doesn't work - I'm new to bug reporting! Cheers, SP

If I set Acquisition Source to Pilot HMD when I am the CPG in multiplayer I cannot see the Cued LOS on my IHADDS, or the dot in the Field of Regard. I can slave the TADS to it, though.

As CPG in MP, if I created a point and set it to Direct To, I get the correct symbology on IHADDS but The pilot does not. If I pick a point the pilot creates as Direct To it seems to work fine. If I connect a point I made as CPG to a route containing points the pilot made, that also seems to work ok.

Agree. To use Voiceattack etc you would need to figure out how to work it with the ‘continuous’ commands like sliding L/R in a hover, but even without that would be good.

On your second point re blocking voice, I don't think it blocks it because in the manual it shows one of the channels being selected for voice and IDM. I don't know for sure though.

I think on MP in the Gazelle the left-seat slew controls are bound to the cyclic. Weird and annoying, but just about usable. More of an issue is that the tv picture can get out of synch, and it is the right-seater’s view that counts, so the pilot needs to verify aim before firing. Most of it works in MC, but only if you follow a pretty specific sequence to get into the aircraft. More info on the PC Discord.

+1 However, if you want a solution that will tide you over until it happens: 1 - Find C:\DCS World OpenBeta\Mods\aircraft\A-10C_2\Input\A-10C_2\joystick\default.lua (or equivalent location for your installation). Make a backup copy just in case. 2 - Open it, find the line: axisCommands = { 3 - Add the following just below it: -- extra axes {action = 3011, cockpit_device_id = 54, name = _('UHF Radio Volume Axis'), category = _('Extra - Radio Volumes')}, {action = 3005, cockpit_device_id = 55, name = _('VHF AM Radio Volume Axis'), category = _('Extra - Radio Volumes')}, {action = 3005, cockpit_device_id = 56, name = _('VHF FM Radio Volume Axis'), category = _('Extra - Radio Volumes')}, {action = 3005, cockpit_device_id = 49, name = _('Flood Lights'), category = _('Extra - Lighting')}, {action = 3001, cockpit_device_id = 49, name = _('Engine Inst Lights'), category = _('Extra - Lighting')}, {action = 3002, cockpit_device_id = 49, name = _('Flight Inst Lights'), category = _('Extra - Lighting')}, {action = 3003, cockpit_device_id = 49, name = _('Aux Inst Lights'), category = _('Extra - Lighting')}, {action = 3009, cockpit_device_id = 49, name = _('Formation Lights'), category = _('Extra - Lighting')}, {action = 3006, cockpit_device_id = 49, name = _('Console Lights'), category = _('Extra - Lighting')}, 4 - Save it and try it out. There should now be bind-able axes for radio volumes and the lights. It is not perfect, though, as you'll need to mess about with custom curves to get something that behaves close to properly, but it is still a lot better than pressing and holding buttons in my opinion! 5 - The file may get replaced when updates happen, so either keep a copy to switch in manually, or use OVGME or something to turn it into a mod. Now... if they'd get the HSI course/heading knobs to be bind-able axes I'd really be delighted. Tried the above approach with those and couldn't make it behave the way you'd expect.

As above. Tried editing the lua file and can get a bindable axis but it behaves very strangely and is not usable.

I think it matters whether you’re in VR or not. I suspect a lot of the tips you can read or watch for one apply much less to the other. I also learned A10 before Hornet, and found the Hornet much harder. I wouldn’t call myself an expert in either, but one thing I found made it easier was just not worrying about the ‘tiny inputs’ advice on the throttle. Not saying I’d ram the thing back and forth, but I had a tendency to undershoot with throttle inputs and drift back too far. I then started to intentionally overshoot then bring it back to a lesser deflection a second later. I found this meant I could think a little less about the throttle and gave me more bandwidth for the stick inputs. I have noticed my throttle hand moving less recently, so maybe it was just something I needed while learning. Might be worth a try since you have tried everything else!

I'd also really recommend the qualification campaigns by Maple Flag. They are not training missions in that they mostly don't tell you how to do stuff, but they do present a structured way to learn the aircraft and build up your skills, and they force you to learn how to do things right rather than just going straight out to blow everything up. I took perverse pleasure in the fact that you don't even carry a weapons until part way into the second campaign, but instead have to make sure you can navigate efficiently at night and then land in a cross-wind, or carry out AAR reliably (that one took me a good few goes!). I also like the fact that the first examiner is a real hard-ass - forget to test the pitot heater during start up? "You have performed poorly - do it again!". One or two missions had the odd bug, and the progression of difficulty seems a bit off in places, but overall these campaigns added a great deal to my experience of learning the A10C (to the extent that I have). I just wish other aircraft had something similar.