Consider this post for FSX newbie's, or as a reminder to do periodic FSX config file backups. If I am preaching to choir about this, then just ignore the rest of this post.

 

I have learned the value of saving periodic backups of my "fsx.cfg" file. This has saved my rear end on multiple occasions when something has polluted my current config file.

 

For newbie's, assuming that you are running Windows 7, click on the Start icon in lower left-hand corner, then where you see "Search programs and files" type in %appdata%. I then select the fsx.cfg file, and do a "Save As". I augment the file name by a meaningful scheme to include the date and a brief description of the backup. This puts the backup files in the same library as the fsx.cfg file. Please see samples below showing file names.

 

fsx.cfg

fsx.cfg 12-19-12 everything running OK

fsx.cfg 12-27-12 before install of xyz software

 

I am not suggesting that you use the same naming scheme, but something that works for you. By doing this every week or two, has enabled me to retrieve a fairly recent config file that I know was working at the time. Note that I most always do this before installing a piece of new FSX software.

 

Just yesterday, FSX wouldn't open as it said I was "out of memory". Yes I did reboot my computer first and still got the "out of memory" messages. So I first saved the current fsx.cfg file with an appropriate date and description, and then I retrieved the most recent backup of the fsx.cfg that I knew was working correctly and renamed it to "fsx.cfg" and my problem was solved.

 

This has been of invaluable help on multiple occasions!

You do not need to save your FSX.cfg. Some delete it occasionally, restart FSX and the config will always rebuild. Using older versions of FSX.cfg is not recommended and especially if you have to reinstall FSX you should start with a fresh config. Using an older version could cause problems. So if something nasty happens to your system and you lose the fsx.cfg, simply restart FSX and it will be rebuilt for you.

 

Regarding the out of memory messages. This is quite common with individuals who install the 32 bit version of Windows 7, Vista, or XP. The 64 bit version hands memory better than the 32 bit so that's why most flight simmers install the 64 bit version. To solve you out of memory problem, you need to employ the /3GB switch and it all depends on what OS you have installed. Here's a link to a description on how to do that - http://www.simforums.com/forums/topic29041.html. Scroll down to the Memory section which is not far from the top.

 

Best regards,

Jim

I keep a backup of my fsx.cfg and restore it with a batch file before starting the sim whenever something gets messed up. The only problem with "older versions" that I've run into is that sometimes when you restore the backup you have to "trust" things again if they've been added since the last backup was made; gauges, objectflow .dlls, etc. I usually update my backup whenever this happens by adding the new [Trusted] lines to my backup file.

 

Deleteing and rebuilding the FSX.cfg is a bad idea in my opinion unless you're working on a brand new fresh install of FSX or maybe if you've recently done a hardware upgrade. You'll loose all your special tweaks, graphic settings, etc, but worst of all you'll be clicking "run" and "trust" for an hour and a half before you get everything added back into the FSX.cfg the way it was before. What was that line again that stops the screen labels from displaying? Search the forums for an hour, oh yeah, "HideInfoText=1", close the sim, add the line, now how do I get the wide view thing going on? Search the forums for an hour, oh yeah, "WideViewAspect=True", close the sim, add the line... If you're lucky in about a month you'll finally get everything back the way you want it.

 

Making and keeping a backup of the fsx.cfg when everything is working right is a good plan as far as I'm concerned. My backup .cfg is a work in progress, I concentrate on setting it up so when I restore it everything gets adjusted just the way I want it. Any time I try a new tweak that becomes a "keeper" I add it to my backup file. I can experiment with settings in the sim until I have everything screwed up totally beyond repair, then just double click the batch file and everything returns to normal again.

 

Jim

Before a major install, I back up the fsx.cfg, the standard.xml, the dll.xml, sometimes the scenery.cfg, and also Fsuipc.ini (try the pain of losing that one, and I have before!). Additionally I have an entire backup of my whole installation that has saved my butt on a number of occasions, because you never know what can happen. For instance not even a week ago, I noticed that none of my beacon or strobe lights were working on any plane. I tracked the problem down to a missing FSX effects texture file (fx_2.bmp) that I can only assume must have gotten deleted by the uninstall of any one of several payware products (which is really sloppy form to mess with stock FSX files, developer guys). Thankfully it was only a matter of restoring that one file from backup.

You do not need to save your FSX.cfg. Some delete it occasionally, restart FSX and the config will always rebuild.

 

Firehawk44,

 

I am the first to admit that I am no expert on any of this. I just got back into flight sim about six months ago. If deleting the config file and letting it rebuild itself, will all of the changes I have put into it as gleaned from the NickN and Kostas sources still show up...or will I have to start over and re-add all of my tweaks. If I have to add the tweaks in each time, then that is kind of painful.

 

Also, why has my method worked for me numerous times in the last six months? Have I just been lucky?

pdx I also save different cfg files but may or may not use them mostly not - I use them for reference as to what I had tweaked before as a reminder so usually now just rebuild a new one and add from my old ones or just use bojoites tool and be done with.

To solve you out of memory problem, you need to employ the /3GB switch and it all depends on what OS you have installed

 

One more question for Firehawk44. Regarding the OOM error, I am running Windows 7 64 bit. The link you provided only makes reference to XP and Vista. Any thoughts about Windows 7 - 64 bit systems and OOM errors. Also, thanks for your reply --- I wasn't looking to cause problems for anyone.

One more question for Firehawk44. Regarding the OOM error, I am running Windows 7 64 bit. The link you provided only makes reference to XP and Vista. Any thoughts about Windows 7 - 64 bit systems and OOM errors. Also, thanks for your reply --- I wasn't looking to cause problems for anyone.

 

Vista and Windows 7 are nearly the same so you would use the rules for Vista. Nick just did not update that when Windows 7 was released. I did not know you were running a 64 bit OS (I strongly suggest all members post their system specs in the membership profile. Look at my specs in my sidebar for an example). There are OOM's in 64 bit systems but they are very rare. That's why I assumed (wrongly) that you had a 32 bit OS. The 64 bit OS provides better memory management. FSX can see up to 4GB of memory and any memory left over is taken by the OS. So, it is important you have more than 4GB's installed and I recommend at least 8GB. How much do you have installed?

 

I'm not the only one who recommends you not use an old FSX.cfg or use a saved FSX.cfg if you reinstall FSX. NickN, a Microsoft MVP and FSX Guru, stated it too in the link I provided above. At the top of the page he has a link to optimizing Windows 7 64 bit. You might want to download and run AppCrashView - http://www.nirsoft.n...crash_view.html and see what the OOM was all about. I would recommend too that you look in your Event Viewer as all of these types of events are recorded. To get to the Event Viewer, click on the Start button, type Event then look up in the Menu and click on Event Viewer. Once open, click on Custom, then Administrative Events. I like this view as it shows all the recent events from all of the Windows logs. It should give you a clue as to what might be malfunctioning in your system to cause and OOM when trying to start FSX.

 

will all of the changes I have put into it as gleaned from the NickN and Kostas sources still show up...or will I have to start over and re-add all of my tweaks. If I have to add the tweaks in each time, then that is kind of painful.

 

Painful, but there had to be a reason why you had to go to another FSX.cfg. When you have problems and you want to rebuild your FSX.cfg, the best method is to save your FSX.cfg to FSX.orig. Then restart FSX and let the config rebuild. You can then look in the original config and maybe copy and paste tweaks over to the new config but I wouldn't right away. You need to find out what's wrong with your FSX which is the reason why you wanted to install a new config. You can also start up FSX and, at the startup screen click on settings then Save. This will save your current FSX settings. I have several of these depending on the areas I'm flying in or the scenario. Word Not Allowed and NickN also have suggested certain configurations. For instance, if I recall correctly, Word Not Allowed recommends setting your FPS at 30. If you own Orbx/FTX scenery, they recommend Unlimited. So you could set up various configurations for several different products as they suggest. You could name one Firehawk44, er I mean Word Not Allowed, for his settings. Then one for Orbx/PNW, etc., etc. Then, you can load the appropriate config for the flight you will be taking. Some of the developers have already set up configs and, when you click on Load, they will be there if you have their products installed.

 

Hope this helps explain my rationales for my Post 2.

 

Best regards,

Jim

Firehawk44: Thanks for taking the time to provide detailed and excellent advice. I hope there are other Flight Simmers out there who will also benefit from the time you took to respond. Much appreciated!

pdx I also save different cfg files but may or may not use them mostly not - I use them for reference as to what I had tweaked before as a reminder so usually now just rebuild a new one and add from my old ones ...

 

That's exactly what i do to: i have a collection of 35 since i started with FSX, each one with (slightly or completely) different tweaking.

 

The first 15 with NickN and later Bojote's tweaking. Then 20 started from a fresch FSX.cfg with Word Not Allowed's method and several tryouts and variations on it.

 

At this moment completely back to 100% Word Not Allowed like it is now at:

 

http://#####...hardware-guide/

 

^_^

Firehawk44: Thanks for taking the time to provide detailed and excellent advice. I hope there are other Flight Simmers out there who will also benefit from the time you took to respond. Much appreciated!

 

Hey, that was nice of you to say this and I certainly appreciate it.

 

Best regards,

Jim