SGT Coyle

Line 92. You were missing double "//" in front of "r - Letter". That line needed to read like this MapKey(&Joystick, H3U, DCS_1_Macro);[b] [color=Lime]//[/color][/b]r -Letter Link where you got this script from, I'd like to what the T-Rudder is doing there.

Try it now // ========================================================== include "target.tmh" include "DCS_Default.ttm" include "DCS_1.ttm" include "DCS_2.ttm" int main() { if(Init(&EventHandle)) return 1; //****************************************************************** // Common config for Pilot and RIO //****************************************************************** // This config will be set up once and never changed. Settings are for both Pilot and RIO. //****************************************************************** // Setup some basic settings // Configure exlude list Configure(&T16000,MODE_EXCLUDED); Configure(&T16000L,MODE_EXCLUDED); Configure(&TWCSThrottle,MODE_EXCLUDED); Configure(&HCougar,MODE_EXCLUDED); Configure(&LMFD,MODE_EXCLUDED); Configure(&RMFD,MODE_EXCLUDED); Configure(&TFRPRudder,MODE_EXCLUDED); Configure(&TFRPHARudder,MODE_EXCLUDED); //Configure(&Throttle,MODE_EXCLUDED); SetKBLayout(KB_ENG); // this file designed for English keyboard. SetShiftButton(&Joystick, S3, &Throttle, 0, 0, 0); // IO Shift and UMD Setup //****************************************************************** // Map DirectX axis // JoyX, JoyY MapAxis(&Joystick, JOYX, DX_X_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); MapAxis(&Joystick, JOYY, DX_Y_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); // Throttle - Left and Right MapAxis(&Throttle, THR_RIGHT, DX_Z_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); MapAxis(&Throttle, THR_LEFT, DX_ZROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); // Slew Control MapAxis(&Throttle, SCX, DX_XROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); MapAxis(&Throttle, SCY, DX_YROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); // Throttle Friction Control MapAxis(&Throttle, THR_FC, DX_SLIDER_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); //****************************************************************** // Throttle Controls // Coolie Switch (HAT) MapKeyIO(&Throttle, CSU, 0, DCS_ZoomInSlow); MapKeyIO(&Throttle, CSD, 0, DCS_ZoomOutSlow); MapKeyIO(&Throttle, CSL, 0, DCS_LabelsAll); MapKeyIO(&Throttle, CSR, 0, DCS_ZoomNormal); printf("----------------------------------\xa"); SetUpFA18(); // Configure FA18 specific mappings. (Default to Pilot config on startup) } // end main() int SetUpFA18() { printf("Setting up config for FA18...\xa"); // Swap to F16config when shifted Left Throttle Button pressed MapKeyIO(&Throttle, LTB, EXEC("SetUpF16();"), 0); // ... MapKey(&Joystick, H4U, DCS_1_Macro); // v -letter } int SetUpF16() { printf("Setting up config for F16...\xa"); // Swap to FA18 config when shifted Left Throttle Button pressed MapKeyIO(&Throttle, LTB, EXEC("SetUpFA18();"), 0); // Place all RIO specific configs here // This can include all normal config commands like MapKey, MapAxis, etc // ... MapKey(&Joystick, H3U, DCS_2_Macro); // r -letter } //****************************************************************** int EventHandle(int type, alias o, int x) { DefaultMapping(&o, x); } //****************************************************************** What was the error TARGET threw out?

How can I kill the lights in an area/zone ? Simulate blackout / power station kill / grid transformer destruction. I like the the new lighting progress, but now I want to turn them out.

Same here

That's a great marketing slogan, but not very helpful. It doesn't at all represent what the customer is getting. Yes, it's an Alpha, but I think it was debated and demonstrated on Hoggit, how the industry practice of releasing Alpha/Beta state product is a double edged sword. Project financing requires it, but it can be some what, if not absurdly abused by developers. I am not making any accusations here. It's marketed as a study level sim and that's what customer expects. I don't presume to tell them their business, but where I sit they aren't delivering the goods. At least not in a timely manner. I believe it's a management issue. That statement is ludicrous, and is a slap in the face to people who have tried to helpful and nice. Maybe this is what you mean by an exaggerated expectation? Is it too much to expect to have Keyboard mapping for system switches and knobs. All of those systems are modeled and in some state of WIP. After two years I think a little inpatients is understandable. Tried that.:ranting:

Though this might be misconstrued as hating Razbam for the fun of it. How complete is the Harrier? About 50%.

vstolmech513, Great pics man. Thanks

For the Speed Brake I use this: //Speed Brake ************************* MapKey(&Throttle[color=#ffffff],[/color]SPDF, SPD_BRK_Switch_Fwd_RETRACT); MapKeyR(&Throttle[color=#ffffff],[/color]SPDF, SPD_BRK_Switch_OFF); MapKeyR(&Throttle[color=#ffffff],[/color]SPDB, SPD_BRK_Switch_OFF); MapKey(&Throttle[color=#ffffff],[/color]SPDB, SPD_BRK_Switch_Aft_EXTEND_Momentary); I get full control over the brake in or out.

Talking about "Works" and "Works as expected" I expect at least all the mouse clickable switches to have keyboard equivalents. I'm not trying to be a rivet counter, and I don't think I'm in the minority. There are systems that have been in a some state of progress since release and have not yet had they're keyboard switches accessible through keyboard mapping.

Frustration factory. Can be fun to fly, but progress is glacial and seems to be destined to take a back seat to a French Air Force contract.

Check this

If you want to know the truth of the matter, it's a lack of "Buyer Beware". I've recently posted, can't remember where, that I intend to ask very specific questions on the included features a module. When it is announced. I am no longer assuming compatibility or the presence of features at Alpha, Beta, or Release state. I find it more and more incredible, the lack of detail in the marketing of new releases. Looking at the Super Carrier store page, I see no mention of compatibility issues with other naval aviation assets. I don't think there's any reason to expect that a third party module would not be compatible. There was an announcement, a while back, of Razbam doing an A6 Intruder. Am I to assume it won't be compatible?

That just leaves "What's on deck for the Next Beta Update?" It's not a trap. It's healthy curiosity.

Thank you guys for all your efforts.

How can I install this via the "Saved Games" folder? And is there a version with just the "Message" functionality. I really struggel with that aswell and think this is exactly what I've been looking for. Thanks for your efforts.

Anything that's video ready/worthy? I luv this stuff.

looking forward to this

Anything on Deck for the March 19th Open Beta Update?

Ya!!

Safety off?

You didn't happen to use Windows to calibrate controls?

Are they plugged in to USB3? Open device analyzer and Ctrl + E. Something should be there. You may need to uninstall and reinstall Drivers/Software. When you reinstall unplug Thrustmaster devices first. Plug them in when directed, and restart. I had issues from not restarting and some error got built up and made everything go kurflunkered.

Rudel_chw, Thanks for the reply, but triggers aren't what I'm looking for. Its the CAS Page Record entries I'd like to edit. Witch I can do in game, but I'd like to set it up for the player in a mission. Thanks anyway

No worries

Attention to detail looks awesome.