bertieb

Thanks for the quick reply Neo (my browser ate my quick reply). It's really handy to have the git repos to see how things are done. We had a quick glance at the scripts and we're getting a feel for how things fit together. Meantime we are using both 1.6 and your 1.7 dev pbo :) 1.6 seems to have the debug [semi?] invulnerability still enabled in the Altis version. Haven't had much of a chance to try 1.7 yet; first attempt the server segfaulted but I wasn't able to replicate this in a quick test. The slightly different start is interesting, and I'm keen to see how it plays out! Looking forward to it! :D

Hey NeoArmageddon, thanks for the work that you (and others) have contributed to this great mission. It's really good to see that you are still keeping it active - it's by far my most played mission! :) A couple of my friends and I are looking into making some of our own additions - eg one of the Arma 2 / Chernarus variants had 'ambient combat' which we really liked - and contributions. I took a quick look at Vormulac's GitHub and found yours as well. The latest commit seems to be from August 2014; I was wondering if any of the additions you have been making are going to be pushed out? Say to an 'experimental' branch if you wanted to keep master in line with releases. If we come up with anything useful we'll of course make it public as well, but don't hold your breath- although we can all code, none of us are familiar with SQF syntax... and the last proper editing I did in the series was way back in the OFP days... and we all have other projects and busy lives... but we play it enough that we have a strong desire to add to it ;) Thanks again for all your work!

Let's not put words in folks mouths, no-one said anything about malware, we're all just trying to get the alphas to run. The last official release (and the betas before 1.62) ran fine. However, these alphas have been crashing with glibc errors; perhaps that's where the confusion has arisen? There's no blame here :) As I understand it what complicates matters is that it's not as straightforward for Steam users to do a rollback of their client, so some people are champing at the bit for a release of 1.62 (some more vociferously than others!). I think it's a bit much to ask everyone to try a recompile of glibc when there's other avenues to be explored and there's no guarantee that will alleviate the problems.

I'm confused; does that mean you ran the first 1.62 alpha okay? Is there another pre-1.62 alpha I'm unaware of? Fair enough. I reckon a small minority were whining (which admittedly is pretty sad given how much support BIS have given the community but idiots will be idiots) and they've been booted out.

I have no idea :P The CIT page on reporting issues talks about Windows crashes. I'm not even sure how useful that size of a core dump is. My intention was to put anything that might possibly be useful into the relevant issue on the tracker. The crashes are easy to reproduce (leave it running!) but it's not obvious to me what's causing the glibc errors. I'm guessing that if we had a build with debugging symbols included we could perhaps do more; but I'm sure if there was something else we could do the likes of Dwarden et al would pipe up and say. There's a lot of folk waiting quietly to help. At the moment we're likely best off waiting for the next alpha which will hopefully come next week :)

I linked to a core dump on the CIT (Dev-Heaven) along with backtraces, gdb output etc. It was over 800 MB so uploading it to the forums or the CIT itself wasn't practical. I'm not sure how useful it is, but they have it anyway.

Thanks to Dwarden et al for this release, it's been eagerly awaited :) First impressions are that it is less prone to crashing than the previous alpha, which would reliably crash within minutes of starting a mission. 1.62.95946a on the other hand is stable enough to play on for tens of minutes, though I've only tested that with one person connected. It will still crash eventually however; but this isn't predictable or reliable (the best kind of crash!). What can I do to help? Upload 'core' files? I have .rpt and .bidmp files but they seem to be from the earlier alpha according to their dates. Thanks :)

I'm pleased to report the server launches successfully more often than not. It occasionally crashes on starting, watchdog restarts it and it then succeeds. So far I've tested with Escape Chernarus (1.8) (can't link as this is my first post) and while the mission loads, the server will reliably crash upon starting the mission. Eg: 19:06:05 Roles assigned. 19:06:05 Reading mission ... 112/07/09, 19:06:17 Warning: looped for animation: ca\anims\characters\data\anim\sdr\mov\erc\wlk\non\non\amovpercmwlksnonwnondf.rtm differs (looped now 0)! MoveName: amovpercmstpsnonwnondnon_amovpercmstpsraswpstdnon 112/07/09, 19:06:18 Warning: looped for animation: ca\anims\characters\data\anim\sdr\mov\erc\wlk\non\non\amovpercmwlksnonwnondf.rtm differs (looped now 1)! MoveName: amovpercmrunsnonwbindf_rfl 112/07/09, 19:06:19 SetFace error: class CfgFaces.CooperHead.FaceTanny not found 112/07/09, 19:06:19 Error: Error during SetFace - class CfgFaces.CooperHead.FaceTanny not found 112/07/09, 19:06:19 SetFace error: class CfgFaces.CooperHead.FaceTanny not found 112/07/09, 19:06:19 Error: Error during SetFace - class CfgFaces.CooperHead.FaceTanny not found 19:06:19 Mission read. 19:07:24 Game started. 112/07/09, 19:07:24 O 1-1-A: Cycle as first waypoint has no sense Global namespace not passed (script ) Global namespace not passed (script ) Global namespace not passed (script ) WATCHDOG (8121): [Thu Aug 9 19:07:34 BST 2012] Server died, waiting to restart... Is there a place that crash dumps are saved? At the moment some of the dumps seem to be dumped right to my terminal! Thanks in advance :)