Noble75

It is good to know that currently Arma 3's built in key binding editor is missing at least one binding which is for "pause" key. It is assigned by default at least for some gamepads and such, so if you want/need to edit it, go directly to My Documents\Arma 3\USERNAME.Arma3Profile and find row with "keyIngamePause[]={KEYCODES};".

What?-) I just said that I decided to switch train and start using another excellent application instead which seems to work as well as any professionally coded solution. If you find that annoying - it is really unfortunate and was not my intention. I just tried to hint that this wonderful new software (which is still utilizing six rsync network) was ultimate solution to things I described earlier and hence you can forget everything I said and keep doing stuff as you wish without me complaining about it. It even comes as 64bit solution as u can see: http://www.armarize.com/downloads.php Any ways sorry about not using your bug tracker system. I usually tend to get quicker results and more accurate and honest answers with more direct approach. In this case man can clearly see that there is very little wrong with your software and that I was just unsuitable customer to use it. Both things solved in record time. Case closed - lets move on :)

lol... I'm starting to see the full picture here then. Downloaded installation packs clearly do not belong to temporary folder but to appdata folder where they can rotten until doomsday in case you would someday want to reinstall older six updater version w/o downloading anything. Do not worry - wont bother you any more. I just leave this here http://www.youtube.com/watch?v=JVXsysRM3bI as a hint what happened.

Yes - but it should be users decision whether to install 'em or not - always. Not all people play @dayz and there will be plenty of people who lack the knowledge, will and/or time to downgrade their installs if their servers stop working. Try to remember now that people use six updater to get addons/updates which their chosen server requires - not vice versa. Yes I learned this the hard way after I finally went desperate on some point of my program behaviour studies and deleted entire beta folder before manually installing new beta. After that six launcher stopped trying to modify files in there. Anyway are you saying that my problems with this "update beta patch or not"-button were, that I had .rsync subfolder in my beta folder before the configuration button was introduced to six launcher in some patch and at that point .rsync folder needed to be manually deleted to get the configuration button to work... Or did I misunderstand something here ?-) I'm sure it will and obviously these 1.60-1.61 problems are temporary. In the end fact is that without six project managing addons would be rather impossible. I do value the work and time you people have (and will) put to it and don't want this thread to start sound like whining which it isn't. Thanks for taking the time to reply. ---------- Post added at 16:45 ---------- Previous post was at 15:48 ---------- Awesome! Anyways while doing that could you possibly tweak the installer also not to save itself to "WINDOWSROOT:\Users\XXXXX\AppData\Local\Downloaded Installations\{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}", but to "UserTMP". Nowdays people tend to use SSD drives for windows partition and it is not very fun to lose additional 16MB from somewhere where disk cleanup won't reach _every time_ six updater gets updated (yes I've forwarded this directory to temp directory with symlink myself now to get around this bit sink, but still... plenty of wasted space for many there). 10 updates and you have suddenly lost 160MB SSD space which wont be coming back unless you know where to look. As related comment... Arma2 OA saves plenty of MP cache stuff to that same "local"-folder under "Arma2 OA"-folder. That folder can also be moved to other partition/disk and replaced with symlink pointing to the new location if c:\ is starting to get full or if you just want to keep it cleaner. For those interested... creating symlinks in win7 is rather easy. Just move/create folder to somewhere and delete the original. Then open command prompt in admin mode and use 'mklink "{path to original location of the folder you moved}" "{path to new location of folder which you moved}" /j'-command to create linked folder. For example 'mklink "C:\Users\YourWinUserName\AppData\Local\ArmA 2 OA" "D:\MySymLinkedFolders\ArmA 2 OA" /j'

If this is the case then it is what most likely happened and I am falsely blaming six updater from forcing the BE update. However in the end the end result stays the same. Clients should not be updated before servers have been updated (specially if this happens against the will of the end user no matter what settings he changes). The downgrade process from 1.61 back to 1.60 is real pain. I got banned at least from one server because of using "wrong" BE version while trying to connect it. Six launcher is the 1st software I encounter which pretty much installs anything it wants w/o asking any questions. It definitely should prompt before touching beta/battleye and tbh it would not harm having option not to load and install every point patch of the six client either. Most software have option to download only updates which are tested and working "release"-versions. The software you guys distribute is helpful and useful in many ways, but there is lots to be learned about user friendly and stable solutions. I understand that the software is _free_ and you people do this from your good hearts, but still... For fairness I must say that six launcher compared to six updater as a whole is great step forward as user friendlier way (and gui) to start the game, but as said - it still does not justify the ninja installs. Please fix them as soon as possible.

You don't seems to be aware that manual (at least older) beta install didn't force BE install unless BE was manually uninstalled before executing the beta installer. Latest six launcher did and this caused all wonderful problems. Dunno but you might want to add prompt to this other ways fine software which would ask permission before touching the battleye or beta folder files. I believe that I might not be the only one who thinks that "if it works, don't touch it". I really don't want to update either as long "my servers" agree with the versions I'm using. The goal is to update client stuff after servers have updated theirs - not vice versa. ---------- Post added at 12:05 ---------- Previous post was at 11:54 ---------- Not exactly because the battleye has been updated to version which 1.60 servers definitely doesn't support. You have to also uninstall the battleye manually and find version which works with your preferred server. This kind of version may or may not come with the latest beta client "the server" would other ways support. Best way I've found out so far is to reinstall steam version of the BE and let MP server to update it to latest version it supports. Better walk-through for downgrading here: http://forums.bistudio.com/showthread.php?137408-Six-launcher-beta-no-response-from-server-client-crash-during-mp-init&p=2190998#post2190998

Yep I noticed that deleting entire beta folder and reinstalling beta manually obviously did get rid of .rsync folder and after that six launcher stopped updating the beta folder. However before doing that it was restoring the beta always to latest version it had previously installed whether "update beta patches" was checked or not. I want to clarify that I have been write protecting those folders as last measure and only after this problem appeared and the method has not prevented any modifications to .rsync folder by the six launcher client. The original problem to "update beta patches"-button not having any affect has appeared during some previous patch or it has been there since introduced being unable to change the configuration somehow. That being said - after deleting the entire beta folder and reinstalling beta manually obviously removed also the .rsync folder and starting six launcher now w/o any update configuration present, it obviously doesn't try to update beta any more. However I believe that patching six launcher to next version would bring these folders back ? I will if the problem repeats itself after next version of six launcher is out and I install it (obviously with all write permissions enabled so it can freely create the files). Actually this is just the problem what broke my MP. This is not how the manual install works. The manual beta installer did not force battleye update when it was executed. It updated files in the beta folder and skipped battleye install unless you had manually uninstalled the battleye before executing the beta installer. Six updated forced this BE update with beta update and this caused big problem. I ended up having such BE version on my client which did not communicate properly with 1.60 servers and in fact caused client to crash when MP game was initializing. Only way to get working version of battleye back was to manually uninstall it and go through steam installer to fetch the old one which you then updated @ MP server. Dunno but you might want to add prompt to this other ways fine software which would ask permission before touching the battleye or beta folder files. I believe that I might not be the only one who thinks that "if it works, don't touch it". I really don't want to update either as long "my servers" agree with the versions I'm using. The goal is to update client stuff after servers have updated theirs - not vice versa.

Yea there seems to be some issues with the link - here is one to the download page http://www.arma2.com/beta-patch.php

If you have been having problems with your arma2 MP connectivity after some six launcher updates lately, here is working fix to get your Arma2 OA (steam) client back up and running on multi-player servers. - First of all it seems the "leave beta alone"-button in six launcher may be non functional at least in some circumstances. It may try to update your beta no matter if it is checked or not. At least that is what was going on in my computer. Many servers do not support betas above "ARMA2_OA_Build_94700". - Secondly latest six launcher forces battleye update which may not be supported by your favourite MP server. Manual beta update doesn't do this. Many servers wont support any "beta" battleye versions. In worst case your client files are pretty messed up atm after six launcher updates - so here is at least how I got it fixed: 1. Download latest working "old school" beta from ftp://downloads.bistudio.com/arma2.com/update/beta/ARMA2_OA_Build_94700.zip 2. Let six launcher to patch itself to latest version (six launcher v1.0.2.9 and six updater v2.9.7pre14 were latest while writing this). 3. Go to six launcher options and make sure that option "update beta patch" is not checked (even this option seems to be broken) and that option "force enable beta patch" is checked. Then close six launcher. 4. Find your expansion folder (ie "I:\Games\Steam\SteamApps\common\arma 2 operation arrowhead\Expansion\) and delete entire "beta" folder (including all six launcher update files). 5. Manually install beta "ARMA2_OA_Build_94700" which you downloaded earlier. Just run the file what you find inside the archive. Don't worry about the invalid cd key promt. It seems to give it even you're using perfectly legal, valid and paid Arma2 steam client. Just click ok and it will continue the installation normally. 6. Now go back to your expansion folder, enter folder and execute the "uninstall battleye" file. Then launch steam, right click on "arma2 OA" for pop up menu and choose "reinstall battleye anticheat system" to get working battleye version to your computer. 7. To update battleye to version which your server supports you have to run beta client manually for 1 time (do not start six launcher!) and join the server. This is done by creating shortcut pointing to your arma2 beta executable. Go back to your expansion folder, then to beta folder and you will find your "arma2oa.exe". Make a shortcut from it by dragging the file to your desktop with right mouse button and by choosing "create shortcut from dropdown menu" after you release your rmb. Then right click the shortcut icon what you just created and apply following data to end of "target"-field: -beta=Expansion\beta;Expansion\beta\Expansion -nosplash After this your target field should look something like this (obviously the patch to the expansion folder will be your own): "I:\Games\Steam\SteamApps\common\arma 2 operation arrowhead\Expansion\beta\arma2oa.exe" -beta=Expansion\beta;Expansion\beta\Expansion -nosplash Now just click the shortcut icon and your game should start with the beta. There should be version "94700" visible on bottom right corner when it does. If everything seems fine, click multiplayer, find your server and join it. Battleye should update during the process and your game should be working fine again. -------------------------------------- At this point six launcher should be safe to use again as long there is no "dot" folders in your beta folder and there shouldn't be if you deleted the folder earlier as instructed. Everything from this point forward is done to precaution measure and to give you some additional safety with six launcher and absolutely prevent it from ruining your installation (till the author gets it fixed or when all servers you use support v1.61 client). The following steps are not recommended to anyone who doesn't know what they are doing and/or understand what other problems may arise after performing the steps mentioned here.). You will also need administrator rights to your computer to do this. -------------------------------------- 1. Go back to your expansion folder 2. Deny write access from programs like six updater/launcher to "battleye"-folder, "beta"-folder and all the files inside them. -> In win7 you probably right click the folder, go to security, edit permissions and check authenticated users -> deny write. Remember that game might want to update battleye itself so you might have to give it access back in some point if further problems arise. However I recommend keeping these 2 folders "write denied" as long six updater/launcher is going to update these files w/o actually asking permission from the user. -------------------------------------- Final keywords: This fix applies to Arma2 OA - domination2 - crash to desktop during the MP game init - no response from server - server does not respond - wait for host - six launcher - beta - v1.61 - v1.60 -------------------------------------- Hopefully this helps someone yours, Noble

Yea I tested that before also, but it didn't fix the already active problem unless combined with reboot (which I obviously didn't do back then). Didn't even know that my GPU had locked to lower clock back then because wasn't monitoring it. This has totally fixed it for me... no problems in arma2 multi player what so ever after the setting change. Even the domination2 end game works like charm now and graphics card doesn't do any nasty tricks. CPU load is distributed rather evenly to all 4 cores and there is plenty processing power to spare. I even have the advanced power management set to allow 5% minimum processor state and that doesn't cause any problems either. So now in multi player I have rather low GPU usage and rather low CPU usage. Could probably boost the view distance and gfx settings up quite a bit if needed, but haven't gone there yet. One thing at the time. Just enjoying the constant and smooth fps now - through the entire session. All in all - I don't know if my case was isolated faulty hardware issue or is the problem something what has roots in some specific graphics chips or nvidia drivers. If having problems, changing that setting and rebooting should be worth trying at least.

Haven't tried this "solution" yet, but I am having exactly same issues while playing domination2 MP takistan coop map. In start fps is smooth and way over 25. At some point during late game it always clogs up and frame rate drops to unplayable level (approx 12 or so). This only happens in multi player and I do have decent 8/1mb dsl connection so it should not be the problem either. Arma CPU usage is around 30% in this point (AMD Athlon II X4 645 3,1GHz). Restarting the client won't fix the issue. It continues to have low fps even on the "welcome texts" when u re-enter the server. Sound like server side issue to me, but is it something you can fix or something what is related to hardware limitations of the server. ---------- Post added at 14:44 ---------- Previous post was at 14:22 ---------- If I may guess something I would say that it has very little to do with GPU and plenty to do with CPU. Is it about servers or clients CPU - no idea, but it seems that when CPU (on one core) is fully utilized, the FPS (and GPU usage) starts to drop. In other words perhaps the multi processor usage could be tweaked further? For those referring to "only 55% or 30% CPU usage" in previous posts I have to remind, that windows task manager doesn't necessarily tell the whole truth as 25% or 50% load indication may actually mean that one of 2 or 4 cores is running on 100% load and is unable to perform everything what Arma2 wants it to do. so... further investigation to this direction might be worth it? Or not? Like I said - just a guess. Now forget everything what I just said. After long and painful investigation I found out that my graphics card (nvidia GT430) seems to be bugged somehow and always repeats it's behaviour in (and so far only in) Arma2 multi player environment. This is rather funny and strange coincidence. Arma2 multi player environment seems to be the catalyst for the bug and only computer reboot resets it (temporarily at least). Problem origin: GPU Graphics clock drops from (default) 700mhz to fixed 405mhz and gets stuck there. You can't get it back up with tools like official Nvidia over clocking utility either (which I installed just to test this possibility). Card just doesn't want to throttle itself back up even temperatures are way below any trigger levels (and it doesn't want to throttle itself further down either when gpu usage drops to 0%). Computer reboot seems to be the only way to reset the clock rate. This is not GPU heat related issue - that is clear already. The card might be somehow broken, but giving it a change and investigating ways to prevent this GPU from throttling down in 1st place. Will update this post if I have found some working solutions. Somehow I still feel that this is software based problem. Note to self: I'm not sure if alt tabbing the client might have something to do with the "trigger" going off. Gotta keep eye on that. Current test: GPU power management settings turned to "maximum performance" from "adaptive" in global nvidia settings. Current test "fresh start" notes: -> GPU still throttles between 50mhz, 405mhz and 700mhz in desktop while arma2 is not running. -> GPU throttles up to 700mhz after starting arma2. -> GPU doesn't throttle down from 700mhz when alt tabbing from arma2 to desktop. important fact: while in "adaptive" power management mode GPU did throttle down when alt tabbing from arma2 to desktop. Related to problem? Current test "playtesting" notes: -> So far no problems, GPU staying at 700mhz, usage around 40-50% on 40/60 man domi/warfare server. -> GPU temp at 50-55C, fan speeds at 35% most of the time. -> Normal fps, game well playable even after plenty of stuff has been destructed. -> Alt tabbing doesn't cause any issues. Conclusions: At the moment it seems that at least my FPS problems vanished after turning GPU power management settings to "maximum performance" from "adaptive" in global nvidia settings and restarting computer (GT430, driver version 301.42, win7 64bit, AMD Athlon II X4 645 3,1GHz). Will provide further info if facts change.