Stable Branch 1.54: My operation using just CBA, @alive and @aliveserver can't connect to WarRoom

  1. 8 years ago

    Hi folks,

    although an avid BIS games player since OFP, I started serious mission editing just this year. Serious as in "I'm getting stuff done with LOTS of help from friendly forum members so the editor based missions finally offer more than just S&D."

    I made two MP Missions using standard Editor tricks and when a gaming buddy of mine pointed me to ALiVE, I was instantly hooked! Those cool Modules are actually shortcuts to achieve immersive, large-scale missions in just a fraction of the time I would need via conventional mission editing.

    The ONLY feature of ALiVE I can't get to work at all is Persistence via WarRoom. I'm sooo happy with my own ALiVE mission; everything works as "advertised", but sadly, Persistence does not. All other features work well in Editor previews and, after finishing and packing the mission to PBO, also when playing alone on my Dedi server opened on the same PC.

    I tried hosting this custom ALiVE Mission with a Dedi Server set up on my own PC using TADST. And despite the looong list of mods, my buddy reforger could join, then we received an autogenerated "Defend against Attack" task. Unfortunately it didn't complete because no enemies showed up, but we simply followed some BLUFOR to support them with our ability to call in CAS and Artillery. and happily played for many hours.

    Anticipating that with Batallion sized OPFOR and BLUFOR troops we wouldn't beat the mission in a single session and would need to try the Persistance Feature, I had enabled all related options in the modules during mission editing and later had created a WarRoom account, then a group and finally had invited reforger to join. Then I registered my Dedi server as instructed.

    But our Operation didn't show up in WarRoom, and we had to give up all our achievements unsaved. I then tried all the tips and hints from various forum threads both BIS and here. First thing I realized was that the remote IP I had copied out of the TADST interface that we had typed in to join my Dedi was an internal IP; it's the very same one I had set up months ago for an FTP server I use to share custom addon collections with my buddies. It's IP is static and set to port forwarding for A3 ports some other ports necessary for the FTP software.

    After reading about internal IPs being unfit for WarRoom here, I checked and found I had named this internal IP as Server IP in WarRoom server setup. Since my buddy could remote join, I thought everything was fine. But hey, I checked my external IP and changed the server's IP in WarRoom setup accordingly - to no avail!

    Then I did it step-by-step and by-the-book:

    • re-downloaded all files from alivemod.com
    • set up e new server with just @CBA,@alive and @aliveserver
    • hosting one of the Demo Missions you have kindly provided
    • joined typing the external IP in the remote join field of my client A3 instance and made myself Admin
    • fired a few rounds to give the Hunter a flat tire
    • hit ESC, then pressed save&exit Admin

    I saw the ALivE Tablet, it stated the saving had started - but it never finished!

    The server .rpt says amongst other error reports that my version of ALiVE is for 1.52 and my game is 1.54 - true enough, but there is no newer version of ALiVE than 0.9.10.1510131 available!

    Here comes this .rpt:

    http://www.filedropper.com/arma3server2015-12-0523-54-02

    or, if not readable in this forum:

    <a href=http://www.filedropper.com/arma3server2015-12-0523-54-02><img src=http://www.filedropper.com/download_button.png width=127 height=145 border=0/></a><br /><div style=font-size:9px;font-family:Arial, Helvetica, sans-serif;width:127px;font-color:#44a854;> <a href=http://www.filedropper.com >file storage online</a></div>

    I hope there is some super-stupid little thing I missed that can quickly be corrected - please help me get the most out of this fantastic masterpiece of modding! If you need more info, just spell it out nice and slow what files or info I need to provide, then I'll post them here.

    tourist

  2. Thanks for the RPT.. some errors in there for sure. The warning you saw is just an FYI.. you are using the latest ALiVE version.

    Will get a DEV to take a look.

  3. I'm back after some more testing with mixed results:

    The bad news are that I'm still unsure if persistence works completely and that I still can't successfully server save+exit with one of the ALiVE demo missions "as they are delivered" because when opened in editor some have ourdated modules or additional scripts or modules not set to persistence.

    The good news are that I can definitely connect to WarRoom with my account when hosting my own heavily modded ALiVE missions. Using some supported mods like RHS along some not fully supported mods like ACE and the BWMOD, I get mission recording nontheless. Also my kills are recorded, vehicle guns OR rifles. When starting the mission, I get the popup notice that connection to my ALiVE Player Profile is established. And finally, after voting myself to admin, I get the "server save+exit" button and when I press it, the ALiVE saving process starts and completes, giving the "mission progress saved" screen as end result. The logs from the @ALiVEServer folder show that the profiles are read and data is recognized, e.g. it shows the correct external IP like I have set it up in my ALiVE WarRoom account.

    But apparently ALiVE can not access the dedicated server's config file. I'm using TADST to set the server up, and let it generate a new and, according to it's displayed properties, readable/writable config for my ALiVE mission. ALivE obviously finds the config because the log shows the correct path to:
    C:/programme(x86)/steam/steamapps/common/Arma3/TADST/ALIVE_FALLUJAH_BW_PESH_VS_IS

    Here is the server config saved. Could some failure (no idea where from, though) to read this file after server restart be the cause for a failing "savegame restoration" despite a successful saving process?

    My ALiVe config is ONLY in A3 main directory - I have no duplicate in App/local!

    Maybe I have overlooked other errors in the ALiVE log, so please let more skilled folks than me have a look at my logs to find that last tiny error that stands between me and "Total Mission Persistence"!

    I have yet to build a mission with stock BIS units only; in the meantime please check my complete logs, packed into a ZIP togehter with BattlEye and TADST server data, from the mod-heavy mission for first hints:

    http://www.filedropper.com/killingthehydracosize

    or

    <a href=http://www.filedropper.com/killingthehydracosize><img src=http://www.filedropper.com/download_button.png width=127 height=145 border=0/></a><br /><div style=font-size:9px;font-family:Arial, Helvetica, sans-serif;width:127px;font-color:#44a854;> <a href=http://www.filedropper.com >file upload</a></div>

    Hope you find some useful information to help me find the last obstacle ;-)

  4. It sounds like everything is persisting based on what you're describing. What exactly is resetting upon server restart?

  5. I don't keep my task state, i.e. I don't see my already completed tasks. Also I always start at the FOB where the mission begins - but that is NOT the respawn point; this location is at another place and in case I die, I correctly respawn there during mission.

    That means that my location at the time of my pressing server save+exit is not saved, also my equipment state isn't saved.

    To me it looks as if ALiVE saves overall casualties of both sides, but not location and ammo/health state and also gives me new tasks every time I log in after shutting down the dedi and at next day or few hours later firing it up again.

    Modules are set up correctly; i must've checked that 1000 times, LOL!

  6. Ok. I gotcha now. Yeah, that must be frustrating. You're not the first person to talk about this here. Hopefully a Dev can look at your logs and determine whether the issue is on you, or on ALiVE itself.

    While we're on the subject, does anyone know even if Persistence is working correctly, if the C21STAR tasks are designed to save their state in Admin Server Save & Exit? I don't use them myself but I'm just curious for future reference.

  7. Yes C2ISTAR tasks should be persistent.

    Things are a bit slow over the next few weeks (XMAS) so you might not see much action until the new year. Thanks for the logs they will get looked at.

  8. @SavageCDN Yes C2ISTAR tasks should be persistent.

    Things are a bit slow over the next few weeks (XMAS) so you might not see much action until the new year. Thanks for the logs they will get looked at.

    Hopefully 1.0 can come as an XMAS gift :)

  9. Happy New Year Everybody!

    During the Christmas Holidays I had enough time to build a Test Mission for my persistence issues that uses ONLY BIS Vanilla content.

    The results are exactly the same as with my modded missions before. I'll provide a 7zip file again with logs and mission PBO to help tackling the problem - I hope it helps finding the reasons why I can't enjoy this key feature of an otherwise fine working mod and I hope the best for the upcoming ALiVE 1.0 version.

    Keep up your great work, ALiVE Devs!

    http://www.filedropper.com/alivetestmissionbytourist

    OR

    <a href=http://www.filedropper.com/alivetestmissionbytourist><img src=http://www.filedropper.com/download_button.png width=127 height=145 border=0/></a><br /><div style=font-size:9px;font-family:Arial, Helvetica, sans-serif;width:127px;font-color:#44a854;> <a href=http://www.filedropper.com >upload files free</a></div>

 

or Sign Up to reply!