Hello girls and boys, is the any grass in pak0.pk3 for landmines /textures, what are they using in wursburg radar?
landmine grass
You can download the core map sources and see by yourself:
http://www.splashdamage.com/content/wolfenstein-enemy-territory-map-source-files-released
An other way is to read the .shader files or make one specific shader with the features you’re looking 
Oh f…k
I used the find texture replace thing and maked some experiments with my terrain which terran texture that looked best but now all things i try got a metal shader argggg
So when you shoot at it, there is no brown spray just a kloooong sound like metal, and landmines cant be placed, even my original texture dont work…
surfaceparm metal or landmine (without s I think, check any core map shader, some starts by mp_) in your shader.
Like you have textures/oveove/metal.jpg, you can make a shader textures/oveove/metal for it.
[QUOTE=Mateos;486025]surfaceparm metal or landmine (without s I think, check any core map shader, some starts by mp_) in your shader.
Like you have textures/oveove/metal.jpg, you can make a shader textures/oveove/metal for it.[/QUOTE]
I got already a texture and shader…
textures/ove_terrain/f_radar_grass
It got surfaceparm landmine
It worked before…
But not now…
Do you think i want a shader for both landmine and metal?! No just terrain, surfaceparm landmine and surfaceparm grass i think, however i wrote the shader for 6months ago… it have worked until now. The shader stop working!
Yeeeh i guess so or?
Ive pack the map in 3 pk3 same time…
But the other ones is removed now
But the shader exist in all of them…
I probably most clean up my etmain folder?
From uneeded or old files
should always have one install for mapping and one for gaming. I’ve learnt this the hard way… Then you are also able to test your pk3 for missing textures etc.
Oh hm i got 2 versions/2 et
One is a little bit played so common maps is there, like adlernest sw-goldrush-te fata morgana and thing/maps like that-maby i should remove thoose…
However i can install a new et and delete all things;)
you should always have a clean et install to start the mapping with, then add your textures and scripts and stuff along the way,
if you have other map pk3 in that folder their texture will also show up in textures in gtk. and then suddenly you got missing textures in pk3
For testing your maps, you don’t always pack a PK3 I hope?
If so, with sv_pure 0, you can directly test the map after the compilation. This is better in a game install dedicated to the mapping 
[QUOTE=Mateos;486053]For testing your maps, you don’t always pack a PK3 I hope?
If so, with sv_pure 0, you can directly test the map after the compilation. This is better in a game install dedicated to the mapping :)[/QUOTE]
Sv_pure 0
Devmap nb_firsttest
And
Developer 0
If i want
Yes ive learn some stuff here becuse of you boys, thank you.
Okey;
This is crazzzzzzy!
When i load the textures in radiant are they sorted by shaderfile.
The are for exemple called ove_terrain.
When i open the thing textures in radiant will all textures load, usefull if you searching for something, however.
But when i open my own shader is the textures like metal,
If i searching for them in the textures (all shaders same time) is there 2 of my textures one with my shader and one with a metalshader
Do you mean you have 2 different shaders for one file in your custom .shader file?
I’m reading your post over and over, I still am not sure what you mean ^^’
[QUOTE=Mateos;486376]Do you mean you have 2 different shaders for one file in your custom .shader file?
I’m reading your post over and over, I still am not sure what you mean ^^’[/QUOTE]
It seams like got 2 shaders for the same texture -yes.
One of them seams to produce itself…
Becuse i ddoonntt apply metalshaders on grass:(
However ive find my original texture with grass and landmine surfaceparm…
I hope they have a different shader name? ^^’
There’s no problem having several shaders for a file, just name them differently; Check for typos too if something isn’t well working: a typo and all the instructions after it are ignored, but not the one above (could explain why some stuff work and not other).
