安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
Different mod versions cause crashes like that. Headlight specifically were changed in 0.30 so mechs can have "Spotlight" which increases the light intensity. I imagine someone is using an old mod version :)
I absolutely love your 'Yet Another Mechlab' ... it brings so much value to this game, on so many levels.
But recently, my friends and I have tried to play COOP Career mode. At first, the game crashed for the host, we found the mod responsible and removed it.
Everything works fine until we load into the mission. All the guest players can HEAR the game, but no one can LOAD into the mission except the host.
We stripped it down to vanilla and started adding core mods, and found the culprit: 'Yet Another Mechlab' ... we were devastated. It's just not the same playing MW5 with all the vanilla feel, it leaves a bad taste in the mouth.
The host player has all the DLCs, we tested all the mods for compatibility issues, which took 2 weeks, adding & removing combinations in hopes that somehow we could get YAML to work.
We would much rather play career mode coop with YAML, than without it. Please tell me you have a fix or know why this is happening?
8th Inf Bge, 1st Inf Div, Can North Shore Regiment.
"Pro Jure Constans"
Cmd. E.B.