WallysWorld

Wilbert, the 560TI version generally performs better than the plain 560 version. You can see the difference in gaming performance in these links:Tom's Hardware 2011 graphic cardsAnandTech 560 reviewWhether or not, the 560TI works better in FSX than the plain 560 version is unknown to me, but I do second TechguyMaxC's recommendation of the TI version.

I just went to a 560TI over the weekend over my old GTX 285 and I'm pretty happy with it. Gained about 25% more frames in heavy load FSX areas (with a 4.0Ghz i7-920) with less stuttering and more smoothness over the 285. But I also wanted the 560TI for the quietness of the fan and that fact that under load, the 560ti runs at around 52C. My GTX 285 would climb up to around 75-80C under load and the noisy fan would kick in.

This is what I did to confirm the REX files were being copied into the Texture folder for FSX:1) Remain the Texture folder to Texture_backup.2) Create a new folder called Texture.3) Run REX to install the files.4) Check to see if the new Texture folder you just created has the REX files in it. If it does, then you know REX is copying the files to the right folder. Make sure to take your backup folder and rename it back to Texture.

I sort of had this problem whenI thought REX clouds were being correctly copied into the Texture folder. They were not as the default cloud texture files were marked as "Read" only and couldn't be copied over. This was using Windows 7. Make sure that the REX cloud files are correctly being copied into FSX's Texture folder and overwriting the default cloud files. ASE doesn't care whether the clouds are default or REX like Jim wrote.

I also use MTX 5.3b with 50/20 settings and medium setting for airport vehicles and get around 17 fps around JFK as well. I don't want to remove the airport vehicles because, like you wrote, it makes the airports look dead. The real killer is the jetways that move for the aircraft. From what I read, the airport vehicles should not be that big of frame rate killers.

Pete released the newest version of FSUIPC for both FSX and FS9: Pete's FSUIPC pageI'm very happy to report that it appears the FSX version completely stopped the delay that sometimes occurred when using RC4 with ASE with Direct Wind Control on. Just flew a flight and there was absolutely no delay with RC4 contacting the tower on approach.

Fantastic! Love FRF airports!

I tried the demo. It only works good with the default airports. Addon airports will not really work with it because the animated gate might appear in a weird area of the airport.If you only use the default airports, then it's a good addon.

After using FSX for just over a year with my i7-920 and never bothering to try turning off HT even though I read about it, I finally tried it for the first time today. I have to say it's made a nice improvement with the flying experience with FSX. The stutters have been reduced quite a bit and I think I might have gained about 4-5 fps. I'm using the frame rate limiter set to 35fps and turning off HT definitely helped with the stutters.

Flight1 does have Audio Environment: Airliner Edition which replicates AI sounds and does a good job. But it's only for FSX. FS9 on Vista/Windows 7 desperately needs some sort of AI sound generator.

It's right here available for download: Gary Widup's KSTL

Yes, it only works in FS2004. I tried the demo and it worked pretty well except that you need to use the default airports only. It will not work with any addon airports.

Some OOM errors are also caused by empty texture folders for addon scenery. I used to get this error when flying into CYEG until I looked and saw that the texture folder in the CYEG addon folder was completely empty. Once I deleted the empty texture folder, no more OOM's.

Terrain.dll errors can be very hard to find sometimes as I had one that took me about 3 hard days of researching before I finally found the cause.1) Take note if the error always occurs within a certain area. My terrain.dll always occurred whenever I flew within 80nm of CYYC: always! Make sure to save your flight around the crash area to make it easier to repeat and test.2) If the errors always occurs within a certain area, inactivate all of your addon sceneries for that area. Fly again and see if the error disappears.3) If the error disappears, reactivate each addon one at a time and fly again.4) Activate each addon until you get the crash again and the last addon you reactivated before the crash should be the troublesome one.My advise above only holds true if you can reproduce the error in the exact same flight area. For my terrain.dll error around CYYC, it turned out it was a landclass bgl file addon for CYYC that was causing the issue.If the terrain.dll error occurs at random and at any place on the map, then other methods are needed.

Works very well in FSX. Thanks very much, Dutch!

FSHotSFX was the only reason I also installed 64-bit XP as a dual boot with Windows 7 64-bit on my new PC. Can't imagine using FS2004 without FSHotSFX. I've searched for equivalents of FSHotSFX, but nothing comes even close to the spool-up and reverser sounds that the program makes.

Right here: Gary Widup's KSTLAnd don't forget the update for the airport by Julio Birman which changes the old Northwest jetway signs with the new Delta logos: Update to Widup's KSTL

An error shows up when trying to run the install of FSHotSFX. It just doesn't install. I found the following on the internet about the error which I got as well when I tried to install it months ago:"FSHOTSFX failed to load properly.CHeck the FSHotSFX.log file in the install director. If you do not understand the error codes, email the log to support@FShotSeat.com.FSHotSFX will end now."Pressing OK gives the following message:"Run-time error '91':Object variable or With block variable not set"

I've been using the 197.45 drivers for a long time and have had absolutely no problems and good performance with my GTX 285 with an i7-920@4 Ghz and resolution at 1920x1080.I don't think I'll go to the 2xx drivers until nHancer is updated to handle them.

David,I was one of those that tried everything to get FSHotSFX to work in Windows 7 to no avail. I tried almost every trick in the book and nothing worked. If anyone else can get it to work, then they deserve massive kudos. Otherwise Windows 7 users are sadly out of luck with FSHotSFX.

FSHotSFX works just peachy in my XP 64-bit. I had to contact the support email for a new key and they responded back within a day.

Yes, too bad the developer gave up on the product as I consider it one of the best addons available for FS2004.

I have a dual boot PC with Windows XP 64-bit for only FS2004 (with FSHotSFX as Martin indicated) and also any games that won't run on Windows 7 like Madden NFL 2005. I use Windows 7 64-bit for everything else including FSX. On a 1.5GB hard drive, I partitioned it so that Windows 7 has 1.2GB and XP has 300GB to themselves. I then have FS2004 and FSX installed on the same Raptor hard drive which is obviously separate from the main drive.I have had no problems with either OS and have found drivers for everything I need in XP 64-bit. When XP 64-bit came out, drivers were hard to come by, but after reading up on the web about the now availability of 64-bit drivers, I went with XP 64-bit instead of 32-bit.It's really a judgement call, Martin. I really like Windows 7 and its new features plus it's super stable. But I would totally miss FSHotSFX when I use FS2004 as it's just not the same without it. If I had to give up FSHotSFX, I would probably give up FS2004 altogether and stick with FSX alone.

I can confirm that it does not work with Windows 7 after I tried many different things to no avail. I also know that someone else tried hard to get it to work in an XP virtual machine under Windows 7 and it didn't work that well. Like you Martin, I like FSHotSFX so much that my new PC is a dual boot with Windows 7 for FSX and then XP for FS2004 with FSHotSFX.

I just bought a Samsung 23" LED monitor to replace my old 19" non-widescreen and I don't know if like going to widescreen or not. It just seems that the screen is too big and that my eyes seem to want to dart all other the place. I understand that most 2D panels will stretched in widescreen unless specifically made for it, but the outside of the plane looks great. But I'm really having trouble getting used to the larger and wider screen. I've only had the new monitor for two days and I have two weeks to return it. A couple of people have told me that it will take me some time to get used to the new screen and that I'll never want to go back to a square monitor. I'm hoping that is the case with me. But has anyone here ever gone to widescreen and ended up regretting it later and returned back to a smaller square monitor?Many thanks for any and all replies.