Frazzetta

Thanks for the reply bk. I've resolved this problem (been meaning to post to let folks know, but got a little busy). Turns out the version of TAWS sold by the SurClaro FlightSim shop was a debug version of the software and not a release version. This explains why the software was asking for mfc100ud.dll rather than mfc100u.dll. The average flight simmer wouldn't have the debug version of that .dll installed on their computer unless they were using commercial versions of C++ (as I understand it). DBS Studios sent me a release version and after that the install and subsequent registration went smoothly. Once installed, I have to say I'm really happy with the software. The resolution of the terrain warning system is fantastic and has really helped me fly my GA IFR around the pacific northwest with more confidence. No more worries about RC4.3 vectoring me into the side of a mountain on departure! So, just a head's up - if anyone else is considering purchasing TAWS from SurClaro you may run into this issue. Hopefully DBS will update the version available at SurClaro's store to the correct release version in the future (if they haven't already)

Interesting...By the looks of it though, each gesture represents a specific command in a very general user interface kind of way.(ie, pulling your arm towards you = zoom). And each gesture is tied to a specific function (ie. rewind, play, etc.) That leads me to believe there would be a gesture say, for clicking a switch (a flick of the finger perhaps) but that gesture would only work for switch "A"...you'd need a different gesture that it could recognize for switch "B". Not sure how many switches, buttons and knobs are in a 737 cockpit, but I don't think I could come up with that many gestures (or remember them for that matter!).

Wow really?! I didn't hear anything quite that ridiculous (that I can recall anyway). Most of the offending ATC calls I remember were commanding 9000 feet or so. Good to know this is a "known" issue though...perhaps that increases the odds it'll get fixed one day. Maybe I'll shut off GA as well. Shame though as I'm grinding it out using Air Hauler right now and most of my flights (at this stage in my "Air Hauler" career anyway) are to and from very small airports and airfields, so GA is the only traffic I see on a regular basis.

Hi all, So I just purchased DBS Studios "TAWS" software for FSX and I’m getting an error on install warning me that it can’t continue due to a missing “mfc100ud.dll” file. I have Microsoft Visual C++ 2005, 2008 (both x86 and x64), 2010 (both x86 and x64) and 2012 (both x86 and x64) installed on my system (the 2010 x86 version should have this .dll I beleive) so I'm at a loss as to how to fix this. I've uninstalled both 2010 x86 and x64 and reinstalled them but no joy - still get the error. Anyone have any experience with DBS TAWS? Anyone else run into this problem? I've sent an email to DBS Studio's support but I've read that their support can be spotty and slow at best (based on posts on their other products here at Avsim) so I thought I'd give this a go as well. Cheers, Adrian

Have only had Ultimate Traffic 2 installed for 2-3 days, but I'm noticing a substantial increase in the number of "please expedite climb" requests from the FSX ATC to respective AI planes. When you have 3 or 4 smaller GA planes getting hammered by the ATC to climb faster every 2 minutes, it gets old fast and makes the default ATC more annoying than usual. I have RC4.3 which I use as my primary ATC, but I do like to have the FSX ATC running at low volume in the background - I find it provides plenty of background chatter and I use it for progressive taxi and ground ops (especially on arrival...the Radar Contact "Taxi to the ramp" is woefully inadequate). I know the most obvious solution is to lower the ATC volume to "0" once I'm in the air, but messing around with the settings menu resets all of the AI traffic in UT2, so I'd rather not if I can avoid it. Anyone else experience this or have any thoughts on a solution?