Misty Moorings Forums
Return to Misty Moorings (FSX/P3D/MSFS2020) => Help and Troubleshooting => Topic started by: Infinityplusone on March 04, 2011, 12:20:35 PM
-
I have been having this problem ever since I did Jesus's online fsx.cfg tweaking tool. Textures load fine when im flying my cub since its a much slower aircraft. However, when I switch to my 185 the ground texture have a hard time keeping up and quickly become "blurry".
I cant for the life of me figure out what the tweak did or is trying to do that is causing this. The original file works fine, but gives a performance cut of at least half. I have tried removing lines, tweaking numbers, etc.
Im planning on upgrading the cpu from the e6400 to the e7600 soon (last upgrade i can make on this mobo before replacing) and that should help, but is there anything in the meantime that I can do?
-
Exactly the same problem for me too, the ground textures load really slowly, have you tried asking Bojote himself? (I am getting to the point of asking but haven't yet)
-
Hmmm... must be system specific - I got an improvement on scenery loads.Well, I usually only fly low and slow, so that is subjective I guess. I very rarely, if ever, fly a blowtorch simply because my system as such, is not powerful enough to reload scenery fast.
And if I do, I have to screw back on detail - and that is far more important than speed.
I will watch this with bated breath.
-
I had this very bad a while back. Just looking at my FSX.cfg file to see what I edited to correct it somewhat.
Okay I think it was the:
TEXTURE_BANDWIDTH_MULTI=40 line that was causing me the issues.
Or it could have been:
FIBER_FRAME_TIME_FRACTION=0.33 line.
Either way pop along to HERE (http://www.flightsimworld.com/forums/index.php?showtopic=92583) for explanations. Hopefully you will sort something out. Mine still gets very bad when I fly fast jets, but it's ok upto around 200 knots.
-
Quick update after a day full of tedious trial and error.
I have managed to improve my situation concerning the slow loading textures. A couple of things I did were:
1) Set my RejectThreshold to 250000 vs the 101xxx that it was at.
2) Stopped using the external FPS limiter and set FSX to a limit of 99 within the game.
*This one seems counterintuitive to all the tweaks and fixes I have read, but around 170mph I get some decent loading of textures. Above that is still a problem.
I did this testing at Friday Harbor which is within my Orbx Library territory, so tomorrow I will move outside of that and try again.
It did seem that not using the external fps limiter made a drastic improvement in texture loading.
Hope to have some more luck tomorrow.
-
RE: Blurry ground textures.
I have not really tested this carefully yet but I have been flying in PNW scenery for a few days checking out Mike Mann's Tofino and Gold River Float bases on Vancouver Is. I have been using both the default Beaver (Misty repaint) and the Carenado C185 float plane.
My normal ride is the Carenado C185 Tundra Tire for RTMM scenery but due to Mike Mann's scenery being water based I used the default Beaver and the C185 floatplane. I have noticed that it "seemed" that with the C185 the ground texture would become blurry and stay that way quite quickly. With the default Beaver although I do get a very slight pop-in of scenery loading ahead of the airplane for the most part the textures stay sharp and do not 'go blurry' in PNW. As I mentioned this is mostly my perception and not really tested as yet but there is a difference in the two A/C and blurriness.
8)
-
RE: Blurry ground textures.
I have not really tested this carefully yet but I have been flying in PNW scenery for a few days checking out Mike Mann's Tofino and Gold River Float bases on Vancouver Is. I have been using both the default Beaver (Misty repaint) and the Carenado C185 float plane.
My normal ride is the Carenado C185 Tundra Tire for RTMM scenery but due to Mike Mann's scenery being water based I used the default Beaver and the C185 floatplane. I have noticed that it "seemed" that with the C185 the ground texture would become blurry and stay that way quite quickly. With the default Beaver although I do get a very slight pop-in of scenery loading ahead of the airplane for the most part the textures stay sharp and do not 'go blurry' in PNW. As I mentioned this is mostly my perception and not really tested as yet but there is a difference in the two A/C and blurriness.
8)
this is an interesting observation. I will try to do some testing on this tonight. Although, if it is the 185 causing it, im not quite sure how to fix that.
-
I don't have the 185 and don't see any difference between planes, however, I have also done the very same tweaks (Bojote's and the external limiter) Some research threw up an interesting aspect about rejectthreshold, and it's relationship to the card memory, Jesus' tweaker ahd set ming very low (like yours) I altered the value to 1048756 as I have a 1GB card, I did not disable the fps limiter but did briefly disable the pre render option and // the usepools=4000 line in the FSC cfg, I noticed a distinct improvement in the loading times, I am now about to re-enable the usepools line as I did notice a bit of stuttering and want to see if this smooths out, plus I also re-enalbed the prerender line in the fps limiter. Back later.
-
Today I flew from Bowser Lake Fire Base to Stewart and while enroute switched back and forth between the TopCub Super Cub and the Carenado C185 several times in both wide river valley and narrow mountain valley textures and sorry to say but the C185 will cause blurry ground texture within 2 min. of a switch. Go back to the TopCub and the textures will get sharp in less than 30 seconds and other than very minor blur, that last just a few seconds, will stay sharp and clear.
My system is only low middle of the road for FSX, Dell XPS 600, 3.4GHz, 2MB memory and dual NVIDIA G-Force 7800 GTX video cards so that would make a difference I'm sure.
The main point being that the aircraft does make a difference on my system. Now it it were aPDGM 767 et al I could understand that a frame rate intensive airplane like that would make a difference, but come on people a lowly C185. Glad I did not spring for the more expensive C185 package if this is what to expect from the airplanes.
8)
-
Well I am happy to report that I have gotten the textures loading at an acceptable rate even with the 185. For me it actually was a pretty simple fix. After corrupting my display drivers and having to redownload (don't ask :p ), I stumbled across these xg267.24 drivers from tweakforce.com. they, along with the rejectthreshold tweak I did above, fixed most of the.loading problems I was experiencing. The 185 is a little slow still, but not near as slow as before.
I have a gts250 graphics card.
Hopefully this helps y'all that are also having the same issues.
-
Hi Spud,
the Carenado C185 is well known as FPS-hook!
Cheers Rainer
-
Ah... another reason not to get that plane ;)
-
Hi Spud,
the Carenado C185 is well known as FPS-hook!
Cheers Rainer
Apparently I do not read the proper forums only visit 10 of them every day at least once and this is the first time I have heard that about the C185. I do not read the AVSIM forums much so if it is there I would have missed it. Seems like some of the other would have something like that.
8)
-
Well the 185 aside (I don't have it) My results and tweaks so far are thus.
I changed the line RejectThreshold to the figure below, I have a 1GB card, the commented out number is for a half GB card I tried it as apparently this should be as low as possible, I don't know why, but I found the terrain textures loaded faster with the high number and no loss of FPS, the commented out numbers are for reference back and forth during the test:
[BufferPools]
RejectThreshold=1048756 //524288 //1048756
Another tweak that had a major impact was the Lod radius, I changed this from 4.5 (default) to 6 (I tried 5.5 and 6.5) 6 was the best setting. What this setting does is determine how far out from your plane the high res texture will be loaded, it is therefore a very system specific setting and will require some experimenting, but having a higher number means that the lower res textures are now a good deal further out and so I don't see as much very blurry terrain as before and the whole thing looks a good deal better. It doesn't seem to load up any slower either, but at 6.5 it did start having a job to keep up and thus the effect was spoiled, so 6 was the highest I could get to.
[TERRAIN]
LOD_RADIUS=6.000000
I did not disable the external FPS limiter (this is really a pretty important part of getting a smooth look, reducing the stutters etc) and also to allow for better terrain tex loading.
So, now I can see decent res textures out to a good distance (about a mile) at that range the next lower res textures look very good and so on, it keeps up pretty well at around the 170 kias but struggles a little over that, but not so it is a constant struggle, just doesn't always catch up in time with every tile etc. But overall the performance and appearance have improved dramatically and I am happy with it now. My external FPS limiter is set to 20FPS, internal to no limit.
-
Hi Spud!
After doing some actual research I have to admit that I´m at fault concerning the Carenado C185 :-\
Sorry for that!
Rainer
-
Well the 185 aside (I don't have it) My results and tweaks so far are thus.
I changed the line RejectThreshold to the figure below, I have a 1GB card, the commented out number is for a half GB card I tried it as apparently this should be as low as possible, I don't know why, but I found the terrain textures loaded faster with the high number and no loss of FPS, the commented out numbers are for reference back and forth during the test:
[BufferPools]
RejectThreshold=1048756 //524288 //1048756
Another tweak that had a major impact was the Lod radius, I changed this from 4.5 (default) to 6 (I tried 5.5 and 6.5) 6 was the best setting. What this setting does is determine how far out from your plane the high res texture will be loaded, it is therefore a very system specific setting and will require some experimenting, but having a higher number means that the lower res textures are now a good deal further out and so I don't see as much very blurry terrain as before and the whole thing looks a good deal better. It doesn't seem to load up any slower either, but at 6.5 it did start having a job to keep up and thus the effect was spoiled, so 6 was the highest I could get to.
[TERRAIN]
LOD_RADIUS=6.000000
I did not disable the external FPS limiter (this is really a pretty important part of getting a smooth look, reducing the stutters etc) and also to allow for better terrain tex loading.
So, now I can see decent res textures out to a good distance (about a mile) at that range the next lower res textures look very good and so on, it keeps up pretty well at around the 170 kias but struggles a little over that, but not so it is a constant struggle, just doesn't always catch up in time with every tile etc. But overall the performance and appearance have improved dramatically and I am happy with it now. My external FPS limiter is set to 20FPS, internal to no limit.
Kim, what do your system specs look like?
Im definently going to try the LOD_radius tweak you have here. As I understand it, the RejectTheshold number is the highest amount of data (in bytes) you want of textures loaded from the pool before being loaded straight from the video card. So in theory, if you have a fast card, the lower the number the better since your card will do most of the texture loading. Im still going to play around with this a bit and see what happens.
Thanks for the update.
-
Checked this thread earlier and modified my FSX.cfg file using some of the suggestions in the link posted by Tigerclaw. Specifically:
[Bufferpools]
Poolsize=5000000
[Display]
TEXTURE_BANDWIDTH_MULTI=400
[Main]
FIBER_FRAME_TIME_FRACTION=0.40
It made a lot of difference in curing the blurries with the C185 in fact could not really see anything to complain about considering my ancient Video cards
I do have other tweaks in the .cfg file from ORBX threads but did not change any of those.
I will try the the RejectThreshold=1048756 //524288 //1048756, and LOD_RADIUS=6.000000 tweaks and see how that goes will probably muck about with the numbers and see the results.
At least with what I have now the ground texture do not blur. It is so noticeable because while the ground is blurry the trees and sharp as a tack so the blurries really stand out like hooker in the front pew!
This is what is so great about the site, good info, good company and great scenery. Thanks to one and all!
And No Worries Rainer.
8)
-
CPU intel 2 core duo E8400 @ 3GHz (Pentium III Xeon)
GPU Nvidia GTX460 1GB
4GB Ram.
I don't know why, but I get a better result with the higher number on the rejectThreshold.
I left the external FPS limiter in place as although it seems it does have an impact, without it I seem to get much worse stutters, especially looking sideways out the plane, so it's a trade off really.
WRT the LOD radius, someone elsewhere explained the principle, (other places you will read, "if your system cannot sharpen the textures at 4.5 no way will it at 6.5!" However, the LOD radius effects how many tiles around your plane are high res.
Imagine then you are in a dark room, you have a flashlight, it lights up a set area of wall, as you move the flashlight you light up new areas, if the beam is narrow (a smaller LOD radius) then you arm has to do a lot more work (GPU swapping textures in and out) if the Beam is wider (larger LOD radius) you need to move your arm less to light up more wall (less swapping in the GPU)
Now logically this would suggest a very large setting might initially take time but would pay off in that as you advanced across the terrain the system would be loading the higher res textures well before you got to them, of course it doesn't work this way as the amount of work is too great, so you have to find the right balance between the load time and the overall appearance, but the default setting of 4.5 means that the third level mipmaps are really pretty close to the plane so you never see decent middle distance textures even when it is all running well. With a setting of 5.5 or 6 you do at least get a better looking overall terrain even if the highest level mipmaps are lagging a little.
That's how it seems to me anyway.