Tooltexture: Difference between revisions
Jump to navigation
Jump to search
Bug:VTF files without mipmaps will not display correctly in the texture preview, regardless of resolution (tested in
). [todo tested in ?]
Confirm:%tooltextures can be a different resolution from the base textures, but Hammer will report the material resolution via the tooltexture. Does this break anything?
SirYodaJedi (talk | contribs) mNo edit summary |
No edit summary |
||
| Line 21: | Line 21: | ||
{{bug|VTF files without mipmaps will not display correctly in the texture preview, regardless of resolution (tested in {{tf2}}).}} | {{bug|VTF files without mipmaps will not display correctly in the texture preview, regardless of resolution (tested in {{tf2}}).}} | ||
{{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?}} | {{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: | [[Category:Shader parameters]] | ||
Revision as of 09:31, 15 August 2023
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.
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 without compiling.