Hi everyone,I have been trying to solve the problem that bothers me for some time, since I finally got my new rig.First two scenery I installed was ORBX Tamworth and Harvery Bay.At first I was very impressed with the graphic my new system provided me, that was even more than I expected.Everything around the aircraft, at first, seemed, crystal clear, fps was so smooth. I am using Boyote's tweak with external fps limiter set at 30 fps, autogen is on very dense.After some time I have noticed that some texture in a far distance are not in hi res. Then found some discussions about LOD radius and change it to 8.5 which gave me excellent result with photo scenery texture but not with the texture of the Harvey Bay town, for example, where there are two many textures of the buildings, streets, parking places... Those hi res texture are loaded just to slowly. It is obvious they are in low res when the plane is even very close to them and become hi res when the plane is almost above them. This is pop up effect and suddenly they are loaded in full hi res texture, but really too late. My question: is there any tweak in fsx.cfg that would force hi res texture to load much earlier in there hi resolution. I have to mention that I tried to change every single line in fsx.cfg but nothing seems to work. Playing with texture max load, texture multiplier, lowering all settings in fsx... nothing helped at all. I am about to start thinking that is the way those sceneries are made and there is no way to change this, but it definitely looks to bad. I will try with some other scenery but I doubt it will help. I was thinking to buy ssd drive only for fsx but if this remains a problem I will not to waste my money. I would also like to know, while making a certain scenery, is there some determination that makes some texture to become hi res at a certain distance from the aircraft and there is no way to change that fix with any tweak? If that is the case, I will understand that I am asking to much from FSX.Thank you.

If you want to see the higher definition objects earlier, you have to reduce the demands on the CPU by moving some of the sliders to the left and reduce the LOD radius to something more manageable by your system.FSX loads the low res image, because it has no time to load the higher res one without slowing the frame rate to a crawl. When FSX has some time to spare, it updates some of the low res images to higher res, but it can happen that FSX never has enough time to spare and all textures remain lower res.

If you want to see the higher definition objects earlier, you have to reduce the demands on the CPU by moving some of the sliders to the left and reduce the LOD radius to something more manageable by your system.FSX loads the low res image, because it has no time to load the higher res one without slowing the frame rate to a crawl. When FSX has some time to spare, it updates some of the low res images to higher res, but it can happen that FSX never has enough time to spare and all textures remain lower res.

Thank you for reply.Belive me I did everything to relief the CPU. Put the sliders almost left, experimenting with fiber frame in fsx.cfg, using texture max load under both graphic and display section with 80, 100, 200, 300 multi in fsx.cfg, making my GPU take over most of the texture loading, lower LOD to 4.5, also add mipbias=6 line in fsx.cfg. Not to mention that have set all filtering using nvidia inspector, with of course 16x anisotropic. Pretty much everything I could think of but nothing helped.I have read somewhere when pause the sim texture are loaded after some time, but not in my case. They just remain low res until plane is closed to them. Still I haven't try with some other scenery apart from these two to check if situation is better. To be completely clear. This has got nothing with blurry texture, it is just transition from low to high resolution as it should be but not this late. It would be absolutely acceptable to happen much earlier, at far distance but not when this low res textures become to obvious. It is also strange that this exist only with urban texture but not with landscape which is crystal clear wherever I take a look.

Thank you for reply.Belive me I did everything to relief the CPU. Put the sliders almost left, experimenting with fiber frame in fsx.cfg, using texture max load under both graphic and display section with 80, 100, 200, 300 multi in fsx.cfg, making my GPU take over most of the texture loading, lower LOD to 4.5, also add mipbias=6 line in fsx.cfg. Not to mention that have set all filtering using nvidia inspector, with of course 16x anisotropic. Pretty much everything I could think of but nothing helped.I have read somewhere when pause the sim texture are loaded after some time, but not in my case. They just remain low res until plane is closed to them. Still I haven't try with some other scenery apart from these two to check if situation is better. To be completely clear. This has got nothing with blurry texture, it is just transition from low to high resolution as it should be but not this late. It would be absolutely acceptable to happen much earlier, at far distance but not when this low res textures become to obvious. It is also strange that this exist only with urban texture but not with landscape which is crystal clear wherever I take a look.

Urban textures seem to stress the system the most... this is a common problem.The two things that help on my system, are to lock the framerates at 30 within FSX,and to leave LOD_radius on 5.5.With framerates on Unlimited, texture loading in urban areas lags badly when the CPU gets busy..

I think I have finally found the answer for the problem. Unfortunately, as I supposed, this is due to limitation of the FSX itself, in fact it's autogen.Here is the final explanation for the problem that I have experienced so far:http://www.simforums...322.html#207322This finally clarifies why my textures looks fantastically clear, even at the greatest distance and, on the other hand, buildings and other autogen elements are in low res even at only 7 miles distance.Is there, maybe, any way to influence on autogen to start loading elements at distance further than 7 miles away.

I think I have finally found the answer for the problem. Unfortunately, as I supposed, this is due to limitation of the FSX itself, in fact it's autogen.Here is the final explanation for the problem that I have experienced so far:http://www.simforums...322.html#207322This finally clarifies why my textures looks fantastically clear, even at the greatest distance and, on the other hand, buildings and other autogen elements are in low res even at only 7 miles distance.Is there, maybe, any way to influence on autogen to start loading elements at distance further than 7 miles away.

Autogen is "buildings". You started out talking about "urban textures" - not the same thing.If all your textures are highest resolution at 7 miles out, you do not have a problem. :( Your original issue can be helped by limiting fps within FSX, rather than via an external limiter.For reasons that have never been explained, FSX uses a different algorithm for loading textures iffps are locked, rather than set at unlimited within FSX. The external limiter does not change this.BTW, the advice to get rid of road traffic (in your post) is a good suggestion since it eases the load on the CPU.

Autogen is "buildings". You started out talking about "urban textures" - not the same thing.If all your textures are highest resolution at 7 miles out, you do not have a problem. :( Your original issue can be helped by limiting fps within FSX, rather than via an external limiter.For reasons that have never been explained, FSX uses a different algorithm for loading textures iffps are locked, rather than set at unlimited within FSX. The external limiter does not change this.BTW, the advice to get rid of road traffic (in your post) is a good suggestion since it eases the load on the CPU.

Yes I have finally realized that I had a problem with autogen not textures. So shame to finally find out that fsx autogen has nothing with hardware and will always produce popping up the objects in front of the eyes.Simply can't believe that nothing has been possible to fix this problem for all these years. I have always thought that is due to my poor hardware but finally when I got myself a decent system this still exists. To bad to know.

Yes I have finally realized that I had a problem with autogen not textures. So shame to finally find out that fsx autogen has nothing with hardware and will always produce popping up the objects in front of the eyes.Simply can't believe that nothing has been possible to fix this problem for all these years. I have always thought that is due to my poor hardware but finally when I got myself a decent system this still exists. To bad to know.

The popping of Autogen (or batching of Autogen as the Aces team called it) was a compromiseby the development team, in order to get better performance. It was introduced with SP1&2.I most certainly hope that the new MS Flight will have this changed back, to fading in levelsof detail, just as the original release of FSX had it, or better.