Shader Cache Primed???

[Aharon]

Shalom and greetings all my pals,

While I am doing ground testing of FSX Deluxe with SP1 and SP2 in my new laptop with Windows 10, everything looks good but I am puzzled by one thing.

Why does my new laptop's FSX.cfg's [GRAPHICS] section show SHADER_CACHE_PRIMED=1 while my old laptop's FSX.cfg's [GRAPHICS] section shows SHADER_CACHE_PRIMED_10=1693458432
SHADER_CACHE_PRIMED=1693458432
D3D10=0

which is also same on all people's FSX.cfg too?

Regards,

Aharon

[DaveB]

Yikes.. this is stuff I never look at but my first entry is SHADER_CACHE_PRIMED=1693500672 and the second Shader entry is SHADER_CACHE_PRIMED_10=1693500672. What ever you do.. don't ask me what it means

EDIT: Oh.. my install is FSX ACC. Not sure if this makes a difference.

ATB
DaveB

[Aharon]

Yikes, DaveB your numbers are different from the same number that everybody and my old laptop have!!!!

Regards,

Aharon

[Aharon]

DaveB,

Somebody explained to me as in his own words:

I believe that the shader cache rebuilds itself every time FSX is run as it contains codes and instructions that are accessed frequently and allows FSX to optimise itself over time. Just leave it with the number built by FSX as it will slowly optimise and the number will change. If you check "C:\Users\<user name>\AppData\Local\Microsoft\FSX" you will find the folder called Shaders that is the cache the .cfg is referring to. I think it only builds the "shader10" folder when you access DX10 and will then put The "Primed_10" entry in the .cfg

If you find further down the track that you are developing stutters and strange anti-aliasing issues, deleting the contents of the shaders folder will force FSX to rebuild everything and will rest the number in the FSX.cfg.

At this stage though, just leave it and let it do its thing.

Regards,

Aharon

[DaveB]

Tks Aharon I knew about the Shaders folder.. in fact I rebuilt the shaders the week before last

ATB
DaveB