_Hoss

It would all be modern, like everything else they do. I don't want a modern Korean Peninsula, or Vietnam map. 50s, 60s, 70s. Make me a F8F Bearcat so I can be a French fighter pilot at Dien Bien Phu. I'd get more use out of the Bearcat than I would the i-16 on the Caucasus map.

I've got the same problem, but an added one as well, my comms only works with the Ground Crew, and I can't get any towers to respond to me no matter what I do. And I'm no noob to LOCKON/DCS. I can't get VOIP in-game comms to work either, Everything works, the guys hear my mic clicks, and see the colors change, but no audio. TS works, discord works, but no joy on DCS VOIP comms or cockpit game radios.

I agree, give it a tail hook and make it an FJ-3.

Well, there should be an Off/STBY/REC/RPT...or.... RX/TX? If so, turn it to REC/RX after take off, at Fence In, put it in RPT/TX once out of the A.O. back to REC.

That second part looks like the Mini-Boss' space. And we only had white and red lights on the three bird farms I was on.

I used to have that problem with MP years ago. Now it's just keyboard emulation. Both issues always after an update. The old remedy was always doing a repair, but....... you needed to turn off your Firewall, un-install mods, reboot, do an update, repair, clean, reboot, then test your connection to MP, if it works, turn Firewall back on, reboot. On occasion I had to do it two or three times, but it always worked. I have found it fixed my keyboard/HOTAS problems, here of late. Or just tell your Firewall/AV to ignore DCS.

It didn't have Sea Legs.......

Slughead, you need to change your handle to, Moriarty.......

I prefer the AVA now that I've used it for a while. I have a center mounted Hornet stick, on a 10cm curved extension. But......... I do hope they come out with adjustable clutch dampers at some point.

I think I'm still going to paint mine green. I wish now I had gotten the encoder version.

Love mine

I'm loving mine so far.

I would rather they built NAS Fallon....Strike Fighter U, it's in Nedava...... China Lake isn't, it's just a test range. Fallon is where the Navy goes to play.

The button has a secondary lock function, I use RSMapper's sequence mode. It's actually a "Chain" event. I press my speed brake button forward (TMWH) and the first action is press WEP button, 0 ms delay, 500 ms duration. 2nd action is lock the button, 500 ms delay, 500ms duration. When I pull the SPD BRK back it gives a unlock command. But none of that works right now because DCS/ED have broken keyboard emulation for me yet again. It's the main reason I've stopped buying aircraft modules from them.

TARGET, RSMapper, and Joy2key do not work...... LOL, so restarting the computer isn't going work in this case. Something they did in the big update broke all my software's ability to talk to the game. If I knew where that line of code is I could fix it. I'm starting to think DCS and ED, stands for "Diligently Crashing Systems" with "Egregious Data". Or... BOHICA. When ED breaks it, it becomes a large waste of disc space. Because I generally won't play it until they fix the emulation problem. DCS/ED's quality processes are extremely flawed, which constantly breaks the form, fit, and function of their product as seen by the customer. Any way you spell it, it's W.A.S.T.E....... of my money and time. Please fix it. JMTCW

Well, that's awesome. I would love to know, what it is, you use to get keystrokes from your HOTAS to the game.

...........

That's because they constantly break the keyboard emulation from our HOTAS software to the game. I've programmed "spacebar" to my TM AVA w/Hornet stick, using TARGET w/hold press........ and nothing.... no guns. I've done the same with RSMapper and Joy2key..... needless to say.... no joy. BUT... I can reach up and push space bar on the key board, and VOILA!! guns fire. This has to be something they break everytime they mess with settings with new modules. I imagine there is a line of code somewhere in the Input folder that says use keyboard = 1 on, 0 = Off. If only they would tell us where that line is so we can change that 0 to 1. The processes they use to ensure module integrity is extremely flawed, and they could care less it seems. The update broke it, the hotfix ignored it, and its still broke. And they want me to buy more modules that are unfinished, flawed, and useless without keyboard control through a HOTAS. ED.... (Extremly Defective) JMTCW

FIXED IT.......... thanks MAXsenna...... I was looking at the wrong file... device manager HID devices......

Like I've said, this happens more often than not. No matter which program I use, TARGET, RSMapper, Joy2key, no keyboard keystroke from the DCS settings gui is seen in game. I will use TARGET Event Tester to see if the keystroke is being sent out to the system, and everything registers on the tester.. All my programing works as advertised. I've spent hours double checking my set up. And it is not a problem of my making. It's just shoddy process management on ED'S part. I would compare them to the major US aircraft manufacturer I used to work for. Money comes first, maybe it'll get fixed in the next batch, to hell with quality assurance, doing it right the first time, for the last time. JMTCW.......

Nothing should of been deleted. Only the F-86, Mig, and F-5 should be the difference. But I did see J-11 in the list. I have the F-86 and Mig-15 modules, I wanted the F-5....

I had waited to see if this hotfix would fix the problem but it hasn't. This is a common occurrence with updates, but all of the profiles for Warbirds in my hanger will not respond to my HOTAS. Keyboard emulation commands in all of the software I've got no longer work in game. TARGET, RSMapper, Joy2key.... but everything registers on TARGETS Event Tester no matter which software used. so I lose a lot of functionality in just one button press, or swtch. Which means lots of time wasted going and finding ways to remap things with dx commands, and not blowing things up in a Jug. Hopefully when we go to a public release we won't see these types of problems anymore....... Hopefully we don't have to wait to long for a fix.

LOL, crap........... this last update killed a lot of my warbird profiles. I'm really getting fed up with their Open Beta and constant broken updates. I'll give that a look to see if I can get rid of the virtual device. Thanks...

Where is the virtual stick, I deleted it from the device manager... still shows up in DCS and IL2 device.txt.