<sigh> Okay, I have a terrible issue with the texturing on my new project.  No matter what I seem to do, I get the translucent look at dusk/dawn and no textures whatsoever at night.

I first tried using "texture_T" in the Diffuse Color and Specular Color sections of the Material Editor in Gmax, and "texture_L" in the Self-Illumination section.

Then I tried using just "texture_T" in the Diffuse Color section, and left all the others blank.  But no matter what, I still get the same issue.

What am I doing wrong?

I know I've done this before, but I guess it's been so long that I just can't remember what I did to make it work right the last time.

Boikat wrote on Jul 31^st, 2008 at 6:26am:


For FS9, _lm are only used for scenery objects,
_l are used for aircraft.

For FSX, either suffix may be used interchangably. 

Travis wrote on Jul 31^st, 2008 at 3:37am:



Travis Forget this post if is not ..

Are you using makemdl9 FS9-SDK???

Have you applyed to every single XX_T texture a Light map XXX_L in the lightmap slot? ,is well known among desoiners that every single map with reflexion effects (_T) will require a light map (_L) otherwise all the objets map will be transparent , you can use a 0,0,0 256x256 map without alpha, Don't ask me why,I don't know this crazines of FS9 stuff ,but this has to be done to all _T maps  

That is correct , Fuselage1_L doesn't need an alpha ,the Fuselage1_T has its alpha according to the shine part and chrome parts you want ,but It can also be without alpha channel ,the proble seems to be the suffix..

Ok I will ask you some questions to review and see if we can find this issue>:
 ,do you have in the material window above the map the opacity in 100,.. right? and in the map slot is in 100 too,.. correct?, Now in this same map the Fuselage1_L should be in self illumination slot and make sure they both are selected..
T        these two has to have the exact same name with the diference just in the suffix in the texture folder ,make sure they are in dtx3 or 1  (It could be that the lightmap (fuselage1_L) could be bad compress too..
L


Make sure you are not using FlightSimX mode (The new FSX-SDK) you have to use standard material when you pick them up..
Also make sure the square box(Show map in view port) IS selected ,try to compare this drawing I made as example it has to be like this:

     

I'm not sure If you can use the FSX-SDK fetures neither DX dialogs for FSX in a makemdl9 ,and I'm almost sure that's what causing the issue,it has to be standard ..

Of course Im not 100% sure

. . . oh . . .

You sure it isn't any easier than that?  I mean, can't any of YOU guys do it for me?

Alejandro Rhodes wrote on Jul 31^st, 2008 at 1:20pm:


Actually Alex, in FSX what you name any bitmap is completely irrelevant...

...with the sole exception of vc panel textures where the $ prefix is required. The "$" (dollar sign) is a special flag that tells FS to auto-generate a virtual bitmap on which to display gauges.

As an experiment, I named the fuselage texture for Diffuse Color "Fred.bmp" and the Self-Illumination texture "Ginger.bmp"...

"Fred.bmp" displayed the fuse texture just fine, and "Ginger.bmp" supplied the lightmap without problems!  

But, for the sake of our continued sanity, I highly recommend that folks continue to use a rational and meaningful system for naming their model's files!!!  

I had that same problem with when fooling around with a texture, and I think the little black  "whatever_lm" was what fixed it.

Okay, well I was reading, but I guess not comprehending.

I have a texture labeled "Texture_L" along with "Texture_T", and the _L is the pure black (0,0,0) with a pure white (255,255,255) alpha channel, saved in DXT3.  What I'm reading you saying is that the black needs to be (5,5,5) right?


EDIT: Oh, right.  White alpha means that it goes transparent, right?  Everything is fixed now . . .