bavella1

That´s possible, we will check this! THX for the hint!

Tooltips are always on in multiplayer, even if they are disabled in Options/Gameplay.

Hello and sorry for the long response time! Unfortunately, my problems have not yet been resolved. I noticed that the checkmark "Aircraft Carrier Comms" under AIRIO cannot be removed, it cannot be clicked, the mouse pointer simply disappears at this windowposition. In addition, I like to tell that I use the SRS integration, as a short PTT press triggern VAICOM, a long PTT press SRS. Maybe that also plays a role? It was quite a bit of work to convert VAICOM to the SRS integration and I'm a little hesitant to convert it back. - Is there actually an easy way to save the settings so that you can switch back to the current settings quickly and reliably? Many greetings, bavella

Thx for your support vtf_acher - excellent work!!! Keep it on

Wilco Thx, will report

I often have the problem that no radio menu commands are executed using VAICOM Pro. In this case, it is also not possible to open the menus using the DCS key. This seems to me to work randomly sometimes, then not again. Example: I hit the PTT and say "Crew" (darker beep) then "request rearming" (bright beep). The armament menu should now appear, but it doesn't. Similar if special radio commands are to be called up via the F10/others menu in a mission. It may well be that in one mission this doesn't work, I restart DCS and all of a sudden it works. I've also experienced that it didn't work at one point in a mission (that a fellow player then triggered the F10/others command) and a few minutes later it worked again via my VoiceAttack/VAICOM. For information I have to mention that I use the SRS integration. So short PTT = VAICOM, PTT held down = SRS. But this works without any problems and I think the VAICOM side also works partially because the beeps report the understood voice commands as recognized. - Only the DCS menus are not called up. Who knows advice? Best regards, bavella

OK, Supmua and KungFu thx for your reply! So I stop searching for failures from my settings!

So you have the same problem and it's not failure caused by my settings?

I´m having trouble with seeing double pictures for the George AI in VR at the Copilot/Gunner seat. I think it is caused by rendering the George on both Glasses and it is occuring with the sight forwards and downwards. The IHDAS looks good as it is only displayed for the right eye. At the pilot seat George is shown on the top of the IHADS wich looks good. At the CP/G it is underneeth the IHADS were it causes the split picture for me. When I raise the look as CP/G up George is looking ok too. The VR headset is an HP Reverb G2. I set the DP in the VR-Section to 63,5mm and took the same setting at the physikal slider of the G2. I guess I´m doing something wrong but I can´t find any solution.

Same question as Sharkku here! What are we supposed to do with/for these AI Sead in overcast conditions?

I also had the "listening suspended" problem and the only way to solve it was by deleting DiCE. Vaicom Pro now works without any problems. It seems to me that unfortunately you have to choose one of the two mods. A pity

It works! - Many thanks to @Svend_Dellepude and @Lange_666 for the support, I learned a lot! include "target.tmh" char MRM; char DGF; char AA; char AG; int MRM_mode_ON; int MRM_mode_OFF; int DGF_mode_ON; int DGF_mode_OFF; int AA_mode_ON; int AA_mode_OFF; int AG_mode_ON; int AG_mode_OFF; //program startup int main() { Configure(&LMFD, MODE_EXCLUDED); Configure(&RMFD, MODE_EXCLUDED); Configure(&HCougar, MODE_EXCLUDED); Configure(&T16000, MODE_EXCLUDED); Configure(&TWCSThrottle, MODE_EXCLUDED); Configure(&TFRPRudder, MODE_EXCLUDED); Configure(&T16000L, MODE_EXCLUDED); Configure(&TFRPHARudder, MODE_EXCLUDED); if(Init(&EventHandle)) return 1; // declare the event handler, return on error SetKBRate(32, 50); SetKBLayout(KB_ENG); SetShiftButton(&Joystick, S3); MRM_mode_ON = EXEC(" MRM=1; ActKey( KEYON+ PULSE+ DX21);"); MRM_mode_OFF = EXEC(" MRM=0; ActKey( KEYON+ PULSE+ DX22);"); DGF_mode_ON = EXEC(" DGF=1; ActKey( KEYON+ PULSE+ DX23);"); DGF_mode_OFF = EXEC(" DGF=0; ActKey( KEYON+ PULSE+ DX24);"); AA_mode_ON = EXEC(" AA=1; ActKey( KEYON+ PULSE+ DX25);"); AA_mode_OFF = EXEC(" AA=0; ActKey( KEYON+ PULSE+ DX26);"); AG_mode_ON = EXEC(" AG=1; ActKey( KEYON+ PULSE+ DX27);"); AG_mode_OFF = EXEC(" AG=0; ActKey( KEYON+ PULSE+ DX28);"); MapKeyIO(&Throttle, PSF, AA_mode_ON, MRM_mode_ON); MapKeyIO(&Throttle, PSB, AG_mode_ON, DGF_mode_ON); MapKey(&Throttle, PSM, EXEC(" if (MRM) ActKey( KEYON+ MRM_mode_OFF ); else if (DGF) ActKey( KEYON+ DGF_mode_OFF ); else if (AA) ActKey( KEYON+ AA_mode_OFF ); else ActKey( KEYON+ AG_mode_OFF );")); } //event handler int EventHandle(int type, alias o, int x) { DefaultMapping(&o, x); //add event handling code here }

It is really very difficult for me because I have a few but very little experience with programming languages. Maybe we should make it easier for now: I would like the Pinkey switch - Push it forward once and trigger e.g. DX25 - If it then comes back to the middle position, e.g. DX26 should be triggered - if it is pushed backwards, e.g. DX40 should be triggered - and if he !! well !! comes back to the middle position, DX41 should be triggered The middle position should trigger a different DX as a function of the previously operated forward or reverse position. I am familiar with the MapKeyR command, in the above example (without Shift) it would work. However, it no longer works if the operator can trigger shifted and non-shifted commands for the front and rearposition of this 3-way-switch, but in a stressful situation it should always be ensured that the center position always resets each of the 4 different modes. Hence my thought (not written down in syntax): (1) front / normal = flag MRM_Mode and PULSE + DX21 (2) front / shifted = flag AA_Mode and PULSE + DX22 (3) rear / normal = flag DGF_Mode and PULSE + DX23 (4) rear / shifted = flag AG_Mode and PULSE + DX24 ---> middle (a) IF flag = MRM_Mode THEN MRM_Mode = 0 and PULSE + DX25 (b) IF flag = DGF_Mode THEN DGF_Mode = 0 and PULSE + DX26 (c) IF flag = AA_Mode THEN AA_Mode = 0 and PULSE + DX27 (d) IF flag = AG_Mode THEN AG_Mode = 0 and PULSE + DX28 My thought is that the flags should control the reaction of the switch in the middle position. I don't seem to be able to send a DX button and set the flag at the same time with one switch position. It's probably not very difficult and I keep getting tangled up in my own spaghetti code ...

Should work, I think! - But doesn´t... In the picture red marked is the shifted Mode (Shift-Button =S3IN) and it should call - the DGF-Mode when Pinkey Switch Back is pressed - OR the MRM-Mode when Pinkey Switch Forward is pressed. Same for AG- or AA-Mode when S3 (Shift-Button =S3OUT) is not pressed (green). So there must be only one flag at time (DGF-Mode/MRM-Mode) OR (AG-Mode/AA-Mode) be "1". - I think... All flags are set to "0" at the beginning of the programm. I guess there is something wrong with setting the flags...

Hello! I'm trying to write a small program fragment that programs the Pinkey switch on the throttle in such a way that the A / A and A / G modes or dogfight and missile override modes for the F-16 Viper in two layers always resets correctly. I would like to save the setting / resetting in DCS via DirectX buttons. The Shift key is the Pinkey Switch S3 on the joystick. First try Primary mode (no S3): PSB = A / G mode = DX20 PSF = A / A mode = DX21 -> PSM = reset = DX22 Secondary mode (S3in): PSB = DGF mode = DX23 PSF = MRM mode = DX24 -> PSM = reset = DX25 Unfortunately, my "else" condition doesn't seem to work. It is also possible that setting the flags does not work at all. A simple solution would of course be to set up the reset in the correct mode via S3in as well. However, this harbors the source of error that the user starts e.g. the DGF mode using S3in, but then sets the Pinkey back to the middle position without S3in - which would then start the A / A or A / G mode, for example. I would love to receive a tip on how to reset the middle Pinkey button depending on when the mode is triggered! Thanks in advance! bavella include "target.tmh" //here we link this file to the file that contains function code int DGF_Mode = 0; int MRM_Mode =0 ; int AA_Mode = 0; int AG_Mode = 0; int main() { Configure(&LMFD, MODE_EXCLUDED); Configure(&RMFD, MODE_EXCLUDED); Configure(&HCougar, MODE_EXCLUDED); Configure(&T16000, MODE_EXCLUDED); Configure(&TWCSThrottle, MODE_EXCLUDED); Configure(&TFRPRudder, MODE_EXCLUDED); Configure(&T16000L, MODE_EXCLUDED); Configure(&TFRPHARudder, MODE_EXCLUDED); if(Init(&EventHandle)) return 1; // declare the event handler, return on error //script and function functions go here SetKBRate(32, 50); SetKBLayout(KB_ENG); SetShiftButton(&Joystick, S3); ////////////////// AXIS CONTROLS ////////////////////////////// MapAxis(&Joystick, JOYX, DX_X_AXIS); SetSCurve(&Joystick, JOYX, 0, 2, 0, 0, 0); //a small center deadzone for the joystick; feel free to rem out this line MapAxis(&Joystick, JOYY, DX_Y_AXIS); SetSCurve(&Joystick, JOYY, 0, 2, 0, 0, 0); //a small center deadzone for the joystick; feel free to rem out this line MapAxis(&Throttle, THR_LEFT, DX_ZROT_AXIS); SetCustomCurve(&Throttle, THR_LEFT, LIST(0,1, 65,70, 65,70, 100,100)); //start at 1% for idle cuttoff & create a deadzone between 65% and 75% for AB MapAxis(&Throttle, THR_RIGHT, DX_Z_AXIS); SetCustomCurve(&Throttle, THR_RIGHT, LIST(0,1, 65,70, 65,70, 100,100)); //start at 1% for idle cuttoff & create a deadzone between 65% and 75% for AB MapAxis(&Throttle, SCX, DX_XROT_AXIS); SetSCurve(&Throttle, SCX, 0, 10, 0, 0, -1); //Negative number at the end reduces the sensitivity of the cursor X-axis MapAxis(&Throttle, SCY, DX_YROT_AXIS); SetSCurve(&Throttle, SCY, 0, 10, 0, 0, -1); //Negative number at the end reduces the sensitivity of the cursor Y-axis MapAxis(&Throttle, THR_FC, DX_SLIDER_AXIS); SetSCurve(&Throttle, THR_FC, 0, 0, 0, 5, -1); //Reduce sensitivity in the center //////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////// THROTTLE KEY MAPPING ////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// // ----- PS -- Pinky Switch / Throttle leftside ----- MapKeyIO(&Throttle, PSB, CHAIN(EXEC("DGF_Mode = 1;"), PULSE+DX23), CHAIN(EXEC("AG_Mode = 1;"), PULSE+DX20)); MapKeyIO(&Throttle, PSF, CHAIN(EXEC("MRM_Mode = 1;"), PULSE+DX24), CHAIN(EXEC("AA_Mode = 1;"), PULSE+DX21)); if("DGF_Mode = 1;" | "MRM_Mode = 1;") { MapKey(&Throttle, PSM, CHAIN(PULSE+DX25, EXEC("DGF_Mode = 0;"), EXEC("MRM_Mode = 0;"))); } else { MapKey(&Throttle, PSM, CHAIN(PULSE+DX22, EXEC("AG_Mode = 0;"), EXEC("AA_Mode = 0;"))); } } int EventHandle(int type, alias o, int x) { DefaultMapping(&o, x); }