SGT Coyle

I never use the stop except to TO and shortly afterward set to zero(or no stop set). AFAIK the stop settings are a mechanical blocking by use of an indexed track that the stop lever locks into via a spring loaded pin in the handle. Setting custom stops isn't possible. Having the stop set during hover could be problematic if you need more travel than your stop is allowing. If I have that wrong, someone please correct me.

Why would you remove chocks before you have control of the AC? You would need brakes. I knows it's been reported and it's ED bug, but for Pete's sake, aren't these things supposed to get caught in testing?

You have wheel chocks placed by default. You need to have the Chief pull them prior to APU start. It's a brake pressure thing and an ED bug.

Looking forward to trying this in a mission.

I'm starting to wonder what the value is. Short of that what's the magic sequence you need to get the Chief off his ample posterior to pull the chocks.

Nothing has changed for me. I'm still mapped to Axis. There is stuttering, stopping, and jumping, in the DMT that isn't present in other Modules. I haven't even tried the TPOD. ELMO if you or someone else at Razbam are not experiencing these issues, please post your settings related to TDC slew so we can do an apple to apples comparison. I posted a video awhile back and nothing has changed for the better. In fact slew interaction has gotten worse with recent updates that's been reported already.

Tried to fly my favorite Campaign: Vulcan Forge. Coldstart, Easy coms, ground crew greyed out, and unable to comply to remove chocks command. One step forward. Two and a half steps back. Maybe a Tick box in settings to auto place chocks or not.

Ya! Finally get to pull chocks.

At least What's a reasonable number of haters? What is a hater? Am I a hater? So many questions. I like to think I'm an informed consumer demanding high standards of quality. At least it's only 6 pages. This is light reading.

Hows that working for ya?

These instructions are for an upcoming update?

Check the Q4 , and December post in the Razbam section. ELMO provided some explanation and procedures. I don't have the links handy but they shouldn't be to hard to find.

In the spirit of eliminating the hardware. Press WIN + r type "joy.cpl" and hit run Select "Joystick - HOTAS Warthog" and click properties Play with the stick. Move it around, hit the buttons, and watch the lights. Let go and watch for lights 1 and 6 to light up. Those are the first and second stage triggers. If nothing happens for a period of time then it's probably programming related. If you do get a light without squeezing the trigger, then you probably have a hardware issue. Contacting Thrustmaster would be a good idea. Do you use TARGET GUI or Script Editor? If so would you post you Profile or Script.

I would say, that it is still bugged, but not how you may think. Using the TDC axis still stutters and pauses inexplicably. It's been doing that forever. But the latest is the HUD indicator jumps all over the place. It's been reported. So keep checking in. One day...

Same here. To replicate: Open kneeboard Use mouse pointer to change page (just to ensure pointer is in the kneeboard frame). Try to move pointer straight down( It hangs on bottom of frame). You can move the pointer either right or left and then go around the bottom frame to get to what you want. The above stricken text needs to be checked. I just tried on the Harrier and the pointer is blocked from accessing anywhere below the Kneeboard frame.

Try this!

Is this "Easy Comms" enabled? No freqs in the briefing screen or docs.

How do figure it's a "News Thread"?

I'll give printing one a try. If it comes out I'll post file here.

Thanks for the backup. I've been going through all my .ttm files looking for duplicates. In a few cases I had already started editing out USB scancodes all together.

Right out of the box, the Warthog Stick and Throttle have DirectX (DX)buttons assigned to it. You'll have to assigned those available buttons to controls in game. Since I haven't relied on those basic settings in years, I'm more than just rusty on the particulars of where the config files reside in the game folders. I use TARGET Script Editor to map my controls. I'd be happy to offer my script, but it would be way to complicated for a TARGET beginner, but I'd be happy to help you get started.

Sure. This is an example of an SE script that worked fine a couple months ago. Viggen.7z

Well I might have posted too soon. It seems that any .tmc command that calls a macro defined with a USB scancode throws a compiler error. This is getting frustrating.

Lange_666, I recently found my macro generator was assigning defines of WIN key modifiers to default USB scan codes as "L_WIN". Deleting all WIN key references in macro file got rid of "Define Stack Error".

Don't know what it was, but redoing it seemed to work. Found that automated Macro File Generator was placing "L_WIN + " as a modifier. That was breaking any USB[0x] commands.