Jump to content
  • Hawaii Time Pacific Time Mountain Time Central Time* Eastern Time Western European Eastern European Eastern Daylight
    (GMT -10) (GMT -8) (GMT -7) (GMT -6) (GMT -5) (GMT 0) (GMT +1) (GMT +10)


    *Official unit time is Central Time. All times posted are in the Unit time unless otherwise indicated.

Task Force Bravo Server durring ITX crash


Recommended Posts

While running this evenings ITX all started fine and after about an hour I got a full CTD. After the CTD every time I would load back into the server and get teleported back to my last crash loc. I could ace interact and set up radios, look around...no problem, as soon as I went to move CTD again. This was consistant for me the rest of the night. Tried restarting my box to see if an issue, no avail. I know a few others were having the same issue.disco.png

  • 15th 1
Link to comment
Share on other sites

Looks like you might be bottlenecking on memory allocated to Arma. I had this happen to me a few years back after a fresh install of Arma. If you haven't messed with any of your settings in the launcher parameters, you're probably still playing Arma on the base 2gb of memory and Arma is a CPU intensive game. I'm not sure how much you have or are willing to allocate but I recommend at least 8gb if you can.


To do this,

- Open your ARMA 3 Launcher,

- Go to 'Parameters',

- Press the tab for 'All Parameters',

- Scroll down to 'Advanced' and check the 'System Memory Limit (64-bit)' box.

After that, you can specify what you want to allocate.


Just be sure to leave enough for the rest of your computer.

Link to comment
Share on other sites

Okay I will definitely go ahead and adjust that, I just reinstalled about three months ago. I just installed 64gb of some fresh ram too. First time I’ve experienced it so I was unsure if something to do with the persistence. :) 

Link to comment
Share on other sites

Something I personally experienced recently is I had the 3.6.0 beta version of TS3 installed and a recent change on there is causing a crash between the ACRE Arma 3 mod and the ACRE TS mod that was giving that exact error on Arma. You can verify your version of TS3 via Help > About TeamSpeak and it should say "3.5.6".

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.