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
Have you tried one of the default Arma 3 missions just to confirm that it is this game-mode that is causing it? I don't see any reason why loading on Linux would cause scripting errors that you wouldn't see on windows. Can you also confirm for me you are running v0.8.2 and at least 1.44 Arma 3 just so I know you are not using an outdated version?
Unfortunately, I'm not too optimistic about fixing this because I do not currently have a dev environment that allows me to test Linux easily; but I also don't see any reason why the scripting environment should differ either. I will take a look and post back if I come up with anything.
Thanks for letting me know about this.
prior to this i was running epoch with @mas weapons and vehicles along with aiatp pack and im not a complete retardo (as i wrote multiple scripts, released on epoch mod forum) so i dont think anything would give an error on my end and just to be clear, i did disabled all the mods before starting this mission.
i have a sneaky suspicion this is caused by some uppercase letter somewhere, but i have yet figure out what and i havent felt like coaming through all 6mb af scripts to find that one line that is causing this, i was hoping you had some kind of idea what could be the problem.
i dont think the scripting enviorment changes much if any at all, however linux tends to crash or fail to read uppercase lettered pbo files, however i already changed it all to lower case already, so im not sure what this could be caused by.
regards
Halv
I have found a handful of threads where capitalisation appears to throw a spanner in the works for linux builds but nothing concrete. I also hear that setting -maxMem=2048 was apparently a fix for some issues. I haven't been able to replicate your error so far, but I do have a tweaked version you can try if you're interested. It's at https://mega.co.nz/#!dEUAnbJa!Xt02S2HBNdbtNoohEOyfdrajLbSzGAfX7ZcM4_15T4g
This version simply reverts to using the standard bis_fnc_mp call, rather than my performance-minded alternative. Any or no errors will certainly help narrow down the problem and if you are happy to share your entire .rpt that would be appreciated too.
The most intriguing part at the moment is why it would cause the whole mission not to load — typically an error at this level (on Windows at least) would still allow the mission to be read and joined, but some features just wouldn't be functional.
to begin with i was hoping i was just something simple i was missing aswell, but the further i come with this, i think that unfortunatly thats not the case.
ill try this version and see what happends, i also updated to 1.46 now (not sure if thats actually a pro) ... worst case i guess ill just have to find why this error happends and come back to you, as i really want to try this "mod".
I'd actually like to extend this offer to you, with the Bro unit, we run dedi linux servers if you wanted to playtest your missionfile and all that as a developer we have a spot open, if you're interested, add me, DM me, etc whatever is easiest for you.