S

Shamorshin

Member

Last active 5 years ago

  1. 6 years ago
    Thu Mar 15 00:45:23 2018
    S Shamorshin started the conversation Units setting waypoints at map origin point.

    Hey guys. Remade a new mission yesterday and today noticed that some of the units are setting waypoints at the map origin point. They are still moving some patrols around but some units seem to be setting waypoints at map origin, and then a secondary waypoint to a patrol location near their actual position. Is this intentional, or a bug? I can add a screenshot for clarity if needed.

    Map is Chernarus, faction is Cup's Chernarus rebels, and AI commander is set to insurgency.

    Thanks!

  2. Wed Mar 14 02:34:11 2018

    Thanks so much. I appreciate it. For the moment, my unit has voted to move to Chernarus instead of Esseker, as I suspect that the map was a big problem.

    The biggest issue we had was that the AI commander kept pinging his units to travel to map origin instead of where they really were intended to go. I hope this was a bug and not something I have wigged out.

    Is it possible to have ALiVE running fine without connecting to the war room? As of now I've set everything to save locally. That should function the same -- just without the stats reported on the website -- right?

    Thank you so very much for getting back with me so quickly.

    ...also are there any issues with Chernarus before I pour another 80 hours into tweaking another map? haha.

  3. Wed Mar 14 01:56:12 2018

    Okay, but is alive.cfg required for the server to work, or to connect to the war room?

    I've connected to the war room, and still don't see how I'm supposed to download this necessary file.

    This is beyond frustrating because I really want this mod to work.

  4. Wed Mar 14 01:55:14 2018
    S Shamorshin posted in No RHS factions working?.

    I've been able to get rhs_faction_msv and rhs_faction_vdv working fine. What issue are you having?

  5. Tue Mar 13 20:55:33 2018

    Update: As it stands right now, we have persistence of AI-controlled units, vehicles, and I'm testing object placement. Objects placed via fortify without activating player logistics actions are not persistent.

    I don't know what was going on before. I've disabled player saving between sessions, so I respawn appropriately after server save and exit, and vehicles stay where they were. testing objects.
    ----------
    Update:

    • server save and exit saves some objects when picked up and dropped via player logistics actions
    • server save and exit saved player position data as appropriate, but did not do this last time. will test again.
    • player backpack with very limited supplies also dropped on the ground where player respawned. ???

    So, object permanence on server-save-and-exit is established as long as player logistics is enabled, and the object is placed, picked up, and dropped by a player. EX: I used my fortify tool to spawn an H-barrier wall segment (guess that's enabled through a mod we're using)....and just placing it does not allow it to persist. BUT -- placing it, then picking it up with the scroll wheel player logistics action, and then dropping it, allows it to persist through server-save-and-exit. Is this working as intended?

    It sucks because that means that player logistics needs to be constantly enabled, which means players can conceivably destroy the carefully made compositions I've placed for them as bases.

    Is there a way to enable and disable player logistics actions mid-mission?

    -------

  6. Tue Mar 13 20:17:38 2018

    Here's my debug.

    [2018-03-13 00:13:08] [info] ALiVEPlugIn v2.1a-
    [2018-03-13 00:13:08] [debug] >>> ParseMessage [StartALiVE ['true']]
    [2018-03-13 00:13:08] [debug] Function: StartALiVE
    [2018-03-13 00:13:08] [debug] Params:
    [2018-03-13 00:13:08] [debug] - [true]
    [2018-03-13 00:13:08] [info] Disable Performance Monitor: true
    [2018-03-13 00:13:08] [info] Reading 'alive.cfg'
    [2018-03-13 00:13:08] [error] ###### HandleMessage - StartALiVE ######
    [2018-03-13 00:13:08] [error] Error: Unable to open alive.cfg
    [2018-03-13 00:13:08] [error] RAW: StartALiVE ['true']
    [2018-03-13 00:13:08] [debug] Return value [['StartALiVE','ERROR','Unable to open alive.cfg']]
    [2018-03-13 00:13:08] [debug] |/-\ Elapsed time: 0ms
    [2018-03-13 00:13:08] [debug] >>> ParseMessage [ServerAddress]
    [2018-03-13 00:13:08] [debug] Function: ServerAddress
    [2018-03-13 00:13:08] [debug] Params:
    [2018-03-13 00:13:08] [warning] ALiVE not initialized yet!
    [2018-03-13 00:13:08] [info] ServerAddress - Querying for IP @ ipify.org
    [2018-03-13 00:13:08] [info] IP returned: 160.202.167.13
    [2018-03-13 00:13:08] [debug] Return value [['160.202.167.13']]
    [2018-03-13 00:13:08] [debug] |/-\ Elapsed time: 37ms
    [2018-03-13 00:13:08] [debug] >>> ParseMessage [GroupName]
    [2018-03-13 00:13:08] [debug] Function: GroupName
    [2018-03-13 00:13:08] [debug] Params:
    [2018-03-13 00:13:08] [warning] ALiVE not initialized yet!
    [2018-03-13 00:13:08] [info] GroupName:
    [2018-03-13 00:13:08] [debug] Return value [['']]
    [2018-03-13 00:13:08] [debug] |/-\ Elapsed time: 1ms
    [2018-03-13 00:13:08] [debug] >>> ParseMessage [SendJSON ['GET','sys_data/config','']]
    [2018-03-13 00:13:08] [debug] Function: SendJSON
    [2018-03-13 00:13:08] [debug] Params:
    [2018-03-13 00:13:08] [debug] - [GET]
    [2018-03-13 00:13:08] [debug] - [sys_data/config]
    [2018-03-13 00:13:08] [debug] - []
    [2018-03-13 00:13:08] [warning] ALiVE not initialized yet!
    [2018-03-13 00:13:08] [error] ###### curlGet ######
    [2018-03-13 00:13:08] [error] Error: curl_easy_perform() failed
    [2018-03-13 00:13:08] [error] RAW: URL using bad/illegal format or missing URL
    [2018-03-13 00:13:08] [error] ###### HandleMessage - SendJSON ######
    [2018-03-13 00:13:08] [error] Error: curlGet() failed
    [2018-03-13 00:13:08] [error] RAW: ['curlGet','ERROR','curl_easy_perform() failed']
    [2018-03-13 00:13:08] [debug] Return value [['SendJSON','ERROR','['curlGet','ERROR','curl_easy_perform() failed']']]
    [2018-03-13 00:13:08] [debug] |/-\ Elapsed time: 1ms
    [2018-03-13 00:13:51] [debug] >>> ParseMessage [ServerName]
    [2018-03-13 00:13:51] [debug] Function: ServerName
    [2018-03-13 00:13:51] [debug] Params:
    [2018-03-13 00:13:51] [warning] ALiVE not initialized yet!
    [2018-03-13 00:13:51] [info] Config file: D:\TCAFiles\Users\DanielG2\23796\config.cfg
    [2018-03-13 00:13:51] [info] ServerName:
    [2018-03-13 00:13:51] [debug] Return value [['']]
    [2018-03-13 00:13:51] [debug] |/-\ Elapsed time: 1ms
    [2018-03-13 01:21:17] [debug] >>> ParseMessage [StartALiVE ['true']]
    [2018-03-13 01:21:17] [debug] Function: StartALiVE
    [2018-03-13 01:21:17] [debug] Params:
    [2018-03-13 01:21:17] [debug] - [true]
    [2018-03-13 01:21:17] [info] Disable Performance Monitor: true
    [2018-03-13 01:21:17] [info] Reading 'alive.cfg'
    [2018-03-13 01:21:17] [error] ###### HandleMessage - StartALiVE ######
    [2018-03-13 01:21:17] [error] Error: Unable to open alive.cfg
    [2018-03-13 01:21:17] [error] RAW: StartALiVE ['true']
    [2018-03-13 01:21:17] [debug] Return value [['StartALiVE','ERROR','Unable to open alive.cfg']]
    [2018-03-13 01:21:17] [debug] |/-\ Elapsed time: 1ms
    [2018-03-13 01:21:17] [debug] >>> ParseMessage [ServerAddress]
    [2018-03-13 01:21:17] [debug] Function: ServerAddress
    [2018-03-13 01:21:17] [debug] Params:
    [2018-03-13 01:21:17] [warning] ALiVE not initialized yet!
    [2018-03-13 01:21:17] [info] ServerAddress - Querying for IP @ ipify.org
    [2018-03-13 01:21:17] [info] IP returned: 160.202.167.13
    [2018-03-13 01:21:17] [debug] Return value [['160.202.167.13']]
    [2018-03-13 01:21:17] [debug] |/-\ Elapsed time: 59ms
    [2018-03-13 01:21:17] [debug] >>> ParseMessage [GroupName]
    [2018-03-13 01:21:17] [debug] Function: GroupName
    [2018-03-13 01:21:17] [debug] Params:
    [2018-03-13 01:21:17] [warning] ALiVE not initialized yet!
    [2018-03-13 01:21:17] [info] GroupName:
    [2018-03-13 01:21:17] [debug] Return value [['']]
    [2018-03-13 01:21:17] [debug] |/-\ Elapsed time: 0ms
    [2018-03-13 01:21:17] [debug] >>> ParseMessage [SendJSON ['GET','sys_data/config','']]
    [2018-03-13 01:21:17] [debug] Function: SendJSON
    [2018-03-13 01:21:17] [debug] Params:
    [2018-03-13 01:21:17] [debug] - [GET]
    [2018-03-13 01:21:17] [debug] - [sys_data/config]
    [2018-03-13 01:21:17] [debug] - []
    [2018-03-13 01:21:17] [warning] ALiVE not initialized yet!
    [2018-03-13 01:21:17] [error] ###### curlGet ######
    [2018-03-13 01:21:17] [error] Error: curl_easy_perform() failed
    [2018-03-13 01:21:17] [error] RAW: URL using bad/illegal format or missing URL
    [2018-03-13 01:21:17] [error] ###### HandleMessage - SendJSON ######
    [2018-03-13 01:21:17] [error] Error: curlGet() failed
    [2018-03-13 01:21:17] [error] RAW: ['curlGet','ERROR','curl_easy_perform() failed']
    [2018-03-13 01:21:17] [debug] Return value [['SendJSON','ERROR','['curlGet','ERROR','curl_easy_perform() failed']']]
    [2018-03-13 01:21:17] [debug] |/-\ Elapsed time: 0ms
    [2018-03-13 01:21:59] [debug] >>> ParseMessage [ServerName]
    [2018-03-13 01:21:59] [debug] Function: ServerName
    [2018-03-13 01:21:59] [debug] Params:
    [2018-03-13 01:21:59] [warning] ALiVE not initialized yet!
    [2018-03-13 01:21:59] [info] Config file: D:\TCAFiles\Users\DanielG2\23796\config.cfg
    [2018-03-13 01:21:59] [info] ServerName:
    [2018-03-13 01:21:59] [debug] Return value [['']]
    [2018-03-13 01:21:59] [debug] |/-\ Elapsed time: 0ms

  7. Tue Mar 13 20:01:03 2018

    Hey there.

    Reporting back! So I figured out that the units which were primarily showing up were units I had deleted to assist in cleanup. Should have let the garbage collector handle that, and when I didn't manually delete AI controlled units, they don't virtualize at the map origin -- so that's good.

    Question 1: If I manually delete AI-controlled units, are they supposed to appropriate re-virtualize, or does this bug the AI commander?

    So I thought that fixed my problem, and then I added an Air commander module set up to RHS_faction_vdv. Note that my primary units are set to rhs_faction_msv. What I found then is that a Mi-24 spawns at the map origin point and doesn't seem to do anything. I haven't gotten far enough into fighting the AI commander yet to see if he moves it, but I'm guessing he won't. When I placed a friendly Air commander, the same thing occurred and he was tasking player air to attack the enemy units at map origin, so the friendly AI helicopter (rhs_faction_usarmy_wd) was spawning down there as well.

    Is this likely caused by a map conflict, or a configuration conflict? All other units seem to be spawning, tasking, and re-inserting appropriately.

    As an aside, where the hell do I find alive.cfg to place in my arma 3 directory? I'm not finding it and realizing now that ALiVE isn't appropriately loading (per the logs) as it can't find that file. I have no idea where to find it.

    Here's my most recent log:

    [2018-03-13 00:13:08] [info] ALiVEPlugIn v2.1a-
    [2018-03-13 00:13:08] [debug] >>> ParseMessage [StartALiVE ['true']]
    [2018-03-13 00:13:08] [debug] Function: StartALiVE
    [2018-03-13 00:13:08] [debug] Params:
    [2018-03-13 00:13:08] [debug] - [true]
    [2018-03-13 00:13:08] [info] Disable Performance Monitor: true
    [2018-03-13 00:13:08] [info] Reading 'alive.cfg'
    [2018-03-13 00:13:08] [error] ###### HandleMessage - StartALiVE ######
    [2018-03-13 00:13:08] [error] Error: Unable to open alive.cfg
    [2018-03-13 00:13:08] [error] RAW: StartALiVE ['true']
    [2018-03-13 00:13:08] [debug] Return value [['StartALiVE','ERROR','Unable to open alive.cfg']]
    [2018-03-13 00:13:08] [debug] |/-\ Elapsed time: 0ms
    [2018-03-13 00:13:08] [debug] >>> ParseMessage [ServerAddress]
    [2018-03-13 00:13:08] [debug] Function: ServerAddress
    [2018-03-13 00:13:08] [debug] Params:
    [2018-03-13 00:13:08] [warning] ALiVE not initialized yet!
    [2018-03-13 00:13:08] [info] ServerAddress - Querying for IP @ ipify.org
    [2018-03-13 00:13:08] [info] IP returned: 160.202.167.13
    [2018-03-13 00:13:08] [debug] Return value [['160.202.167.13']]
    [2018-03-13 00:13:08] [debug] |/-\ Elapsed time: 37ms
    [2018-03-13 00:13:08] [debug] >>> ParseMessage [GroupName]
    [2018-03-13 00:13:08] [debug] Function: GroupName
    [2018-03-13 00:13:08] [debug] Params:
    [2018-03-13 00:13:08] [warning] ALiVE not initialized yet!
    [2018-03-13 00:13:08] [info] GroupName:
    [2018-03-13 00:13:08] [debug] Return value [['']]
    [2018-03-13 00:13:08] [debug] |/-\ Elapsed time: 1ms
    [2018-03-13 00:13:08] [debug] >>> ParseMessage [SendJSON ['GET','sys_data/config','']]
    [2018-03-13 00:13:08] [debug] Function: SendJSON
    [2018-03-13 00:13:08] [debug] Params:
    [2018-03-13 00:13:08] [debug] - [GET]
    [2018-03-13 00:13:08] [debug] - [sys_data/config]
    [2018-03-13 00:13:08] [debug] - []
    [2018-03-13 00:13:08] [warning] ALiVE not initialized yet!
    [2018-03-13 00:13:08] [error] ###### curlGet ######
    [2018-03-13 00:13:08] [error] Error: curl_easy_perform() failed
    [2018-03-13 00:13:08] [error] RAW: URL using bad/illegal format or missing URL
    [2018-03-13 00:13:08] [error] ###### HandleMessage - SendJSON ######
    [2018-03-13 00:13:08] [error] Error: curlGet() failed
    [2018-03-13 00:13:08] [error] RAW: ['curlGet','ERROR','curl_easy_perform() failed']
    [2018-03-13 00:13:08] [debug] Return value [['SendJSON','ERROR','['curlGet','ERROR','curl_easy_perform() failed']']]
    [2018-03-13 00:13:08] [debug] |/-\ Elapsed time: 1ms
    [2018-03-13 00:13:51] [debug] >>> ParseMessage [ServerName]
    [2018-03-13 00:13:51] [debug] Function: ServerName
    [2018-03-13 00:13:51] [debug] Params:
    [2018-03-13 00:13:51] [warning] ALiVE not initialized yet!
    [2018-03-13 00:13:51] [info] Config file: D:\TCAFiles\Users\DanielG2\23796\config.cfg
    [2018-03-13 00:13:51] [info] ServerName:
    [2018-03-13 00:13:51] [debug] Return value [['']]
    [2018-03-13 00:13:51] [debug] |/-\ Elapsed time: 1ms
    [2018-03-13 01:21:17] [debug] >>> ParseMessage [StartALiVE ['true']]
    [2018-03-13 01:21:17] [debug] Function: StartALiVE
    [2018-03-13 01:21:17] [debug] Params:
    [2018-03-13 01:21:17] [debug] - [true]
    [2018-03-13 01:21:17] [info] Disable Performance Monitor: true
    [2018-03-13 01:21:17] [info] Reading 'alive.cfg'
    [2018-03-13 01:21:17] [error] ###### HandleMessage - StartALiVE ######
    [2018-03-13 01:21:17] [error] Error: Unable to open alive.cfg
    [2018-03-13 01:21:17] [error] RAW: StartALiVE ['true']
    [2018-03-13 01:21:17] [debug] Return value [['StartALiVE','ERROR','Unable to open alive.cfg']]
    [2018-03-13 01:21:17] [debug] |/-\ Elapsed time: 1ms
    [2018-03-13 01:21:17] [debug] >>> ParseMessage [ServerAddress]
    [2018-03-13 01:21:17] [debug] Function: ServerAddress
    [2018-03-13 01:21:17] [debug] Params:
    [2018-03-13 01:21:17] [warning] ALiVE not initialized yet!
    [2018-03-13 01:21:17] [info] ServerAddress - Querying for IP @ ipify.org
    [2018-03-13 01:21:17] [info] IP returned: 160.202.167.13
    [2018-03-13 01:21:17] [debug] Return value [['160.202.167.13']]
    [2018-03-13 01:21:17] [debug] |/-\ Elapsed time: 59ms
    [2018-03-13 01:21:17] [debug] >>> ParseMessage [GroupName]
    [2018-03-13 01:21:17] [debug] Function: GroupName
    [2018-03-13 01:21:17] [debug] Params:
    [2018-03-13 01:21:17] [warning] ALiVE not initialized yet!
    [2018-03-13 01:21:17] [info] GroupName:
    [2018-03-13 01:21:17] [debug] Return value [['']]
    [2018-03-13 01:21:17] [debug] |/-\ Elapsed time: 0ms
    [2018-03-13 01:21:17] [debug] >>> ParseMessage [SendJSON ['GET','sys_data/config','']]
    [2018-03-13 01:21:17] [debug] Function: SendJSON
    [2018-03-13 01:21:17] [debug] Params:
    [2018-03-13 01:21:17] [debug] - [GET]
    [2018-03-13 01:21:17] [debug] - [sys_data/config]
    [2018-03-13 01:21:17] [debug] - []
    [2018-03-13 01:21:17] [warning] ALiVE not initialized yet!
    [2018-03-13 01:21:17] [error] ###### curlGet ######
    [2018-03-13 01:21:17] [error] Error: curl_easy_perform() failed
    [2018-03-13 01:21:17] [error] RAW: URL using bad/illegal format or missing URL
    [2018-03-13 01:21:17] [error] ###### HandleMessage - SendJSON ######
    [2018-03-13 01:21:17] [error] Error: curlGet() failed
    [2018-03-13 01:21:17] [error] RAW: ['curlGet','ERROR','curl_easy_perform() failed']
    [2018-03-13 01:21:17] [debug] Return value [['SendJSON','ERROR','['curlGet','ERROR','curl_easy_perform() failed']']]
    [2018-03-13 01:21:17] [debug] |/-\ Elapsed time: 0ms
    [2018-03-13 01:21:59] [debug] >>> ParseMessage [ServerName]
    [2018-03-13 01:21:59] [debug] Function: ServerName
    [2018-03-13 01:21:59] [debug] Params:
    [2018-03-13 01:21:59] [warning] ALiVE not initialized yet!
    [2018-03-13 01:21:59] [info] Config file: D:\TCAFiles\Users\DanielG2\23796\config.cfg
    [2018-03-13 01:21:59] [info] ServerName:
    [2018-03-13 01:21:59] [debug] Return value [['']]
    [2018-03-13 01:21:59] [debug] |/-\ Elapsed time: 0ms

    As it stands right now, we have persistence of AI-controlled units, vehicles, and I'm testing object placement. Objects placed via fortify without activating player logistics actions are not persistent, which I'm sure is working as intended.

  8. Tue Mar 13 19:42:41 2018
    S Shamorshin started the conversation Where is alive.cfg? Mission working, but no persistence..

    So I've downloaded ALiVE, added it and the ALiVE Server folders to my server's mod list, ensured that they're loading in, and I'm getting the error that the server is unable to open alive.cfg.

    For the life of me, I can't find alive.cfg anywhere. Where do I get this file? Do I need to just create an empty alive.cfg in my server's root directory?

    If not (and I assume not), where can I find this file? Googling the issue isn't helping find out where it is, and I don't see alive.cfg anywhere in the downloaded mods.

    I've been running ALiVE well with everything going fine on the mission side, except persistence is totally non-functional, despite all modules with the option to enable persistence enabled, and database saved to local. Where am I going wrong? I hope it's just that I'm missing this.

    Also, is there a way to clear out old database saves? I've changed the server name with every updated version (adding in what the players have done throughout a mission via EDEN after the mission is complete and then re-uploading the mission file as a newly named .pbo to avoid conflicts). For a few updates, we had persistence working at least for vehicles, but now there is none whatsoever following an admin-logged server save and exit.

  9. Mon Mar 12 17:40:47 2018

    Hey Angus. Yeah it did seem that the commander was having problems assigning units tasks, as the ones that would spawn just stuck to their initial patrol routes but nobody did anything else.

    Esseker is still listed on the compatible maps list. I'm going to test in a little bit with just CBA and ALiVE and see if the map still bugs.

  10. Mon Mar 12 05:21:39 2018
    S Shamorshin started the conversation Esseker - All reinforcements spawning at Map Origin.

    Hey all.

    So I've been on vacation for the past week and have wisely decided to spend 8 hours a day tweaking my unit's ALiVE map.

    Finally this morning I've got it to a great, balanced, playable state. We tested it tonight and everyone enjoyed the 8-man OP, but we had one big problem -- the reinforcements seemed thin.

    Turns out what the players thought were reinforcements were just the motorized patrols I'd set to spawn. The actual reinforcements never came because Every reinforcement that was supposed to spawn in spawned at map origin in the bottom right and just sat there.

    Is this an issue with Esseker? It seems from looking things over in the last hour or so that the map is abandoned by the dev and that it may have never been indexed properly.

    I have a strange feeling that there's no way to fix the problem easily. I know that the modules are all configured appropriately. Everything is working great, but at the bottom left corner of the map I've got an area that, when activated by player presence, spawns in every unit that the OPCOM has tried to call in for reinforcement. They don't move, they just sit there as the vehicles pile up and explode. Trucks, cars, helicopters, and armor.

    Using RHS Faction MSV as primary and a handful of mods. Can provide further info if needed, but it seems like the map may be the primary culprit.

    What should I do now?

View more