White Terrain Textures
by Steve Lamperti · in Torque Game Engine · 01/08/2004 (1:18 pm) · 10 replies
I'm seeing something kind of strange, which I was hoping someone could enlighten me on. When I open my Torque project on another machine other then the one I develop on, the terrain textures are initially being rendered as all white. I'm using the terrain textures that come with the grasslands terrain in the FPS demo.
What I see on the target machine is just a terrain, where it doesn't matter which of the three textures was painted, instead it draws a white texture for all the ground.
If I then go into the terrain editor, and lift any part of the terrain a little bit, all the terrain regains it's color. If I then save the mission, the next time I open it, it renders fine.
I'm curious about a couple of things here, the first is just if anyone has any idea what is happening here, and the second is if there is some call I can add to the engine to work around this behavior.
Thanks for any suggestions,
What I see on the target machine is just a terrain, where it doesn't matter which of the three textures was painted, instead it draws a white texture for all the ground.
If I then go into the terrain editor, and lift any part of the terrain a little bit, all the terrain regains it's color. If I then save the mission, the next time I open it, it renders fine.
I'm curious about a couple of things here, the first is just if anyone has any idea what is happening here, and the second is if there is some call I can add to the engine to work around this behavior.
Thanks for any suggestions,
#2
01/08/2004 (2:35 pm)
Desmond I dont think is the problem because he says the textures suddenly appear when he raises a bit of the terrain in the editor. so the texture ARE there, just not being displayed initially...
#3
01/08/2004 (2:44 pm)
I checked the .mis file, and there are no paths in there to the terrain texture files at all. I think there may be paths in the .ter file, which is rebuilt when you save the mission. Perhaps I need to add explicite paths in the mission file, but it's based on the stronghold mission file, which doesn't have those paths either. 
#5
Did you ever fix this? I'm having the same problem after a rebuild of my computer. I know I had it before and fixed it but can't remember how. I know the texture paths are in the .ter file but I can't remember how to fix them.
04/23/2004 (8:35 am)
@SteveDid you ever fix this? I'm having the same problem after a rebuild of my computer. I know I had it before and fixed it but can't remember how. I know the texture paths are in the .ter file but I can't remember how to fix them.
#6
I have a cross platform project, and it turned out that I don't think I was reconstructing everything on the mac side after moving things over from the PC side. Specifically, I think it was the terrain file. I believe that the terrain file is rebuilt when you resave the mission, so tweeking your mission file, and selecting save mission from the menu should be ok. (I also would suggest throwing away all .dso files, as they also should be compiled on the machine that you are running on.)
I think this is what solved this problem for me. I haven't had it in a while.
04/23/2004 (9:33 am)
@jeff,I have a cross platform project, and it turned out that I don't think I was reconstructing everything on the mac side after moving things over from the PC side. Specifically, I think it was the terrain file. I believe that the terrain file is rebuilt when you resave the mission, so tweeking your mission file, and selecting save mission from the menu should be ok. (I also would suggest throwing away all .dso files, as they also should be compiled on the machine that you are running on.)
I think this is what solved this problem for me. I haven't had it in a while.
#7
Thanks, but I found it.
@Anyone Who Wants to Know
I figured this out late last night. This happens anytime that you move missions from one directory within .\example to another regardless of whether the platform changed.
In order to fix this you need to:
1) Start the mission that is having the issue
2) Go into the Mission Editor (F11)
3) Go into the Terrain Texture Editor (F8)
You'll see on this screen that the subdirectory is indeed embedded in the .TER file.
4) Press Delete for each of the textures on this screen
5) Do an "Add Material" for each of the textures from the new location (supposedly the same ones just in a different place).
6) Go to into the Terrain Texture Painter. The etextures to the right will still be labeled something like "grass', 'rock', etc.,...
7) Use the 'Change' button on each texture and reselect the textures you want for each.
8) Save the mission file, and it's fixed (until/if you move it again).
9) Return to the game play (F11 again)
It's fixed!
04/24/2004 (8:31 am)
@SteveThanks, but I found it.
@Anyone Who Wants to Know
I figured this out late last night. This happens anytime that you move missions from one directory within .\example to another regardless of whether the platform changed.
In order to fix this you need to:
1) Start the mission that is having the issue
2) Go into the Mission Editor (F11)
3) Go into the Terrain Texture Editor (F8)
You'll see on this screen that the subdirectory is indeed embedded in the .TER file.
4) Press Delete for each of the textures on this screen
5) Do an "Add Material" for each of the textures from the new location (supposedly the same ones just in a different place).
6) Go to into the Terrain Texture Painter. The etextures to the right will still be labeled something like "grass', 'rock', etc.,...
7) Use the 'Change' button on each texture and reselect the textures you want for each.
8) Save the mission file, and it's fixed (until/if you move it again).
9) Return to the game play (F11 again)
It's fixed!
#8
04/24/2004 (9:49 am)
Glad you found a fix!
#10
08/24/2006 (3:00 pm)
Hehehe and over 2 years later I just used that same fix..... thanks Jeff.... and thanks Search function!! :D 
Torque Owner Desmond Fletcher
fletcher