Jump to content

125548 on DayZ Commander


TheHound

Recommended Posts

 

Step 3a. Download and install DayZLauncher from DayZLauncher.com

Then Open And Search The SERVER NAME

 

This would be viable if it properly joined every server. I tried using DZL but after going through the PIA of renaming a bunch of mod folders so it would recognize them it only connected properly to two of five servers I tried to get into. The really messed up part is that after I get disconnected from the three in question I can find and join them no problem from the server browser, in the game instance the DZL opened for me. I can join through commander, (even though that launcher is f'd and shows no version numbers or ping), I can join through the game launching it from Steam but DZL just waits for host until I get disconnected.

Link to comment
Share on other sites

Ok totally frustrated now. This is what I have tried, not in any particular order.

 

1) I have re-installed Arma 2, Arma 2 OA, DZC. - not working.

2) Double checked and triple checked that my server is running 1.0.5.1/122548 - not working

3) Did the whole check integrity through Steam - not working

4) Made sure the proper mods are running and also added -mod=@DayZ_Epoch - not working

 

a. Server is greyed out on DZC and the name doesn't match what I have entered in my config.cfg

b. Server isn't even appearing in the multiplayer list of Arma 2 anymore...

 

When I launch through DZC or DZL it hangs on the "wait for host", I cant log in through Arma 2 multiplayer.

 

Still waiting for a reply from Vilayer.... Can anyone help, none of my players can log in.... No errors in my RPT

Link to comment
Share on other sites

a. Server is greyed out on DZC and the name doesn't match what I have entered in my config.cfg

 

I think you might be looking at your own DZC cache file. Remove the settings file in C:\Users\{USERNAME}\AppData\Local\DayzCommander\ (Note: This will also remove all your history, favourites and added friends).

 

Also - if you did not already do this - use the steam port (default 2301) instead of the game port when adding your server.

 

--

 

Can't help you with the other issues you are having. Hope you did not follow the advise dansoe gave in this thread because that is crap. The waiting for host might indicate a possible port issue, your host should be able to determine that.

Link to comment
Share on other sites

I think you might be looking at your own DZC cache file. Remove the settings file in C:\Users\{USERNAME}\AppData\Local\DayzCommander\ (Note: This will also remove all your history, favourites and added friends).

 

--

 

Also - if you did not already do this - use the steam port (default 2301) instead of the query port when adding your server.

 

Under Local I only have Teamspeak listed....

 

"Also - if you did not already do this - use the steam port (default 2301) instead of the query port when adding your server." - Where do I change this?

Link to comment
Share on other sites

Edited my post a little. When adding the server to the favorites in DZC use SERVERIP:STEAMQUERYPORT instead of SERVERIP:GAMEPORT.
 

Hmm the entry should be there. Are you sure you are looking in the right place? Might be another drive for you if you installed DZC on that.

Link to comment
Share on other sites

Edited my post a little. When adding the server to the favorites in DZC use SERVERIP:STEAMQUERYPORT instead of SERVERIP:GAMEPORT.

 

Hmm the entry should be there. Are you sure you are looking in the right place? Might be another drive for you if you installed DZC on that.

 

Definitely not there. :(

Link to comment
Share on other sites

If you have updated your servers correctly, the most recent version of DayZCommander (0.9.1.95) works just fine and as it did before the whole gamespy steam shenanigans.

 

If you are getting garbage in DayZCommander delete you settings/cache file located %appdata%\Local\DayZCommander then relaunch and refresh your server list.

 

LIke many, I was led to believe that dayzlauncher was the only launcher that would work post gamespy shutdown. It isn't and DZC still works like it did before.

Link to comment
Share on other sites

If you have updated your servers correctly, the most recent version of DayZCommander (0.9.1.95) works just fine and as it did before the whole gamespy steam shenanigans.

 

If you are getting garbage in DayZCommander delete you settings/cache file located %appdata%\Local\DayZCommander then relaunch and refresh your server list.

 

LIke many, I was led to believe that dayzlauncher was the only launcher that would work post gamespy shutdown. It isn't and DZC still works like it did before.

 

I dont have DayZ Commander listed there, only Teamspeak, I can take a screenshot. I have two drives and only one of them has appdata\local

Link to comment
Share on other sites

The appdata map is actually hidden by default. You sometimes need to actually type it.

Other thing you can do is CTRL+R -> Type in %appdata% and press enter. This will get you to your Appdata/Roaming directory, go back one dir and select Local.

Link to comment
Share on other sites

The appdata map is actually hidden by default. You sometimes need to actually type it.

Other thing you can do is CTRL+R -> Type in %appdata% and press enter. This will get you to your Appdata/Roaming directory, go back one dir and select Local.

Ok great, that worked. Found it and removed it. Now I entered my server IP in the favs and used the 2301 port like states above. Server name isn't displayed just the number and it's greyed out. Ping is red /1000.

Link to comment
Share on other sites

Wow, there is some seriously flawed information on how to update your Arma2OA in this thread, uncluding wiping and reinstalling WTF??

 

 

Here's what I told my players to do, and NONE of them have had any issues:

 

 

1. How-to update your Steam beta version to stable:
 

  •  Go to your Steam Library
  •  Right click on Arma2 Operation Arrowhead
  •  Goto Properties
  •  Goto tab BETAS
  •  In the drop down box select NONE- 
  •  Let Steam update.  - If Steam does not download anything, see section 2.
  •  Close the Properties window.
  •  Your Arma2OA is up to date and running on Steam version
  •  If you game successfully updated Go to section 3.

 

2. If the game does NOT update:

(You can tell by looking in the downloads section in Steam to see if it has downloaded anything for Arma2OA)

Steam will not update if you have replaced the Arma2OA.exe in the A2OA root folder with the beta version (manually or via DZC), as it does not know the file has changed because it wasn't done by Steam
 

  • In the BETAS tab, select the 1.62 beta version of the game.
  • Stay in the BETAS tab.
  • Let Steam Update.
  • Select NONE again.
  • Let Steam Update.
  • Close the Properties window.
  • Your Arma2OA is up to date and running on Steam version.

 

***** Verifying your game cache of Arma2OA via Steam is not required but optional if you choose to do so. *****

 

 

3. DayzCommander setup:

  • In Dayz Commander click on Settings
  • UNCHECK the "Replace original Arma2OA files with Beta so Steam works" option.
  • Click Done.

If you do not uncheck this option DZC will replace the Steam version executable with your previously installed beta-version, giving you "Bad version" errors when you try to connect.

 

If you recieve the above error on connecting you will have to back up to Section 2 and do that part of the guide again and double check your DayzCommander setup before launching the game!!

 

 

 

 

 

All of my players have followed this guide, as well as my guide for them to give me thier SteamID's so I can update my databases with thier new information.

None have reported issues after we updated all servers to the Steam version.

 

 

OT: Our transition to the Steam version has went a lot smoother than I was expecting, primarily because I informed all my players PRIOR to updating via scheduled BEC messages and threads on our forums about the issue.  I also had these guides up in plenty of time before the update.

 

 

Hope this helps anyone lost on how to update :)

 

 

 

 

Link to comment
Share on other sites

Okay, that confirms what we already thought and that is that your server is indeed not reachable. (btw your steamqueryport could be setup different, check your config.cfg to be sure) I'm not with Vilayer so i'm not sure what options you get with them in terms of changing ports and such. But that is where i would start.

Link to comment
Share on other sites

config.cfg should look like this:  - and you should have the UDP ports open in your firewall from 2300 - 2310.  Also the host name has been significantly shortened now. 

hostName = "server - chernarus";
password = "";
passwordAdmin = "changeme";
maxPlayers = 64;
steamport = 2300;
steamqueryport = 2301;
logFile = "server_log.txt";
voteThreshold = 2;
voteMissionPlayers = 3;
reportingIP = "arma2oapc.master.gamespy.com";
timeStampFormat = "short";
motd[] = {"Welcome to Chernarus",
"Team up and talk with other players",
"Please respect other players and have fun!"};
motdInterval = 0;
vonCodecQuality = 11;
disableVoN = 0;
kickduplicate = 1;
verifySignatures = 2;
persistent = 1;
BattlEye = 1;
doubleIdDetected = "";
onUserConnected = "";
onUserDisconnected = "";
onUnsignedData = "kick (_this select 0)";
onHackedData = 	"kick (_this select 0)";
onDifferentData = "";
regularCheck = "";
requiredBuild = 125548;
requiredSecureId = 2;
class Missions
{
    class Mission1
    {
    	template = "DayZ_Epoch_11.Chernarus";
    	difficulty="veteran";
    };

};

Link to comment
Share on other sites

@echo off
start "arma2" /min "arma2oaserver.exe" -port=2230 "-config=instance_11_Chernarus\config.cfg" "-cfg=instance_11_Chernarus\basic.cfg" "-profiles=instance_11_Chernarus" -name=instance_11_Chernarus "-mod=@DayZ_Epoch;@DayZ_Epoch_Server;"

Also make sure that you update your launch bat file.  Notice "arma2oaserver.exe" is no longer "expansions\beta\arma2oaserver.exe"

Link to comment
Share on other sites

@echo off
start "arma2" /min "arma2oaserver.exe" -port=2230 "-config=instance_11_Chernarus\config.cfg" "-cfg=instance_11_Chernarus\basic.cfg" "-profiles=instance_11_Chernarus" -name=instance_11_Chernarus "-mod=@DayZ_Epoch;@DayZ_Epoch_Server;"

Also make sure that you update your launch bat file.  Notice "arma2oaserver.exe" is no longer "expansions\beta\arma2oaserver.exe"

 

 

Where do i locate this file?

Link to comment
Share on other sites

Wow, there is some seriously flawed information on how to update your Arma2OA in this thread, uncluding wiping and reinstalling WTF??

 

 

Here's what I told my players to do, and NONE of them have had any issues:

 

 

1. How-to update your Steam beta version to stable:

 

  •  Go to your Steam Library
  •  Right click on Arma2 Operation Arrowhead
  •  Goto Properties
  •  Goto tab BETAS
  •  In the drop down box select NONE- 
  •  Let Steam update.  - If Steam does not download anything, see section 2.
  •  Close the Properties window.
  •  Your Arma2OA is up to date and running on Steam version
  •  If you game successfully updated Go to section 3.

 

2. If the game does NOT update:

(You can tell by looking in the downloads section in Steam to see if it has downloaded anything for Arma2OA)

Steam will not update if you have replaced the Arma2OA.exe in the A2OA root folder with the beta version (manually or via DZC), as it does not know the file has changed because it wasn't done by Steam

 

  • In the BETAS tab, select the 1.62 beta version of the game.
  • Stay in the BETAS tab.
  • Let Steam Update.
  • Select NONE again.
  • Let Steam Update.
  • Close the Properties window.
  • Your Arma2OA is up to date and running on Steam version.

 

***** Verifying your game cache of Arma2OA via Steam is not required but optional if you choose to do so. *****

 

 

3. DayzCommander setup:

  • In Dayz Commander click on Settings
  • UNCHECK the "Replace original Arma2OA files with Beta so Steam works" option.
  • Click Done.

If you do not uncheck this option DZC will replace the Steam version executable with your previously installed beta-version, giving you "Bad version" errors when you try to connect.

 

If you recieve the above error on connecting you will have to back up to Section 2 and do that part of the guide again and double check your DayzCommander setup before launching the game!!

 

 

 

 

 

All of my players have followed this guide, as well as my guide for them to give me thier SteamID's so I can update my databases with thier new information.

None have reported issues after we updated all servers to the Steam version.

 

 

OT: Our transition to the Steam version has went a lot smoother than I was expecting, primarily because I informed all my players PRIOR to updating via scheduled BEC messages and threads on our forums about the issue.  I also had these guides up in plenty of time before the update.

 

 

Hope this helps anyone lost on how to update :)

 

I followed your steps, now I get these errors:

 

1) Addon 'sauerland' requires addon "Chernarus'

2) No entry 'bin\config.bin/CfgWorlds/Chernarus.ilsPosition'.

3) No entry 'bin\config.bin/CfgWorlds/Chernarus.worldName'

 

I have the following expansions checked, actually the only ones on the list:

 

ca

Arma 2: Operation Arrowhead

Arma 2: British Armed Forces

Arma 2: Private Military Company

DayZ Epoch 1.0.5

 

The option to disable is greyed out and unavailable.

 

Btw thank you everyone for your help!!!

Link to comment
Share on other sites

I followed your steps, now I get these errors:

 

1) Addon 'sauerland' requires addon "Chernarus'

2) No entry 'bin\config.bin/CfgWorlds/Chernarus.ilsPosition'.

3) No entry 'bin\config.bin/CfgWorlds/Chernarus.worldName'

 

I have the following expansions checked, actually the only ones on the list:

 

ca

Arma 2: Operation Arrowhead

Arma 2: British Armed Forces

Arma 2: Private Military Company

DayZ Epoch 1.0.5

 

The option to disable is greyed out and unavailable.

 

Btw thank you everyone for your help!!!

 

 

You dont have Arma2 in your expansions list.  Launch the vanilla game through steam and check your expansions from there.

 

If its still unavailable, verify the cache of your Arma2 and run the game once, then try again with A2OA

Link to comment
Share on other sites

You dont have Arma2 in your expansions list.  Launch the vanilla game through steam and check your expansions from there.

 

If its still unavailable, verify the cache of your Arma2 and run the game once, then try again with A2OA

 

Followed your steps exactly and it did nothing...

Link to comment
Share on other sites

f3cuk, I have tried so many things im desperate at this point. Here is my config, what else can I post to help?

// GLOBAL SETTINGS
hostname = "[SHG]DayZ Epoch Chernarus 1.0.5.1/122548 www.slaughterhousegaming.org (UTC-8)";

motdInterval = 1;					// Time interval (in seconds) between each message


// JOINING RULES
maxPlayers = 40;					// Maximum amount of players. Civilians and watchers, beholder, bystanders and so on also count as player.
kickDuplicate = 1;					// Each ArmA version has its own ID. If kickDuplicate is set to 1, a player will be kicked when he joins a server where another player with the same ID is playing.
verifySignatures = 2;					// Verifies .pbos against .bisign files. Valid values 0 (disabled), 1 (prefer v2 sigs but accept v1 too) and 2 (only v2 sigs are allowed). 
equalModRequired = 0;					// Outdated. If set to 1, player has to use exactly the same -mod= startup parameter as the server.
requiredBuild = 125548;					// Require clients joining to have at least build 12345 of game, preventing obsolete clients to connect


// STEAM SETTINGS
steamPort = 2300;
steamQueryPort = 2301;

// VOTING
voteMissionPlayers = 1;					// Tells the server how many people must connect so that it displays the mission selection screen.
voteThreshold = 2;					// 33% or more players need to vote for something, for example an admin or a new map, to become effective


// INGAME SETTINGS
disableVoN = 0;						// If set to 1, Voice over Net will not be available
vonCodecQuality = 10;					// Quality from 1 to 10
persistent = 1;						// If 1, missions still run on even after the last player disconnected.
timeStampFormat = "short";				// Set the timestamp format used on each report line in server-side RPT file. Possible values are "none" (default),"short","full".
BattlEye = 1;                                           // Server to use BattlEye system
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Advertisement
×
×
  • Create New...