安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
http://imgur.com/hgSHDK7
http://imgur.com/3HUmiU8
http://imgur.com/2TPEJ94
http://imgur.com/Na8aWuL
http://imgur.com/gN4Ur8K
http://imgur.com/VoSljmf
http://imgur.com/Yo80NXZ
http://imgur.com/8iSKsD0
Basically I can't see the customisation options for the weapons.
I'm just wondering if you have a fix.
Evidence:
http://imgur.com/a/MH9Yd
This is what the console says when I equip the weapons:
[Halo Reach - MA-37 Assault Rifle] lua/weapons/tfa_ishi_ma37/shared.lua:179: attempt to index field 'Bodygroups_V' (a nil value)
1. unknown - lua/weapons/tfa_ishi_ma37/shared.lua:179
To my knowledge TFA hasn't released any updates today, and Im holding in an update until I finish the DMR and BR55. Check your most recent subscriptions, I suspect something there is causing conflicts with the TFA base or my weapon specifically.
It could be another swep pack or base, but there is a chance that its a Halo RP server content pack that has an old model of it in it (although the error looks more like a weapon base conflict).
Brilliant, thanks!
The problem with the sight alignment is not a conflict issue, its an issue with me being sloppy, I'll update the pack when I'm home, fixing both the sights alignment and adding/updating the materials of the weapons.