SGT Coyle

I agree with alot of what you say here, but this where I disagree. I won't except lower quality than the A10C Warthog for any study level sim. I'm not asking for more, just the same level I've come to expect from DCS. This thing is still an Alpha an it costs $70.00 + tax. with no refunds. It's supposed to be Feature Complete, but that isn't really the case. Where did Lazer Rockets come from. That was never on the list. And what happened to non-lazer rockets? Ahhh....

To be clear, I'm not saying or claiming that there hasn't been progress, but problems with the TDC axis control, via "Controller Axis" and as of late "Keyboard Commands" have been known for some time and persist as of this posting.

I keep going back after updates to see if it's any better. It's not.

Too many Show stopping bugs for me. I've been flying DCS products since before the A10C Warthog and I own/fly all the A/C and Terrain Modules. The Harrier is by far my favorite to fly, but I haven't for months. As I said, too many show stopping bugs as of this post.

So 82H is for "High Drag" (Ballute will deploy), 82L "Low Drag" (NO ballute deployment).

Bug reports go in the Forums

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); }

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.

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.

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.

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.

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?

I've been spending more time doing VLs and of the opinion that control sensitivity, including throttle, is more my issue to be ironed out. I always hate this part. I'm trash with making the adjustments. It's like sanding drywall. I never know when I'm done until I've sanded too much. Other than my failings, I think it handles great.

Well something is definitely borked. Try clearing out the bindings for all SSS switch positions. Save. And then restart game. See if the shaded spots go away. I Noticed you have JOY_BTN30 + LShift + RShift + N in SSS Down. I don't think that's even possible. Clear that out and hit OK. Don't Save! Then restart and see what happens.

How do I clear notifications I've read without marking everything as read?