Jump to content
Bohemia Interactive Forums

MATR1X

Member
 View Profile  See their activity

  • Content Count

    62

  • Joined

  • Last visited

  • Medals

  • Medals

Posts posted by MATR1X

  15. Posted

    Wow! That is an impressive server mod set. There are a lot of errors relating to those mods in your rpt, which is not unusual. But you did write that it would crash with only CBA.

    If you can upload a rpt with only CBA running, as you wrote, then it may assist another member who is knowledgable enough to help identify information that may relate to the crash.

    I will setup and test ArmA 3 on our server with cba only launched sometime in the next few days and see what happens. I don't think I can be of any more help, but maybe someone else around might.

  16. Posted · Edited by MATR1X

    Is there a way to use the config parameter "guaranteedUpdates = false;" when launching with TADST? If so, could you please explain how?

    I don't believe so. that is a setting that has a required value (number).

    https://community.bistudio.com/wiki/ArmA:_Server_configuration

    https://community.bistudio.com/wiki/basic.cfg

    https://community.bistudio.com/wiki/server.cfg

    https://community.bistudio.com/wiki/Arma2:_Startup_Parameters

    @Kuunmies: Could be a number of things. I believe for ArmA 3 you need a Registered version for each instance. A CD key for each. Which may be why you are being kicked.

    The non "Server" folder and .exe can be used for Headless client connection to the ArmA 3 Server instance.

    I have noticed ArmA 3 updates are quite frequent at the moment so making sure the version on the server or other machine is using the same patch (as your game pc) may also help.

    ArmA 3 may have updated on your client and if using the same copy on the other machine (does work with the same key) may need an update. If a server instance is running, it cannot update.

    We are not running multiple ArmA 3 instances, or any at the moment for that matter but we have not had to change anything in the basic or server cfg to see it listed or be able to join for that one.

    What we did need to do on the server was to allow and application (the server .exe for each game) to work through windows firewall. And this may require a restart, depending on OS.

    As for ArmA 2 since 1.63, there have been changes including the server using a steam and steam query port. We had to add extra lines to the standard server cfg for it to be listed in the browser and to be able to join.

    TADST v2.6 does not write the extra ports to the cfg by default. I have tried to explain (as best as possible) the process and steps I took on a previous page in this topic.

  17. Posted

    1.63 Arrowhead 1.63 Steam Patch Help

    Windows 2012 R2 (or other) Firewall

    - Allow an app or feature through Windows Firewall.

    - Add Steam/A2OA and A3 Server (.exe)s to the list.

    - If needed for Private/Public and Domain.

    - In Inbound Rules for each added. Right click, Properties, Advanced, Edge Traversal. Allow Edge Traversal, Apply, Ok.

    TADST v2.6 Settings

    Create a new profile or use an existing one.

    Even if you only have one game server instance, do this to check and confirm it launches, opens the port and you can connect and join to it.

    This example is specifically for multiple 1.63 ArmA 2 Operation Arrowhead Servers, which has worked for us.

    Server #1: TADST Launcher Options.

    Set all options as normal as you have done with other tadst/arma patch versions. Set server name, server file (.exe), admin password, difficulty etc, etc first. Then save.

    Do not check (tick) launch as is yet if you do not have a TADST_config.cfg in the saved profile folder. When you do then you can edit it, as is needed.

    Now, set:

    Port: 2302

    Steam Port: 2304

    Save and launch to create the required TADST_config.cfg, if you don't already have one.

    Now you can go and edit the file manually. I recommend using Notepad ++

    This has already been saved with\for the ports edited above.

    Add these lines underneath - steamPort = 2304;

    So the text in the file will now look like this.

    steamPort = 2304;

    steamqueryport = 2303; <- NEW

    reportingIP = "master.bistudio.com"; <- NEW

    hostName = "My Server";

    password = "";

    passwordAdmin = "MyServerPassword";

    logFile = "logfile_console.log";

    There will be more underneath, but you should get the idea. This contains the extra lines needed. <- NEW - Do not add this!

    Save TADST_config.cfg with the additions you have just made.

    Now go back to your TADST, check (tick) "Launch as is" and save.

    Now launch and connect. If that doesn't work, maybe try leaving Steam open on the server.

    We created a Steam account for our dedicated server and leave it open anyways.

    For multiple servers, say another Arrowhead, And in the TADST/profile for this instance, the next one could be:

    Port: 2312

    Steam Port: 2314

    Then in the TADST_config.cfg for this one.

    steamPort = 2314;

    steamqueryport = 2313; <- NEW

    reportingIP = "master.bistudio.com"; <- NEW

    hostName = "My Server #2";

    password = "";

    passwordAdmin = "MyServerPassword2";

    logFile = "logfile_console.log";

    Save file, then in Launcher, check (tick) launch as is and save again.

    And so on.

    And for connection via battleWarden, inside the Battleye folder for each profile should be a Bans.txt

    and a BEServer.cfg. Just create a text document, rename it to BEServer.cfg. The edit it and add this.

    RConPassword MyServerPassword <- "MyServerPassword" being your password of choice. The same as admin password in TADST Launcher makes it simple!

    MaxPing 300

    ~FIN

  20. Posted

    Hi Tophe glad you have time to come back to give us updates.

    I have been getting an error when trying to (double click) fill in the required version on A2/OA/A3 Steam Installation, Server .exe files.

    Error occurred on 2012 R2 64 and so I tried on my 8.1 64 client with the same result. Both fresh installations of Steam and ArmA.

    A quick google search on the exception location results in posts about issues regarding ArmA2net, which I then removed only to find the same errors.

    Works fine without trying to select and find required version, just thought I would mention it to you.

    Screenshot

    tadst.jpg

    Exception Details

    See the end of this message for details on invoking

    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************

    System.IO.FileNotFoundException: C:\Program Files (x86)\Steam\SteamApps\common\Arma 2\arma3.exe

    at System.Diagnostics.FileVersionInfo.GetVersionInfo(String fileName)

    at TADST.MainForm.txtRequiredBuild_DoubleClick(Object sender, EventArgs e)

    at System.Windows.Forms.Control.OnDoubleClick(EventArgs e)

    at System.Windows.Forms.TextBoxBase.OnMouseUp(MouseEventArgs mevent)

    at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

    at System.Windows.Forms.Control.WndProc(Message& m)

    at System.Windows.Forms.TextBoxBase.WndProc(Message& m)

    at System.Windows.Forms.TextBox.WndProc(Message& m)

    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    ************** Loaded Assemblies **************

    mscorlib

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.34014 built by: FX45W81RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

    ----------------------------------------

    TADST

    Assembly Version: 2.6.0.0

    Win32 Version: 2.6.0.0

    CodeBase: file:///C:/Program%20Files%20(x86)/Steam/SteamApps/common/Arma%202/TADST.exe

    ----------------------------------------

    System.Windows.Forms

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

    ----------------------------------------

    System.Drawing

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

    ----------------------------------------

    System

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.34003 built by: FX45W81RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

    ----------------------------------------

    System.Core

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

    ----------------------------------------

    ************** JIT Debugging **************

    To enable just-in-time (JIT) debugging, the .config file for this

    application or computer (machine.config) must have the

    jitDebugging value set in the system.windows.forms section.

    The application must also be compiled with debugging

    enabled.

    For example:

    <configuration>

    <system.windows.forms jitDebugging="true" />

    </configuration>

    When JIT debugging is enabled, any unhandled exception

    will be sent to the JIT debugger registered on the computer

    rather than be handled by this dialog box.

×