func_* blue doesnt go invis...


Kehldon
05-13-2003, 01:30 AM
Hi! My func_wall / illus doesnt go invisible if I texture them with { - textures that contains blue areas. I use render mode solid and fx-amount 255 just like before but they appear with blue showing ingame.

I have repaced some of those in a larger wad with wally, might it have something to do with that? And if so what can I do about it to correct it ?

El Capitan
05-13-2003, 01:35 AM
i thought textures beginning with { were decals or something

I'm probabaly wrong, shoot me :P

Also, what are you using the blue/invisible for - might it be better to use a clip texture to render it invisible or do you not want bullets flying through? what are you covering with it, etc? :)

Kehldon
05-13-2003, 01:55 AM
You are somewhat wrong :D

{ infront of a texture indicates that some parts of the texture contains invisble parts...

Im useing for hedges and ladders so it looks a bit weird atm.
So I dont want it entirely invis, just the blue part like the on a ladder between the ribs...

Inch
05-13-2003, 02:50 AM
texture the brush with the {blue texture

tie it to entity > func_wall or func_illusionary.

next: rendermode = 'solid'
render fx = 10

if it's a func_wall: you can't walk/shoot thru it, if it's an illusionary: no problemo!!

enjoy!!

Kehldon
05-13-2003, 04:20 AM
Hmm... perhaps Im not clear enough...

If I take for example {avaladder from avalanche.wad, apply it to a brush, turn into a entiety, func_wall with rendermode solid and fx amount 255 the invisible part of the ladder still turns up blue ingame.

Now I wondered if Im doing something wrong with the entiety or if its the fact that I manually extracted the texture from avalanche.wad with wally and put it into one of my own wads that messed up it ? If its the texture that is strange what can I do to correct it ?

haircut
05-13-2003, 05:39 AM
I have repaced some of those in a larger wad with wally

You could have screwed up the colour indexing of the texture, make sure the last colour in the pallet is the Blue colour.

Kehldon
05-13-2003, 07:25 AM
You could have screwed up the colour indexing of the texture, make sure the last colour in the pallet is the Blue colour.

Yupp, the last one is the blue one, but examining my textures closely and comparing them with the originals I just discovered that they are diffrent. Wally must have screwed up something, like changeing bmp:s to jpg:s will destroy your pictures.

05-13-2003, 01:55 PM
ok heres teh check list for invisble blu textures

1- make sure the last colour in the pallette is blue
2- make sure the blue is RGB= 0 0 255
3- make sure that is the blue used
4- make sure the texture has the { prefix
5- make sure the brush the texture is on is set to "render mode= solid" "fx ammount=255"

Kehldon
05-13-2003, 02:21 PM
6- make sure that if you extract textures from a wad, use the extract to tga format in order to preserve the exact same texture.

Gorbachev
05-13-2003, 04:56 PM
I've always extracted to .bmp and had no problems, and I deal with wads that are 50-100MB :p

05-14-2003, 02:43 PM
just open a wad in wally, select a texture, right click then copy.
and just paste it into a different new wad

works for me

CptMuppet
05-15-2003, 05:46 AM
Make sure u dont have more than one blue index- pasting in2 wally sometimes means the blue colour isn't the last one, so in my early days of texturing, I found that cud be a problem...

Day of Defeat Forum Archive created by Neil Jedrzejewski.

This in an partial archive of the old Day of Defeat forums orignally hosted by Valve Software LLC.
Material has been archived for the purpose of creating a knowledge base from messages posted between 2003 and 2008.