安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
How and why did this issue surface?
(but this works for any mods you want removed from a mission)
FYI:If anyone has specifically written a mission that refers to sound files directly in an SRS mod its possibly going to break, You should not do that when making missions...
(if its in PBO format you will need to unpack it with a tool like PBO Manager.)
https://www.reddit.com/r/arma/comments/fqhpqm/how_to_remove_mod_dependency_from_mission/
steps
1) make a backup copy of the mission with dependency problem
2) load Arma with the mods u want (less the ones u want removed from the mission)
3) In editor save a new blank mission on same map
4) Then on file menu select merge and select the mission you made a backup of, that has mods u don't want in it.
5)This will merge the two and remove any extra mods from this new mission (ie any mods not currently loaded with Arma are removed from the merged mission). So now editor has a merged copy in memory u can save. (it will complain during merge sometimes about missing mods , just close these errors)
(of course if the mission logic needs these mods to run they will now be gone, but that should not be the case for JSRS SOUNDMOD)
I tried this fix, and does not work.