SGT Coyle

So I tried the following code as a test. It compiles, runs, adn doesn't throw an error when I actuate button, but doesn't produce any output in the "tester". include "target.tmh" include "Rotary_Switch_Macro.ttm" int Rotary_Pos, index; //rotary modes list function & index int count=1; // init with value=1 int main() { if(Init(&EventHandle)) return 1; Rotary_Pos = SEQ(red, white, blue); //Coolie switch is used for Modes selection--------------- if (count < 3) { MapKey(&Joystick, CSU, EXEC("index=(index+1)%3;ActKey(PULSE+KEYON+Rotary_Pos,index);")); } else { MapKey(&Throttle, CSU, 0); } } int EventHandle(int type, alias o, int x) { DefaultMapping(&o, x); }

Yeah, If your not using TARGET, then you're not creating a "Virtual Controller". The "Virtual Controller",for lack of a better word, is a container for all TM devices(minus the racing bs). DCS will see the "Virtual Controller", not the pedals. If you don't modify the target.tmh, then you will have to map the pedals through the "Virtual Controller". That robs you of 3 axis. I prefer to get what I paid for. If I own 10 axis, then I want my 10 axis. I tried a filtered TARGET configuration, but it did not give me the result I wanted. DCS saw the pedals, but would not allow me to assign axis. p.s. I recently got a set of MFDs. I didn't actually want to create a keyboard map for all those buttons, so I edited out the right MFD from the target.tmh, and DCS auto assigns it to the right MFD in the A10C. Leaves me free to do some multiple key assignments on the MFD through TARGET.

I have not had the experience you describe. Unless I remove the TPR rudder pedals from the TARGET profile entirely they are seen by TARGET as a TM product and are captured by the program. They will show in PC devices as a separate device, but DCS will not see them as a controller at all and that is the issue. I've tried Exclusion and Filtering in the profile, and neither has given me the results I desire.

Can the title be changed?

Are you using the A0,A1,and A2 keybinds? Not the three pos switch binds. Because I can't figure how it doesn't change for you. Does your brightness work?

Silver_Dragon, Can you answer the question I asked? Or post a link to that sort of info? There are some great ares of the world to model, but only if the area to play was big enough. The Greenland - Iceland - United Kingdom (GIUK) line. Or the Philippine Islands. Thanks, and Merry Christmas.

How large can a map be?

Trying to write a target script to emulate a rotary switch in game. I can make the switch advance and reverse direction, but having trouble getting my head around a way to have it stop advancing at the last position. Any help appreciated. A little more explanation of what I want to do. In DCS, there are plenty of examples of rotary switches that don't have a Clockwise or Counter Clockwise keyboard equivalent. The AAP in the A10C, for example, has two rotary switches that lack this function. They have the keyboard commands for each position. That's 7 commands for two switches when a simple CW and CCW for each, would do very nicely. I play in VR ,and I have a condition that makes it difficult to turn my head and look down at certain angles, let alone to the rear and down for those pesky ones in the back. Any way. Mapping those to a hat in TARGET is a lot easier than trying to use my head to put the cursor on the switch, or crashing the plane trying find the keys on the board. With this code I want the rotary to act as it would as if I was trying to turn it by hand, and stop turning when I reach the last position. If I try to keep going beyond the last position I want the button to do nothing, until I go the other direction. There may or not be a way to edit the game files, but I loath to touch those. I'm playing OB and I just don't want the headache with updates. I did this before for the Viggen, but I can't find the code anywhere. I believe there was a bizarre gardening accident. Solution:

The only thing I've found to work, is to edit the target.tmh. find and comment out all lines with: TFRPHARudderShould only be three instances. If you have trouble pm me.

Thanx

May be off topic. How many player groups can you place in a mission? How many groups total? Is there a limit? I've played games where there was a hard number of groups (Player or ai)you could put in a mission.

I've been doing it in VR, but only for the ones forward of my shoulders. I have a bad back that limits my neck movement. That's why it's important to me that all rotaries and encoders, that are modeled in the game, have CW and CCW keyboard mapping. I can map those hard to see rotaries to my hats or whatever.

In that case, account for the fact that people have toe brakes. I have the issue with the Heatblur Viggen "Taxi and Takeoff Mission", where they're waiting for a button push to release parking brake. I don't have brakes mapped to a key so that breaks the mission. Just thought I'd throw that out there.

Hey Katmandu, Glad you got it worked out. I wasn't happy with my fix. Sorry I didn't see the earlier.

So what was the change that supposedly was so great that it bined my .dif file?

LMAO! You have to have a sense of humor. Love the mod and look forward to fixes in the future.

Hey Dragon, I really like the way you make use of the "Space Button" to advance the lesson. Seems like a great way to edit in new features and changes in procedures. Looking forward to new releases.

Acknowledgement from the company would go a long way. It's the lack of response that feeds the feeling that they don't care to hear about player issues. The longer the delay the quicker those feelings turn to resentment and ill will.

Wow! Thanks for sharing. I've didled with filters a little to achieve a radio quality, but not as good as yours. Thanks

+1

Excellent, Have a good holiday.

Can we get this moved to the ThrustMaster section?

Wouldn't that be nice. To actually hear from the developer or publisher to have some inkling that you aren't speaking into a black hole. It would be nice to have a bug tracker. At least to see that your complaint/suggestion/observation was acknowledged. Could lead to shorter forum threads. I don't disagree that VR support is still early on. It has come a long way and combined with clickable cockpit very powerful. Hope this issue gets some thoughtful consideration.

Never mind

:pilotfly:I think it's proof you're flying a brand new plane. Take if once we get out of EA, Beta, or whatever we're in.