Could not locate text
by Steve Lamperti · in Torque Game Engine · 10/24/2003 (2:45 pm) · 1 replies
I'm seeing some Could not locate texture messages that I don't understand in my project. I know this subject has come up before, and I have read some of the other posts on it, but I find that I am still confused as to what is happening here, and I would appreciate it if someone that understands it better might be able to clarify it for me.
First it is looking for the texture data/shapes/player/base.lmale. I really have no idea where this one comes from, as I cannot find base.lmale, or just lmale anywhere in either the engine, or in my scripts.
Then it tries to locate data/shapes/player/crossbow, and data/shapes/player/clip. Also texture names that I cannot find, certainly with that path. (The crossbow stuff is currently in the crossbow subfolder of the shapes folder.)
Then It gives me about 7 or so
Could not locate texture:
With a blank texture name.
I know that I could comment out the 'Could not locate texture' error message, but I really do not like this solution, as I will be adding textures in the future.
I know that I could also add dummy textures in the locations that it is searching, but this also doesn't seem like a clean solution. What I would really like to do is to figure out where it is coming up with these texture names and paths, and remove the initial request.
If someone has any suggestions, I would appreciate hearing them.
First it is looking for the texture data/shapes/player/base.lmale. I really have no idea where this one comes from, as I cannot find base.lmale, or just lmale anywhere in either the engine, or in my scripts.
Then it tries to locate data/shapes/player/crossbow, and data/shapes/player/clip. Also texture names that I cannot find, certainly with that path. (The crossbow stuff is currently in the crossbow subfolder of the shapes folder.)
Then It gives me about 7 or so
Could not locate texture:
With a blank texture name.
I know that I could comment out the 'Could not locate texture' error message, but I really do not like this solution, as I will be adding textures in the future.
I know that I could also add dummy textures in the locations that it is searching, but this also doesn't seem like a clean solution. What I would really like to do is to figure out where it is coming up with these texture names and paths, and remove the initial request.
If someone has any suggestions, I would appreciate hearing them.
Associate Kyle Carter