frameratecap=60 (In-game FPS limit)
frameratecapGlue=30 (FPS limit for the battle.net user interface)

still work. It has been said that higher end graphics cards can overheat without this. is this true?

Dghelneshi

Germany82 Posts

January 23 2014 12:04 GMT

#23

On January 23 2014 00:47 JaKaTaK wrote:
frameratecap=60 (In-game FPS limit)
frameratecapGlue=30 (FPS limit for the battle.net user interface)

still work. It has been said that higher end graphics cards can overheat without this. is this true?

If your graphics card overheats then it's not really the game's fault. Limiting your FPS can lead to lower power consumption and temperatures, but also limits input rate (usually not noticable for most people, but it's there) and there are also monitors out there with more than 60Hz.

I'm also not sure why you would want to set color depth to 16bit. You would have to show me a really significant advantage to justify that. Theoretically it could improve cloak visibility if you have really low color depth, but I don't think 16bit is going to do anything.

JaKaTaKSc2

United States2787 Posts

January 23 2014 15:42 GMT

#24

bitdepth=16 improves performance without much loss in visuals. Its more of an option for those with weaker computers than anything else.

Firkraag8

Sweden1006 Posts

January 25 2014 17:51 GMT

#25

I miss having low shaders, simplifiedCloaking=0 and simplifiedShaders=0. I don't understand why Blizzard had to ruin that for everyone. I can play on Extreme without lag, but I liked that old WoL setup better..

JaKaTaKSc2

United States2787 Posts

January 29 2014 17:19 GMT

#26

Found a new dependency:

GraphicsOptionShaderDetail=1
GraphicsOptionShadowQuality=1
for
shadows=1

shadows=1
for
simplifiedCloaking=0
and
simplifiedShaders=0

Also:
lowqualitymodels=0
and
useLowqualitymodels=0

must be the same.

Firkraag8

Sweden1006 Posts

January 29 2014 17:34 GMT

#27

On January 30 2014 02:19 JaKaTaK wrote:
shadows=1
for
simplifiedCloaking=0
and
simplifiedShaders=0

So if I go pick low settings in-game, get into variables.txt and enter Shadows=1 then simplifiedcloaking/shaders 0 it will stick and work like it did in the past? As it is right now simplifiedcloaking/shaders gets reset when i tried in the past since the patch.

JaKaTaKSc2

United States2787 Posts

January 29 2014 17:50 GMT

#28

You need to set everything to low
Then:

GraphicsOptionShaderDetail=1
GraphicsOptionShadowQuality=1
shadows=1
simplifiedCloaking=0
simplifiedShaders=0

It isn't as good as before, but it's the closest we've been in a while.

Shield

Bulgaria4824 Posts

January 29 2014 18:25 GMT

#29

Why do you advise to decrease FPS? Isn't the goal to increase it?

Also, why don't you set the file to read-only to avoid dependencies?

JaKaTaKSc2

United States2787 Posts

January 29 2014 19:18 GMT

#30

Wait what? I advise to increase FPS. I must have misspoke.

I don't think setting it to read only works. Haven't tried in a while so things may have changed.

Shield

Bulgaria4824 Posts

January 29 2014 22:30 GMT

#31

On January 30 2014 04:18 JaKaTaK wrote:
Wait what? I advise to increase FPS. I must have misspoke.

I don't think setting it to read only works. Haven't tried in a while so things may have changed.

You've shown:


frameratecap=60 (In-game FPS limit)
frameratecapGlue=30 (FPS limit for the battle.net user interface)

That certainly is a limit on FPS. Isn't it better to leave FPS the way it is?

MtlGuitarist97

United States1539 Posts

January 29 2014 22:35 GMT

#32

On January 30 2014 07:30 darkness wrote:

Show nested quote +

You've shown:


frameratecap=60 (In-game FPS limit)
frameratecapGlue=30 (FPS limit for the battle.net user interface)

That certainly is a limit on FPS. Isn't it better to leave FPS the way it is?

Most people have monitors which have a 60hz refresh rate. Having it higher than 60 won't do anything besides increase power consumption and possibly heat. Having the menu set to 30 fps again, doesn't really matter since it won't affect performance. If you have a 120 hz monitor it may be worth it to keep it higher, but that affects an small number of posters.

JaKaTaKSc2

United States2787 Posts

February 05 2014 19:20 GMT

#33

New Competitive Settings. Very similar to the old Hybrid Settings from Existor. He and I are working on it together.

Current Solution

Everything on Low
Add or change the following:
bakeTerrainLighting=0
globalhdr=1
glossmaps=1
GraphicsOptionModelQuality=1
GraphicsOptionOverallQualityVer7[15]=5
GraphicsOptionPortraits=1
GraphicsOptionShaderDetail=1
GraphicsOptionShadowQuality=1
hdr8bit=1
lighting=0
lightingLevel=2
lightingregionmapterrain=1
localhdr=1
lowqualitymodels=0
normalmap=1
pixellight=1
preBlendedCreep=0
shadows=1
simplifiedCloaking=0
simplifiedShaders=0
spec=1
textureBasedFOW=1
use20shaders=0
useLowqualitymodels=0

Current Issues

High Models eliminates effect shown on nexus when warping in a mothership core
Medium Effects brings back the above effect but adds unnecessary elements on warping in units, minerals, and other things.

edit: particallod determines the moco animation on the nexus. The best solution I have is to add:

GraphicsOptionEffectsDetail=1
particlelod=1

Unfortunately this obscures some things. Most noticeably the distinct units warping in. Overall though if we're making the best competitive setup this is it so far. We're avoiding splat effects, ribbon effects, tread effects, and something called:

cheapquadselection

If anyone could help find out what that does, I'd appreciate it.

Current list:
Everything to low
bakeTerrainLighting=0
globalhdr=1
glossmaps=1
GraphicsOptionEffectsDetail=1
GraphicsOptionModelQuality=1
GraphicsOptionOverallQualityVer7[15]=5
GraphicsOptionPortraits=2
GraphicsOptionShaderDetail=1
GraphicsOptionShadowQuality=1
hdr8bit=1
lighting=0
lightingLevel=2
lightingregionmapterrain=1
localhdr=1
lowqualitymodels=0
normalmap=1
particlelod=1
pixellight=1
preBlendedCreep=0
shadows=1
simplifiedCloaking=0
simplifiedShaders=0
spec=1
textureBasedFOW=1
use20shaders=0
useLowqualitymodels=0

AFSpeeDy

126 Posts

February 06 2014 17:00 GMT

#34

thank you two for your work you put in.

Already playing SC with Hybrid Graphics.

JaKaTaKSc2

United States2787 Posts

February 06 2014 17:08 GMT

#35

We're improving it even more! Existor is coming out with a baller post soon

esports_Swag

Canada11 Posts

February 07 2014 21:21 GMT

#36

Im playing on a laptop that is power messed and i need to run on low gfx for any play. Why do you have options like globalhdr=1 and shadows and shaders on 1? Seems like this would lag it out a lot more. Also i do not see a "lighting=X" option in the Variables.txt file located in my documents/starcraft 2

JaKaTaKSc2

United States2787 Posts

February 07 2014 21:38 GMT

#37

lighting=0 is something you have to add yourself. Are you looking for lowest possible settings or hybrid?

esports_Swag

Canada11 Posts

February 07 2014 21:48 GMT

#38

On February 08 2014 06:38 JaKaTaK wrote:
lighting=0 is something you have to add yourself. Are you looking for lowest possible settings or hybrid?

I was totally confused. Was looking for lowest settings.

JaKaTaKSc2

United States2787 Posts

February 07 2014 23:04 GMT

#39

Everything on Low
Vsync and AA off
Reduced Violence On
Sound Quality to Low
Reverb Off
Reduce Mouse Lag Off
Health Bars set to Damaged
GraphicsOptionShadowQuality=1
bitdepth=16
frameratecap=70
frameratecapglue=30
hdr=0
lighting=0
mipbias=0
shadows=0
Teen=1

This is the lowest possible setup we have right now