Hallo!

Hab grad mal mit Wally ne Textur im wad Format erstellt. Aber wohin jetzt damit, dass ich sie im Hammereditor auswählen kann?

Danke!

Sys: AMD Athlon64 3000+ @ 4000+ (2600Mhz) // ASUS V9999GT @ 350/700 (71.20)

1024MB Infineon PC3200 CL2 @ DDR 370 // MSI K8N Neo2 Platinum (nForce3 Ultra)

bin sicher das das mit hilfe der forensuche zu finden wäre, aber bin ma so nett:
Speicher die wad-Datei in deinen Half-Life\valve - Ordner. Dort kannst du ihn per Hammer unter Options\Textures auswählen und einfügen (add). Die Texturen sollten daraufhin auswählbar sein.

Ok, ich hab jetzt in den Hammer geadded, aber was jetzt?

http://img50.exs.cx/img50/9016/3459hr.jpg

Im Tool " Texture Application" und auf Browse is es immernoch nicht da...

Sys: AMD Athlon64 3000+ @ 4000+ (2600Mhz) // ASUS V9999GT @ 350/700 (71.20)

1024MB Infineon PC3200 CL2 @ DDR 370 // MSI K8N Neo2 Platinum (nForce3 Ultra)

Was geht'n mit dir ab?
WADs sind für HL1. Les mal die offizielle SDK Dokumentation aka RTFM.

Trollpolizei!!! °_o
"War is God's way of teaching geography to Americans."
"RTFM du beschissener Kack-B00n..."
Forenregeln | TheWall Wiki | Source SDK Dokumentation

Ja, toll, woher soll ich das wissen *rolleyes*

Im 2ten post steht, das ich das so machen soll...

Wie bekomm ich sonst in HL2 Texturen rein?

Sys: AMD Athlon64 3000+ @ 4000+ (2600Mhz) // ASUS V9999GT @ 350/700 (71.20)

1024MB Infineon PC3200 CL2 @ DDR 370 // MSI K8N Neo2 Platinum (nForce3 Ultra)

Zitat:

devil55 postete
Ja, toll, woher soll ich das wissen *rolleyes*

Im 2ten post steht, das ich das so machen soll...

Zitat:

Wie bekomm ich sonst in HL2 Texturen rein?

There is nothing wrong with high standards. It's your problem that you don't meet them.
If you think it's simple, then you have misunderstood the problem.
When a customer says "nothing has changed", assume they're lying.

Öhm, naja, ich hab gedacht mit Wally kann man auch HL2 Texturen machen...

Sys: AMD Athlon64 3000+ @ 4000+ (2600Mhz) // ASUS V9999GT @ 350/700 (71.20)

1024MB Infineon PC3200 CL2 @ DDR 370 // MSI K8N Neo2 Platinum (nForce3 Ultra)

Hmmm, ich find da keine gute Anleitung zum erstellen eigener Texturen...

Sollte einfach nur die einfachste Anleitung sein^^

Sys: AMD Athlon64 3000+ @ 4000+ (2600Mhz) // ASUS V9999GT @ 350/700 (71.20)

1024MB Infineon PC3200 CL2 @ DDR 370 // MSI K8N Neo2 Platinum (nForce3 Ultra)

Zitat:

Compiling Source Textures

The Source engine uses .VTF (Valve Texture) files to store its texture data. These files contain not only the basic source data, but also mip-levels used for rendering the texture over varying distances. .VTF files are created from .TGA files (16, 24, or 32-bits in depth). All .TGA files must have a resolution equal to a power of 2, although the height and width can be different (i.e. 16x16, 32x32, 64x128, 128x128, 128x256, 512x512, etc.).

The tool Vtex (located in sourcesdk/bin) is used to compile .TGA files into the .VTF format. Vtex takes a .TGA file and an optional text file that describes extra parameters for compiling the texture. Using these two files then it creates a .VTF file. The .TXT file containing the parameters must share the same base name and directory as the .TGA file being compiled. For example: the test.tga file must be in the same directory as the test.txt file for the tool to link the files properly.

If a .TXT file does not exist, Vtex will automatically create an empty file with the correct name and in the correct location. The following section describes the compile parameters that can be inserted in this .TXT file.

To compile a texture, simply drag either the .TXT or .TGA file onto the sourcesdk/bin/vtex.exe icon, or supply the filename of either file as a command-line parameter to Vtex. The tool will report that it created the file and a .VTF will be created in the parallel materials sub-directory to where the source texture resided. Note: For this to work properly, you must select the correct game directory for your MOD. If the destination directory in /materials does not exist, you must create it in both locations before continuing.

For example, if you’re compiling a TGA file named "sample.tga" that resides in "sourcesdk_content/hl2/materialsrc/test/MyTexture.tga", the resulting .VTF file will be placed in "/half-life 2/hl2/materials/test/MyTexture.vtf".

Zitat:

Creating a .VMT file

Once the .VTF file has been created, a .VMT file must be created to actually use the texture inside of the engine.

The .VMT will define how the .VTF file is rendered to the screen. There are many shaders that can be used to render a texture. To begin with, we'll use a simple shader: LightmappedGeneric. This shader is used for world surfaces that should receive lightmaps.

The simplest definition of this shader is:

"LightmappedGeneric"
{
"$basetexture" "test/MyTexture"
}

This will render the ”test/MyTexture” .VTF file opaquely and with lightmaps applied to it. This is most generally used for textures applied to brush surfaces (like walls). With a .VTF file and .VMT file created, we can use this texture inside of Hammer on surfaces.

One of the easiest methods of creating new .VMT files is to open an existing .VMT that has similar properties to the material you are creating. Edit the contents of the file and save it with a different name to create a new material.

"LightmappedGeneric"
{
"$basetexture" "*texturname*"
}

Das musst du für jede Textur machen, aber du kannst ja immer die Datei kopieren und umbenennen.

Es gibt sicher einfachere Wege (Batch, Tool) aber das ist der grundsätzliche Vorgang.

Mit *game* ist das Mod / Game Verzeichnis gemeint. z.B. hl2, cstrike, hl2mp bzw- Half-Life 2, Counter-Strike etc.
*texturname* beschreibt den Namen deiner Textur.

Trollpolizei!!! °_o
"War is God's way of teaching geography to Americans."
"RTFM du beschissener Kack-B00n..."
Forenregeln | TheWall Wiki | Source SDK Dokumentation