New error after BIS update (SOLVED)

  1. 9 years ago

    So I have a new error that I can't make heads or tails of. It happens at mission start when previewing in the SP editor. Before the update in the very same mission, I had no error at all. Here's a photo: https://www.dropbox.com/s/i4vtg73nnskcuyg/image.jpeg?dl=0

    I'm not sure if it's caused by ALiVE itself, or some of the scripts found in the forums here? I'm using the Intel on dead bodies script: http://alivemod.com/forum/1636-intel-on-dead-bodies-or-in-buildings

    And also a script to "save" AI teammate location for persistence: http://alivemod.com/forum/1613-ai-teammates-location-persistence

    The mission takes over five minutes to load now on my dedicated server (used to take 30 seconds) so I'd have to imagine it's all related if I were to guess. I'd appreciate any help on what could be causing this.

  2. I think I'm getting the same error despite the CBA hotfix. I'm not sure if it's causing the delays but I seem to have them too. The gamebreaking part of it for me is that it delays the loading time past the mission briefing / map screen and also skips the intro, and also skips the player persistence module init. So no player persistence.. There may be a new mod conflict so I'll do some testing. Seems to be funky with just ALiVE and CBA though.

  3. Edited 9 years ago by HeroesandvillainsOS

    @incontinenetia I think I'm getting the same error despite the CBA hotfix. I'm not sure if it's causing the delays but I seem to have them too. The gamebreaking part of it for me is that it delays the loading time past the mission briefing / map screen and also skips the intro, and also skips the player persistence module init. So no player persistence.. There may be a new mod conflict so I'll do some testing. Seems to be funky with just ALiVE and CBA though.

    I think you and I use a lot of the same scripts. Long shot but have you tried launching or previewing with just the mission.sqm? I can try later if you haven't or don't get to.

    For mods I'm using 3CB (all four), Burnes Foxhound, CAF and the audio patch, SpyderAddons, AiA, ALiVE and CBA for the core. Non essentials are Shacktack UI, 101 Editor, Adjustable Full Screen Night Vision.

  4. Edited 9 years ago by HeroesandvillainsOS

    @incontinenetia Okay, I can confirm this happens with just vanilla and CBA, no scripts, just a basic ALiVE island-wide 3-way err... bang session.

    Edit: interestingly, the error doesn't appear on Stratis. Move the exact same modules / configuration, and you get the error on Altis. Perhaps it is an issue only when load time passes a certain threshold.

    LOL!

    So which issue are we talking about now? The error message I posted a picture of above or the intro being skipped/persistence not initializing?

  5. Edited 9 years ago by incontinenetia

    I'd now say they were almost certainly connected. When the error appears, player persistence fails, the mission takes ages to load, and it all goes a bit wrong.

    So the error is:

    '...=([] call BIS_fnc_listplayers) + (call |#|Alive_fnc_allCurators);
    _anyInRange - f...'
    Error undefined variable in expression: alive_fnc_allCurators
    File x\alive\addons\x_lib\functions\units\fnc_anyPlayersInRangeIncludeAir.sqf

    This error happens in Vanilla, with the latest Arma update, latest CBA (the hotfix version) and latest ALiVE.

    To reproduce, place the following modules on Altis:

    Repro 1:
    Military OPCOM synced to a civ placement module (place units, medium filters, shouldn't matter too much), a logistics module, and an IED module.

    • Alive (required)
    • Alive Data
    • Player Options
    • Virtual AI
    • Alive AI Skill
    • Alive Ambient Weather
    • Civilian Population
    • Civilian Placement

    Then add a player. All of these things set to no debug.

    Repro 2:
    Military OPCOM synced to a civ placement module (place units, medium filters, shouldn't matter too much), a logistics module, and an IED module.

    • Alive (required)
    • Alive Data
    • Player Options
    • Virtual AI

    Then add a player. Only civ military placement set to debug.

    Repro 3:
    Military OPCOM synced to a placement module (place units, medium filters, shouldn't matter too much), a logistics module, and an IED module.

    • Alive (required)
    • Alive Data
    • Player Options
    • Virtual AI

    Then add a player. Only military placement set to debug.

    The key symptoms of shit going wrong are the following:
    Loading screen > Player loads briefly > jumps back to loading screen for a while

    This usually happens with the error, but with only a few modules placed, it seems to happen so quickly you can't see the error. All you see is a brief flicker of the player loaded and then it jumps back to the loading screen. Missions take much longer to load. Take away the civilian population, the mission loads as normal.

    However, as the second repro shows, even with the civ population modules taken out, if you turn on debug in the military civ placement module, you'll get the error back along with the weird loading.

    Another thing I noticed was that the ambient dynamic weather seems to make the mission jump back into the loading screen, which can interfere with player persistence too.

    UPDATE: I can also confirm that player persistence does work when the error isn't present, and fails when the error is present. This is based on a cold start on the server (if the server is up and running and has already had somebody on it, persistence will work fine).

    With EDEN, I think they introduced automatic error reporting so you'll only see the error come up in the editor unless you have show errors enabled in the startup parameters.

  6. Edited 9 years ago by SpyderBlack723

    Will try to get it fixed for the next ALiVE hotfix. CBA introduced quite a few changes that ALiVE will have to adapt to.

    btw, persistence isn't working because CBA changes render the ALiVE menu buttons useless

  7. Would recommend sticking with CBA V2.2 like incontinenetia stated. Took a look at the rpt and it's filled with thousands of references to that error. As mentioned other things such as ALiVE persistence will also be broken.