gbogeaus

2700k, asus p68gen3, intel670 The machine runs for a couple weeks, and then locks up. Six iterations so far. Nothing will dislodge it, not even repair or Acronis disk. The people who built it have taken it apart and put it back together. No change But take the Crucial SSD and put it in another machine - it works fine. When it locks up, it gives an A2 (IDE detect fault) error notice on the motherboard. Is there anything to be done short of reinstalling Windows, which will wipe out FSX? And will reinstalling Windows even fix it? Any help would be very much appreciated.

Is the GTX 970 noisy running FSX? Noisier than, say, the GTX 670? Has anyone experienced the dreaded coil whine?

Is the GTX 970 noisy? Noisier than, say, a GTX 670?

If one didn't like the result, how would one undo the changes made by the Heap Config Device?

FSX will break out your airplanes by manufacturer, publisher or type. It will not factor analyze by livery, ie., airline. Assume you want to fly across England, and you would like to fly an airplane with an English livery. Let's say, British Airways. How to find the BA airplanes in your computer without slogging through them one by one - a task I would hesitate to embark upon as I have over a hundred airplanes, each one with numerous liveries. Well, it can be done. Access the Airplanes file folder with Windows Explorer. Then, in the box in the upper right hand corner that says "Search Libraries", enter "texture.[desired airline]". Here you would use "texture.British". Then, scroll down the results until you find the yellow airline texture folders, and the planes with British Airways textures will be listed. You would also want to try "Texture", as well as "ba","BA", "Brit" or any other possibilities that you might have used in setting up your airplanes Of course, you are out of luck if you have listed your textures by number. "Texture.4" is obviously no help. But you can always go through the airplanes that are cataloged that way and re-list them. Probably worth the effort if your are going to use this idea, not true? You can widen the search by starting higher up the folder tree, let's say "Microsoft Flight Simulator X". But the search may be slow if your search area, or part thereof, is not indexed. There are, however, extremely fast, free programs that will index and search of your entire system, including satellite drives.

1. For FSX, any suggestions for the following Win7 64 bit system?2. Is the Gen 3 spec in the motherboard a problem?3. What brand/type of system memory?4. Should I go to 3072 meg on the motherboard?5. Will the 2700K be any less stable than the 2600K?Asus P8Z68-V Pro/Gen3 MOTHERBOARDCM Storm Enforcer Mid-Tower ATX CHASSISWindows 7 Professional Edition (64-Bit) OPERATING SYSTEMIntel Core i7 2700K Quad Core PROCESSORAntec 920 Dual Stage CPU LIQUID COOLING8GB (2 x 4GB) DDR3 SDRAM, 1866MHz SYSTEM MEMORY1536MB EVGA GeForce GTX 580, GDDR5, PCIe GRAPHICS PROCESSORCooler Master 1200W POWER SUPPLY2 X 256GB Crucial 4 High Performance Solid State (SSD) HARD DRIVES -- Raid 1

Will these FSX related programs/items run on a Win 7 64 bit machine? Flightsim Commander Runway12 Object Placer Airport Scanner FS Force Profile Manager 2 Microsoft Force Feedback 2 Joystick Destination Finder 2.0 FPS Limiter 0.2

The machine passess Memtest86.Voltages remain stable except for the VIN0 voltage at the 560 ti, which varies between .95 and 1.06.

Machine runs cool: CPU cores 44-62 C; GPU core 37-55 C (idle-load).And the CPU is a stock Q6600 at 2.4.

I've tried every config file I could think of: FSX default, variations on Bojote's and my own.I've varied Job Scheduler, BufferPools, HIGHMEMFIX, Texture_Max_Load, TEXTURE_BANDWIDTH_MULTIPLE, and TextureMaxLoad, amongst others.Always the same result. Gone in 60 seconds.

I just swapped an 8800 Ultra for a 560ti because it appeared that the old card started having trouble with FSX (only).I've flashed the bios, reinstalled the chip drivers, insured the new video drivers are properly installed per Noelle's instructions, and tried every fsx config file known to man.The new card, although faster, still does the same thing. It runs FSX beautifully for about 60 seconds, and then 1) colorful artifacts, or 2) the screen freezes.Any suggestions would be very much appreciated. System specs are as follows.Asus Striker Extreme Mobo,Chipset : nVidia nForce 680i SLI SPPIntel Core 2 Quad Q6600 @ 2400MHzKingston 4096MB (4 x 1024 DDR2-SDRAM)EVGA 560 TI 1028 SLI2 X Nvidia Mirror 500GB / Raid 1,Thermaltake Toughpower 1200 PSU,Single SONY SDM-S204 DVI-D Monitor- 20 inchesResolution: 1600X 1200 32 bitXP Professional 32 bit SP3FSX / SP2 Acceleration

My 8800 Ultra is failing and I need to replace it. Any suggestions?My system is as follows:Asus Striker Extreme Mobo,Chipset : nVidia nForce 680i SLI SPPIntel Core 2 Quad Q6600 @ 2400MHzKingston 4096MB (4 x 1024 DDR2-SDRAM)Asus 8800 Ultra,Single SONY SDM-S204 DVI-D Monitor- 20 inchesResolution: 1600X 1200 32 bitXP Pro SP3 32 bit,2 X Nvidia Mirror 500GB / Raid 1,FSX / SP2 Acceleration

My computer wouldn't sleep (went to off instead) until I replaced my power supply.

Is it possible to list the airplanes in your computer by livery?

Thanks, Paul. Concise and articulate. I hope this gives people courage in the face of all this chaos....

I am still uncertain as to how to reinstate the original shaders if that becomes necessary. I understand that it would be necessary to 1) replace the original shader files, and 2) remove the Allow_Shader_30 instruction. Do you still have to change the Shader_Cache_Version number and restart the sim in order to re-compile? And if so, what do you then do with the Shader_Cache_Version instruction - remove it?

Thanks. I apologize for my oversight of the previous thread.

Has anyone tried this successfully? Exactly what does it do? What difference, if any, would this make to a late model NVidia based GPU such as an 8800 Ultra? If one tries this mod without success, exactly how does one get back to where one started? I'd try it myself, but I'm chicken without knowing exactly how to to reinstate the original shaders.

I am one or those Nvidia users who had disappointing results with Nvidia drivers later than 182.50. I stopped trying new Nvidia drivers 2 or 3 months ago, but I am wondering if any of the very newest Nvidia drivers ever solved the problem. Has anyone with the 182.50 issue tried any of the very newest Nvidia drivers? How did they work out?GeoffreyQ6600, 8800 Ultra, XP Pro SP3, FSX Acceleration

With a Q6600, an 8800 Ultra and XP Pro, I experienced degradation to both image quality and frame rates. Gratefully reverted to 182.50.

Same result with 8800 Ultra. All aspects suffered serious degradation, as with all 185's and 186's. Gratefully reverted to 182.50's.GeoffreyQ6600, Asus Striker Extreme, 2 GB DDR2 800, XP SP3, FSX Acceleration

With the 185's, I experienced both a degradation in fps and an increase in stuttering. Just to make sure, I installed them twice using the method promulgated here on Flightsim. Same result. I've gone back to the 182 driver and the problems disappeared.GeoffreyQ6600, Kingston DDR2, Asus Striker Extreme, Asus 8800 Ultra, XP Pro SP3, FSX Acceleration

If I don't like it, does UTX have the option of completely uninstalling it?

A program called FS Force restores force feedback to to the Microsolft FF2 using FS9 in XP (FS Force 2.0 for FSX). The author has advised me by email the program works in Vista and Vista 64 as well. Get more information at http://www.dirks-software.ca/fs-force.

Sorry, I'm not entirely clear here. I use XP Professional 32 bit. I have only 2 gig of ram. I'm not having any trouble with OOM errors. Should I use the 3 gb switch? Can I alleviate the risk of it screwing up my system on the first try? If it does, what are my options? Thanks in advance for these clarifications.GeoffreyQuad 6600 @ 2,4; Asus Striker Extreme; Asus 8800 Ultra; 2 GB DDR 800; Nvidia 500 gig twin drives with Raid; XP Pro 32 bit SP3; FSX Accelleration