Post 1.3.7 no shaders being built at boot time

Post 1.3.7 no shaders being built at boot time.

And judder back and freezing. So what did they do. :eek: Have they removed the Xbone optimization or the Mac optimization.
 
Post 1.3.7 no shaders being built at boot time.

And judder back and freezing. So what did they do. :eek: Have they removed the Xbone optimization or the Mac optimization.

This sounds like one of those "have you stopped hitting your wife?" kind of questions.
 
Last edited:
Just tried again. No shader build when I fire up. me thinks we have an undocumented change in 1.3.7. Can you all please go look at something pretty and see if the graphics have changed. For me I seem to have gone back to pre 1.3. :D

Will try a cold start.
 
Last edited:
Just tried again. No shader build when I fire up. me thinks we have an undocumented change in 1.3.7. Can you all please go look at something pretty and see if the graphics have changed. For me I seem to have gone back to pre 1.3. :D

It's either an undocumented change or more than that - a regression. Both are bad.
 
Just played last night and and the night before and my shaders loaded.

Maybe you have such an uber rig it just rips through the loading process.. :p

For me .7 has been an overall improvement. I haven't had any stuttering in rings (though it varies from ring to ring and I only stopped at a couple which worked smoothly) which was may main issue.

I got a couple micro stutters in SC when trying to do a long approach to station (unlock dest. drop at 25km, can't let anyone see these black boxes) but that was it.
 
Last edited:
The XML file has changed a bit I think. Precaching seems to be set for Nvidia cards by default, and AMD not. Im in the middle of feeding my children but there is a thread about this doing the rounds (under optimization, I think).
 
Last edited:
The XML file has changed a bit I think. Precaching seems to be set for Nvidia cards by default, and AMD not.

Where is this XML? I'd like to keep a copy so I can check for changes in the future.

EDIT: NVM, appconfig.xml...I know where to go
 
Last edited:
AMD cards? if so look at patch notes thread (quoted from there)

This explains it...from AppConfig.xml:

- On both Windows and OSX, ShaderWarmingEnabled="auto" enables shader
warming if the GPU detected by the game is an NVIDIA model, and
disables shader warming otherwise.
-->
<PlanetNoiseTextures
Enabled="auto"
ShaderWarmingEnabled="auto"

Set it to 1 not auto
 
After cold boot still no shaders. I have a low end PC and they always took a minute. So gone. I now have the pre shaders glitches on my low end machine. So they made an undocumented change. Maybe it is to reverse 1.3 changes. To get rid of stutter for you high end users.
 
Guys, I am no expert on this at all, but maybe FD checks to see if you have a NVidia card because it is a pointless proces for ATI cards? I dont think they just added that to spite us ATI users... :)
 
I had a quick try earlier.

Shaders loaded
Stutter present

Appreciate I need to try a longer stint before toys and pram become separated once more :D
 
prebuilding shaders seemed to work at fixing the mini-pauses before a model rendered on screen. It being disabled for amd cards would be a regression on my machine.
 
Maybe...head into appconfig.xml and change the value to 1 as quoted below. Let us know if it helps.

Even forcing "1" in the .xml doesn't appear to be doing anything for me on my AMD cards.

You can change it back, see page 1.

Doesn't work.

Edit: had to restart my system, delete my .xml file, and recreate it before editing it. Now it works.
 
Last edited:

Deleted member 38366

D
--- Deleted ---
 
Last edited by a moderator:
Back
Top Bottom