lcole98296

I'm hearing a lot here about Airbus X as well as FSL Airbus, which I hadn't heard of yet. At the risk of being laughed out of the forum, what are the good points with these two and what are the problems with the Wilco Airbus PIC and the Wilco PIC Evolution? This is the one I have, but I haven't flown it much, preferring Boeing aircraft.

I have a Samsung 500 GB SSD hard drive that I intended to use only as my System (C:) drive and for FSX. It soon became apparent that this drive was not large enough for my needs. So I added a "normal", but fast, 2 TB hard drive (7200 RPM), and reinstalled FSX on it. My plan is to only install flight sim related software on it. Have currently used 269 GB, and still have 1.55 TB available. I'm thinking this will be adequate for the forseeable future.

Lotus did an awesome job with this aircraft. Great tutorial video too. Part one of three attached. Watch all three in 720p HD, full screen.

The average user is best served by LEAVING THE PAGE FILE ALONE. Windows 7 does an excellent job of managing the page file settings for most people. Eliminate it and the main danger is that if you do run out of memory, your system will crash. Ordinarily, your system would slow dramatically as it pages to the swap file, at which point you will notice something is wrong. With no pagefile, it will crash with warning. However with 8GB, you have much less chance of that happening (running games etc) unless you get a bad memory leak from an app or program. They would have to be 64bit though due to the 2GB 32 bit standard restriction or have multiple 32 bit apps leak (not very likely). If you are running memory intensive apps that can use 8GB+, you shouldnt disable the pagefile.

fltsimguy, There's no problem with your setup. It's just that KSEA is an extremely dense scenery area, and no one, even with a top-of-the-line computer, is going to get maximum FPS in that area. Note that in my previous post, I said that, "once I get out of downtown Seattle, FPS consistently stays up around 30". This bothered me for a long time, as I live in the Seattle area and want to fly out of here. I couldn't understand why everyone else claimed to have such great FPS, but mine was so slow. Then I realized you can't judge your computer's abilities based on the FPS you see on the runway or in the air near Seattle. Flying in a more unpopulated area will give you a more accurate feel as to what your PC can do. Myself? Sitting on Rwy 31L at Boeing Field, my FPS pretty much hovers between 14 and 24 frames per second.

Thanks Jim. I have no idea how my pagefile got set to 1024. I don't know the difference between automatic & system managed either. Hopefully, someone more knowledgeable will chime in. Re: Bjote, my system is running much better since I discarded his changes & went to Word Not Allowed's. By the way, when I originally posted this, I had included a link to Word Not Allowed's recommendations. AVSIM would not allow it, saying something like that link was not allowable. My post would not go online till I deleted the link. What's up with that?

This probably won't work if you have all your PC settings at default. I thought mine were, but just checked the size of my pagefile. To my surprise, it was set for a CUSTOM size of 1024 MB, which is way too low for my 8 GB system. I changed the setting from "Custom size" to "Automatically manage paging file size for all drives". Now, it says my pagefile is set at 8192 MB. What a huge difference. I'd set my FSX up to Word Not Allowed's recommendations, but was still getting stutters, and FSX was struggling to maintain the 30 FPS locked target frame rate. Now, it's smooth as silk, and once I get out of downtown Seattle (default start is Boeing Field), FPS consistently stays up around 30. To check the size of your pagefile (I have WIN 7 - 64), go to Control Panel/System/Advanced System Settings/Advanced, and then select "Settings" in the "Performance" field. Then click on "Advanced", and in the "Virtual Memory" field, select "Change". Note what it says is currently allocated. If it's not checked, place a checkmark in "Automatically manage paging file for all drives". Then "OK" & reboot. Come back to "Virtual Memory" and hopefully, if yours was set too low, it'll be at a more reasonable size. P.S. Re: the above referenced "Word Not Allowed" recommendations, the only difference I have compared to what he recommends is that I am not using "Bufferpools". He says that if you use his recommendation (poolsize=0) then you must have your water effects set at High 2.x or higher. That high of a setting slows down everything by several FPS for me, so while I placed the setting in my fsx.cfg, I have it "commented" out by placing 2 slashes (//) in front of both lines referencing bufferpools. P.P.S. If you have the Bjote tweaks in your fsx.cfg, try Word Not Allowed's instead. Save your fsx.cfg as another name, such as fsx.org.cfg. Then, with no fsx.cfg in your Appdata/Roaming/Microsoft/FSX folder. run FSX. A new, bare-bones fsg.cfg will be created. Use this one to add Word Not Allowed's tweaks. You might be surprised how much better FlightsimX runs.<br /><br />Intel I7 3770K CPU @ 3.50GHz overclocked to 3.9 GHz. Radeon HD 6850 graphics card moderately overclocked. 8 GB RAM. Windows 7 - 64 Home

Here's a little memory fix from Microsoft: http://support.microsoft.com/kb/947246 I did it using the "Fix It For Me" option. Also, read this thread, re: bcdedit, Starting at (currently) comment#18: http://forum.avsim.net/topic/402872-pmdg-737ngx-crash-to-desktop-when-choosing-end-flight-even-on-a-fresh-and-clean-windows-installation-some-interesting-facts-i-found/?p=2627134

{{ Make sure AA is turned off in the sim, and FXAA usage in Nvidia inspector is set to disallowed }} My graphics card is a Radeon HD 6850. Scrolled through this whole thread and did not find an answer to my questions, which are: Should anti-aliasing also be turned off in Catalyst Control Center? In regards to the above, is the anwer different depending if SMAA is enabled or disabled in SweetFX_settings.txt?

Haha - Took me a while to figure that out. I use Boeing Field, in Seattle, as my default airport. Couldn't figure out why my framerates were so low, compared to when I got out of town. Not really an issue anymore though, once I upgraded to an I-7 (3.5 - Overclocked to 4.2) & Redeon 6850.

At the time, the graphics were awesome. I had all the books by Charles Gulick. His writing style really got one into the sim, with all his adventures. I still have all his books. Considering trying some of those adventures in today's flightsim.

I have my FSX installed on a 250GB SSD (FSX, scenery, everything). Win 7 is there too. I install everything else not related to flightsim now on my old "C" drive, which is F: now. Flightsim loads much faster. Runs better (& faster) too. Running faster probably has a lot to do with the fact that I also upgraded to an AMD Radeon 6850 and an Intel I7 3.5 GHz processor. But the huge speedup in loading must be due to the solid state drive. I just wish that I would have gotten at least a 500GB drive though, as I see that someday soon, I could be running out of space. I would have thought that absurd back in the eighties when my Commodore Amiga was state of the art with a 40mhz Motorola 68030 processor, eight MB RAM, and an 80 MB hard drive. SubLogic's Flight Simulator II for the Amiga was miles ahead of the IBM compatible version of flightsim. My how times change.

{{Regret may be too strong, but the Dreamfleet Dakota was the only addon I had that couldn't make the transition to Win 7 x64. It did have a problem f me of the aft position light not showing correctly, but it still was good to fly while I was on XP.}} I have the Dreamfleet Dakota running perfectly on my Win7 - 64 setup. You have to replace all original RXP based gauges with the current GNS WAAS (payware) equivalents, and then editing the panel.cfg file. Make sure all UAC Windows security crap is disabled during installation & tweaking..

{{Just run the update and it will tell you, I just did }} Mosteen - I added to my post after you answered. Do you know if I'll have to go through the whole install process again? Edit - Never mind - I just tried the update and it told me it can't find my installation of the plane.

I wish they'd put the date on their updates. I don't recall if I've applied these latest updates or not. Anyone know if there's a way to tell what version you have? p.s. I recently reinstalled FSX, as I got a new processor, graphics card, and "C" drive (solid state). Can I just copy my PMDG 737s from my old "C" drive (now "F:") to my new C:/FSX/Simobjects/Airplanes, or will I have to reinstall them from scratch?