GPU_OFFSET question about nvoc_by_fullzero_community_release HOT 9 CLOSED

We know, as script writers, that leaving those variables unset will be equivalent to a variable set to 0, but users may get confused easily. I'd rather keep all initialized to 0.

from nvoc_by_fullzero_community_release.

from nvoc_by_fullzero_community_release.

So isn't it better to set all GPU_SPECIFIC values to blank to prevent misuse problems?

from nvoc_by_fullzero_community_release.

from nvoc_by_fullzero_community_release.

If you think that a rig will likely be composed of a fixed set of (hopefully not mixed) gpus you'll quickly find how useless would be a chunk of code which always detect the gpu type and decides "optimal" oc values at runtime. Then you should also consider tthose values are "ggod for all" only as a starting point, then everybody should check each car for stability and eventually tweak configs. You would obtain the same effect by simply suggesting users to visit buriedone checking for what kind of OC their cards support.

from nvoc_by_fullzero_community_release.

Agree with Luke
And as I said before we have seen the same manufacturers use different parts and that makes different OC values even for same cards from same company with different manufacturing patch
So if we nvOC going to set values for card types for sure it will cause so many problems

from nvoc_by_fullzero_community_release.

@LuKePicci , should I set salfter values to 0 as well, or just the uppercase oc values?

from nvoc_by_fullzero_community_release.

All of them, since every policy equally applies to any kind of switchers.

from nvoc_by_fullzero_community_release.

Done in PR #60

from nvoc_by_fullzero_community_release.