Game Development Community

Argh, help, anyone?

by dsfsd · in Torque Game Engine Advanced · 06/15/2004 (2:09 am) · 5 replies

My latest problem:

www.subreal.net/tse/wtf.gif
Ok, so I've coded about 60+ materials in, in one shot, enough to cover all the stuff I'm working on at the current moment. So I try to load up a simple cube test, one cube per texture (many cubes) and I keep getting that error.

So I figure it must be a error in my definitions, but I've been scouring these things OVER & OVER, and I've fixed a few bugs I missed, but everything is pointing in the right place, checked, triple checked everything. But...I'm still getting that. Is there any easier way to have TSE point out exactly where the problem texture is that's causing a conflict?

I keep seeing this in my crash log right repeatedly:

demo/client/scripts/serverConnection.cs (168): Unable to find function

So I'm pretty sure that means I still have a goof-up somewhere in my definitions, but with the huge amount of materials I have in there I'm having tons of trouble finding the problem 'nick.

Any suggestions on how to make my life a tad easier?....Anyone?

(Just in case.... console.log)
NextNext Thread
PrevPrevious Thread
More from Torque Game Engine Advanced


Torque 3D Owner dsfsd
#1
06/15/2004 (2:22 am)
Hrm, now I'm really confused. I made a single cube, with one texture. I sat down and went over the material definition for that texture and made sure it was PERFECT, same with materialMap.cs and I still am getting that error.

Talk about confused, I just had this working fine two days ago when I tried some test level geometry.

Torque 3D Owner dsfsd
#2
06/15/2004 (2:44 am)
Alright, this is freaking driving me insane.

Here is my code:

//*****************************************************************************
// Rust Town Group Textures
//*****************************************************************************

//******
// Group:Cement
//******

datablock Material(cement_2)
{
   baseTex[0] = "~/data/interiors/rust_town/cement/cement_2";
   bumpTex[0] = "~/data/interiors/rust_town/cement/cement_2_bump";

   pixelSpecular[0] = true;
   specular[0] = "1.0 1.0 1.0 0.1";
   specularPower[0] = 32.0;
};

//---------------------------------------------------------------------------
// Rust Town
//---------------------------------------------------------------------------

//----
//Group:Cement
//----

addMaterialMapping("cement_2", "material: cement_2");

And my PNG file & Bump map:

gremlinstudios.com/tse/cement_2.png
gremlinstudios.com/tse/cement_2_bump.png

No matter what I do, that texture will NOT work, I get the above error message. I've tried changing it to a jpeg, and also tried resizing it to 512x512. Why does TSE hate me? Blah!

Yet oddly enough.....

When I use the EXACT same code as above (just changing the name to cement_1)...this texture works fine:

gremlinstudios.com/tse/cement_1.png
gremlinstudios.com/tse/cement_1_bump.png

I'm missing something, but is there a difference between these two sets of files?

Anyone know why one file works fine but one doesn't?

<----Going crazy.

Torque 3D Owner dsfsd
#3
06/15/2004 (4:01 pm)
Hmm

Update on this, I don't think it's the texture. By renaming cement_2 to cement_1 I was able to use the texture I thought was "bad" easily enough.

However, by using cement_1 (the original one that worked fine) and renaming it to cement_2 I get the crash that I got before, and this texture works fine when named cement_1. Which makes me thing it's a code thing.

By just changing a single digit (1->2) I get these problems....

Ugh.

Torque Owner Peter Dwyer
#4
06/16/2004 (10:37 am)
Just a quick question

Is cement_2 the name of the texture your object is using or is the object you created assigned a texture called cement_1?

in which case your material map would need to be

addMaterialMapping("cement_1", "Material: cement_2");

just a thought

Torque Owner Brian Ramage
Black Jacket Games
#5
06/16/2004 (11:31 am)
Are you trying to connect over a network, or are you just running on your local machine? Sending Material data across a network has not yet been implemented, so that may be your problem.