Game Development Community

Hardcoded directory paths to the "Common" directory

by Mikael "soho" · in Torque Game Engine · 11/22/2005 (8:43 am) · 1 replies

Around line 388 in interior.cc:
mWhite = new TextureHandle("common/lighting/whiteAlpha255", MeshTexture);
mWhiteRGB = new TextureHandle("common/lighting/whiteNoAlpha", MeshTexture);
mLightFalloff = new TextureHandle("common/lighting/lightFalloffMono", BitmapTexture, true);

Around line 800 in terrData.cc:
mDynLightTexture = TextureHandle("common/lighting/lightFalloffMono", BitmapTexture, true);

Around line 1420 in fxSunLight.cc:
mLocalFlareTextureName = StringTable->insert("common/lighting/corona");
mRemoteFlareTextureName = StringTable->insert("common/lighting/corona");

Since im not a wizard on the engine, so I'm not sure exactly what these does, but might it not be an idea not to hardcode these paths? Some people (like me) are not using the default directory structure.
NextNext Thread
PrevPrevious Thread
More from Torque Game Engine


Associate Kyle Carter
#1
11/22/2005 (10:01 am)
It's actually a fairly crufty thing to do; they should be driven by script variables or by some other heuristic, or just procedurally generated so there's no dependency.

On the other hand, it has been brought up several times in the forums, and you'll get console spam about them (as it should report it was unable to find the texture), so it's not the end of the world... And completely departing from the default directory structure is a fairly advanced thing to do, so it's not as important a thing to fix as, say, world editor crash bugs.

If somebody posted a fix for the issue, I'd definitely add it to the list for the next Torque revision! Otherwise it may have a hard time getting high enough on the priority queue to get done in-house. Even our shipping console games keep the common directory around... it's just never been an issue for us to need to change it.