Cài đặt Steam
đăng nhập
|
ngôn ngữ
简体中文 (Hán giản thể)
繁體中文 (Hán phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bungari)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (tiếng Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraine)
Báo cáo lỗi dịch thuật
but that error occurs usually when the .vmt is a blank, 'lightmappedgeneric' type. if you open the .vmt and change that to something like vertexlitgeneric you should have your texture appear.
in addition to the links 8sian provided, i would also recommend referencing and looking at what other people have done a bit more. for example look at the things they've used and research the topic (so for example if a .vmt is using phongexponenttexture, try looking it up on the valve developer community wiki to see its purpose and how it works)
(maybe missing fields or mismatched vertex compression?),
mesh will not be rendered. Grab a programmer!". Any ideas on what I need to change?
have you checked to see if the .vmt file for the texture is the same name as the material in blender? also is the $cdmaterial in the .qc the same as the actual folder structure, does the .vmt also follow this structure
regarding the other points, 1024 resolution is fine. and regarding the suffixes (d and e) that's the common naming convention for mods like these, they mean 'diffuse' and 'exponent' respectively. they aren't necessary but help with organizing.
displacement and elevation maps are afaik, something source would never really use, i think that's more for actually deforming the mesh according to the black and whiteness of the texture. don't take my word for it on that part; i could be wrong.