Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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.