May 12, 201313 yr When editing the FSX.cfg file 1. does it matter if there are empty lines between entries? 2. is the syntax sensitive to upper case vs lower case? 3. can you include some kind of non-alphanumeric character for formatting purposes, such as an underscore line ________________________________________________ 4. is it possible to repeat sections throughout, or do all the instructions of a certain type have to be grouped together example -- is it permissible to do something like this: [display] WideViewAspect=True [main] disablepreload=1 [display] upper_framerate_limit=30 Vic
May 12, 201313 yr When editing the FSX.cfg file 1. does it matter if there are empty lines between entries? A- Nope 2. is the syntax sensitive to upper case vs lower case? A-Nope 3. can you include some kind of non-alphanumeric character for formatting purposes, such as an underscore line ________________________________________________ A-Should work, I know it will if you proceed that line with "//", such as... //_________________________ 4. is it possible to repeat sections throughout, or do all the instructions of a certain type have to be grouped together example -- is it permissible to do something like this: [display] WideViewAspect=True [main] disablepreload=1 [display] upper_framerate_limit=30 A- Don't know. I would keep them together. You could easily make a backup and test to see if this will work, using your example to see what the framerate shows in the sim. regards, Joe The best gift you can give your children is your time.
May 13, 201313 yr Author is it possible to repeat sections throughout, or do all the instructions of a certain type have to be grouped togetherexample -- is it permissible to do something like this:[display]WideViewAspect=True[main]disablepreload=1[display]upper_framerate_limit=30 It doesn't work exactly -- only partially. FSX makes further adjustments to the .cfg file after your modification, adding what I think are default values to fill out the section that you added. So you end up with, in this case, two [Display] sections, one with values that you had already had and the other with default values. I'm not sure which of those values take precedence when you then subsequently rerun FSX. Vic
May 14, 201313 yr You can also add a comment at the end of a normal line of code. Everything after the double forward slash is ignored: RUNWAY_LIGHTS_APPROACH_SCALAR=1.6 // this scales the approach light bars
May 14, 201313 yr You should have only one [display] section, and up to two [display device xxx] sections. One for dx9 and, maybe, one for dx10. Dave
May 14, 201313 yr Author The reason I was asking about that is that it would be convenient to be able to put all of your changes in one place (just deleting the corresponding lines from the other sections) example: //modifications [Display] WideViewAspect=True [Main] DisablePreload=1 [Graphics] HighMemFix=1 //Default Settings [Display] ... [Main] ... [Graphics] ... Then if you wanted to make any additional changes, you could very quickly find what changes you had already made in that file. Vic
May 14, 201313 yr This is a good thread. I never thought about putting blank lines in the file to further separate sections.
May 14, 201313 yr The reason I was asking about that is that it would be convenient to be able to put all of your changes in one place (just deleting the corresponding lines from the other sections) example: //modifications [Display] WideViewAspect=True [Main] DisablePreload=1 [Graphics] HighMemFix=1 //Default Settings [Display] ... [Main] ... [Graphics] ... Then if you wanted to make any additional changes, you could very quickly find what changes you had already made in that file. What I do is... [Graphics] HighMemFix=1 //my initials To find any of my hand edits I search for my initials. regards, Joe The best gift you can give your children is your time.
May 14, 201313 yr [sections] should not be duplicated. There is no assurance that FSX will search for more than one so it's likely that only those values in the first [section] will be read with the others being ignored.. Gerry Howard
May 14, 201313 yr One thing I've been hunting down for a while is a list of equivalent numeric values in the .cfg for the slider positions in FSX Settings. It would be nice to have a complete list of these so you could make most changes inside the config. For example these few that I've been able to find: Mesh_Resolution=17 = 305m18 = 152m19 = 76m20 = 38m21 = 19m22 = 10m23 = 5m24 = 2m25 = 1mTexture_Resolution=22 = 10m23 = 5m24 = 2m25 = 1m26 = 60cm27 = 30cm28 = 15cm29 = 7cm CLOUD_DRAW_DISTANCE=1 = 40mi2 = 50mi3 = 60mi <----------------- ZERO SLIDER4 = 70mi5 = 80mi6 = 90mi7 = 100mi8 = 110mi <----------------100% SLIDER Also, you can easily keep track of changes you make along with annotations while keeping all of the settings together under their respective groupings. Just add lines like this at the top of the config file: // 20130504: Changed [JOB_SCHEDULER] AffinityMask from 244 to 84 per Word Not Allowed's guide// 20130504: Changed [DISPLAY] Texture_Bandwidth_Mult from 120 to 40 per Word Not Allowed's guide// 20130504: Changed [JOB_SCHEDULER] AffinityMask from 84 back to 244. Poor performance at 84. - Jev McKee, AVSIM member since 2006. Specs: i7-2600K oc to 4.7GHz, 8GB, GTX580-1.5GB, 512GB SSD, Saitek Pro Flight Yoke System, FSX-Acceleration
May 15, 201313 yr Author Also, you can easily keep track of changes you make along with annotations while keeping all of the settings together under their respective groupings. Just add lines like this at the top of the config file:// 20130504: Changed [JOB_SCHEDULER] AffinityMask from 244 to 84 per Word Not Allowed's guide This is how I've decided to do it. Vic
Create an account or sign in to comment