SGT Coyle

Got It!!! After almost four months of trial and error, furious googling, and feelings of disgust mixed with admiration of what some of you people do. I got it. .tmc include "target.tmh" include "TD_Functions.tmh" int counter = 1; int listmode, index; //program startup int main() { if(Init(&EventHandle)) return 1; // declare the event handler, return on error listmode = SEQ('a','b','c','d'); //add initialization code here MapKey(&Joystick, H1R, EXEC("ClockWise();")); MapKey(&Joystick, H1L, EXEC("CounterClockWise();")); } //event handler int EventHandle(int type, alias o, int x) { DefaultMapping(&o, x); //add event handling code here }.tmh //*************************************************** // ClockWise and CounterClockWise functions int ClockWise() { if (counter<4) { index = (index + 1)%4; counter = (counter + 1); ActKey(PULSE+KEYON+X(listmode,index)); printf("CW \xa"); } else if (counter >= 4) { ActKey(PULSE+KEYON+0); printf("CW end \xa"); } } int CounterClockWise() { if (counter>1) { index = (index + 3)%4; counter = (counter - 1); ActKey(PULSE+KEYON+X(listmode,index)); printf("CCW \xa"); } else if (counter <= 1) { ActKey(PULSE+KEYON+0); printf("CCW end \xa"); } } //**************************************************** Thanks, Thermal. Your solution worked fine, but I knew there was another way. Appreciate you help.

Can we get a Clockwise and Counter Clockwise keyboard shortcut for the "Master Test Panel" Selector switch as well as a push pull toggle please. OP, thanks for starting this thread

So I'm trying to determine my needs, as far as a new build this year. Preferably the 1stQ. Gotta be able to suport 9 usb 3.0 devices (Controllers, mouse, keyboard, and Oculs), and at least 2 SSDs, and an M.2 device. Primarily a DCS/VR dedicated machine. How do see your choice of hardware fairing with these requirements?

What devices are you using that aren't mappable? I have a DIY device that DCS picks up just dandy.

As well as CW and CCW key commands for all encoders and rotary switches that are modeled in the module.

I always look forward to the "News Letter". It usually informs of current projects and future plans. It's a marketing tool to be sure, but I do enjoy seeing it in my inbox.

Would be nice to have this feature.

Are you using Mods? NOT, Modules. Mods, like sound, skins, objects, ect.... You definitely shouldn't have to deactivate Modules.

I'm looking at switching out my ssd, that is exclusively for DCS, with one that is bigger and faster, but I have zero confidence in the system ED has concocted. This post, for example, only reinforces my trepidation about moving forward with hardware upgrades. Let alone migrating to a more capable system altogether.

Sorry, Should have done this earlier. Be advised that I'm only running the openBeta. The instructions I give should be interpreted as good for Release as well. Make the appropriate inferences. See OP for resolution.

After removing all my Mods and then doing a repair, everything runs fine. Weird though. Originally I hadn't done anything I had done before.

Excelent, that's just what I'm looking for. Thanks

This would be amazing for everyone that needs it. Not everyone in the community has all their fingers and toes. Let alone the dexterity to hunt and peck in the dark.

Can I make a KB airframe specific in the same mission? Say, my player spawns in a Harrier, can I have a KB built for that airframe, that he/she uses, or if the player spawns in a Hornet, they see a differen't KB.

Hey, Great minds think alike. I was just revisiting an SP mission I wanted to do the same thing with, to a certain degree. Hope you will continue to share, as I hope to have something to contribute. Don't hold breath, as I have no idea what I'm doing. Thanks,

I playing open beta 2.5.4 Kutasi ATC 134.000 VHF AM. No Easy Comms Have never gotten this to work. Can only talk to Kutasi ATC on 263.000 UFH. Am I crazy? Love the campaign so far. Only on mission 3.

Beta 2.5.4.25729 Purchased MIG-15bis. When I click install my game crashes. Never had this issue before. Logs attached: Hope it's nothing big. Thanks, ****Resolution: Remove all Mods. Made sure all mods were removed. Use what ever mod manager you use, if any, to disable/remove mods. Also if you are using the DSC.openbeata/Mods/ or DSC.openbeata/Tech/ folders in "Saved Games" dir to aply mods. Move them out as well. Do a repair on your DCS install. Start DCS as usual and try to install new mod. The above worked for me. I don't propose to know what was wrong with my install before, but it works now. Good luck! dcs.zip

With the nosewheel steering button pressed and held, nosewheel steering is controlled by movement of the rudder pedals. When released, the nosewheel will be held in orientation it was pointing when you released it. To go straight down the runway, you need to hold the button in until you are pointing and traveling down the runway forward a bit, to ensure the nosewheel is inline with the fuselage. I hope that helps. Good luck.

Love to hear it. C you in the new year.

Thanks, I'll play with it tonight.

So "MAC"is not "LOMAC-Flaming Cliffs"? Or is it? I never saw the announcement. Just second hand references.

+1 on this.

DCS 2.5.4.25729 Beta In VR. Left, Right, Scroll UP, and Scroll Down, assigned to Controller in UI_Layer, does not work in the Control Setting Page of Options. Works in all other pages as far as I can tell. This is new behavior. UI_Layer functionality, and my controller were working quite nicely on all pages. If a Moderator can move this to a more appropriate section please do Thanks.

Mission 2 follow me jeep? 2 out of 5 times failed to lead. Had to go around.

+1 that. Contrast, brightness, and back lighting. Its a killer in VR.