ever tried the alpha/z material i posted at the very beginning of this thread? --> edit: ah, ic you use EXTRA, so this possibly works only for comm and pro.

if you use a model with multiple textures and only one texture has an alpha channel then the whole model with all of its parts gets treated as transparent. couldn't this be the reason?

I'm quite sure this is how it works. Use the material DaBro0zar posted. Theres also this if your models transparency is messed up within, usually this is used on your vegatation and the such:

Code:

---

 
function mtl_plants_int
{
 mtl.ambient_red    = 220;
 mtl.ambient_green  = 220;
 mtl.ambient_blue   = 220;

 mtl.diffuse_red    = 50;
 mtl.diffuse_green  = 50;
 mtl.diffuse_blue   = 50;

 mtl.emissive_red   = 10;
 mtl.emissive_green = 10;
 mtl.emissive_blue  = 10;

 mtl.specular_red   = 0;
 mtl.specular_green = 0;
 mtl.specular_blue  = 0;

 mtl.albedo = 2;
 mtl.power = 0;
 mtl.skill1=pixel_for_vec(vector(120,0,0),0,8888); // the first value in the vector is the threshold
}

material mtl_plants
{
 event=mtl_plants_int;
 effect=
 "
 texture entSkin1;
 dword mtlSkill1;
 technique vegetation
 {
  pass p0
  {
   Texture[0]=<entSkin1>;
   ZWriteEnable=true;
   Zenable = true;
   AlphaBlendEnable=false;
   AlphaTestEnable=True;
   AlphaRef=<mtlSkill1>;
   AlphaFunc=Greater;
   CullMode=CCW; // CCW or None
 
   ColorArg1[0]=Texture;
   ColorOp[0]=Modulate2x;
   ColorArg2[0]=Diffuse;
  }
 }
 technique fallback{pass p0{}}
 ";
} 

---

But be wary, if A7 turns out to be DX10 based, FFP will be ommited. In this case you can always set it directly in your shaders:

Code:

---

 technique t0
{
 pass p0 //colormap
 {
  AlphaBlendEnable=true;
  //zwriteenable= true;
  zenable = true;
  //FogEnable=true;
  VertexShader = compile vs_1_0 vs_main0();
  PixelShader  = compile ps_1_0 ps_main0();
 }
} 

---

You'll find that due to A6 being slower when theres multiple entities present, your going to have quite big models. Since transparency is based on origin, this causes some problems(because your ground is multitextured). That's why you need to use some of this code from time-time.

Also, you'll find that once the origin of your models pass your clip ranges, the entire model dissapears! This is really annoying, due to it I have to keep the cliprange high all the time(since roadway is one model, can't split it up or their will be many seams in 3dgs, possibly due to the 1quant inaccuracy I think, cause they are no seams in 3ds Max). Hopefully this will change sometime soon, Octree may solve both problems(will split models to take advantage of Octree, and no more inaccuracy)...

camera.clip_near = 25;
Camera.clip_far = 70000;//150000

Jetpack_monkey: There's maybe either something wrong with your models, or it's a bug in Gamestudio.

I suppose that you are using 6.40.5. Make sure that the background object is intransparent. Check the DDS texture. Only the DXT1 format is intransparent. All other formats have an alpha channel. As a test, apply a PCX or BMP texture that is certainly intransparent. If this does not solve the problem, please post again.

Hi all, and thanks for your feedback

Jcl: I've tried both dds dxt1 and bmp for the non-transparent objects, but nothing changes.

Ventilator: these are all single-textured objects.

DaBrooz: Up until today I have been using Extra-- so materials would not help. However I just bought Commercial. After I get it installed I will post if it changes things.

UPDATE: I also tried a piece of new clean geometry with the same texture map on it, and the same problem happens with that too, so it's unlikely that it's the geometry. As I am updating to Commercial sometime today, it will be interesting to see if this phenomenon is an Extra-only problem.

Try using a BMP or TGA file without alpha channel once to possibly rule out a DDS issue. If you still get it, try making a smaller, simpler test level that has the same symptoms and upload this test level somewhere so it can be tested and looked at by other users.

Since the sort order is dependent on the position of the camera from the origin (quoting from above), and that your screenshots don't show the debug panel so the positions are not known, could you post the screenshots to show the position of the camera?

Ulillillia: Thanx, but see my last 2 posts! Already tried the different formats

I'll make a little jr. test level though.. good idea

yours,

The test level doesn't need to be advanced, just enough so that the problem can be replicated and/or seen by others.

I think we've gotta bug!

When the MDL has the transparent texture as an EXTERNAL texture, the problem happens. Not when it's internal. There ya go, one fresh and delicious bug for the bug bbq!

If you cannot reproduce this (conitec) I can provide you with the mdl and external texture.

Which MDL do you mean - the tree or the background object? If that one contains an external transparent texture, the reason for the problem is clear.

Otherwise it could indeed be a bug. But the external texture alone can not be a reason for the problem. You can send the project to the support - please not only the model but a level where the problem is visible. I'll be away the next 10 days, but I'll look into it after my return. The address is support1(at)3dgamestudio(dot)com.