Added a second vect4f to tempvars so renamed the

first one to follow other conventions.  Seems like
Material is the only thing using it (and I think it
could get away with a vec3 really but no harm done).
This commit is contained in:
pspeed42 2014-08-12 16:31:06 -04:00
parent 079c4c6482
commit e0ee685466
2 changed files with 3 additions and 2 deletions

View File

@ -841,7 +841,7 @@ public class Material implements CloneableSmartAsset, Cloneable, Savable {
Quaternion tmpLightDirection = vars.quat1; Quaternion tmpLightDirection = vars.quat1;
Quaternion tmpLightPosition = vars.quat2; Quaternion tmpLightPosition = vars.quat2;
ColorRGBA tmpLightColor = vars.color; ColorRGBA tmpLightColor = vars.color;
Vector4f tmpVec = vars.vect4f; Vector4f tmpVec = vars.vect4f1;
ColorRGBA color = l.getColor(); ColorRGBA color = l.getColor();
tmpLightColor.set(color); tmpLightColor.set(color);

View File

@ -179,7 +179,8 @@ public class TempVars {
public final Vector3f vect8 = new Vector3f(); public final Vector3f vect8 = new Vector3f();
public final Vector3f vect9 = new Vector3f(); public final Vector3f vect9 = new Vector3f();
public final Vector3f vect10 = new Vector3f(); public final Vector3f vect10 = new Vector3f();
public final Vector4f vect4f = new Vector4f(); public final Vector4f vect4f1 = new Vector4f();
public final Vector4f vect4f2 = new Vector4f();
public final Vector3f[] tri = {new Vector3f(), public final Vector3f[] tri = {new Vector3f(),
new Vector3f(), new Vector3f(),
new Vector3f()}; new Vector3f()};