Bob F

I don't see that it was addressed directly by SP3, but in my case it fixed my Xgauge. Previously, if I installed Xgauge on my planes, FSX would crash when I attempted to load a plane. My only option was to leave Xgauge uninstalled.After SP3, Xguage seems to load without any problem. I'm looking forward to using it. Thanks for the update.

I hve the TrackIR for a couple of years. I wouldn't fly without it. I don't turn it off , but I have mapped the pause (F9) to the keyboard spacebar and when I need to adjust a gauge,I focus on the gauge, hit the space bar to freeze the view, make the adjustment and hit the space bar again to unpause it.My only problem using the unit is that I wear bifocals and they are very difficult to use with the TracIR. I solved the problem by buying a cheap pair of single vision reading glasses and the problem was resolved.

My ram is shown at 1.8 on CPU-Z. The specs for the sticks rate it at 1.9. When I change the VCore voltage from "auto" my board says this will unlink the voltages to my Northbridge, Southbridge and CPU VTT, whatever that is. When I changed these last weekend, I had a heck of a time recovering. Sometimes I could get into the bios, but my wireless keyboard would not respond, so I couldn't make any changes. I finally realized the keyboard was live for about 15 seconds after I entered the bios and then went dead. I was finally able to go in and hit F10 to restore the bios defaults and then all was well. My next option would have had to have been the motherboard jumper.I'll check all of this out when I have a little time play with it, hopefully before the weekend. After last weekend, I get a little nervous messing with the voltages.Thanks again for your help.

I got the FSB up to 311.1 X 4 =1244 (2.8) to run stable. When I tried to bump it up to 322 X 4 = 1288 or higher it wouldn't post. I checked my Vcore voltage and it does appear the "auto" setting boosts the voltage when I increase the FSB.As I said before, 2.8 was my original goal because I was going to buy a Q6800 chip @2.8. If I could OC the Q6600 up to the same speed, I'd save about $500. That's not to say I wouldn't like 3.0 or 3.2, but I just not sure how much aggravation I want to go thru to get there.Since starting this little experiment, I've read that my motherboard is somewhat finicky about memory. I have Corsair Extreme memory and maybe the board has a little problem with it. I haven't seen this type of memory specifically mentioned, but maybe no one but me is using it with this board.I really do appreciate your help and if you have any magic bullets, I'd be glad to try them.Bob

AspenleafI had a little time to try your overclock suggestions this weekend. I set my memory to manual and was able to input the ram speed at a constant 800mhz. I was able to increase the FSB until I was able to get to 2.8. I tried 2.9 and it wouldn't post so I upped the Core voltage up to 1.35 and that's when I ran into problems. I spent the next hour trying to get back into the bios so I could undo my changes. Finally, was able to get back to 2.8 and it runs cool and stable at that speed. 2.8 was my original goal, but I got a little greedy when I saw people getting up to 3.2. I think I'll stay right here for the time being and not worry about trying to push it harder.SamI know my Vcore voltage is holding me back as you suggested. I have an Asus P5N32 680i SLI motherboard and when you take the Vcore voltage off "auto" to specify a particular voltage it disables several other "auto" voltage settings. Since I have no idea what those settings should be, I think I'd better leave them alone.Thank you both for your help and excellent advice. In a few months I'll probably forget about the problems I had resetting my bios and try to push it a little harder. In the meantime I'm satisfied with my 30 to 45 frame rate. I only fly the GA stuff, so I can crank everything pretty well to the right and enjoy the ride and not worry about tweaking too much.Thanks again for your help.

Hi BruceHope you enjoy the scenery, I sure do. Try a flight from Telluride to Creede. The scenery is awesome and the landing is pretty challenging.My brother-in-law lives in Boulder and I went to CU. Had season tickets to the Buffaloes & Broncos for several years after I graduated. Haven't been back to Boulder for 25 years, bet a lot has changed. Is it still a toll road between Boulder and Denver?Bob

I lived in Colorado for about 35 years prior to moving to Phoenix. My wife's family lived in Estes Park for a number of years. It's sure pretty country up there.I still have a cabin in the southern part of the state near Creede. It's just below the Continental divide about 15 miles North of the summit of Wolf Creek pass. It's nice to get back to the mountains during the Phoenix summers.If you like to fly in the mountains check out this website. (http://www.blueskyscenery.com/) Creede, Durango and Teluride are in the Avsim library and he is working on Estes Park and Rocky Mountain National Park. Very realistic to fly over.Again, thanks for your help.

Thanks for clearing up the memory timings for me. I couldn't understand why I couldn't get the darn thing to boot with only a 10% overclock when everyone was saying 3.0 to 3.2 was easy. I'm anxious to get my memory timings adjusted and see if that will solve my problem. I doubt I'll get to it until the weekend.Thanks very much for your help and I'll let you know how it turns out.With a name like aspenleaf, do you happen to be from Colorado.

SamI have Core Temp loaded on my machine. My TJ shows 100 and the core temps below that number show in high 50's under moderate load. I'll try bumping my Vcore up and see if I can do it without sending the temps thru the roof. My computer is located under my desk in a fairly confined space. I may try putting a small fan under my desk to see if that will help with keeping the temps down.In my reply to Aspenleaf above,I told him what my memory timings show in CPU-Z and it appears by leaving my memory timing set to auto results in overclocking my memory to 965mhz even with a 5% CPU FSB overclock. Could that be the reason my computer won't post with anything higher than a 270.9 X 4 FSB?Thanks for your help.

I only had a few minutes on my computer last night, but I did take a quick look at my bios and everything relating to memory is set to auto. I checked the memory using CPU-Z and it shows under the memory tab, timings of Dram Freq of 419.6 and FSB Dram of 2.3. If I am understanding you post, that would put the memory timings at 965.08 which is much higher than the ram is rated. That may be the reason the computer won't post with anything higher than a 5% overclock. I'll have to spend some time looking at how to change the memory timings. I thought I had read somewhere that if you left your memory timings set to auto it would maintain you timings at optimum for your RAM rating. Apparently this is not the case.As I mentioned I'm new to this overclocking business and I view changing the bios with about as much trepidation as disarming a bomb. I am always afraid I will do something I can't undo. If the computer doesn't post I go into panic mode. I guess the newer boards make it easier to recover from a bios mistake. At least I hope so! Thanks for all your help. I'll let you know if I can figure out how to change the timings.

I haven't changed anything in my bios except the FSB. What puzzles me is that if I set my FSB to 289, The computer won't even boot. I wouldn't think heat would be an issue at that point and I wouldn't think it would be necessary to increase the vcore to get to that clock speed.I'm a complete novice at overclocking and find myself going into panic mode when the computer won't boot. So far I have been able to recover by restarting and going directly to the bios and resetting the FSB, but I don't want to get to the point where that won't work.I don't think there is any way I can get in the 3.6 range with my cooling issues, but I would think 2.6 to 2.8 would not be unrealistic.Any suggestions are appreciated.

Memory timings are set to Auto and vcore reading is 1.264. I have made not changes in the Bios except the FSB everything else is default.I have not been too impressed with the liquid cooling. I've run far cooler with air. Thanks for the suggestion of checking the mounting of the heat sink. I hadn't thought about that. Maybe it just needs to be remounted. I've never worked with liquid cooling, so I'll have to read up and find out how complicated it is to remove the heat sink. I don't want to do more damage than good.I really can't complain about my systems performance, as I get frame rates in the 20's & 30's most of the time with most of the sliders to the right except traffic.Thanks for the help.

I downloaded the two programs you suggested and ran them this weekend. CPUID shows my CPU is a Q6600 Kentsfield , revision G0, Stepping B, Model F. Core Temp shows my VID at 1.2875v.I'm still puzzled why I can't over clock past (279.74 X 9) 2.5176mhz. It appears I have about the same set up as people who are sucessful getting it up in the 3.2 to 3.4 range. If I advance my FSB beyond 280 my computer won't post. I have 2 Gigs of Corsair Dominator memory @800 mhz, so memory shouldn't be an issue. I live in Phoenix, so the ambient temperatures could be causing my CPU to run a little hot, in the mid to high 60's. I have liquid cooling and a full tower Cooler Master case with three case fans.Anyone have any ideas as to why I can't overclock this rig at lease up to 2.8?Thanks for any suggestions.

Thanks, I'll give it a try this weekend. I'm at the office, so I am not in front of my computer, but I think my voltages are set at 1.4.

I also have a Q6600, but I am afraid I must have the B3 version because mine runs in the 60s at full load with liquid cooling and a Cooler Master full tower case. If I try to overclock it, it won't post after I get it to 2.57. Is there a way to tell which chip version I have without having to remove the liquid cooler. Any suggestions how I can get it to at least 2.8?Thanks for your help.

Thanks GottfriedI think my density setting are full right, but I'll have to check on it this weekend. I'm really looking forward to exploring your scenery this weekend. I lived about 40 miles east of Creede for 35 years and as I mentioned earlier, still have a cabin on a lake about 15 miles from Creede. I've explored most of that area at one time or another and one of my favorite flights is from Creede to Teluride, both in real life and flight simming.Thanks for creating this scenery and I look forward to more of your work. I'll be sending a donation this weekend to support your efforts.Thanks again.

Thanks GeofI thought I had possibly installed it incorrectly. I'll try the email and see if I can get it sorted out. I don't have any buildings at Creede, Durango or Teluride.John Wayne used to have a large ranch south of Creede and the guys at the airstrip used to talk about how his pilot would bring him to Creede in his Learjet. I never did see the plane at the field so I can't say it definitely happened. The guy had to be pretty good to pull it off. I had some anxious moments just trying to land a Cessna 337.Thanks for your help.

Thanks for pointing out the Blue Sky scenery of the Creede and Durango areas. I didn't think anyone on this board even knew of Creede, CO, let alone create scenery of it. I have a cabin about 15 miles SW of Creede and am very familiar with the area. The scenery looks great, but all of the airport buildings have disappeared. Do you have that problem or do I have it improperly installed.Sorry to have to ask you, but there doesn't seem to be a way to contact the authors on their website.Thanks for your help

GeofThanks for pointing out this scenery. I didn't think anyone on this board even knew of Creede, CO, let alone create scenery of the area. I have a cabin about 15 miles SW of Creede and am very familiar with the area. The scenery looks great, but all of the airport buildings have disappeared. Do you have that problem or do I have it improperly installed.Thanks for your help.

When I uninstall the gauge I have no problems. ASX and ASG work perfectly with the guage uninstalled. I'm running an 8800 GTS 640 mb video card. I think the drivers I'm using are are the second most current WQL drivers.Also, I have not tweaked FSX at all. I only added the addons listed above.

JimSame size as mine. Maybe the problem is not in the Xgauge.dll.Any other ideas? Everything works fine except xgauge won't run.

JimI don't think that is very likely as it is new computer and only has FSX and a few addons installed. My bet is a corrupt download.

I Tried deleting the xgauge from the FSX gauges folder then running the gauge wizard again but the result was the same. Windows asks me if I want to run the gauge, but it won't let me click on run, then FSX crashes. Below is the error log, if that will help you any: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61355.0 Application Timestamp: 4643ee0a Fault Module Name: window.dll Fault Module Version: 10.0.61355.0 Fault Module Timestamp: 4643f2ad Exception Code: c0000005 Exception Offset: 00003cda OS Version: 6.0.6000.2.0.0.768.3 Locale ID: 1033Additional information about the problem: LCID: 1033My Xgauge.dll if 648Kb. Can you tell anything by the size if is corrupted or not?Have a Happy New Year!

I tried starting starting both the gauge wizard and FSX with the right click method and still got the crash. I also tried using both options in the installation screen, append and I can't remember the other one. Everything works fine after I run the uninstall gauge routine. I only have 4 addon planes, the Cessna FSD 337, the FSD Satatoga, Eaglesoft Twin Comanche and the Eaglesoft cirrus.I wonder if the xguage.dll is corrupt. Is there an easy way to replace the file or will I have to re-download Active Sky and reinstall. I have reinstalled the program once without success, but I did it from my original download.Thanks for all your help.

I am the only user and am logged on as the administrator. No other user accounts have been created.Thanks