Hmmm..? Agree? Not really. But I'm buzy at work, so won't post a long story!I have W7 and XP as doubleboot with FSX on both.W7 64 is a special "Nvidia 7 Edition" - slimmed and trimmed, it works OK, but not like XP.My XP 64 is the "Superior" edition, 120 Mb footprint on the OS, Google it...Both OS's of course registered with keys and what not... :(

So I googled as requested and it turns out that both are tweaked to death operating systems by self proclaimed "experts" and pirates (included serials and removed online activation) :(Nothing to brag about

I'm not trying to find the Holy Grail by looking here. I am just trying to find something that can cure the black screens and disappearing textures at the end of a flight. I can have a completely smooth flight for several hours only to find missing or corrupted scenery elements upon landing (missing ai, missing jetways, invisable ui aircraft...). Right now the only true solution I have found is ditch W7 - not an option. I have too much time invested in this current install and too little time to redo things. I need a fix (or workaround) for my current OS and the only way we will discover one is by experimenting.Nick is an amazing resource and his guides are a must read. I can't tell you home much he helped my when I was setting up my rig. The one point I missed, however, is don't get Windows 7, get XP64. I know this now. That being said, his guides are advertised to get you in the ballpark (YMMV) and they don't apply to Windows 7. Since W7 will be the OS of choice in the future, we need to figure something out. If we wait for MS to do it, we will all be siting at home with $2,000 paperweights. Right now, I am at the point that I would urinate on my computer if I thought it would help.There is something up with Windows 7 and I am sure there is a fix but the only way we will get there is to understand the problem. Trial and error is a lot better than doing nothing at all. Since everything here is easily reversible and easy to test, I see no harm.I can say that after lowering bufferpools to 300, I was able to complete a flight. I still have to test it a little more as I changed a couple other settings at the same time (I know this is a no no). I have already uninstalled my sound card and reverted back to on board sound with MS drivers and that didn't help. Since I have tried onboard with Soundmax, onboard with MS and a PCI sound card, I think the sound has nothing to do with the problem.A few settings I needs to check out but have little time to test in the next few weeks:I noticed in another thread that there are power settings in W7 - My rig was set to balanced but I changed it to performance before the successful flight.During many of the bad flights I was using HD clouds. The successful flight used 1024 clouds.I was also using a tweak to increase cloud coverage so that overcast displays as overcast - MAX_CLOUD_COVERAGE=12. I changed it back to 8 for the successful flight.As it stands, any of these 4 things or combination of settings (bufferpools, power settings, HD clouds or cloud coverage) could be cause of the texture corruption. Even if I can stop the texture corruption, it would still be nice to know why it is happening and how it can be avoided.

Hmmm..? Agree? Not really. But I'm buzy at work, so won't post a long story!I have W7 and XP as doubleboot with FSX on both.W7 64 is a special "Nvidia 7 Edition" - slimmed and trimmed, it works OK, but not like XP.My XP 64 is the "Superior" edition, 120 Mb footprint on the OS, Google it...Both OS's of course registered with keys and what not... :(

HelloWhy not just BUY the operating systems instead of stealing them ?

Stealing them?Would I post here if they were stolen?Come on folks, a bit too sensitive I think!I use the keys for my PAID and bloated, overloaded with junk, ordinary OS's.What's wrong with a little sharing among friends.This thread is named "The Holy Grail of FSX performance" - people should be ashamed, to use a mystical and holy symbol like The Grail in connection with a flightsim!Are people out of their freaking minds?? :(

Stealing them?Would I post here if they were stolen?Come on folks, a bit too sensitive I think!I use the keys for my PAID and bloated, overloaded with junk, ordinary OS's.What's wrong with a little sharing among friends.This thread is named "The Holy Grail of FSX performance" - people should be ashamed, to use a mystical and holy symbol like The Grail in connection with a flightsim!Are people out of their freaking minds?? :(

HelloFSXBuster , admitting to using pirated operating systems is not the cleverest thing to do on these forums.In the last two days you have called the marketing director of a major FS publishing house a crook (do you spot any irony there).Threatened a long standing member with physical violence and then in a piece of classic comedy admit to using pirated software then complaining that your windows 7 did not work properly.Personally I hope the mods let you hang around a bit longer just for the entertainment value alone.But I would not bet money on it.

I'm not trying to find the Holy Grail by looking here. I am just trying to find something that can cure the black screens and disappearing textures at the end of a flight. I can have a completely smooth flight for several hours only to find missing or corrupted scenery elements upon landing (missing ai, missing jetways, invisable ui aircraft...). Right now the only true solution I have found is ditch W7 - not an option. I have too much time invested in this current install and too little time to redo things. I need a fix (or workaround) for my current OS and the only way we will discover one is by experimenting.Nick is an amazing resource and his guides are a must read. I can't tell you home much he helped my when I was setting up my rig. The one point I missed, however, is don't get Windows 7, get XP64. I know this now. That being said, his guides are advertised to get you in the ballpark (YMMV) and they don't apply to Windows 7. Since W7 will be the OS of choice in the future, we need to figure something out. If we wait for MS to do it, we will all be siting at home with $2,000 paperweights. Right now, I am at the point that I would urinate on my computer if I thought it would help.There is something up with Windows 7 and I am sure there is a fix but the only way we will get there is to understand the problem. Trial and error is a lot better than doing nothing at all. Since everything here is easily reversible and easy to test, I see no harm.I can say that after lowering bufferpools to 300, I was able to complete a flight. I still have to test it a little more as I changed a couple other settings at the same time (I know this is a no no). I have already uninstalled my sound card and reverted back to on board sound with MS drivers and that didn't help. Since I have tried onboard with Soundmax, onboard with MS and a PCI sound card, I think the sound has nothing to do with the problem.A few settings I needs to check out but have little time to test in the next few weeks:I noticed in another thread that there are power settings in W7 - My rig was set to balanced but I changed it to performance before the successful flight.During many of the bad flights I was using HD clouds. The successful flight used 1024 clouds.I was also using a tweak to increase cloud coverage so that overcast displays as overcast - MAX_CLOUD_COVERAGE=12. I changed it back to 8 for the successful flight.As it stands, any of these 4 things or combination of settings (bufferpools, power settings, HD clouds or cloud coverage) could be cause of the texture corruption. Even if I can stop the texture corruption, it would still be nice to know why it is happening and how it can be avoided.

Same here with BS, testing having FSX in XP-SP3 compatibiliy mode and I cant get it to BS, but testing is not final and it yet has to tested as to FPS in a canned flight, aso tested for ImageQ...But give it a wirl yourself and see if it helps.

Amazing! 5 pages of pure BS due to semantics. The OP posting (initially) the "Holy Grail", J van E posting the "W7 is THE OS", etc, etc.In all this time have we not finally realized that EACH SYSTEM is different and will react differently to each tweak?Yes, NickN's guides don't delve into SSD and W7 at this point but what I walked away with in my conversations with Nick is that you need to get the comoponents of your system in balance. That point will be different for everyone. For example, on my system - XP64 - GTX280 - 4G 1700 8-8-8-24 1T - my cpu speed is BEST at 3.88ghz. I can easily go to 4 and pass all the benches BUT FSX doesn't like it - on MY system - 3.88 is the sweet spot.Take the guides as a starting point and make adjustments from there.The OP says the BP=0 works on his system - setting Water to 2High works - who am I to tell him it doesn't? Well, it doesn't work for me and it "shouldn't" work for him but it does - ergo - if you have the same things going on in your system that the OP has in his, it MIGHT help you. If it doesn't - it doesn't mean that he is full of it, it just means that it works for him and that he put an unfortunate spin on the concept with the "holy grail" part.All *I* know is that my system runs FSX just the way I like it and I now spend more time flying that I do tweaking.What I'd like to see happen from this thread - and if past history is any measure it won't, is for people to feel free to post a tweak that works for them *BUT* with the caveat in BIG BOLD LETTERS that it works on MY system.Just mho,Vic

I noticed in another thread that there are power settings in W7 - My rig was set to balanced but I changed it to performance before the successful flight.During many of the bad flights I was using HD clouds. The successful flight used 1024 clouds.I was also using a tweak to increase cloud coverage so that overcast displays as overcast - MAX_CLOUD_COVERAGE=12. I changed it back to 8 for the successful flight.As it stands, any of these 4 things or combination of settings (bufferpools, power settings, HD clouds or cloud coverage) could be cause of the texture corruption. Even if I can stop the texture corruption, it would still be nice to know why it is happening and how it can be avoided.

Well, all those things you mentioned make clear that there are 'tweaks' and there are 'tweaks'. :( I only use the kind of tweaks that makes FSX perform better, not worse... So for me no HD clouds, no more cloud coverage, etc.: when using things like that you KNOW you are making things harder for your computer! I am sure that, depending on your computer, these things could cause texture corruption. Now that you've disabled those options, the best thing to do is try various BP settings.If 300 works for you now, try something a bit lower or a bit higher and see where things go wrong again. You have to find your own sweet spot.

Advise?You are shooting with a pumpgun, 360 degrees around you, BLINDFOLDED!Sure, something will fall from the sky then, good hunting...

didn't notice the 'Joined: 13-December 09' in your profile. You almost got me! no further comments needed ;)

Fair enough, let's do that!OK, time to stop looking for "The Ultimate FSX Truth" out there.Each simmer has his own individual truth and it's OK for him to have it, and nobody should give him a friendly wink, wink, nudge, nudge or a kick somewhere, telling him that he's WRONG!I have my Sim-Truth and you have yours!BTW, I would never tell how excellent my crappy HP 2.6 Ghz something PC performs with FSX, you would think I was joking. I've tried every conceivable tweak out there, and nothing can compare with the advise from NickN.

Stealing them?Would I post here if they were stolen?Come on folks, a bit too sensitive I think!I use the keys for my PAID and bloated, overloaded with junk, ordinary OS's.What's wrong with a little sharing among friends.This thread is named "The Holy Grail of FSX performance" - people should be ashamed, to use a mystical and holy symbol like The Grail in connection with a flightsim!Are people out of their freaking minds?? :(

What are you "sharing among friends"?

...need to get the comoponents of your system in balance.

That's it! Balance - IOW find the slowest component in your setup and cater to it.jja

Hi, just today I was trying to reduce flickering, mainly at distance, and using nhancer I teste bias to 0.125 and 0.250 what helped but introduced some corruption in FSX on screen texts. I returned bias to 0.00 and set antialias to combined 8x and anisotropic to 12x what gave me a good result at my resolution (1680x1050)...also, clamp is on and filtering is set to high quality.. in a GTX 275. BTW I'm using BP at 5000000. After each nhancer change, FSX must be restarted for see the effect.Ulisses

Thanks! I will give it another try.EDIT:When i was using XP and my older PCs i thought all tweaks are BS but since i'm using the GTX260 and Win7 i have to tweak to avoid sound problems because even the default BP value is leading to sound problems on my system.I still have to find the perfect value to avoid sound issues and flashing squares. So i'm thankful for all contributions, no matter how crazy they sound.

To me the Holy Grail to FSX is having FS 2004 on your other harddrive also. :( I do think if you let it FSX could drive you bonkers.So when it crashes or gives you problems go to FS9 for a quick spin.I did try the 0 poolsize thing it seems to be about the same fo me in FSX using DX10.

I have FS9 and FSX on same drive, with occasional crash (black screen) when loading FS9 ported over aircraft in FSX if panel is 'not right'. Change panel and everthing is back to normal. What I came in here to do is show how you can have a 'stupid old rig' and still get GOOD performance (29-30 fps, locked at 30) from FSX. And before I give any advice (not going to - please refer to NickN tweaking guide) is perhaps suggest that in this type post that the poster show us his specs BEFORE he says anything. (Run 'dxdiag' to get info, and copy/paste relevant 'tweak' add from fsx.cfg ('prnscrn' and make jpg then post). Just my 2 cents. Here are my specs.CBNapamule