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.