I think I don't understand your first question, sorry.
However, I am not sure if the scaling is (framerate) dependent on rendering or not, I'd guess it's not the case (one would have to test that, and maybe with or without PASSABLE flag).
I am not familiar with writing shaders like the default engine shaders (because I don't know or really like those macros) or Shade-C at all but in my own vertex shader I'd proceed as follows:
For pretty much all of my shaders I use the following base shader (roughly taken from the shader tutorial):
float4x4 matWorldViewProj;
float4x4 matWorld;
float4 vecAmbient;
float4 vecSunDir;
texture entSkin1;
sampler ColorMapSampler = sampler_state
{
Texture = <entSkin1>;
AddressU = Clamp;
AddressV = Clamp;
};
void DiffuseVS(
in float4 InPos: POSITION,
in float3 InNormal: NORMAL,
in float2 InTex: TEXCOORD0,
out float4 OutPos: POSITION,
out float2 OutTex: TEXCOORD0,
out float3 OutNormal: TEXCOORD1)
{
OutPos = mul(InPos, matWorldViewProj);
OutNormal = normalize(mul(InNormal, matWorld));
OutTex = InTex;
}
float4 DiffusePS(
in float2 InTex: TEXCOORD0,
in float3 InNormal: TEXCOORD1): COLOR
{
float4 Color = tex2D(ColorMapSampler, InTex);
float Diffuse = 0.5+0.5*saturate(dot(-vecSunDir, normalize(InNormal)));
float4 final = Color*Diffuse;
return final;
}
technique DiffuseTechnique
{
pass P0
{
VertexShader = compile vs_3_0 DiffuseVS();
PixelShader = compile ps_3_0 DiffusePS();
}
}
Then I modify it as needed. In this case I'd add vecSkill41 as a float4, then multiply InPos.xyz in the vertex shader with vecSkill41.x or vecSkill41.xyz (when I want to have axis independent scaling) (and of course initialize those skills in script with floatv()).
