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 (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
Open your mission.sqm file.
look for the follow code
and change it to
The mission will then re evaluate what addons are required and make a new list next time you open it, should fix your issue
Mission v2.7 is the one i like to use
All I've ever had to do (except in one instance, which I'll give you in a sec), is to delete the Binarized Addons section of the mission.sqm (leave the brackets). Then open the editor, place an object, delete it, and save (this repopulates the Binarized Addons section of the file). What Hortzy (who is a mission maker himself) suggested seems even more thorough so you could try that too.
One time, I had an error for a mission object and this wouldn't work. However, if you read through this thread: https://forums.bistudio.com/topic/192473-way-to-find-the-real-missing-addon/
We found a way to replace the object itself with a headless client module, which was genius. I was then able to finally open the mission, to then delete the newly added module and replace the faulty object that led to the error.