No persistence for certain elements and errors in logs

  1. 7 years ago

    Hi,
    Had some struggles with persistence, i can get persistence in the same mission, but if the server restarts, nothing and im not sure the entire campaign resets each restart. I'm so close to nirvana here and am pleading for some pointers. I've updated and tested today and here is a log snippet that concerns me. I've put the optional pbo's in, persistence is all on in the mission, =1 in server config, respawn set to -1 in description.ext, alive server is active, I reset the group name in warroom to avoid special characters, i've spent hours but I feel I miss something fundamental in my understanding of persistence, it very much seems that the server side isn't working but the player is and whilst i'm here, why is there a local Couch DB if we export settings to War room? I searched the CouchDB error and only got this and its beyond me, im a SQL man. http://stackoverflow.com/questions/6098933/couchdb-view-url-shows-couchdb-errornot-found-reasonmissing-wh

    I'm doing something stupid aren't I?

    [2016-04-23 18:19:02] [debug] >>> ParseMessage [SendJSON ['GET','sys_spotrep/42VFG_42CampaignNew','']]
    [2016-04-23 18:19:02] [debug] Function: SendJSON
    [2016-04-23 18:19:02] [debug] Params:
    [2016-04-23 18:19:02] [debug] - [GET]
    [2016-04-23 18:19:02] [debug] - [sys_spotrep/42VFG_42CampaignNew]
    [2016-04-23 18:19:02] [debug] - []
    [2016-04-23 18:19:02] [debug] Return value [['{"error":"not_found","reason":"missing"}
    ']]
    [2016-04-23 18:19:02] [debug] |/-\ Elapsed time: 311.018ms

    Also in
    [sys_logistics/42VFG_42CampaignNew]
    and sysmarker, dictionary and spotrep

  2. There's some player items not working also, eg, "Revert to save" is blacked out, despite there being a save and health isn't persisting (in the same server session)

  3. Tupolov

    23 Apr 2016 Administrator

    ignore that missing error, just means you don't have any spotreps stored.

    There is an issue with player restore at mission restart in 1.0.4 we are investigating.

    Please share your RPT and plugin log file

  4. https://drive.google.com/open?id=0BwUQri1lYjQ8VFh6VFdSQlprbmM
    https://drive.google.com/open?id=0BwUQri1lYjQ8WGpURHZfMjF5QmM

    logs linked above. Had some inconsistent behaviour with this, Because im not great at Arma or this mod if you can tell me how to provide better information. Steps to reproduce are easy enough (for me) but Im not sure what the expected behaviour is, also, Im sure in the case above I had logistic and marker information but the DB is finding nothing saved. Also should we have to log in as admin and press save, should this not be automated? Can it be temporarily scripted as a workaround?

 

or Sign Up to reply!