Victim ZSU

Thanks for the updates, and the tip on spawning the right radio. We're all still coming to terms with how good this add-on is and how much it significantly improves our experience.

(taking the bait) Batteries? Really? I can understand it for the laser designators which have a very short battery life. But how long are you expecting to be in the field? if a typical mission is 2-4 hours, how many times are you expecting to change batteries? once? a dozen times? While that might tick all the boxes for the sim-core among us, battery management just to be able to speak to a team member is a bit much... ---------- Post added at 12:19 PM ---------- Previous post was at 12:15 PM ---------- Agreed, particularly if they are game changing, like adding Javelins, but this is a functionality change which means ACRE is half-implemented on non-native missions. Agreed also, it is straight forward to un-pbo, add it in and re-package it, was just hoping for something a bit more streamlined - seeing as I see this as an ACRE functionality issue rather than an unbalancing / mission content issue. Yes, 5W on the 148 improves things significantly, guess I'm just unreasonably griping at the loss of radios from the vehicles :) Anyhow, I've whipped up a small client-side add-on which gives all group leaders the option to spawn a LR radio on the ground in front of them. Problem solved...

Quick question, Many downloaded or pre-canned missions don't bother to include radios in the gear crates by default. Which means without opening, adding and re-packaging we can't enjoy LR radios in these types of missions. Would it be possible to work out a way of automatically adding either the AN/PRC-117F or the AN/PRC-119 to the gear compartment of any unlocked vehicles? in the same way the PRC-148 gets swapped out on any players?

Big Dawg KS / Cougs - are you ok if we use this in our mission framework? it is currently a closed framework, but we do track all attributions, just in case.

Was this on a dedicated server? When we tried it the other week on our dedicated server, we had civilians flickering on the rooftops and appearing / disappearing. The mission tested fine in Player hosted server.

Is the (expansion) version still bugged on a dedicated server?

I've got the opposite request. I want to place launched scuds (as in empty) in my mission. I'm guessing if I can set the right anim?

I have this issue. That link 404s Is this the beta patch? or the official 1.52 patch?

Thanks I'll give it a go... As an aside, I already know that there's a way to prevent cinematics on the main menu when you first start ArmA 2, but what about on subsequent returns to the main menu after playing / editing?

Because I know this community has a sense of humour...

I've always had it, occasional hang at a grey screen on exit - only fixable with ctrl-alt-delete -> task manager -> ArmA2.exe -> end task button. While it is only a little thing it is damn annoying.

All sorted, one of the files failed an MD5 hash check, so re-downloaded it.

FMD, piss on his idea why don't you. I personally think this is a cracking idea and have a similar thing that works by filtering the weapon displaynames using CBA string functions rather than updating classes. e.g.: M4A1 RCO M4A1 RCO M4A1 RCO SD M4A1 RCO SD M4A1 M203 CCO M4A1 M203 CCO SD M4A1 CCO SD M4A1 Holo M4A1 M203 M4A1 M203 SD M4A1 M203 RCO M4A1 M203 RCO M4A1 M203 RCO M4A1 M203 RCO All start with M4A1 - which means working out the variants and removing duplicates is just a set of string functions. In addition, you can exclude the ACE _CQB variants for those weapons which have them. It uses the dialog from Kronsky's weapon selector as a base, so it even gives you a picture preview of the weapon you are switching to. Will have a look at your scripts.

I did an online chat with sprocketidea support, of all things they suggested upgrading my audio drivers. He gave me a link to an AC97 driver which allegedly contributes to the installer crash as the installer plays a soundfile on startup immediately after extraction. Weird thing is I'm running a Creative Labs XiFi setup and the drivers are current. Still no dice...

Well ain't that just dandy, I'm trying to do the install myself on a new rig and I'm getting this error under Windows 7 x64. I know it was a while back, but did you get a resolution?

Just gave it a go and found it quite challenging, we'll be playing it again for sure.