Game Development Community

Request for CShop Pipeline

by Todd D. Degani · in Artist Corner · 05/31/2005 (5:25 pm) · 3 replies

Tom do you think you could remove the lines in the map2dif source that make it look for NULL, ORIGIN, TRIGGER, and FORCEFIELD? Its a pain having these extra textures around just so the console wont throw warnings at me.

I would post the code but its a public forum. A quick grep for FORCEFIELD in all caps should find you the offending code pretty quickly.
NextNext Thread
PrevPrevious Thread
More from Artist Corner


Associate Tom Spilman
Sickhead Games
#1
06/01/2005 (10:39 pm)
I don't understand the problem. You shouldn't need these textures to export or use a DIF from Pipeline. Maybe you could give me a detailed explanation of your problem so i can better help you with it.

Torque Owner Todd D. Degani
#2
06/01/2005 (10:57 pm)
They are not required but you get warnings in the console.

For example, I have a file called pot.dif and when TGE goes to load it in I get the following in my console:
Could not locate texture: FFL/data/interiors/mall/Pot/NULL
Could not locate texture: FFL/data/interiors/mall/Pot/ORIGIN
Could not locate texture: FFL/data/interiors/mall/Pot/TRIGGER
Could not locate texture: FFL/data/interiors/mall/Pot/FORCEFIELD

I believe the reason I get this is because the map2dif code calls InsertTexture on each of these file names.

Associate Tom Spilman
Sickhead Games
#3
06/02/2005 (4:39 pm)
I believe that is normal behavior in map2dif and the interior object. I think it was Ben who said that the Interior object needs to be fixed to not try to load those special textures. A quick look at the map2dif code it seems that you have to export *something* for each surface texture and for all i know someone writing some custom code for their game could be expecting to see these special texture names.

So being the industrious code monkey that i am i went ahead and submitted a fix for this to 1.4 RC1.