Terrain Painter [LOGGED]
by Paul Yoskowitz · in Torque 3D Professional · 09/21/2010 (3:55 am) · 5 replies
Any terrain material that was in the terrain painter material selector prior to upgrading to beta 3 works fine. However, now when you try to enter a new material and select a new diffuse it comes up as a blank box. If you select it in the material selector and try to paint the terrain with it nothing happens.
Looking at the material.cs file this is an example of an old terrain material:
new TerrainMaterial()
{
diffuseMap = "art/terrains/LavaFlow";
internalName = "lavacrust";
};
Since the beta3 upgrade this is what the new entries look like:
new TerrainMaterial()
{
diffuseMap = "../../../../Torque 3D 2009 Pro 1.1 Beta 2/My Projects/Dungeon1/game/art/water/LavaCrust";
internalName = "test";
};
What seemed to get it to work was to go into the materials.cs file and delete the excess information and make it look like the old versions. Then save the materials.cs file and reload torque it then came up as a preloaded material to select and it seems to be working. I have to do this every time that I want to add a new material.
Looking at the material.cs file this is an example of an old terrain material:
new TerrainMaterial()
{
diffuseMap = "art/terrains/LavaFlow";
internalName = "lavacrust";
};
Since the beta3 upgrade this is what the new entries look like:
new TerrainMaterial()
{
diffuseMap = "../../../../Torque 3D 2009 Pro 1.1 Beta 2/My Projects/Dungeon1/game/art/water/LavaCrust";
internalName = "test";
};
What seemed to get it to work was to go into the materials.cs file and delete the excess information and make it look like the old versions. Then save the materials.cs file and reload torque it then came up as a preloaded material to select and it seems to be working. I have to do this every time that I want to add a new material.
About the author
http://winterleafentertainment.com/
#2
I think I see what the problem is. The directory for your new entries is pointing to the Beta 2 directory. Make sure to point it to assets that are within your game directory.
09/21/2010 (8:27 pm)
@PaulI think I see what the problem is. The directory for your new entries is pointing to the Beta 2 directory. Make sure to point it to assets that are within your game directory.
#3
I see that now.... however, i had copied everything over to the BETA3 directory after the upgrade. Ill try it again later tonite.
09/22/2010 (3:35 pm)
@ScottI see that now.... however, i had copied everything over to the BETA3 directory after the upgrade. Ill try it again later tonite.
#4
I finally had a moment to try this.... like the Forest editor, it automatically was pointing at BETA2 directory and this had to be changed manually - each time.
this seems to be a common issue imo. Am i missing a setting to change this somewhere? i dont see why this stuff wouldnt be automatically remapped with the upgrades. just my thoughts.
09/28/2010 (5:28 am)
@ScottI finally had a moment to try this.... like the Forest editor, it automatically was pointing at BETA2 directory and this had to be changed manually - each time.
this seems to be a common issue imo. Am i missing a setting to change this somewhere? i dont see why this stuff wouldnt be automatically remapped with the upgrades. just my thoughts.
#5
Sorry for the delayed response, looks like I forgot to check notify.
Was Beta 2 and Beta 3 installed? If you have have both Beta 2 and Beta 3 installed then it's possible for wires to get crossed there as they share the same registry and app settings. It sounds like that's what you're experiencing. I've had it happen myself a couple times where I needed both installed at once for testing purposes.
It's best to remove previous Betas before installing new ones. When porting a project from one Beta to another all you need to do is copy the project folder and the engine folder (if you made any engine changes of course).
10/18/2010 (8:48 pm)
@PaulSorry for the delayed response, looks like I forgot to check notify.
Was Beta 2 and Beta 3 installed? If you have have both Beta 2 and Beta 3 installed then it's possible for wires to get crossed there as they share the same registry and app settings. It sounds like that's what you're experiencing. I've had it happen myself a couple times where I needed both installed at once for testing purposes.
It's best to remove previous Betas before installing new ones. When porting a project from one Beta to another all you need to do is copy the project folder and the engine folder (if you made any engine changes of course).
Full Sail QA&U Lab Intern