Jump to content

Forums Announcement

Read-Only Mode for Announcements & Changelogs

Dear Survivors, we'd like to inform you that this forum will transition to read-only mode. From now on, it will serve exclusively as a platform for official announcements and changelogs.

For all community discussions, debates, and engagement, we encourage you to join us on our social media platforms: Discord, Twitter/X, Facebook.

Thank you for being a valued part of our community. We look forward to connecting with you on our other channels!

Stay safe out there,
Your DayZ Team

clockcar

no entry bin config.bin CFgWeapons.

Recommended Posts

I'me having trouble playing Dayz, most of the time I can't join a server because it says that I have a bad version but it's up to date and when I can join a server it says bin config.bin CfgWeapons and start in the woods or hill (no trees) whiff nothing but a flash light, pain killer and a ban-deg and there are no buildings.

it's happening all the time but I did the install correctly and it says that the integrity failed wen I try to verify it please help.

Share this post


Link to post
Share on other sites

It happens to the most of us. There's nothing wrong with it. (the bin error)

Share this post


Link to post
Share on other sites

START OVER, GUYS...

There are five or six steps to getting this all installed right unless you use Six Launcher. That program didn't work for me, so I don't know how many steps there are.

1. Uninstall the programs.

2. Install ARMAII and run it as an admin. If you have a Steam shortcut, you need to make sure it is running as admin. Possibly for both the Steam program, and ArmaII. The admin option is under PROPERTIES, Advanced button. If this runs correctly, go to 2. When you run it, jump into Boot Camp or something and make sure it actually runs.

3. Install OA, and run OA (NOT Combined Ops) as admin. (I have Steam version. When you run OA it gives you an option between OA or Ops. I do not know how the retail versions will do this.)

4. Run Combined Ops. If this is working correction, I believe you will have two icons in the bottom left. ArmaII and OA. Your version number in the bottom right is probably 1.xx.93xxx or something smaller.

5. Download the beta patch and run the executable that is in the archive. The site is: http://www.arma2.com/beta-patch.php. (It isn't asking me for a password, but it isn't working RIGHT NOW. You need the one at the top, which is 94444 unless they issue a new patch in the next couple hourse, which COULD happen...)

6. READ THE README FILE that is in the archive. You need to pass some new parameters to the executable. Specifically, you need

-mod=Expansion\beta;Expansion\beta\Expansion

*** If you are using Steam, you almost certainly need to go to the directory where OA is installed and rename arma2oa.exe. This is the executable file for OA. Rename it to BACKUP_arma2oa.exe, or whatever you want. The "exe" probably doesn't show up in your directory. If it does not, ignore it. It's old-school vernacular for an application file.

*** If you are using Steam, from the install directory for OA, go into the Expansion folder, then into the beta folder. There is another file called arma2oa.exe. Right click and COPY it. Go back to the installation folder for OA and PASTE that in there. When Steam runs OA or Combined Ops, it should now use the patched executable.

7. Run Combined Ops. If all this has worked so far, two magical things will happen:

A) At the bottom right, your version should be 94444 or whatever the latest patch is. If it is not, you are probably still running the original executable. Either Steam or a shortcut or Six Launcher are pointing at the wrong executable. (I don't know if that is possible with Launcher...) Nobody on these boards can figure out exactly how you are doing that. FIX THAT.

B) At the top right, under the icons, you should have tiny letters in some bright color that say arma2, Expansion, beta. You may or may not have arma2 - I do, so I am guessing you should also. If you do not have Expansion and beta, the -mod parameters are not being passed to your executable properly. FIX THAT.

8. Put the DayZ mod files in your OA directory under \@Dayz\addons\. Add the -mod=@DayZ parameter in Steam or in your shortcut.

FINALLY, run Combined Ops again. In addition to A and B above, you should now have tiny, bright letters for @DayZ in the top right.

You should, most likely, hopefully, I am praying that you can, be able to connect to a server now.

It is very important to remember you are installing two separate programs that could have their own bugs between them. Then you are installing a BETA fucking patch for one of those programs, which requires that you run a different executable AND modify your command line parameters. THEN you are installing an ALPHA mod for a program, half of which is BETA.

You CANNOT just throw all this crap together and then post saying "I am invisible and I cannot eat beans" and expect other people to figure this out.

Install one step at a time and make sure it is working.

Or use Six Launcher and read the instructions. My guess is it works really well if you follow the instructions, or Rocket would not have adopted it to assist the community.

Share this post


Link to post
Share on other sites

×