Yoma

Question for Dwarden: Would making a symlink from the operation arrowhead folder to the a2 folder be a solution? Something like *removed to avoid confusion* I cannot test this because i don't have the Steam installation... Or would that cause major issues for the steam upgrade/patch/verify cache procedure? *just did a small test and it would probably work, but is a bit tricky as you need empty folders first...*

I'm not managing any repositories at all... I just provide the tool. Try contacting the dear people of Kelly's Heroes if you want their repo to get updated/altered.

You can also just ignore the complaints and it will still launch the beta... The reason this message was implemented is for users that don't realise they have to have addons subfolders for loading addons... Or simply to warn people that they haven't downloaded the stuff yet... I'll see if I can make some exceptions (like for loading the beta)... In most other cases it's actually a usefull message.

If you need to specify the OA location: check out if the correct registry settings exist. You'll probably like having them set when patches come out... It may be a lot better to specify the folder in settings, OA folder. By the way did it detect anything in there?

What version of Arma? What addon are you trying to load? Btw i think this is in the wrong forum? It's not really related to editing?

Maybe because they have better drivers? Just have a bit of patience and hope for a decent ATI driver in the near future. Developer size IS NOT irrelevent at all especially not when it comes to fixing drivers or adding driver profiles. Good luck and sorry for my crappy attitude. Thing is multigpu setups have had issues from day one and time after time, game after game this gets proven. Don't worry, it will work out in the end, but it will need time.

It will install mods to the OA main folder detected in the registry. (Or to any folder you select...)

Remove all stuff from that folder asap. If you ever want to play online you'll be very very sorry...

First of all: to all crossfire/dual GPU core users: This is one reason why I don't buy your setups. As new games come out you're dependant on a 3rd party company (ATI/NVidia) to sort out new crossfire/blabla profiles. That in turn means that if a big big big company churns out a new game, you'll have an updated profile within days/ a week. Smaller developers... you have to pray. Please do tell us all how BIS is supposed to create a working crossfire profile for your ATICard and push that out automatically to all ATI users. Don't blame a developer for buggy technology that should be standardised accross the board and should really not even NEED profiles or at least be able to default to a decently working one if none exist. The only real reason crossfire and it's NVIDIA counterpart were invented is for you to buy more cards, while they can stall new technology. Historically you'll see that each new highperformance card just about adds up to the performance of 2 combined earlier tech cards. This is not a coincidence, it's called marketing and you bought into it. Second: turn down the postprocessing setting in your config, stop upscaling to 200% of native resolution, stop trying to set all settings superhigh (except for shadows which should be high/very high to use GPU). Third: Ati has some strangeness in Anti Aliasing implementation which makes it run slower then on NVIDIA cards. Either drop it or live with it. Fourth: If the game runs at 40-50 FPS on average you don't have great performance issues and are simply moaning. For me the game is running pretty good but that's a pretty subjective thing. If you can't put up with installing a patch now and then, this game/engine might not be for you. Go play something optimised with 400m VD and all the rest faked. Sorry for my blatentness... i'm just so fed up with people moaning about they ultra mega super crossfire setup giving them hassles that it makes me puke.

Made a preliminary version that should be OA compatible. Tries detecting OA Gamespy search seems to work Can launch OA with addons. The beta is a bit of a bitch but should work if you create a modset having modline Expansion\beta;Expansion\beta\Expansion . NO NEED TO SELECT THE BETA EXE! Can tell who's playing etc Should enable admins to create OA repositories As with anything that brings a lot of changes, this is bound to have some bugs :D

If you like OFP/Arma/Arma2 you really should just buy it, it's just a natural evolution of the engine. -The flir is really good. -The soundengine is a lot better (more sounds can be played at the same time, giving fights a lot more atmosphere...), this might seem a small change but i think it's huge. -The new content is very good and detailed. In short: to me it's just the best version of the engine up to date. A lot of other companies would sell OA as a full fledged new game and not as an expansion. I personally think that this might mean that BIS is not considering this the last iteration of Arma. Maybe they are waiting for better pchardware that could allow a lot more features in a further enhanced engine. Note that this is, of course, pure speculation. Months of fun for the price of 2 meals. I don't know if it would change much to the A2 campaign. Don't really feel like replaying that.

Have you tried renaming the OA exe to Arma2.exe (to fool your crossfire)?

The problem with this approach occurs when playing on multiple servers using different version of the same filenames. No one wants people to download files over and over again...

I don't think people like Dwarden, Maruk, Suma or pretty much any developer/ex-developer of the OFP/Arma/Arma2 games will have much to learn from a simple bloke like me. Addonsync is pretty much the idiot's approach to a complex problem. A lot stands or falls with how deep/complex you want to make the solution. For example BIS could take a "managed" approach where they set up a network that allows to download verified and tested full mods. (Stable ACE releases for example) Somewhat like Apples appstore but for Arma mods. The big benefit this would have for BIS is that they would get less hammered for problems that aren't theirs but have a source in buggy addons/scripts/blabla. The big downer with this approach is that it would reduce addonmakers' freedom a lot and would require extensive resources for testing, reviewing, serving files... Another approach could be a more liberal "dump whatever you use somewhere and we'll make sure you can easily get to it". For this system the local filecache I was talking about would be more suitable as at least it would restrict the number of local copies of a file to 1. However it would probably mean extensive changing of the way Arma processes addons. Diskspace might be an issue when people use smallish SSD's for optimal streaming performance... The great thing is that it would greatly enhance overall stability as you could make sure everyone is loading the exact same files and have the exact same game. If they could tightly integrate this kind of stuff with a torrentlike protocol that has several http mirrors for ensured performance they could make a network where every single addon is "up in the cloud" somewhere and the game can fetch whatever it needs, if needed. The big benefit of a torrentlike approach is that managing the actual network could be a breeze. Upon starting the server it could check if every addon loaded is on the network, and if not ask to upload the files to the network. When downloading clients could simply ask the cache for a list of files to use or download the missing files from the network.

A question on the internal mod manager: how does it handle mods in subfolders? Stuff like c:\ARMA2\MyReallyGoodMods\MOD1\Addons c:\ARMA2\MyReallyGoodMods\MOD2\Addons ---------- Post added at 09:44 AM ---------- Previous post was at 09:17 AM ---------- Terox: what i would personally do if I were BIS is something like -Create an addons-cache folder that simply has all addons but not listed by name, but by some sort of unique filecheck, something like #UNIQUECHECKSUM#.pbo -Then the server could publish a list of it's unique checksums and the client could try to load up the checksummed files and give a resume of the lacking files... Also this could be a base for synchronising addons... The biggest problem this system would have is "when to purge the cache". A suggestion there would be to keep track of the last time a cached file got used and on what server. If you've only used a file on server x and server x changes the file the cache can get purged. This system would move away from "modfolderbased" loading of addons, but more towards "checksumbased" loading of addons. The beauty of this kind of system is that it would allow everything we have today without being intrusive at all, versioning included! The biggest drawback would be diskspace.

I'm pretty confident BIS will indeed solve the matter. As for Sickboy's little explosion: completely justified if you ask me. People simply don't realise the amount of work he's doing. (let's not discuss Ace any further here please) I wouldn't expect BIS to have a clearcut solution from day one though. Implementing it will probably take time, trial and a well tought out strategy. However it's clear they are working on to implement a more userfriendly situation. For me personally Addonsync has been a nice ride with ups and downs, support of some great people. A great learning experience. Damn I'll need to find myself another little project to tinker with :p

Yes, probably. Note: the patches can be extracted using 7z For example: -extract the Arma2Patch_1_05_to_107.exe, it will contain a file called [0] -extract the file called [0] -this will create a subfolder called [0]~\ARMA2Patch_1_05_to_1_07\ -just "find" all files in this folder an its subfolders for a complete list. Some will be listed multiple times... Copy all the files to some folder, 7z them with max compression, upload them. You could also try something funky with AddonSync if you have full control over the server/your machine at home.

Hmm were you by any chance trying to load up 1.07 with the beta folder loaded?

Remove overclock, check system memory using some diagnostics tool (e.g. memtest from a bootcd), let it run overnight and see if it finds errors. Are you by any chance using more then 4GB ram?

The message is not "get CA", the message is "Are you sure you want to launch without addons". All this means is that you haven't selected any addons for online play. As my tool is mostly geared towards using addons with Arma2, a message might be appropriate as the user probably just forgot to select any addons...

Would it be possible to make a "better" ammobox in some kind of mod? What i would personally like is something where you can just type part of what you're looking for instead of scrolling for ever... Like type "G36" and get all the different styles of them with potential ammo filtered out. This doesn't really apply to Ace only, but to just about any crate/vehicle stuffed with all sorts of nice goodies. I just wonder if it would be feasable to make it.

Did you copy the file from a CD/DVD? Windows tends to keep files readonly when copied manually from optical media.

Then you can still use cpucount=8... Have you actually benched it, in really "stressfull" situations? Win7 probably does use all cores a bit more by itself then WinXP which could explain what you're experiencing. However I'm personally not convinced HT would not be a limiting factor on any OS when putting the CPU under stress... Then again, if it works for you, all the better :D

And the COLOUR of the surface (white heats up less fast then black) This seems totally cool!

Bug #10150: Detection of TS3 exe does not work on win7 x64 if 64 bit version of TS3 is installed. Bug #10266: TS3 port setting ignored when not using "Nickname" parameter (TS3 doesn't like extra '&') Bug #10393: in XML, <TSChannel></TSChannel> not working Feature #10151: Add support for autolaunching Mumble Feature #10325: Better detect version number of new beta... Feature #10648: Add in the exThread option Feature #10941: Replace linux server generated forward slashes with backslashes in modstring Feature #11015: Remember value for "Clear output folder on build" in gui