Here is a thread I posted on REX forums: http://www.realenvironmentxtreme.com/forums/index.php?/topic/25852-hd-clouds-weather-injection-blurries/

 

Posted here just in case someone else has this problem and/or has a solution.  I can't seem to resolve this problem other turn off REX weather injection.  This only started happening with the most recent update to REX OD.

 

Some things I've tried in my FSX.CFG that has made no difference:

 

[Display]

TEXTURE_BANDWIDTH_MULT=40
UPPER_FRAMERATE_LIMIT=0
 

[Main]
FIBER_FRAME_TIME_FRACTION=0.99
DisablePreload=1

ProcSpeed=10175
PerfBucket=7
 

[Weather]

CLOUD_DRAW_DISTANCE=7
DETAILED_CLOUDS=1
CLOUD_COVERAGE_DENSITY=8
 

[DISPLAY.Device.NVIDIA GeForce GTX 680.0]
MipBias=10
Mode=2560x1600x32
Anisotropic=1
AntiAlias=1
 

[GRAPHICS]
MultiSampleQuality=4
MultiSamplesPerPixel=16
NIGHT_THRESHOLD=4096
DAY_THRESHOLD=32768
SHADER_CACHE_PRIMED_10=1693500672
STALE_BUFFER_THRESHOLD=2147483647
HIGHMEMFIX=1
ForceWindowedVSync=0
ForceFullScreenVSync=1
SHADER_CACHE_PRIMED=1693500672
TEXTURE_MAX_LOAD=4096
D3D10=1

 

[sCENERY]
ObjectsToBatchPerFrame=50
MAX_ASYNC_BATCHING_JOBS=4
SmallPartRejectRadius=0
IMAGE_COMPLEXITY=5

 

[TERRAIN]
SWAP_WAIT_TIMEOUT=4
IMAGE_PIXELS_FOR_AUTOGEN_POLYGONS=2048
BATCH_AUTOGEN2=1
LOD_RADIUS=9.500000
MESH_COMPLEXITY=100
MESH_RESOLUTION=25
TEXTURE_RESOLUTION=29
AUTOGEN_DENSITY=5
DETAIL_TEXTURE=1
WATER_EFFECTS=4
 

I've tried changing many of these settings, but the problem remains even at 1024 textures and 4.5 LOD (with REX set to 1024 also).  I've also just used the FSX default weather and did not have a problem, only when REX injects weather do I get this problem ... I'm baffled??  I can use REX cloud textures and not have a problem, but as soon as any weather is injected, I get the problem.  Tried Swap_wait_Timeout=2 to 10, no difference.  Increased SmallPartRejectRadius=10, no difference.  Also tried BufferPools but I don't think that value is used in DX10 mode with frames set to Unlimited, it didn't make any difference.

 

Plenty of memory headroom both in the GPU (4GB) and in FSX.EXE (1GB free) ... SSD's tested fine (very fast as usual). 

 

I'm stumped.

 

Rob.

Hmm. Strange.

 

So do you run unlimited and fullscreen, correct? What FPS are you having when this happens?

 

Does it help if you lock internally to 60 FPS? (I take it you use regular Vsync)

 

The FFTF value doesn't do much difference unless you have the internal FPS lock set.

 

What affiinitymask do you use? And is HT on or off?

 

I'm just asking about things that can make a big difference with (ground)texture loading. I don't know how come the textures go blurry in an instant.

I tried locking to 30 fps, but that made no difference.  Clear sky I was running at 60 fps, when REX injected the weather (clouds) dropped to about 40 fps.

 

[JOBSCHEDULER]
AffinityMask=4102

 

Forgot to include:

[Display]

TextureMaxLoad=30

 

Just tried HT OFF ... sadly the same (I normally run with HT ON for the 3960X)

 

Yeah, it's very odd, all the textures instantly go blurry ... all of them, including aircraft.

 

I'm wondering if FSX has a limit on scenery library entries -- I'm currently at 587 entries, but I don't understand why weather inject from REX would do this??  Wondering if a specific REX Cloud texture set is corrupted or has some type of error?

Hmm... did you get any issues using time fraction @ 0.99? I'm currently at the default and then moved to 0.66 but didn't see much effect. Also, perhaps could that be the problem? Did you try reverting to 0.33? Afaik, this settings sets the priority between scenery loading and other stuff.

I know one thing for sure. Setting the LOD above 4.5, say 8.5 or higher is giving higher loading time BUT I *think* it makes for less blurries and better LOD in the distance. Above 8.5 I noticed an annoying excess in the loading time so you need a REALLY fast SSD for this. I'm talking about RAID setup or Revodrive.

PS,
I also read here or some other forum that setting fps counter to unlimited not only resolve fps issues but it also makes the scenery show better detail in the distance (hard-coded feature). This is speculated although it does make sense somehow.

 

On my setup, I didn't noticed blurries upon REX injection. Something in the cfg screws up things for you or maybe something in the rex control panel.

I'm going to double-check my .cfg file when I get home, but I immediately see a few things that might cause problems:

-Set the internal FPS lock to 30

-Your Affinity mask looks a bit weird - you're only using Core #1 and #2 and #12 for FSX. Such a waste with a six-core CPU.
For your CPU, 62 would be a good value with HT off (FSX will use 5 cores, leaving one unused in FSX and free for the REX process and background Windows tasks. Personally, I prefer to use all cores for the sim (no Affinity mask defined) and lower the fiber_frame_time_fraction instead if stutters occur.

-FIBER_FRAME_TIME_FRACTION should be between 0.12 and 0.20, or you can just remove the line which will reset it to the default 0.33, this should also work fine. Values above the default are really only useful for photo-scenery or TileProxy.

-Remove the MipBias=10 line to revert to default.

-LOD Radius should never be raised above 4.5 until you're absolutely sure your system can handle it. Yes, it makes the scenery sharper, but *only* if your system can handle it. If you have other problems, the scenery engine will be busy rendering distant textures in sharp detail, causing near and mid-distant scenery to get blurry.

-SmallPartRejectRadius can be increased to 4 for a small performance improvement with no noticeable loss of detail

 

Edit: Swap Wait Timeout is also strangely configured at 4 which would cause problems with blurries. I believe default is 30, but just deleting the line will also go back to default.

 

 

Personally, I think your best bet is to rename your FSX.cfg to FSX.cfg.old and start from scratch. FSX does work fine without tweaks - tweaks are applied to fine-tune the sim, not "fix" it. If you have problems, tweaks are not going to fix them.

@JimmiG SmallPartRejectRadius was removed from having any use in FSX SP2. I just saw that in another forum when looking up this property. If so, thread starter should just delete it.

Ok Rob,

As you say. It's very strange that the high quality textures get evicted and needs to be re-loaded. Tried updating/reinstalling the GfxDriver?

 

I was very surprised to hear that it took you a minute to re-load the terrain given your CPU/SSD combo but looking at your settings explains a lot.

 

1. As been said previously, you're not making use of your 6 cores. You only use 2 cores for loading ground textures with that affinitymask. If you want to significantly shorten the time it takes to re-load the textures set AM=4081 or AM=4089.

 

2. At the same time lock the frames within FSX.

Setting the internal FPS lock improves on ground texture loading and it also goes hand in hand with your FFTF setting. Setting the FPS lock sadly lowers what FPS you can achieve. Well that's the general opinion. It actually trades FPS for texture loading. Upping it improves on texture loading, but only to around 0.67 while lowering FPS. Going above 0.67 just continue to lower FPS while not improving any more on texture loading. Not a good idea.  

By lowering the FFTF value you can slow down the texture loading and at the same time be able to achieve higher FPS.

It also depends on if you can maintain the FPS you have locked. If you have locked it low enough so you can always maintain it, it doesn't matter what FFTF value you set. Changeing it then won't make any difference (as long as you stay below 0.67). So please also lock the FPS to 30 and also lower the FFTF value to 0.67.

 

Do the different AM value combined with the FPS lock and FFTF significantly shorten that minute it takes to reload the textures?

 

I know it's just a way to treat the symptoms, not a way to cure the illness.

Great suggestions all, will try a few ... in the office today, but will try tonight.

 

On the texture re-loading to higher quality ... I pause the flight and wait and watch the scenery "evolve"

 

As I understand FIBER_FRAME_TIME_FRACTION from Microsoft's documentation, 0.99 is allowing MORE CPU time to the loading of textures ... but what the heck, I'll try 0.33 and see.

 

What I think is the most puzzling is that I don't have a problem until REX weather cloud injection.

 

1.  No problem if I use REX clouds but "default weather partially cloudy and static" - no injection

2.  No problems with any other clear sky and REX textures

 

But anyway, will try these suggestions and see how it goes.

 

My SSD's are very faster (over 500 MB/sec with incredibly low latency running from a 6GBs ports) ... Don't want to RAID SSD's unless one has a VERY high-end RAID controller and uses "Supported" SSDs.

 

Cheers, Rob.

Hi,

 

I've got the same problem.

 

My FSX with REX been running perfect. Tonight installed the update, and now everything in FSX has gone blurry/jaggy.

 

Tried uninstalling REX and then reinstalling the older version which was working perfectly - but still have blurries.

 

Can anyone help? Driving me mad!

 

Thanks,

Rich

 

 

As I understand FIBER_FRAME_TIME_FRACTION from Microsoft's documentation, 0.99 is allowing MORE CPU time to the loading of textures ... but what the heck, I'll try 0.33 and see.

You can use the higher FFTF numbers to allowe more CPU time for textures If you have FSX without any ServicePack or if you use a single-core CPU. You can go as high as you wish then. So that is correct but not the whole truth.

With a multi-core CPU and SP1 or higher installed you'll only get faster texture loading up to FFTF 0.67. Over that you'll just loose FPS for no other benefit.

 

 

 

What I think is the most puzzling is that I don't have a problem until REX weather cloud injection.

 

 

Tried uninstalling REX and then reinstalling the older version which was working perfectly - but still have blurries.

 

It sounds like the high-res ground textures get evicted from the Gfx memory for some unknown reason. And if the problem still exists when you revert to the older REX version again it makes me wonder if there's something up with the gfx driver...? Windows update hasn't decided to change driver on you?

Hi,

 

As an example this is what planes now look like below. Also just did a short test flight and any straight line (in the cockpit or runway line etc) is blurry.

 

What is gfx? How can I check the windows update?

 

Thanks for your help,

Rich

 

 

 

What is gfx

 

Think gfx  is  your  graphics  card but I could  be wrong

Ah think you are right!

 

My graphics card is a  GeForce GTX 680 card with drivers 311.06 installed

 

Nvidia website says latest drivers are 314.22.

 

Sort of reluctant to update drivers, as there wasn't any problem before the REX update to SP1.

 

Thanks,

Rich

There is no way that our service pack would cause this Rich.

Hi,

 

The problem is though - I had used fsx literally 30mins before updating REX and it was fine. I made no changes and nothing updated - so do you know what else it could be?

 

Pretty stuck at what I can do and it's really frustrating.

 

Cheers,

Rich