Hi,Like many of us, I suspect ;) adjustments/tweaks are made in FS9.cfg without really understanding the whys and wherefores. For example, the following 3 entries are often recommended, usually without explanation:RenderToTexture=0TextureAGP=0PanelAsTexture=0Now, if I remember correctly, the PanelAsTexture=0 line sharpened up either the 2D or VC, I forget which, but what exactly does this switch do at hardware/software level?The other lines also remain a mystery, but there they are, added to my FS9.cfg. Why did I do it? I haven't a clue...LOL ;)*********************************************************Now, in return, I can help those of you anxious to get Concorde up and flying again in FS2004.Install the FsFrance's Profect Mach2 Concorde, including Pedro's enhancements (http://fsfrance.free.fr/Mach2/Main_eng.htm). Then revert back to the Concorde.air from the original Concordebase executable (Just point the installer to a temp folder and get the file from there). This eliminates the crazy uncontrollable yawing and subsequent flat spinning before crashing that occurs soon after takeoff).She is a bit of a dog to get in the air (some work required there to the airfile) but once airborne and trimmed out she looks and flies great AND the autopilot seems to be ok. After creating a flight plan I flew all the way from KSEA to KABQ under IFR and the whole flight, including an elegant smooth landing, went without a hitch.After having mourned seeing Concorde G-BOAE land and takeoff for the last time at EGPH I returned home desperate to see her again in flight. The Project Mach2 creation is just about as good as you are likely to get at the moment and I believe it is a Gmax model. Finally, I noted that there was a delay loading the textures while switching from the 2D to the 3D(VC). This appears to have been eliminated by simply increasing my AGP aperture from 128MB to 256MB. Another of those unexplained mysteries! There is still a short delay loading the 2D side views after looking straight ahead for several minutes. Still, that I can live with. Otherwise, everything seems to work (including animated wipers that I can't seem to switch off) and while in VC mode with ActiveCamera installed you can go for a walk down the isle to the back of the plane. If you have never been on Concorde, I can assure you that this is the next best thing.*******************************************************Right, in case, dear reader, you have forgotten the original reason for this post (LOL), those arcane entries in FS9.cfg?Mike :-wave

Lets see if I can get 2 out of 3 right.. :-)On my system, the PanelAsTexture line fixed the 2d panel in FS9, where I was getting an ugly black border around the Yoke that was overlayed over the panel. (Flight1 Meridian). Now, it looks like it did in FS2002.As best I know, the TextureAGP line determines if the AGP cards's capability to store textures in main memory should be enabled.I have never found this capability to do any good on my system, but having this switch set or not, seems to make no difference in framerates, so I ignore it..As for the RenderToTexture line.. there is a setting in FS9 under display hardware properties that is called just that, and is equivalent to FS2002's multitexturing option... is it reasonable to assume that this overrides whatever you set it to in FS9?

In case any of you want to try the AGP aperture thingy I thought I should include my system specs:P4 2.4GHz (400FSB), 1Gig PC2100 DDR Crucial, ATI Radeon 9800 Pro 128MB (Omega 2.4.96b), Gigabyte GA-8IRXP MoBo, Ultra-Quiet PSU 400W, WinXP Home (SP1), DirectX 9.0bJudging by the number of views (>100) versus the number of replies (0) so far, I guess most of you share my ignorance! So, where are the gurus who can relieve our frustrations? :)Mike :-wave

Hi,A simplified explanation of the AGP Aperture Size setting in the BIOS is that it sets aside/allocates an amount of your System RAM that can be used for texture storage when the Video Cards RAM becomes filled up. This comes more into play when your video card doesn't have very much RAM. Also, when running WinXP and FS2004 you need to have (probably) 1 GB of RAM or more when setting this size to 256 to make sure you have enough RAM left for system usage. Otherwise, if you have a lower amount of System RAM you will begin stealing RAM that is needed for System usage (WinXP, FS2004, ect.) and begin seeing a degrade in performance as that code is swapped out for texture storage. I set this to 256 on my system quite some time ago and thought I would not see much of a difference in FS2004 if any, because, like you I have a 128 MB video card. But FS2004 is not your average game and I was wrong. I got an overall smoother experience after raising the APG Aperture size from 128 to 256. For the most part, raising the AGP Aperture size does not increase your FPS, but gives you a smoother experience, such as when switching views, or turning when flying. For a more technical and detailed explanation on this BIOS function visit www.rojackpot.com and look at their BIOS Optimization Guide(BOG). It does more than my simplified explanation given here. This is also in my 'FS2004 and WinXP Optimization Guide' post found here(which could use a little updating)...http://forums.avsim.net/dcboard.php?az=sho...topic_id=149511Cheers,Jim

I have a Dell 8300 2.6 gig, I don't have the option in my BIOS to change my AGP Aperture size.....

Hmmm, interesting Dillon. I don't have the option to turn 'Fast Writes' on/off in my BIOS. But I do have the option as a checkbox in 'Display Properties --> Settings Tab --> Advanced --> SmartGart Tab'. BIOS options and settings differ quite a bit from system to system, but I would think that the majority of people have the AGP Aperture setting option in their BIOS, as I had it even in my old 800 MHz PIII P3V4X motherboard.Jim

The AGP aperture is sometimes found under slightly different names in some BIOSs- for instance "Graphics Window size" and other variations on the theme.Like Jim says ,it would be surprising if it wasn't there under some name or other.I seem to remember when playing around with an old(1997/8) PC bought at a garage sale that the Phoenix BIOS called it something wierd like "Graphics hole".CheersDave

"DISAPPOINTED"

Guys, the bios thats shipping with these new Dells is very basic... If somebody else with a Dell can conferm, it's not there... It's almost like dealing with a Celeron.

Hi Bert, "As for the RenderToTexture line.. there is a setting in FS9 under display hardware properties that is called just that, and is equivalent to FS2002's multitexturing option... is it reasonable to assume that this overrides whatever you set it to in FS9?`RenderToTexture line is not equivalent to FS2002's multitexturing option.Multitexturing in Fs2004. It's the terrain details slider in fs2004 DisplayTerrain details Slider to None = No MultitextureTerrain details Slider to Land Only = Multitexture EnabledThanksChris Willis[link:fsw.simflight.com/FSWMenuFsSim.html]Clouds And Addons For MsFshttp://fsw.simflight.com/fsw.jpg

Ah well, can't please everyone! I guess none of this is news to you - sorry m8 :(Mike

Hi Jim,Thanks for taking the trouble. I'm reasonably familiar with much of the content of your full explanation.However, if we accept:"A simplified explanation of the AGP Aperture Size setting in the BIOS is that it sets aside/allocates an amount of your System RAM that can be used for texture storage when the Video Cards RAM becomes filled up."......does the line 'TextureAGP=0' disable this capability in system ram and force texture storeage onboard the graphics card? I'm just trying to get a handle on this one before deciding whether or not to delete the line.It was interesting to discover that increasing the AGP aperture (with all three of the above lines in my original post in place) from 128 to 256MB in some way allowed faster loading of the VC textures. Switching from the 2D panel to the 3D/VC is now instantaneous whereas before there was a short lag as the textures were reloaded from the HD. Seems to suggest that the VC textures are being retained in graphics memory.The same is not happening with the side views from the 2D cockpit, but this is probably explained on the basis that the delay is caused by virtue of the fact that as the a/c progresses new ground textures are needing to be loaded. After initial loading of the side views view switching is instant. However, if you look forward for a few minutes during a flight and then switch to a side view there is, once again, a short lag as fresh texture loading occurs. There may be a direct correlation with the complexity of the a/c panel and the amount of graphic card memory useage as it is not really noticeable while flying the default a/c. We're talking PM2 Concorde here and a mighty fine example of a/c and panel design :)Regards,Mike

Hi Bert,Thanks for your input."As best I know, the TextureAGP line determines if the AGP cards's capability to store textures in main memory should be enabled."....can anyone confirm this is the case or is it the other way around as per my speculation in my rambling reply to OneTinSoldier?Mike

Hi Chris,So Chris, what does the RenderToTexture=0 line in fact do?And, while I've got your attention ;) can you provide a definitive explanation for the purpose of the other two lines:RenderToTexture=0PanelAsTexture=0Regards,Mike

>Hi Jim,>>Thanks for taking the trouble. I'm reasonably familiar with>much of the content of your full explanation.>>However, if we accept:>>"A simplified explanation of the AGP Aperture Size setting in>the BIOS is that it sets aside/allocates an amount of your>System RAM that can be used for texture storage when the Video>Cards RAM becomes filled up.">>......does the line 'TextureAGP=0' disable this capability in>system ram and force texture storeage onboard the graphics>card? I'm just trying to get a handle on this one before>deciding whether or not to delete the line.>>It was interesting to discover that increasing the AGP>aperture (with all three of the above lines in my original>post in place) from 128 to 256MB in some way allowed faster>loading of the VC textures. Switching from the 2D panel to the>3D/VC is now instantaneous whereas before there was a short>lag as the textures were reloaded from the HD. Seems to>suggest that the VC textures are being retained in graphics>memory.>>The same is not happening with the side views from the 2D>cockpit, but this is probably explained on the basis that the>delay is caused by virtue of the fact that as the a/c>progresses new ground textures are needing to be loaded. After>initial loading of the side views view switching is instant.>However, if you look forward for a few minutes during a flight>and then switch to a side view there is, once again, a short>lag as fresh texture loading occurs. There may be a direct>correlation with the complexity of the a/c panel and the>amount of graphic card memory useage as it is not really>noticeable while flying the default a/c. We're talking PM2>Concorde here and a mighty fine example of a/c and panel>design :)>>Regards,>>MikeHi Mike,I just want to concur with everything you said here except maybe one thing. And I want to say that I notice pretty much the exact same things with texture performance loading."Switching from the 2D panel to the 3D/VC is now instantaneous whereas before there was a short lag as the textures were reloaded from the HD. Seems to suggest that the VC textures are being retained in graphics memory."From my short explanation of the Aperture setting I believe what is happening here is that that textures are not having to be reloaded from your HD becasue they being retained in 'System Memory' that has been allocated by the higher Aperture size you set. Therefor the graphics card can load them extremly quick from your system memory and not have to go to the HD now.Cheers, :)Jim