CTBlankenship

NEVER MIND: Problem resolved ... the LX-3000 was showing up in FSFDT as Wave-Modem #3 Line Record and Wave - Modem #3 Line Playback. Really screwy that that was the problem. Problem: I cannot receive or transmit voice using my Microsoft LifeChat LX-3000 headset/mic. When I enter the FSFDT Control Panel (Voice | VATSIM selected) ... the Microphone and Headset combo boxes do not show this USB device. Closer inspection in Device Manager (in the Sound, video and game controllers section) in fact does display the Microsoft LifeChat LX-3000 peripheral and it is operating properly. So, my question is why would FSFDT Control Panel not recognize the headset? Also, when I go to the VATSIM | Key mappings section, for the FS PTT Joystick Button I am able to assign Button7 to that function using the Set button and pressing Button7 on the joystick. To test the microphone I entered Sound Recorder and it is working properly as I can record an audio file. Entering the Sound dialog and setting Playback to the LX-3000, then, playing a windows sound shows the earphones are working. Finally, I'm using Norton Security and the FSFDT Control Panel, FSInn Application and FSInnUI are all assigned "Allow" as an Access setting. Stumped, Charles T. Blankenship

For me the third time was the charm ... first time the descent rate was over 400 fpm ... the second time I landed more than 4,000 ft. from the threshold ... then, after adopting a tip from Tabs (of PMDG fame) I nailed it as well. Always looking for great visual approaches to work with ... LOWI is next.

Yes ... pause doesn't work ... Y (slew) does ... I'm sorry ... I didn't realize I was in the 777 forum <s> ... I'm using the 737-800 to do this visual approach. The turn radius is just fine ... but the descent is steep ... hard to keep her at Vref prior to threshold. The scenery, on the other hand is fantastic! I'm using FTX Global and the mountains are breath-taking. On another note, I had to do a check ride with my VA ... it was the Parkway Visual for 13L at JFK ... that approach is very fun as well if you haven't tried it ... here is a link to the real thing ... http://www.youtube.com/watch?v=0EQ9-m-nuPI. To make it totally realistic download the trial version of JFK from FSDreamTeam ... it gives you five minutes of time ... which is just enough to get the bird down and enjoy all of the great graphics.

I've been practicing the Roaring Fork Visual Rnwy 15 at KASE ... did the usual trick of saving the flight through FSX and then reloading ... PMDG is great about reinitializing ... anyway ... after loading the flight I have to wait 18 seconds for the plane to start back up. By that time I'm down 300 to 400 ft. ... I lucked into a solution. Most of you probably know this trick ... but I found that if I press "Y" ... or slew mode ... everything freezes ... the countdown ends ... I press Y again to get out of slew mode ... and my plane is up and running ready for another go at a challenging visual approach. Just thought others might get some use out of this information.

Oh my goodness ... I purchased an EVGA GTX 780 on August 8th, 2013. From the beginning I experienced problems with the video ... I used the DVI-I and the DVI-D*** ports to provide input to two ASUS PA248Q monitors. I experienced flashing and tearing on a consistent basis ... 60 seconds between events. After, approximately one to two minutes, the entire monitor went black ... and then reappears ... EVGA's answer, in part, is as follows: I would recommend installing the latest drivers off of our website. When installing, run it as a "Custom Installation" and select the check box on the next page to "Perform a Clean Installation". Honestly ... I realize the need to make sure one is not dealing with a complete idiot ... that is the FIRST step in any troubleshooting procedure They continue: If the issues continue please check the +12v rail in your motherboard's BIOS. To do this you will need to go under the HW Monitor in the BIOS and read the voltage output for the +12v. This reading should be between 11.6-12.4v and should not be fluctuating more than about .05v within a few seconds. If it is outside of this range I would suggest testing with a different power supply. Oh my Goodness ... I told them previously I purchased a Sasonic PLATINUM power supply. Here is a video of my system using HWMonitor ... http://www.dropbox.com/s/00xnd4wva49bm32/12VRail.mp4. That power supply is doing what I paid it to do ... 12.000V forever. It gets better!!! Also, another good way of narrowing it down solely to the card would be to test the card in another system such as a family member's or friend's computer. OK ... let me get this straight ... I just purchased a top of the line video card worth $700+ and you want me to test it in another machine? Not only does my family NOT own a machine like this ... there is barely anyone in my whole TOWN that owns a machine like this: i7-4770K Intel processor OC'd to 4.6GHz ... stable. 16GB of G.Skill 9-11-11-31 @ 1.65V ASUS Maximus VI Hero Motherboard ... (as if my friends or family even know what a F*$KInG ... MOTHERBOARD IS!!!) honestly ... Honestly ... HONESTLY ... that is the BEST YOU'VE GOT? How can a multi-million dollar company get away with service like THIS!!! Mr. Feldman ... I believe I have addressed your concerns. Please let me know if you need further clarification. Regards, C. T. Blankenship

Just thought I'd give you a heads up with regards to competency ... http://www.dropbox.com/s/nwahla3mqv3utkl/ResponseToEVGASupportEMail420088.docx

I was thinking of making this variable ... once every 10 seconds below 10,000 ft. and once every 30 seconds or so at cruse. This is going to take some doing obviously ... after I've banged my head against the keyboard long enough ... I'll figure it out ... eventually ^_^

Yes ... that is the main point of the whole shebang ... using FSUIPC one can interface with MSFX and pull data from the sim (at least that is how I think it is going to work). When I'm done and it looks pretty good I'll release the code as open source and place it in the public domain. C. T.

C# ... .NET 4.5

I flew here 73°48′26″N 54°58′54″E ... the site of the largest nuclear blast (atmospheric) ever ... yield 50 to 58 megatons of TNT, the Tsar bomba. I set it up in LA with a full tank and went to bed ... woke up 8 hours later and she had travelled over the pole ... hit the waypoint ... circled back ... at was over the Midwest when I came back in to the office. I was smoke testing my new computer (i7-4770K OC @ 4.6MHz) temps never left the 50's ... it was a success. Other than that one I usually fly short flights 2 to 3 hours ... as my excitement with the plane is not listening to it hum for hours on end but setting up to takeoff and land with ATC controlling the whole thing. I usually seek out airports that are covered by ATC ... some are better than others however. I've had zero problems with the T7 ... knock on wood.

Yea ... but it is so much more fun to waste time on Google, convert Lat/Long values and enter them into a file that's just going to be overwritten on the next AIRAC update! :lol:

Kyle ... never thought you were ... you are an incredible asset to the forum as well ...slowly working my way through your videos. The app is basically a localized ACARS for people whose virtual airline does not store any telemetry data. I'll be tracking the following (and accumulating it every 10 seconds during the flight): Date/Time Latitude Longitude Altitude Heading Air Speed Ground Speed Mach Vertical Speed N1 N2 Bank Pitch Flaps Wind Speed Wind Heading Visibility Fuel Flow Fuel G/S AOA Framerate COM1 frequency ATC ATC Warnings I'll then take all of that data and use it to make criticisms concerning the flight ... like: Did you blow through the 250K/10,000ft. rule? Did you drop flaps at a speed that would damage them? Was your G-Forces excessive during maneuvers? Did you exceed bank angle? Did you miss the altitude constraint on an approach (which is what the database is for). I'll then put this on a map with points that define the characteristics of each piece of telemetry data. For example, each point, when the mouse is hovered over it, will show the following: 1. Warnings for this particular data point 2. Location (Lat/Long) 3. Time 4. Bank Angle 5. Speed 6. Heading 7. Vertical Speed 8. N1 and N2 9. Fuel Flow 10. Fuel Left 11. COM1 frequency and ATC controlling you I'll design it so that the user can open the raw Excel file ... as well as create a KMZ file that will allow you to view your flight using Google Earth. Yes ... I get bored once in a while and have to keep my programming skills up.

Some of the <ICAO>.TXT files do contain the gate information ... but they are few and far between (that is how I found out what the format of the data should be) ... as a matter of fact KATL.TXT had a gate defined of zero. After playing with it I did notice that the reference airport Lat/Long actually ends up being exactly the location of the gate. So, this is more of a realism exercise than anything else. Also I thought people might be interested in seeing from whence some of the data that drives the CDU originates. The other directory and file content is the NAVDATA folder. It contains the NavAid and NavFixes as well as all the information required to create routes using the "via" and "to" part of the Route setup. If the FIX you enter doesn't exist along the jetway then (as defined in the wpnavrte.txt file ... you get the Not In Database error message. I'm currently writing a data conversion routine that parses all of the information out of these text files and places them inside a normalized database which will support a little app that I'm writing.

Here is a bit of fun for you ... herein resides instructions on how to modify Navigraph's data for all PMDG products so that you can enter gate information into LSK 3L on page 1 of 3 on the POST INIT page of the CDU ... ENJOY!

I just watched your video on how to create a route ... that was fascinating ... thanks!