69iAFMike

That sucks. I've heard of pinched wiring, and even a guy abusing the socket by trying to mount the stick on backwards (moron who can't see yellow arrows)- which could, but didn't, push the connector to the bottom like in your case, but never a socket not held properly by it's metal casing. Mine came with the black ground wire slightly pinched, but no problem. This part is rather easy to replace, two screws and some soldering. This shouldn't happen, though. TM's quality control of these DIN connectors is starting to annoy me.

Yep, same frustration I went through. I even ended up with one bent key! Make sure you place the tip of the allen key right on the middle of the plugs, it's easy for it to slip a tiny bit and press against the inside of the ball itself. Tapping the key with a metal tool of your choice, while pressing with your hand, should help too. You may want to try sanding down the diameter of these plugs a little bit, their fit is way too tight.

Calibration, maybe? http://forums.eagle.ru/showpost.php?p=1084321&postcount=7:

Could it be hot glue? Maybe attack it with isopropyl alcohol from a cotton swab, it should loosen on it's own, and gently peel away.

A conical spring, maybe? But there would be no room inside the Warthog's original base to house such a thing with diameters that make a difference. I guess the smaller diameter would be a problem if we use something smaller than the original spring's diameter, so the only way would be to use a larger diameter going outside the bounds of the current housing. edit: Silly me, a constant diameter, variable pitch spring would do the same.

For example, the flaps switch. UP position activates button 22, DN position activates button 23. So in some game we can map these buttons to whatever commands. But MVR is just off, it doesn't activate any button. So how can we tell DCS, for example, that MVR where no command is sent- has to activate some function? The solution would be TARGET identifying that we turned off button 22 or button 23, and it means we are at MVR position and can send a keystroke for this state. The A-10C module does have recognition of these switches on the Warthog, I guess ED really made it "plug and play". But other modules do not, also other games in general.

Here is the most I could possibly separate the values, when actually twisting the levers during motion. Normally the raw values are no more than 100 units apart, and sometimes under 10 units apart. It's really not a problem at all. Also, the values seem to be more consistently within 10 units of each other when I move just the right lever, letting the left one drag along with it.

Good for you! The Mini-DIN issue reminds me of someone who tried to sell his Warthog set "as new" because he "doesn't use it". His photos of the stick unit had the grip mounted in reverse, as in trigger facing towards the print on the base plate, not towards the USB cable. When asked about the weird configuration, he said he just connected it like that. After further inquiry and proof of how this would be impossible without him disassembling and reassembling the whole thing, he proceeded to prove why this was indeed possible, and why it didn't work for him in FSX: Mangled. Yep, all you need to do to pimp your Warthog, is to just mount the thing on backwards! Break all the mini-din pins. There's some improper assembly for you :). This is at least one proof that the BIG YELLOW ARROWS aren't 100% effective :)

What is this? It looks scary with lots of science. The only opentrack I know is this one: http://github.com/opentrack/opentrack/blob/master/README.md

Spotted in Elysium What's with using it in spacecraft? A Saitek X-whatever would fit right in!

We'll find a misplaced polygon on the model when the next batch of screenshots shows up.

This is fantastic!

What does Hitler have to say about this? He was quite upset with the Mustang.

I usually get shot in the governor. From there it doesn't take long for the motor to fail. Being stupid and playing around with the throttle, setting it from closed to open quickly several times eventually killed my horse too.

Exactly my issues, throttle all good, stick "bulk". Only uninstalling the devices and drivers first, then going through the firmware update, unbricked it all for me. TM support had me do the bootloader method, but without uninstalling first- this method did not work at all. Mentioning the uninstall step to the TM support guy yielded no response. Maybe they're looking into it to improve the instructions, maybe it was just a specific issue with my set up.

Does it appear in Device Manager, under Human Interface Devices, with "bulk" in the name? If so, try Thrustmaster's bootloader method. But before doing it- uninstall ALL drivers and devices related to the stick and throttle (through device manager and uninstall programs). TARGET and the updaters should be OK without uninstalling them. http://ts.thrustmaster.com/faqs/eng/thr_eng_00140.pdf Uninstalling the drivers first, was what made this method work for me. Without reinstalling them nothing worked.

It was too little centering force for me. Put the big one back in. While using only the four small springs, I actually noticed MORE weird friction as the big sliding plastic thingy moved near the top of the pole. The springs were not enough to overcome this and recenter the stick. I removed the white PTFE (?) ring and weird friction was gone! Now the stick centered with only the four springs. It seems that when completely fastened, the ring becomes misaligned and pushes too strong against the poles. I ended up releasing its screws, letting it have a tiny, less then a mm play. No friction now, and using the big spring requires less force and is smoother.

I kept falling off when the helicopter turned. It's just collision models doing their thing, just like standing on the wings of various other models.

Tried it with a friend yesterday. Best I could do was to walk into the Huey, with the pilot just magically stepping up onto the floor, head poking through the top. It was funny.

These shots are mainly for showing who took a part in the mass flight. Replaying that track is always possible. If you want eye candy I can make some too:)

With some labels so you can find yourself :beer: Thanks for another great VFAT, staff and teams! The "Nuke Burst"

Well, not replaying properly is not really the case here. I don't really care that one out of <random huge number> planes crashed in the track. The track just didn't load at all through FC2. Your method and LOTTU pretty much force the simulator to run the track (maybe the issue is extracting the zip\track archive? takes too long for FC2?), and that's exactly what I (or anyone with big track files) need. Thank you and the 104th for this work!

Yep, also works! It does pretty much the same thing! Now I'll have to get the whole 104th some beers too? :surrender:

In the air it was like I was all alone. FPS over 60 as usual. I was very happy to see such performance. This man made these screenshots possible!

The VFAT 2010 mass flight! The missing plane in the A there is me. Damn track crashed my plane!