Jump to content

Jale666

Member
  • Content Count

    8
  • Joined

  • Last visited

  • Medals

Community Reputation

10 Good

About Jale666

  • Rank
    Private

Contact Methods

  • Skype
    jalef666
  1. Have you tried putting serverGeoLocAuto=0; serverLongitude=138; serverLatitude=-34; into your server.cfg file?
  2. 1. Might be helpfull to ask whether 32 or 64 bit system. 2. Ask whether running Crossfire or SLI 2, 3, or 4 way
  3. I have been doing some testing with my own client /dedicated server setup (both standard steam installs A2,A@OA, BAF updated on 13/11/2010). I have discovered that the BattlEye non intialisation problem occured first with beta patch 75445. To elaborate server is running arma2oaserver.exe updated manually from steam on the 15/11/2010 other than that all other files autoupdated from steam on 13/11/2010. If client is running beta patch 74858 (updates client to 1.55) i have no problem joining my own or any other 1.55 server WITH BattlEye enabled.......install beta patch 75445 and then cannot join my own or any other BattlEye enabled 1.55 server. Looking at the changelog for 75445 it seems that a new feature was added that allowed the client to disable or enable vsync.....my guess is that this routine has somehow broken BattlEye initialisation for steam users....maybe not but it appears that something was done by the developers between 74858 and 75445 that broken BattlEye initialisation particularly for Steam users. Conclusion is that this is most likely a Steam/BI problem and not a BattlEye problem. Workaround for steam users is to install and use beta patch 74858 until this is sorted out. Both Systems W7 Pro/64 Asus M/b with x58 chipset I7 CPU
  4. I have been doing some testing with my own client /dedicated server setup (both standard steam installs A2,A@OA, BAF updated on 13/11/2010). I have discovered that the BattlEye non intialisation problem occured first with beta patch 75445. To elaborate server is running arma2oaserver.exe updated manually from steam on the 15/11/2010 other than that all other files autoupdated from steam on 13/11/2010. If client is running beta patch 74858 (updates client to 1.55) i have no problem joining my own or any other 1.55 server WITH BattlEye enabled.......install beta patch 75445 and then cannot join my own or any other BattlEye enabled 1.55 server. Looking at the changelog for 75445 it seems that a new feature was added that allowed the client to disable or enable vsync.....my guess is that this routine has somehow broken BattlEye initialisation for steam users....maybe not but it appears that something was done by the developers between 74858 and 75445 that broken BattlEye initialisation particularly for Steam users. Conclusion is that this is most likely a Steam/BI problem and not a BattlEye problem. Workaround for steam users is to install and use beta patch 74858 until this is sorted out.
  5. I don't mean to be critical here Dwarden but are you sure that you have Steam users that can connect to 1.55 BattlEye enabled servers - everyone who has steam version in my small part of the world has the same problem - no exceptions - perhaps you could post some system/install details of a steam version that works with 1.55 BattlEye enabled servers.........and we could maybe help to solve this problem.
  6. I have w7/64 A2 A2OA BAF (full Version) all from steam - kicked back to multiplayer lobby when battle eye fails to initiate. Happens on all 1.55 servers running battle eye. Date of BattlEye BEclient.dll in users\appdata is 29/09/2010 - date of BEclient.dll in A2OA\expansion is 15/11/2010 so new dll is not downloading from server at all. Almost all of our clan have steam version - all have same problem.
  7. Thanks Placebo, for the link, am I correct in assuming that the server file on its own will work with the steam version of OA?;) Would it be possible for BI (or someone) to post an example server.cfg file and command line parrameters to start the server in the Combined Operations mode for an installation where both ArmA2 and OA are standard Steam installs?...... W7 64bit Pro Thanks again, in advance.:bounce3:
  8. If what you say is correct then where is the dedicated server file (ArmA2OAserver.exe) that, as I have been led to believe, was included with the 1.52 71816 update?.........
×