Fireball

Linux servers showing yellow with a question mark is unfortunately a known issue. <RANT>The whole system with the icons is more or less FUBAR. There is only (red|yellow) and (yellow|green). The current system cannot reliably tell which server you can join and which will boot you, at least you can't, just by looking at the icon. In terms of MP this is IMO a middle heavy catastrophe. </RANT>

Umm, it always only worked on the client, afaik.

Yes. If you make it a ticket in the Insurgency project tracker at DH, we might even consider making this an option. But as usual - Insurgency is considered a COOP mission, and this should probably mean that any team leader should be replaced by some player. After all there is only one special squad member, the medic, so if you're two in the squad, no biggie for someone to change to team leader at some point (e.g. when dying).

Mac, you're not coincidentally lurking somewhere around and just wait for someone to write this? If yes, can you make the FPSAnalyzer work with OA? Pretty please. :D

ArmA2FPSAnalyzer

Well it's a beta after all - everybody using it should realize what implications are connected with it.

Does that recent change in BE mean that everytime a new beta is released, $able has to add it to a central list or nobody will be able to play on BE enabled servers?

For the ACE version there's an ammobox now, next to the servicepoint.

Just a short notice: Legacy version 1.0 (vanilla only) is also playable without A2, i.e. if you own OA only.

I got the same issue, had to disable BE to complete my testing, it was latest beta server with beta client.

I just checked Takistan and Zargabad ACE missions (to be quick) and none of them showed the vanilla wounding system in action.

Please download the newly uploaded ACE PBOs from the files section now.

I'm sorry, I didn't test the missions after I compiled the PBOs, as I was in a rush. Looks like I botched sync'ing the "common" subrepos to the correct branch. Bear with me while I correct this and re-upload fixed PBOs for 1.50. ---------- Post added at 12:49 AM ---------- Previous post was at 12:45 AM ---------- I'm afraid, there is more to it than mismatched submodules. Looks like something got messed up, I'll have to debug the code first. Lay down that whiskey, Kol9yN... :-/ ---------- Post added at 02:21 AM ---------- Previous post was at 12:49 AM ---------- Ok, I've investigated into it using Squint and found out that special comments using 6 slashes (//////), introduced 3 months ago made the preprocessor fail (using preProcessFileLineNumbers). I reduced the comments to the regular double-slashes (//) and there it worked again! Apologies to all those who already downloaded it and couldn't play; please re-download the fixed missions now. On a side-note: Was anyone able to play those missions, e.g. with an earlier version (1.59?) of A2OA?

New release 1.50 - ACE version - it's now an UNO mission (soldiers from many armies) - includes heli lift system - diverse tweaks and enhancements according to the roadmap (see link below) Legacy version: 1.00 - Re-release of 0.81a - Captive RC-Pilot and Base (so the BLUFOR base doesn't get hammered permanently) - Fireball & Kol9yN (aka J-Guid) -------- Project Details Mission available at http://dev-heaven.net/projects/insurgency/files For improvements and fixes, please see the roadmap at: http://dev-heaven.net/projects/insurgency/roadmap Please feel free to post your suggestions here or, better even, file a ticket on DevHeaven in the project issue tracker.

Plus, delete the BAF and PMC folders from the server (or do not upload it in first place), because full BAF/PMC data should not be installed on the server.

A little heads-up from our news page: http://dev-heaven.net/news/683 Summary: Insurgency will new appear in a classic form as version 1.0 (bugfixes only) and new features and experiments in version 1.5.

Oy. Indeed that param was listed twice in my server.cfg, I saw that message before, but didn't attribute too much trouble to it. Fixed it and see there...it starts alright. :butbut: *mumbles something about resilient programming and disappears in the darkness*

Could this be the killer-issue? Do you have a standalone copy of the bin.pbo and sigs?

Nope, it's NOT the same: jail:~> md5 expansion/dta/bin.pbo MD5 (expansion/dta/bin.pbo) = ade4504753a7b5d342492e5affdb808b The 1.60 patch ran without issues though, but I also applied the hotfix, which contains a new bin.pbo.

I don't get this one to run properly. I uploaded all the data, ran tolower copied over the new server binary and that's what I get: WATCHDOG (1947): [sat Dec 24 16:35:08 CET 2011] Starting server (port 2302)... /bin/cat: /proc/cpuinfo: No such file or directory 16:35:39 Dedicated host created. File ../a2oa-dsconfig/server.cfg, line 129: .timeStampFormat: Member already defined. String id 767 is not registered String id 757 is not registered String id 768 is not registered Warning Message: No entry '.CfgVoiceMask'. Warning Message: No entry '.CfgInGameUI'. Warning Message: No entry '.Chat'. Warning Message: No entry '.sound'. Warning Message: Size: '/' not an array No entry '.CfgVoiceMask'. 16:35:42 BattlEye Server: Initialized (v1.126) 111/11/24, 16:35:42 String id 1600 is not registered The server is not registered in gamespy, plus I get 5 processes, of which 1 is stuck at 100% CPU load.

My best bet is, that it was tested against a server build not including the binoc fixes.

And you were making false assumptions and statements thereof, hence it was not so wrong entitling it "BS", that's the liberty I took, with a certain right. To xx-LSD-xx: This is not freedom of speech here anyway, this is a privately moderated forum. I'm not a moderator, but moderators can - if you like it or not - censor you out if you talk about specifically defined forbidden topics (to give one example). There goes your "freedom of speech". EDIT: If you don't like the fact that some OPFOR players have no NVG, play the mission at daylight. Or make sure you set it to a date where the night is bright in the desert or the moon is full.

<message removed by myself>

Also RC2 with both DLCs; clean now, no errors:

http://dev-heaven.net/issues/26722#note-2 I think we need a Linux DS RC urgently.