安装 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(越南语)
Українська(乌克兰语)
报告翻译问题








Other error that pops up
Unfortunately (or fortunately), I'm not getting one of these errors on my side.
Your first image shows an error due to the variable _arrayStrength being undefined, this variable is used to find the strength of a particular signal in the #EM_Values array used by the Spectrum Device. This value is found by the signalSource function, and is passed to the signalCalculation function. I'm confused as to why you're seeing that error when in the editor.
Your second image shows that signalNameArray is undefined, which is an array of all the signal names. This global array is created by the Device Settings module. I can only reproduce this exact error if I don't have a Device Settings module placed, you say in your initial post that you're using that module, but it may be worth double checking.
Arma 3 is a weird game when it comes to modding, I have experienced issues in the past when a function has been updated, but the module is still try to execute the old function. So my initial suggest is to just place down new modules using the exact same settings, and remove the old ones.
If simply replacing the modules doesn't fix the issue I'd recommend going onto a blank VR map and seeing if the issue persists when placing new modules on that.
If you're still getting the issue despite this it may be beneficial to provide a list of the mods you're using, and if possible a copy of the mission you're seeing this on, which could possibly be done through a Google Drive link. I'm aware of at least one mod that conflicts with mine, but that's due to their usage of the Spectrum Device UI, and has nothing to do with the functions themselves as far as I'm aware.