darksider282

F2k Sel your work around worked perfectly. Creating and then immediately deleting (randomly) the vehicle in question allows the !alive check to work, and the mission is now working and triggering perfectly. Thanks all!

First off, thanks all for the suggestions! Mondkalb, that suggestion seems like it could work if I could understand any of it. I'm really fairly new to trying to do some of the more sophisticated things with the editor. F2k sel, I'm looking for the vehicle to not be present due to two possible reasons: first, it has a random appearance rate so it might not spawn at all, and then second would be for it to be destroyed. Will checking distance cover that?

I'm trying to set a trigger with two conditions, namely that an empty vehicle is not present and that all opfor units are not present. I've got the basic trigger settings set to check for opfor, and I'm trying to add the other condition via the settriggeractivation code. This is what I have: this && trig1 setTriggerActivation ["VEHICLE", "NOT PRESENT", false] trig1 being the name of this particular trigger. I suspect that is where the problem is, because I get a message saying "Type any, expected bool" and I can't for the life of me figure out what the problem is. I've even done test triggers set for only one condition using this code and nothing from the menu settings and get the same message every time. Any help would be much appreciated.

We've played through some more missions and the sepia doesn't appear to want to go away. We'll probably just have to learn to live with it. It's really strange though, we can't be the only people who have ever tried to play coop campaign, and it seems like a setting one would have to go out of their way to turn on.

So our experience has been thus: we have this happen playing the default single player campaign cooperatively (operation harvest red). We've played through the intro section where you play as a chernurussian soldier, and then the briefing on the carrier and walking outside the carrier, but we've always stopped at this point. The sepia tone was consistent through this entire portion (again, the default, unmodified single player campaign). We tested a multiplayer deathmatch and there were no problems. This does suggest to me a problem with the mission, as you suggest above, but as this is the campaign that comes with the game... Also, as I said, if we play the campaign single player there is no problems.

We have two different copies of the game, both purchased through our STEAM accounts.

So my wife and I just got Arma 2 and have been looking forward to trying it out. We have the default game, patched up to date, through steam. Everything seems to work fine, including other multiplayer, until we try and play the campaign coop together. Whoever joins the game has some sort of sepia filter applied to the graphics: if she hosts and I join, I get the sepia and she is normal. But if I host and she joins, she gets the sepia and I am normal. On first loading/connecting it shows up normal for about a half second and then the sepia drops over the screen. We tried deathmatch and had no problem, and we can both play single player with no problem. It appears to just be when we join each other's coop games. Our hardware is good and drivers are up to date (see also: no problems in any other modes.) Any ideas? edit: when I say default game, I mean no addons, and no mods. Just Arma 2 fresh install.