安裝 Steam
登入
|
語言
簡體中文
日本語(日文)
한국어(韓文)
ไทย(泰文)
Български(保加利亞文)
Čeština(捷克文)
Dansk(丹麥文)
Deutsch(德文)
English(英文)
Español - España(西班牙文 - 西班牙)
Español - Latinoamérica(西班牙文 - 拉丁美洲)
Ελληνικά(希臘文)
Français(法文)
Italiano(義大利文)
Bahasa Indonesia(印尼語)
Magyar(匈牙利文)
Nederlands(荷蘭文)
Norsk(挪威文)
Polski(波蘭文)
Português(葡萄牙文 - 葡萄牙)
Português - Brasil(葡萄牙文 - 巴西)
Română(羅馬尼亞文)
Русский(俄文)
Suomi(芬蘭文)
Svenska(瑞典文)
Türkçe(土耳其文)
tiếng Việt(越南文)
Українська(烏克蘭文)
回報翻譯問題
issues did not happen on my end, and if you happen to find what is causing conflicts, that would be appreciated
Thank you for your quick response! I'll check if I can find the addon
APPARENTLY I found the problem: it was this addon:
https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=202241938&searchtext=improved+phys+tf2
Yeah! Apparently it works again, Thank you!
Most modelers think that it could be broken stand post tool so its related one of models itself has IK chains. Heavy models is the most common that has IK chains while Scout and Soldier doesn't have IK chains but its easy to decompile them and remove IK chains.
After testing it a few more times, it keeps saying that certain "bases" of various mods are giving errors, which might be a hint as to what is going wrong here. But I'm not a programmer so I can't really say for certain.
Here are the messages if you can make sense of them:
[Standing Pose Tool] lua/autorun/standpose.lua:45: Tried to use a NULL entity!
1. GetBonePosition - [C]:-1
2. func - lua/autorun/standpose.lua:45
3. unknown - lua/includes/extensions/net.lua:32
[Standing Pose Tool] Warning! A net message (StandPose_Server) is already started! Discarding in favor of the new message! (properties)
1. MsgStart - lua/includes/modules/properties.lua:7
2. Action - lua/autorun/standpose.lua:73
3. unknown - lua/includes/modules/properties.lua:60
4. ExecuteListener - lua/slib_framework/extension/gui/cl_listener.lua:5
5. DoClick - lua/slib_framework/extension/gui/cl_listener.lua:29
6. OnMouseReleased - lua/vgui/dlabel.lua:237
7. unknown - lua/vgui/dmenuoption.lua:76
The top error was the most common.
at least it won't try to spawn stuff outside of map's bounds if it works out.