SonofEil

I'll quote myself in response to a skeptic from a different thread. (Also, there are TM WH calibration utilities in that thread if anyone needs them.)

Umm, does that mean it's running nicely? I've seen a lot of crackheads and they don't run too quick. And then, you know, flys...they're fast, I guess...for their size.:helpsmilie:

Whoa. I like my WH waaaaay more than my X52pro. I spent many hours trying to smooth over that bump when the second spring engaged on the stick, and I was never able to get rid of that "springy" feel. The WH stick is considerably smoother, like butter, but still takes a small amount of muscle to move. You have to be deliberate, which I think is good. Now that mine's calibrated, I'm extremely pleased. It's also built like a home defense weapon. You seriously have no idea how solid it feels until you actually handle one. Perfect? Absolutely not! (I would actually advise a wait-and-see approach due to the number of people reporting the throttle frying itself.) Worth $500? Well, that's debatable. Best out-of-box HOTAS out there? Easily.

Hmm. Maybe that was something I was doing as well and didn't realize it. I wouldn't worry about your stick, I suspect that it has a lot more to do with TM's programming.

I had the same problem initially, and I'm using win7 64. I was cursing TM! I just unplugged my stick and plugged it into a different usb port, which the cal tool recognized. I then unplugged it, and moved it back to the original port. (EDIT: It seems that people are also having luck by moving the stick and pushing buttons on it after pressing the spacebar.) The cal tool recognizes it at the original port now. I don't know why. I also don't know anything about the version discrepancy. I've just posted what TM emailed me. Yes! Calibrating makes a hell of a difference! My stick, after cal, reads 32768 X & Y! Dead-nuts center, and it's very noticeable in-game. I am happy. I'm also very surprised that the cal tools aren't incorporated into the TARGET software. Rushed to market? I think so. EDIT: My 100th post!! I'm finally a member!!

And here's the stick calibration tool that they sent me. It seems to actually have worked. More testing needed, but I'm hopeful. It centers up now in the TARGET Device analyzer. Let me know if you guys get any use from it. Hey Mods, would you like to place these calibration tools as a sticky, since the only way to get them is contacting TM, and they're kind of a pain to deal with. HW_Stick Calibration_V1_11.rar

Thank you. I've been doing some research. I certainly would not know what to do in there. (I have a vague memory of destroying a school computer many years ago by getting elbows deep into the registry!) So that I don't hijack this thread, my follow up is here: http://forums.eagle.ru/showthread.php?p=1088048#post1088048 (basically trying to see if there's a consensus on reg cleaning tools or if everybody uses something different.)

I'm wondering what everyone uses as a registry cleaner, if you clean at all! Is there a tool that stands out as trustworthy or does everyone kind of do their own thing? In essence, this post is kind of a poll...without the poll. ___________________________________________________________ Win 7 64 i7 975 @3.33 8GB DDR3 HD4850

I have a problem with Hideout. Every time I start the mission, a Predator spawns in the parking spot directly across from me, pulls out onto the taxiway and then stops...and sits there. I wanted to move him or change his start time from the ME but he's not visible in the ME. Any suggestions how to accomplish this?

I have a follow on question from the OP. A lot of times I'll see someone ask, "did you clear your registry?" in regards to a clean install. What is this, where is it, and how do you clear it?

I see B4 referenced quite a lot as providing us with 64 bit TIR support, but wasn't it NP that (finally) provided the 64 bit drivers? If you wanted to, couldn't you now use TIR with B1, 2, and 3 in 64 bit? (The confusion may lie with the fact that B4 and TIR 64 bit drivers arrived on the same day. What a Christmas present that was!)

I'm getting beamed to the notch right now!!:pilotfly:

Are they multiplayer only?

Yeah, I saw that too! I was all like, WTF! Really? AWESOME!! I can't wait to see it!

Have you checked the CRASH logs in the temp folder? It might help you hunt down the cause. I often have crashes due to an "access violation" of one sort or another. (Used to be 80% or more of my missions would crash, with B5 it's down to +/- 50%. So, you know, trending in the right direction at least.)

Henchman, five letters: GTA:SA Word on the street is that's got the best heli sim around. I think it's right up your alley.

I honestly don't think the quality of the parts and build can justify the $500 tag. Problems that I've encountered include: Stick is off center, biased to the right. (waiting for TM calibration tool....) Throttles are wobbly. Pinky switch is loose. Flaps switch plastic hat keeps falling off. (I didn't expect to have to super-glue parts.) I'll probably be returning mine to Wal-Mart (cringe!) because of the stick problem. It won't calibrate with Windows device manager, I doubt any calibration utility TM sends me will work, if they ever bother to send it. (I've just begun my TM customer service ordeal, and it doesn't look good!) I think it's a hardware issue. The WH has a lot of good attributes, but I expected much better for the steep premium.

True. This is why I'm trying to resolve it now. I've been procrastinating and the return policy window is quickly approaching. If I don't hear from them in the next few days, it's going back for replacement. I had not tried calibrating with windows game controller, but I just now tried (thanks for the suggestion), no luck. Same right bias after calibration. This leads me to believe that I may be returning the Warthog for exchange, but I'll wait to hear back from TM. I had always attributed the right bias to asym loading, but since every load config gave me a similar right bias, I became suspicious. After downloading the TARGET sofware (which I really never wanted to do in the first place), the Device Analyzer in the Script Editor confirmed that my stick "centers" with a right bias. It's actually very surprising that the TARGET software doesn't come with calibration tools. Thanks for the help and suggestions. I'll keep this post updated as the saga continues. Oh, also attached is the throttle cal tool TM sent me if anyone else needs it. I'll post one for the stick if they send it to me. Throttle Warthog Calibration (V1_07)_22_07_2010.rar

Indeed they have...for the throttle! There's nothing wrong with my thottle! I copied and pasted my above post (minus a couple of edits) into an email to thrustmaster and they sent my a throttle calibration program. I have emailed them again, but haven't heard back. It's certainly a livable issue...if I hadn't paid $500 for the thing. At that premium I do expect damn near perfection. If they send me a joystick calibration program I will post it, and the throttle cal, here in the forums for everyone.

EDIT: Calibration tools are in posts 7 & 8. I received mine a couple of weeks ago, and it's had this problem out-of-box. My stick isn't centered. I always have to trim LWD after takeoff because my stick is biased to the right. With a range of 0 to 65535, center should be in the neighborhood of 32767. My center sits between 32950 and 33026 on the X axis. It's not crazy-off, but it is a noticeable annoyance in-game. I can't find any way to re-cal using the target software, thrustmaster's website, or a google search. A search of -Calibrate Warthog- on this forum gives 0 results. Does anyone else have this problem, or a solution to it?

I did about ten minutes of research on "Pro Flight Sim" a couple of months back. It was an easy scam to spot. I'm sorry your wife fell victim, Wad. I imagine that wives and gf's are the actual target of these scams.

I have mine limited to 40 as well. Like stated above, it smooths out the normal stuff, but the effects (gun, etc.) still bring it to it's knees. Disclaimer: I haven't had a lot of time with B4 yet, maybe 2 hours, so I don't know that I've "pre-compiled" all of my effects yet, as has been mentioned in other forums.

Hello, I'll try to make this as short and concise as possible: BACKGROUND: I used to use a X52 pro. I never programmed it using the Saitek software, basically because it was confusing beyond help for me. I assigned all buttons in-game for DCS:BS &WH. The catch was that I had to open the Saitek Control Panel and keep it open while I played, otherwise some of the buttons wouldn't respond at all. It wasn't a big deal, I'd open TIR, then Saitek CP and I'd be off taking care of some bad guys. Now I have a TM Warthog, and it is fantastic (mostly. Slightly over-hyped). Finally a real plug-and-play!! I haven't even downloaded the TARGET software, and I don't plan to. But I'm still using Saitek rudder pedals, because they rock. THE "PROBLEM": I still have to keep the Saitek CP open while I play, otherwise my toe brakes aren't recognized in-game. I can't assign them, can't use them. Without CP open, it's like the rudder toe brakes don't exist. I'd like to finally stop having to do this and just have the damn things "work". I've done some forum searching here and at Saitek, but I haven't found a solution. Any ideas? Thanks!

My experience is this: Such a big improvement over B3!! Fps, as mentioned many times, is significantly better, minus a couple of W'sIP. B3 was pretty much unplayable for me. CTD's nearly every mission. B4 is much more stable on my rig. I do still get CTD's every now and then, randomly. Crash log will say something about an ACCESS VIOLATION or something to that effect. But it only crashes on me, say 25% of the time now, instead of 90%. So we're trending in the right direction!! btw, my TMWH showed up the same day as B4 as well, not to mention TIR 64 support. What a Christmas!!

Having a mechanical background, I never really see this very often. Most problems are relatively linear. If you change your T5 setpoint, it doesn't bugger the overspeed sensor. Or more simply, if you change your brake pads, your turn signals still work, and so on. Although, I did have this old VW beetle.... I appreciate the insight though, from you and EtherealN.