Post a Reply

Dedicated Server Setup Problem [SOLVED]

  1. 8 years ago
    A

    Aarnoman

    5 Jul 2016

    Hi everyone,
    having massive issues getting my dedicated server on my local machine set up with Alive. Using TADST to start the server. Every time I start the server, join as a client from my local machine and start the mission, the server crashes. The error given is the following: http://imgur.com/fABvTcs

    Anybody know what is going on here? I've been trying to run the sample insurgency mission given on the demo section of the Alive site. I can run non-alive missions fine on my dedicated server. Also made sure to unblock the zip file for @aliveserver before extracting, as well as unblocking the alive.cfg file.

  2. H

    HeroesandvillainsOS

    5 Jul 2016 Moderator
    Edited 8 years ago by HeroesandvillainsOS

    Hmmm. I've never had a problem running missions with TADST. That's what I use all the time. I'm assuming unless your PC is ancient, you'd have the C++ redistributable needed for persistence.

    I'm wondering if perhaps it's the mission itself. Have you tried running it in SP just to make sure it still works?

    I'm sure it's irrelevant to the matter at hand, but you don't need @aliveserver unless you've registered on War Room (and remember, @aliveserver goes on the server only). Did you register the server and follow the guide on War Room's site?

    I have a vanilla(ish) mission you could try. I know 100% it works with TADST. It require CBA, ALiVE and Spyder Addons which you can pick up here: https://forums.bistudio.com/topic/186769-spyder-addons/

    And the mission if you want to just see if maybe the one you're using needs an update: https://www.dropbox.com/s/ynql6ruj9vrh1uy/Valor_For_Altis.Altis.pbo?dl=0

    Make sure alive.cfg and TADST.exe are I n your Arma root folder too, along with @ALiVE and @aliveserver. I'm assuming you did that but I figure it's worth pointing out just incase.

  3. A

    Aarnoman

    5 Jul 2016
    Edited 8 years ago by Aarnoman

    Hey Heroes, thanks for your reply. After going on a bit of a hunt with the instructions you've given me, I've found a solution to the problem. Turns out that the issue was due to loading the @alive mod from a location that was not the Arma 3 root directory (I keep most of my mods on a separate HDD to reduce the amount of space taken up on my SSD C: drive). Moving the @alive and @aliveserver to the arma 3 root directory has fully resolved the issue.
    Thanks for helping Heroes :) If anyone runs into a similar problem in the future feel free to drop me a message.

 

or Sign Up to reply!