SGT Coyle

Well.... There is definitely more than one way to skin the proverbial cat with TARGET SE. The one your choosing has advantages, but I'm not going into that here. So, building on what we already have. You need another Function to set an additional trimmer value. You need to add an additional function call. In the function HatSwitchUP() you need to redo the checks. When the original options were values 1 and 3 we only had to check for whether trimmer was ">" or "<" 2. That's a problem that could be solved with a check to see if the value was between two values, but I was having trouble using "&". So I used "==" equal to. exp.. change "if(trimmer>2 );" to "if (trimmer==1);" and likewise for the rest of the conditions. So try editing my example above. PM me if you still have issues

OK.... I'm not sure I understand what you want to achieve. I rewrote your .tmc code to include a function that does most of the heavy lifting. TrimTEST.tmc include "target.tmh" include "Test.tmh" //program startup int main() { if(Init(&EventHandle)) return 1; // declare the event handler, return on error SetShiftButton(&JoystickF18, S4, 0, 0, 0, 0); MapKey(&Throttle,EORIGN, SEQ( EXEC("TrimON();"), EXEC("TrimOFF();") ) ); MapKeyIO(&JoystickF18,H1U, DX1, EXEC("HatSwitchUP();")); MapKeyR(&JoystickF18,H1U, EXEC("ActKey(DX1);")); } //event handler int EventHandle(int type, alias o, int x) { DefaultMapping(&o, x); //add event handling code here } TEST.tmh int trimmer; int TrimON() { trimmer = 3; ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT+LED1)); //set LED 1 On } int TrimOFF() { trimmer = 1; ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED1)); //set LED 1 Off } //********** int HatSwitchUP() { if(trimmer > 2) ActKey(KEYON + DX1); else ActKey(KEYON + PULSE+ DX2); }

You need to provide a track file.

Glad to help.

Fixed. Tested and works. TEMPO command on TG1 will produce a PULSE of DX1 on long hold (500ms). Pull through to TG2 will produce a held command of DX2 as long as you hold TG2. TriggerSplit.tmh int Trigger1() { if(Joystick[TG2]) ActKey(PULSE + 0); else if(Joystick[TG1]) ActKey(PULSE + KEYON + DX1); } int Trigger2() { if(Joystick[TG2]) ActKey(KEYON + DX2); } Split Trigger.tmc include "target.tmh" include "TriggerSplit.tmh" //program startup int main() { if(Init(&EventHandle)) return 1; // declare the event handler, return on error MapKey(&Joystick,TG1, TEMPO( 0, EXEC("Trigger1();"), 500)); // Split Trigger Function Call TG1 MapKey(&Joystick,TG2, EXEC("Trigger2();")); // Split Trigger Function Call TG2 MapKeyR(&Joystick,TG2, EXEC("ActKey(DX2);")); // Release TG2 from held by Trigger Function } //event handler int EventHandle(int type, alias o, int x) { DefaultMapping(&o, x); //add event handling code here }

Bad cut n paste job Go here for working example.

Bump to correct 2nd Post

Yes. This still and issue 2.6.59625 Before I started with DMT off. SSS Forward for INS Mode. Use Slew TDC to get Diamond on HUD. NOW- Start with DMT off. SSS Forward for INS Mode. Use TDC to slew, NO Diamond on HUD. Turned DMT ON. SSS Aft twice for DMT TV Mode. Use TDC to slew, as screwed up as that is, there is a box in the HUD. Turn DMT OFF. SSS Forward for INS Mode. Diamond appears in HUD right away and slews ass described in OP TDC Axis INS FUBAR II.trk

Obviously I screwed up my .trk file. Please mark this appropriately and I'll resubmit when I get DCS installed. Sorry for the mix up.

Start mission as normal. Go through your process of entering coordinates. Once you think you've demonstrated the issue, QUIT mission. At the Debrief Screen choose "Save Replay" (Or something like that. I don't have DCS installed roght now to check). Name file as you like and it will be saved in "Saved Games > DCS or DCS Beta > Tracks" You can just drag the file into your post (Look for the paperclip). Also make sure your opening vanilla DCS(No MODS).

Are you using TARGET Script Editor? Or GUI?

Have Chief remove chocks when engine is off

Thank God (or Carlton2001). I was pulling whats left of my hair out trying to hack my way through Powershell and HTML.

I suggested a toggle to remove the Warning light panels a while back. Having track IR / VR is still unattainable for some. Either financially or technically. A toggle would offer the best solution for those not in a VR / Head tracking environment.

Then it shouldn't be to taxing for the developer to do it as part of the module design.

It's an ED bug, but I think it's been addressed already. It's there to compensate for the increased power at idle. If you're not on the brakes with the engine on and ducts full aft, you'll roll. I don't understand the why parking break isn't enough to hold the plane at idle.

good point

My Warthog talks to me. Tells me what layer I'm in (Up, Middle,Down). Tells me how my Mic Switch is going to work ( SRS, ViaCom Pro, DCS Easy Coms, DCS Realistic Coms) witch I can switch on the fly by use of a custom function. By use of a custom .tmh file I have 120 controller buttons and still have access to 102 keyboard keys and as many Macros as I can think of. At the flip of a switch I can make my throttle mounted mini stick go from an axis behavior to a standard 4-way hat switch. TARGET Script Editor is a handy bit of kit.

Could your mouse be off screen? Make sure to have "Cursor Confined to Game Window in VR" box checked in VR settings. I hope this helps.

I think you've come to the well once to many times. LOL No but it shouldn't be too hard to do. You could always switch the default green for white. But it my bork your game and fail MP IC.

Yes!!! No more disabling lights. This Christmas keeps getting better and better. Pilot Ike, these round is for you, Enjoy!

What? And you can do better? Nah... I think the deck hit him harder than he hit the deck.

OB 2.5.6.59625 Course Set Switch keybinds produce non-stop course adjustment on EHSD course line indicator. In game setup: Instant action mission "Ready on Ramp - Caucasus" Actions to perform: Press Course Set Switch Left (Keymapping in settings still named INS Course Set CCW) --- Observe that course indicator on lower left of EHSD and course line advances in negative (CCW) direction non-stop Press Course Set Switch Right (Keymapping in settings still named INS Course Set CW) --- Observe that course indicator on lower left of EHSD and course line advances in positive (CCW) direction non-stop Trackfile provided to illustrate the Actions to perform on the Course Switch in Keybindings control. Course Switch Key.trk

OB 2.5.6.59625 Left or Right mouse button click produces random number of degrees on EHSD course line indicator. In game setup: Instant action mission "Ready on Ramp - Caucasus" Actions to perform: Left click mouse button on Course Switch --- Observe that course indicator on lower left of EHSD advances in positive direction random multiple degrees Right click mouse button on Course Switch --- Observe that course indicator on lower left of EHSD advances in negative direction random multiple degrees Trackfile provided to illustrate the Actions to perform on the Course Switch in mouse cockpit control. Course Switch.trk

What's the status of the V/UHF Radio Control Set? I noticed there are numerous keybindings in the settings page for this, but some buttons don't seem to do anything. By that I don't see any response in game to either keyboard input or mouse clicks on some buttons. Does anyone know how/or if ADF should work? What are the two buttons in the bottom middle do? (those don't have a working animation when clicked) I have a lot of questions about this, but mostly just curious, what's the level of completeness is and where it's going?