I tried tml=30 tweak yesterday, and after testing only thing it does on my system is to bring DPC latency on very high numbers, over 8000 all the time. Without it DPC latency is in green/yellow (acceptable). So this tweak is a no go for me until I get rid of DPC latency, and that is a mission impossible so far. I heard that Acceleration pack is a culprit for high DPC latency.

I tried tml=30 tweak yesterday, and after testing only thing it does on my system is to bring DPC latency on very high numbers, over 8000 all the time. Without it DPC latency is in green/yellow (acceptable). So this tweak is a no go for me until I get rid of DPC latency, and that is a mission impossible so far. I heard that Acceleration pack is a culprit for high DPC latency.

 

That explains why I have such weird luck with that tweak. On the ground in heavy scenery I get smooth performance, but once I get airborne the sim is unstable and stutters. Removing that line and keeping all the texture settings default like t_b_m=40 makes my sim more smooth in the air but rough low framerates on the ground.

 

I give up. I guess I'll just take a bad performing sim on the ground for better performance in the air. Even though my frames don't go much farther above 15-20fps

 

Can you help me tweak FSX to run better? I do run Acceleration. Do you recommend a different setting than 40 of T_b_m?

I have issue with DPC Latency in DX9 mode, tried every bufferpool values out there. Found that some values will cut in half DPC latency, but with some complex planes with hi-res textures, the latency is hitting the roof, over 8000ms! SO I deleted FSX completely, and reinstalled it yesterday. Except I didn't installed Acceleration this time, I went for SP1 + SP2. Checked the latency in vanilla DX9 setup, it was still there, but acceptable (it was vanilla, right). So I switched to DX10 ogain with the Fixer, and so far the results are better than before, no dpc latency at all, looking good. So, I really hope that I ditched DX9 mode for good, but I'm still taking it with a grain of salt.

 

TBM related, I'm keeping it at 40, or even 30 (because I limited the frames at 30 in nvInspector). Never saw any difference/improvement with 70/80, or even higher. Never saw any improvement with TML also. I currently use only AffinityMask=14, HIGHMEMFIX=1, FIBER_FRAME_TIME_FRACTION=0.15 and ForceWindowedVsync=1. Nothing unusual. So on some machines, keeping cfg closer to default is the best option.

I have issue with DPC Latency in DX9 mode, tried every bufferpool values out there. Found that some values will cut in half DPC latency, but with some complex planes with hi-res textures, the latency is hitting the roof, over 8000ms! SO I deleted FSX completely, and reinstalled it yesterday. Except I didn't installed Acceleration this time, I went for SP1 + SP2. Checked the latency in vanilla DX9 setup, it was still there, but acceptable (it was vanilla, right). So I switched to DX10 ogain with the Fixer, and so far the results are better than before, no dpc latency at all, looking good. So, I really hope that I ditched DX9 mode for good, but I'm still taking it with a grain of salt.

 

TBM related, I'm keeping it at 40, or even 30 (because I limited the frames at 30 in nvInspector). Never saw any difference/improvement with 70/80, or even higher. Never saw any improvement with TML also. I currently use only AffinityMask=14, HIGHMEMFIX=1, FIBER_FRAME_TIME_FRACTION=0.15 and ForceWindowedVsync=1. Nothing unusual. So on some machines, keeping cfg closer to default is the best option.

 

I run DX9 in FSX Acceleration and for the life of me can't get rid of very low fps even though I have fast hardware.

 

I run AffinityMask 62, highmemfix, and bufferpools=0, tried everything to help slow loading textures when changing views like texturemaxload but the negative consequences were too great. Bufferpools and affinity mask make my sim smooth and stable but I can't get rid of low fps.

 So I switched to DX10 ogain with the Fixer, and so far the results are better than before, no dpc latency at all, looking good. So, I really hope that I ditched DX9 mode for good, but I'm still taking it with a grain of salt.

 

TBM related, I'm keeping it at 40, or even 30 (because I limited the frames at 30 in nvInspector). Never saw any difference/improvement with 70/80, or even higher. Never saw any improvement with TML also. I currently use only AffinityMask=14, HIGHMEMFIX=1, FIBER_FRAME_TIME_FRACTION=0.15 and ForceWindowedVsync=1. Nothing unusual. So on some machines, keeping cfg closer to default is the best option.

 

Just remember, guys - all that info in the above posts refers only to DX9, and also Phil's quotes are from 2007, pre-SP2.

In DX9 the CPU and GPU share the graphics "action" and this affects the way these parameters work:- To re-quote Phils' blog:- "The TEXTURE_BANDWIDTH_MULT option in the Graphics section is the target frame rate use for calculating texture bandwidth.  The higher you set this value the more textures we will allocate and copy per frame to the graphics card.  The lower you set this value, the less we will allocate and copy up to a minimum limit. " 

When using DX10 - this now takes place in the GPU itself, and has a more noticeable impact, as do many other parameters. The particular one under discussion - [Display]TextureMaxLoad=6 - is, as Jim (and Nick!) says - better left out of the cfg altogether, leaving the TBM - which has plenty of range - to do the work - and limited to 120 - not 400.

 

pj

Just remember, guys - all that info in the above posts refers only to DX9, and also Phil's quotes are from 2007, pre-SP2.

In DX9 the CPU and GPU share the graphics "action" and this affects the way these parameters work:- To re-quote Phils' blog:- "The TEXTURE_BANDWIDTH_MULT option in the Graphics section is the target frame rate use for calculating texture bandwidth.  The higher you set this value the more textures we will allocate and copy per frame to the graphics card.  The lower you set this value, the less we will allocate and copy up to a minimum limit. " 

When using DX10 - this now takes place in the GPU itself, and has a more noticeable impact, as do many other parameters. The particular one under discussion - [Display]TextureMaxLoad=6 - is, as Jim (and Nick!) says - better left out of the cfg altogether, leaving the TBM - which has plenty of range - to do the work - and limited to 120 - not 400.

 

pj

 

Thank you for this information but it just leaves me more confused. I have said before I run FSX with Acceleration and DX9. So pre sp2 and DX10 mean nothing to me. Also I can't seem to run autogen higher than dense or else I get OOM errors a few minutes after takeoff.

Paul J, c'mon over to my place for some Rum and Jimmy Buffett music (heck, I might even invite a clown and a few broads too if my wife OK's it).

 

Maybe you can set my rig up with DX10 while you're at it  :lol:

With all due respect, I've seen the difference the TextureMaxLoad entry can make. Recently I let FSX produce a new cfg file. Put in the essential extra entries like HIGHMEMFIX, but left TextureMaxLoad out, along with other 'doubtful' tweaks. Then - in flight - I was plagued with flashing groundtexture tiles, oddly enough allways on the left side of the aircraft. Did  a search on this formun and found that a member had cured this exaxt problem with entering under [DISPLAY] in the cfg: TextureMaxLoad=9. I followed this example et voila: The flashing disappeared. Other settings that may be relevant in my case were TBM at 80, FPS locked at 30, BP=0.

 

Kind regards,

René

With all due respect, I've seen the difference the TextureMaxLoad entry can make. Recently I let FSX produce a new cfg file. Put in the essential extra entries like HIGHMEMFIX, but left TextureMaxLoad out, along with other 'doubtful' tweaks. Then - in flight - I was plagued with flashing groundtexture tiles, oddly enough allways on the left side of the aircraft. Did  a search on this formun and found that a member had cured this exaxt problem with entering under [DISPLAY] in the cfg: TextureMaxLoad=9. I followed this example et voila: The flashing disappeared. Other settings that may be relevant in my case were TBM at 80, FPS locked at 30, BP=0.

 

Kind regards,

René

 

Dear René,

 

What do you mean by flashing tiles? Do you run DX10 or DX9? Flashing in a similar way to some textures running DX10 without related fixes?

 

Thank you.

Hello PhugoidEffect,

 

I'm afraid I cannot give you a more precise description, other than that some tiles turned black for a split second. I run DX9 (tried DX10 a few times, but apparently my rig doesn't like it or cannot cope with it; framerate considerably lower under DX10). Can't say anything sensible about flashes under DX10 without the fix(es).

 

Kind regards,

René

Just a quick comment; I run older 'legacy' hardware and thevi Bojote mods work wonders : )

Sorry for resurrecting this old thread, but yesterday I tried setting texturemaxload=27 (along with TEXTURE_BANDWIDTH_MULT=40 and TEXTURE_MAX_LOAD=4096) and not only do I notice almost no black ground squares in heavy custom sceneries, but I also feel that flying is quite smoother. I tried with the PMDG 777 and was almost surprised. Anyone noticed this or is it just my impression? 

Sorry for resurrecting this old thread, but yesterday I tried setting texturemaxload=27 (along with TEXTURE_BANDWIDTH_MULT=40 and TEXTURE_MAX_LOAD=4096) and not only do I notice almost no black ground squares in heavy custom sceneries, but I also feel that flying is quite smoother. I tried with the PMDG 777 and was almost surprised. Anyone noticed this or is it just my impression?

The tweak is simply not recommended. Why not move your Texture_Bandwidth_Multi from 40 to 60 or even 90 (anything much higher is not recommended). In post #29, another member recommended the comments made by NickN, a former employee of NVidia and recognized computer expert, regarding this so-called tweak. What you are seeing now is simply a placebo IMHO. It always happens after you shutdown a fsx and restart it giving your memory (RAM) and VAS a fresh start. Many others have several pieces of commercial software that they run that are frame-rate unfriendly and that takes their system down even with a so-called tweak like texturemaxload. One good thing about fsx, individual users can do about anything they want to do to fsx to make it run best for their computer system. What works great for you does not mean it will work great for others and that's the sad thing about any tweak. Best tweak is to reduce your sliders, let fsx "breathe", and go fly.  Oh!  And before you do that, check out the AVSIM FSX Configuration Guide and try those settings.  Those settings are pretty high but they work for most of us.

 

Best regards,

I noticed that fsx:se defaults TEXTURE_BANDWIDTH_MULT at 160 (!) on my system.

Wow!  That's great!  They must have tweaked the FSX-SE engine to make that the default setting for systems like yours.  This is great news for those who own FSX-SE!  Apologize for being sarcastic but couldn't help it.