avatar
schatten
REGULAR
1Issues
0Score
  • schattenon [A3G-84]

    L'assembly satellite denominato "arma3launcher.resources.dll, PublicKeyToken=" per le impostazioni cultura di fallback "en-US" non è stato trovato o caricato. In genere si tratta di un problema di installazione. Provare a reinstallare o ripristinare l'applicazione.

  • schattenon [A3G-50]

    @davidovitch, as a workaround you can use this code for codeStart param:

  • schattenon [A3G-50]

    @davidovitch, thanks for clarification, that makes sense for me. But I'm afraid the fix may break existing missions. Maybe @bis_fnc_kk can say something about this issue?

  • schattenon [A3G-50]

    @davidovitch, as soon as you activate the action, you immediately assign true to test variable, which blocks the action from being shown. So I don't see any bugs here.


    @julius, the fix is in Capsule mod.

  • schattenon [A3G-52]

    No, I haven't contacted neither Bohemia support nor Steam support because Russian is my first lang. If they don't help, I can only suggest a workaround that helped me change lang of CODMW2 (2009, also "Retail (RU)") to English -- I replaced Russian files with English ones.

  • schattenon [A3G-52]

    I agree with @bis_fnc_kk -- you most likely have region specific copy of the game. I have "Arma 3 - Retail (RU)" (or something like this, you can check in your account, not in the profile) and also have only 2 langs -- English and Russian.
    If you want to have more langs, you most likely should buy another copy of the game in Steam.

  • schattenon [A3G-17](edited)

    The same for me. I only see this on Sefrou-Ramal terrain from Western Sahara CDLC (I have only this DLC), not on vanilla ones, nor on terrains from mods (for example, CUP Terrains).

    AFAIR, the bug appeared after WS 1.1(.x?) update was released -- somewhere at the end of 2022 or beginning of 2023.

  • schattenon [A3G-6]

    Understood, thanks.

  • schattenon [A3G-6]

    It's still somehow strange -- despite the presence of the word "Men", I'll have to use additional filtering to exclude agents: allDeadMen select { _x getEntityInfo 0 }. The same I can do using allDead command: allDead select { _x getEntityInfo 0 }. It turns out that the only advantage of allDeadMen is the smaller size of the returned array.

  • schattenon [A3G-6]

    Did you mean "including agents"? If so, then I expected that the command returns human agents, not all agents. There is allDead command for this. Isn't that logical?

  • schatten
    created issue
    A3G-6·allDeadMen returns not only men