Jump to content

suma

BI Developer
  • Content Count

    3202
  • Joined

  • Last visited

  • Medals

  • Medals

Posts posted by suma


  1. There is now an Arma2 beta deployment channel on Stream. I think you can access it under Properties (right click on Arma2). There should be a tab called "Betas".

    DISCLAIMER: I don't use Arma2 on Steam, but this is how it works with Carrier Command.

    With Arma2 it currently works in a different way. Beta is installed as a separate product, and when you opt-in for a "Test" beta in a beta, you get the performance profiling version instead.


  2. Could we get some more info on the performance profiling beta build 98809? Any suggestions for use?

    It is just a version with the AI performance already fixed, so that anyone can play with it and not be distracted by the issue which is already know.

    I have no particular hints on what to look for and I will not provide any guidance on how to use it. I have posted it in response to https://dev-heaven.net/issues/60304#note-75. If someone wants to write a documentation on Wikipedia about the performance profiling, I can revisit and clarify if needed. There will be no performance beta published updated regularly, but may be refreshed from time to time.


  3. I patched up from 96751 and I now cannot connect to my favorite server (a DayZ Lingor server).

    Rolling back to 96751 makes it show up in the server browser however the server is running the latest 1.62 server side version and I cannot join unless I patch up.

    If you want to us to check the problem, please, write a full server name here.

    ---------- Post added at 09:27 ---------- Previous post was at 09:22 ----------

    I patched up from 96751 and I now cannot connect to my favorite server (a DayZ Lingor server).

    Also make sure you have Dayz Lingor enabled when checking for Dayz Lingor servers - you cannot see them with normal Dayz or with Arma 2 OA without Dayz Lingor. Sometimes the server admin running modified Dayz may need to make some changes as well:

    - either run a recent beta on the server

    - or the server needs to contain Dayz in the server name

    - or the server needs to contain Dayz in the mission name


  4. Then how do you explain that I cant find my server with latest beta on clients, and I can find it no problems, without using beta patch? Gamespy limit? Not.

    I explain it that there must be some bug in the beta implementation. Sorry for that, but such things happen, that is why it is a beta.

    Try it yourself. Open Arma2(CO) with latest beta and go to server browser. Open up filter and type SFRJ ( server name field ). Then stare at empty screen for a moment.

    Thank you for reporting the issue with details needed to reproduce it. Now we have a repro, the bug is likely to be fixed quickly. It is impossible to fix issues like "server browser is borked and does not work", but it is well possible to fix bugs which have an easy to follow and reliable repro. I can confirm I can reproduce the issue and the fix should be ready within a day or two.

    ---------- Post added at 11:03 ---------- Previous post was at 09:35 ----------

    Fixed in 96989. The bug was with handling servers with BattlEye not enabled.

    If you want your server to be visible to players who are not using filters more often, esp. to players using recent beta versions, you can implement following measures to match server browser prioritization:

    - enable BattlEye

    - use beta 96016 or newer so that the server location is known to the browser


  5. Since build 96643 a new value serverGeoLocAuto=0 can be used in ArmA2OA.cfg to allow server admins to work around mistakes made by the automatic geolocation. When this value is used, values serverLongitude and serverLatitude will be used as written in the file and never overwritten by the game. The values detected by the geoip service will be written to serverLongitudeAuto and serverLatitudeAuto for information purposes but not used.

    You can also continue posting major mistakes here, chance is the GeoIP service provider could be able to fix his database.


  6. despite these changes and features, i will be able to see full server list in the future again if filters set to show all?

    No, you will never ever again see the full server list again. There are too many servers and having full list was causing too much load on the matchmaking server. We need to improve or redesign the server browser to be usable even without the complete server list.

    ---------- Post added at 17:19 ---------- Previous post was at 17:17 ----------

    Can you please elaborate/explain a bit what this means for clients/players. Thanks

    This means nothing yet. Once server longitude / latitude info is populated and confirmed to be working correctly, we will start filtering out distant servers by default, so that you can always see the servers close to you.


  7. I hate to split hairs, boss, but I presume you are talking about beta 96015, not 96016?

    Dedicated server exe actually has a revision number 96016. I am interested in reports from dedicated servers. If you are hosting a dedicated server using normal game exe then yes, I am interested in 96015 version as well.

    To keep this thread short and workable, please do not post when your server is reporting OK. Post only when it is not OK, as this is what needs to be worked on, and it would be impossible to find in the OK, OK, OK list.


  8. We have implemented a server geo location in this release, so that we can improve the server browser experience in the future. The coordinates should be save in the server ArmA2OA.cfg file in serverLongitude / serverLatitude values (read only, no need to attempt to change them).

    I would like to ask server admins to check if those fields are correct for them. If they are wrong by a small bit (say off by 1 or 2), it should not matter, but if the value is way off (like locating your server in Australia while it is actually in US), please, report the issue here.


  9. I am not aware of a change which would cause this. The D3D engine does not contain a single change since 94943 at all. As 95417-95883 is still quite a broad range to check every other unrelated change for a possible influence, it might help if you can tell which of the beta builds from http://www.arma2.com/beta-patch.php is the last to work, and which is the first to break this?

    What about versions 95819, 95777, 95724, 95660?


  10. since Sunday july 1st I noticed a change in my Player ID. Before the DDOS attack on the Hive it was:

    103170AX (using Arma X)

    after the attack its now:

    103170

    This is the player Id you see in the player profile screen? If not, where (and what is the player Id in the profile screen)?

    What is the game build number you can see in the main menu?

    ---------- Post added at 09:17 ---------- Previous post was at 09:15 ----------

    For me too, the problem persists. Takes the incentive to play :(

    What is the player ID you can see in the profile screen? What is the build number in the main menu? What edition is your game (Operation Arrowhead, Reinforcements, or X: Anniversary edition)?

    If someone is not comfortable of posting his Player Id here in public, feel free to post the reply to me as a personal message.


  11. I suspect if they were going to recode the dependency issue, they would have stayed with the old build system, the fact they are releasing this alpha suggests they plan on sticking with the new compiler, and therefore the new glibc 2.7... But that is pure conjecture on my part... just a logically conclusion based off other posts and this alpha build requiring glibc 2.7

    It probably would be helpful for the Dev to post the build host OS and version so we can know what other possible issues there would be with dependencies for this build, so that dedicated server admins can migrate to a compatible version of Linux.

    The OS where we do the compiling should be irrelevant (it is some Debian, but this really should not affect the compiler output). What matters is we had to move from old GCC 4.x we were using before to GCC 4.6 or 4.7 because the old version did not support some language features used by libraries we are using now.

×