Tooltexture: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
mNo edit summary
m (re-add important removed information)
Line 1: Line 1:
Used to blend [[texture]] previews in [[Hammer]].
Used to blend [[texture]] previews in [[Hammer]].


In Hammer and in-game, the material is scaled down to the size of the tooltexture. Unfortunately, you can't make the preview smaller to save space. You'll need one as large as the material you want to display.
When using a preview tooltexture in a material, the material is scaled up or down to the size of the tooltexture. If the material is a blend of two 1024x1024 textures but your tooltexture is only 256x256, the 1024x1024 textures will be scaled down to the much lower quality of 256x256. Unfortunately, this means that the tooltexture cannot be made smaller to save space (since nobody will see it in-game). You'll need a preview tooltexture as large as you want the texture to display within the engine.


[[File:Blend texture preview01.jpg|The texture to the left|thumb|190px]]
[[File:Blend texture preview01.jpg|The texture to the left|thumb|190px]]
Line 20: Line 20:
Without a tooltexture, Hammer will only show your first [[$basetexture]], making it impossible to see the blend in the texture browser.  
Without a tooltexture, Hammer will only show your first [[$basetexture]], making it impossible to see the blend in the texture browser.  
{{bug|VTF files without mipmaps will not display correctly in the texture preview, regardless of resolution (tested in {{tf2}} {{dods}}).}}  
{{bug|VTF files without mipmaps will not display correctly in the texture preview, regardless of resolution (tested in {{tf2}} {{dods}}).}}  
{{modernConfirm|%tooltextures ''can'' be a different resolution from the base textures, but Hammer will report the material resolution via the tooltexture. Does this break anything?}}
[[Category:Shader parameters]]
[[Category:Shader parameters]]

Revision as of 13:08, 3 January 2024

Used to blend texture previews in Hammer.

When using a preview tooltexture in a material, the material is scaled up or down to the size of the tooltexture. If the material is a blend of two 1024x1024 textures but your tooltexture is only 256x256, the 1024x1024 textures will be scaled down to the much lower quality of 256x256. Unfortunately, this means that the tooltexture cannot be made smaller to save space (since nobody will see it in-game). You'll need a preview tooltexture as large as you want the texture to display within the engine.

The texture to the left
WorldVertexTransition
{
$basetexture    dirt/blend1_mountain_dirt_a1
$basetexture2   dirt/blend2_mountain_dirt_a1
%tooltexture    preview/blend_mountain_dirt_a1
$bumpmap        dirt/blend_mountain_dirt_a1-ssbump
$ssbump         1
%detailtype     desert1
$detail         dirt/blend_mountain_dirt_a1_DM
$surfaceprop    dirt
$surfaceprop2   rock
}

Without a tooltexture, Hammer will only show your first $basetexture, making it impossible to see the blend in the texture browser.

Icon-Bug.pngBug:VTF files without mipmaps will not display correctly in the texture preview, regardless of resolution (tested in Team Fortress 2 Day of Defeat: Source).  [todo tested in ?]