Unable to find Material?
by cogmac · in Torque Game Engine Advanced · 09/14/2006 (3:16 pm) · 6 replies
I'm new to TSE and Torque in general. When I run TSE and push F11 to get to the new mission editor it crashes and gives a whole bunch of output like this:
MatInstance::MatInstance() - Unable to find material 'TerrainMaterial'
MatInstance::MatInstance() - Unable to find material 'TerrainBlenderPS20Material'
MatInstance::MatInstance() - Unable to find material 'TerrainBlenderPS11AMaterial'
MatInstance::MatInstance() - Unable to find material 'TerrainBlenderPS11BMaterial'
Do I need to copy the material.cs file somewhere else?
MatInstance::MatInstance() - Unable to find material 'TerrainMaterial'
MatInstance::MatInstance() - Unable to find material 'TerrainBlenderPS20Material'
MatInstance::MatInstance() - Unable to find material 'TerrainBlenderPS11AMaterial'
MatInstance::MatInstance() - Unable to find material 'TerrainBlenderPS11BMaterial'
Do I need to copy the material.cs file somewhere else?
#2
If I click the Feature Walkthrough button on the main menu, the demo loads fine. After it loads and I push F11 it takes me to the World Editor and does not crash.
I'm running it on Windows XP SP2, Pentium M 2.13 GHz, 2.00 GB RAM, GeForce GO 6800.
Let me know if theres anything else you want to know.
Thanks for the help.
09/14/2006 (8:37 pm)
Yes it is a clean HEAD build. I'm using VC8. I start debugging and once the window loads (after the garage games logo shows up), I push F11. At this point it begins loading. It says "New Mission - A simple new mission template". After the Loading Objects bar completes, it crashes and spits out a ton of "MatInstance::MatInstance() - Unable to find material " output. If I click the Feature Walkthrough button on the main menu, the demo loads fine. After it loads and I push F11 it takes me to the World Editor and does not crash.
I'm running it on Windows XP SP2, Pentium M 2.13 GHz, 2.00 GB RAM, GeForce GO 6800.
Let me know if theres anything else you want to know.
Thanks for the help.
#3
Hope this helps.
edit: Whoops, it wasn't exactly this problem, but it was this error. Our problem was whenever we would load a mission after setting the mod with the wrong case, not when we were starting up the editor. Although there still might be something related in our solution.
09/15/2006 (7:29 am)
We were having this problem with only one of our programmers (it worked fine for all but one) and what it ended up being was that the programmer was passing along the mod directory with the wrong case on the command line. ie. -game Demo ... instead of: -game demo ... the same thing probably applies to setting the $defaultGame variable with the wrong case as well. The weird thing was that it /would/ actually load up most of the mod functionality except when it came to those materials. It was a pain to track down. So my guess is that those materials are being loaded (or referenced) in a case sensitive way when most everything else is being called in a case insensitive way.Hope this helps.
edit: Whoops, it wasn't exactly this problem, but it was this error. Our problem was whenever we would load a mission after setting the mod with the wrong case, not when we were starting up the editor. Although there still might be something related in our solution.
#4
1. Run TSE
2. Click Feature Walkthrough
3. Click the Home button.
4. Push F11 to create a new mission and enter the editor.
However, now my terrain is black!! I read about the black terrain in another post but it looks like the line/bug that was causing that problem has already been changed and committed. Is this because I am not setting a material for the terrain? (I'm assuming there should be a default one that is displayed.)
Thanks.
09/18/2006 (11:07 pm)
I found if do the following it won't crash:1. Run TSE
2. Click Feature Walkthrough
3. Click the Home button.
4. Push F11 to create a new mission and enter the editor.
However, now my terrain is black!! I read about the black terrain in another post but it looks like the line/bug that was causing that problem has already been changed and committed. Is this because I am not setting a material for the terrain? (I'm assuming there should be a default one that is displayed.)
Thanks.
#5
09/19/2006 (3:49 pm)
Ah, OK, that must have got merged in from TGE. You should not be able to hit F11 from the main menu. You need to be in a mission to be able to edit it. Thanks for the feedback guys, I'll make the appropriate fix.
#6
Presumably there's a path booboo somewhere, but I haven't bothered to investigate it.
09/23/2006 (1:27 pm)
I get the black terrain too, but only in the sample mission. When I make my own terrain, everything is fine.Presumably there's a path booboo somewhere, but I haven't bothered to investigate it.
Torque Owner Brian Ramage
Black Jacket Games
I'm having trouble reproducing this crash in the stock demos. If I hit F11, and try to use the terrain editor in either demo, it does not crash, and it does not report those errors in the console.
Can you give more info? Are you running from a clean HEAD build? Are you simply hitting F11, or are you doing something else in the editor when it crashes?