SGT Coyle

I've been away from this Module for some time now and I can't believe the progress that's been made. Good job! Having to retrain my brain for new operability of some systems, not to mention redoing keymap. Minor tweaks to the manual aside, Was happy to see those "No Photo Available" place holders gone. Thanks, and can't wait for Tom Cat

+1

"Weapon Interval Dial" has no CW, CCW key binding

Give the TARGET Script Editor a try, and skim through the manual. It doesn't make any sense at the start but it will become clear enough to put together a decent script. What A/C are you flying?

Release!

Would love it, if "Weapon Interval Dial" could have CW and CCW keyboard bindings. As of this post no keyboard bindings at all.

After making changes to my control settings and saving to my user profile, I clicked OK at lower right corner of page and got black screen. This happen to me twice now. Once while in VR (Oculus Rift), After clicking OK was sen to main VR menue, but no menu just A/C hangar with plane. Second while Non-VR, After clicking OK was sen to black screen. In both cases I had no "Esc" control to close DCS. Logs attached Moderator please move if more appropriate somewhere else Thanks dcslog.txt

So where in the manual does it say that? I could only find it as "Alternate mic button" with weight off wheels. I have control of the radio again with the setup I described above. I will try to see if the "Nose Wheel Steering Button" mapped as "s", also works, but I've never even thought to try it as I already have a "UHF Radio Microphone Button" mapped and it's worked fine. As always, all good stuff.

I've always used "R_Alt + " and "" for A/C with one radio and never had a problem. "Communications" is "", default mapping. I map the game to that effect so I don't have to change anything if I need to use simple comms for whatever reason. And that mapping works now. The issue is why is there communications on the ground but not in the air. If mapping was the issue, then by using "", default comms menu, I shouldn't be able to talk to the tower at all with "Easy Comms" unchecked. I agree there must be a mapping component to this issue, but the firewall between Easy and Realistic comms seems to have an issue that may need to be explored. It seems there is a bug here, but how best to articulate it. Or for that matter, replicate it. I did a clean and repair and now comms work as they always have and I have the same mapping I've always had: Easy Comms "" UHF Radio Switch "R_ALT + ", "" If I can get this to happen again I'll put up a track and ask that this post be moved to the appropriate forum.

Solved, or as close to it as I can get. So I did a repair and things remained the same. AFU. So I cleaned and then did the repair of DCS and things went back to normal. I checked 2 or 3 times to make sure I wasn't in East Comms. I wasn't. But even if I were, why no comms in the air. Again very weird.

Yeah, I never use simple radio, unless it's the Modules EA, or mission has issues. It's weird. I've flown this mission a lot and never had issue with radio.

I'll check, but I never had this issue before.

No, simple comms. I get menu, response from Ground Crew, F10 Menu, response to Start up, Taxi, and Take Off. Everything works on the ground. I'm thinking hick-up in Comms .lua. Or whatever controls default comms. Unless the mission is queering it some how. Not mentioned before, but mission triggers are firing. I get the Instructor comms as normal. But when it comes time to check-in to range control I have no comms menu at all. Like I said, weird. I'll do a repair and see if that helps tonight.

Weird behavior. While flying the F5 in the 3rd mission of the Aggressors BFM Campaign on NTTR map, my radio stopped working once I was airborne. It worked fine on the ground. I put this here because I'm not sure where to put it and don't want to make multiple posts. It seems to me to be a problem with the Communications System. May be hanging on the "Permission to Takeoff" message. I did get clearance, but afterward I couldn't get a comms menu while in the air. There's nothing wrong with my radio button binding. Again, it works on the ground. Moderators please move this to any forum you think would be appropriate. I will continue to test on other A/C and missions.

Makes me want to fly the M good job

Hey Badger, First thing I would do is uninstall your device completely. Drivers, software, and restart. Then follow the install instructions religiously. Once you've done that try to map in DCS again. If you still have issues, try reinstalling firmware.

Wow! All good stuff. About the ED messages. When I had my problem I got no messages saying anything had been disconnected. I know what you mean. If you loose a device, target will shut down, but in my case anyway it didn't. The joy stick, the device I had issue with, was still recognized by windows, hence still connected, target still running, DCS still thinks it's there, but of course the buttons don't work. So with the current controls debacle right now I haven't been able to go on any extended DCS flight to see if in fact it is fixed. So anyway good luck to the OP.

I was having the same sort of issue. My stick was dying mid stream. I would start the script, then DCS, and get into mission and sometimes just lose button functions. Sometimes axis as well but definitely button functions. My problem was with the stick. Stick showed up in "Devices and Printer" but did not have any function when testing settings. USB drivers I think were the culprit in this case. My board is old and no new drivers available. Put in a new PCIE USB Board. So update or uninstall/reinstall drivers. Also, as long as you have Stick and Throttle present in "Devices and Printers" try to reinstall Firmware. That seemed to work for me. Checking USB events showed I had an error "Device no migrated" I think it is related to Windows update trying to replace old driver with new generic and it don't match. Go figure. I hope this helps Good Luck

So far so good. Seems I have a very old USB drivers that are no longer supported on my MB ASUS Crossfire V formula Z driver by ASmedia. So added a PCIE USB card and reinstalled my Throttle and Stick Firmware. Seems to work fine. Knock on wood.

Copy that

Just a thought to add a little realism to DCS. The disengage message. Ask your wife to put a "Have a nice Day" at the end. I agree with the above. She did a great job.

Miss read the original post. Thought he said rotary switches. But yes, CW and CCW keyboard support for encoders such as: Course Knob Radio Volume Knobs (COM 1 and 2) MPCD Power/Brightness Knob HUD Power/Brightness Knob Video Brightness and Contrast Knobs UFC Display Power/Brightness Knob Standby Attitude Indicator Knob Standby Altimeter Knob RWR Volume Knob Is very important to me, and I believe all the community would be better for it. Just look at some of the ED planes. They're awesome.

I would pay money for this if you sold in in the ED store. Meaning if ED made it an official Mod. It looks and sounds awesome. Following this with great interest.

17 pages and going to 18 I'm sure. In the grand scheme of things, when ED dose whatever it is trying to do. Will I still be able to use TARGET Script Editor to map my TM Warthog Throttle and Stick? Are there going to changes to the way we use the "Combined Virtual Controller"? As of the "announcement" I haven't even bothered to look at or start DCS. I'll wait till the hotfix and see if everything is OK.

Are you sure about the East coordinate? E 055 22min 88sec I sorry but I cant log in now check it myself.