Nielsen

(CIM) Civilian Interaction Module(s) By: Nielsen Updated to v.0.22 (Hotfix: More CRM Readme errors) DISCLAIMER: This is more of an addon than a mod. I use the 'module' designation because the addon adds new modules to the editor. Be adviced that the addon is released as a BETA, and as such I provide no guarantees of functionality or against adverse effects. This addon should work well in hosted MP environments but it might not be fully compatible with dedicated servers yet. The point of release is to get some feedback that might help improve the addon. Also, I would like to make it clear that I do not consider myself a skilled coder, and my approach is probably not the best one. Description: This addon adds three modules to the editor called the ‘(CIM) Civilian Interaction Module’, the '(CIM) Civilian Extraction Module' and the '(CIM) Civilian Reaction Module'. When placed on the map the 'Interaction Module' allows players to order civilians to the ground, inside houses or out of the area or vehicle in a second. Players can also search and key-cuff civilians or detain them. The 'Extraction Module' lets players extract detained civilians in a chopper via radio call, and also allows for smoke marked LZ. The 'Reaction Module' can generate different civilian events (for ambience) at will, or at predefined locations. It also has a feature that will add certain "evidence" items to random (un-searched) civilians around the players. How to use: Install the addon like you would any mod - using modfolders of course. For a quick setup, open the editor and hit 'F7'. Place the '(CIM) Civilian Interaction Module' on the map on a flat spot far away from the action. When in game hold the CIM-Key (default:left shift) and view available commands in the action menu. The 'Extraction-' and the 'Reaction Module' needs to be synchronized (F5) with the group leader(s). For a more detailed explanation of use and customizable setup see the included readme. Features: - Verbal commands for ordering civilians about - Physical actions for searching and subduing civilians - Helicopter extraction of detained civilians - Script to mark LZ's with smoke for pinpoint extractions. - Spawning of ambient civilian events - Makes random civilians have "evidence" - Custom sounds - Global arrays and customizable parameters for mission maker convenience - Works with ALICE - works with surrendered units (thank you stupidwhitekid75 for pointing this out to me) - Works with ACE2, Reezo's EOD mod, and nearly any other mod - SP and MP compatible (not working on dedicated yet) Requirements: - Arma 2 CO - CBA Known issues: - Because of hardcoded limitations, female civilians will not display animation when key-cuffed. However, they will still be completely passive. - Because the action menu cannot be used while holding 'left ctrl' it is not suitable as CIM-Key. - Smoke in the CRM "gathering" event does not work on clients yet. (No idea why. And I do know that it is a local effect) - The 'Reaction module' currently requires that the 'Interaction module' is also present. Credits: • Reezo – for his epic EOD-mod which inspired this module. • SHK – for providing his SHK_Pos function (used in CIM) and for being very helpful on the forums. • JohnnyDust – for helping out with testing and suggestions, and for covering my six. • Clements, Sickem and Inspired Media - For recording and editing of videos/tutorials (thanks guys). • Pellejones and SSG (www.ssg-clan.se) – for testing and advice on dedicated servers. • Ruebe – for taking time to help out on the forums. • LAxemann, Feint, YayForLife, UGLY58, Zwobot, Clements, Raptor 6 Actual – for reporting bugs. • Sickboy - for creating CBA • Armaholic.com – for hosting my (and all other) mod(s). • BIS, ACE2 team and the community – for making this game timeless and priceless. License and copyright: People are free to change this to their needs. If you are planning on changing this addon and releasing it as your own, I request that you contact me first, and of course that you credit me where it is appropriate. In the end, as long as I get credit for my work, you can pretty much do whatever you want with it. Changelog: Download: Beta v. 0.22: https://rapidshare.com/files/1400329955/Nielsen_CIM.rar I hope you enjoy and have fun trying this out. Let me know what you think. Kind regards, Nielsen

This^^

I'm no wizard at this, but I think it is down to the fact that in a (true) racing sim you can move your car as well as your head, combined with the fact that cars have a lot of components that make them move differently, ie. brakes, aero, suspension etc. I play racing sims (mostly rFactor), and I've noticed that here you (read: they) talk about a lot more DoF than in FPS games.

Thanks! I think I know what is causing this, and that I might have allready fixed it. I'll release a new version soon, and hope that will be fixed as well.

Thanks. Glad you are finding use of it :) Hmm. So they do have the wounded texture, but they stand still and do not perform any animations - they just stand totally still? Could you provide me with the .rpt file after reproducing this bug? Then I can take a look. (if you dont know where the file is look further above in the post :) ).

Sure thing :)

Awesome news!!! Thanks BIS. Loving that changelog! Merry christmas

Allright. So, now I am back in business, with a little more time on my hands than the previous week... @Kremator: Yeah I see. I realize the benefit of this, but it is pretty much a choice between two evils. At least for now, you will have to unpbo the missions and add the modules yourself. @SmokeDog: Thanks. I'd like to check out that sample. I'll throw you a pm about it. @Raptor 6 Actual: Thanks for helping out! @SideKilla09: Just to clarify what Raptor 6 said. The only 'setVariable' that is actually required is the variable 'nielsen_crm_locations'. It has no standard value, to make you remember that you need locations for the events. Actually you do not have to put down any markers, but you do have to indicate to the module how many (if any) has been placed. If you wish to place no markers, and just handle/call the events with e.g. triggers, then you should just place the following in the init of the cRm module: You can still spawn any event on any position with the following code: "EventType" = String with the wanted event type (e.g. "Random"). position = An array with a position (e.g. getPos Trigger1). multiplier = The multiplier of number of spawned civs. This variable is optional and does not have to be there. (e.g. 0.8 = 20% less than normal, 1.5 = 50% more civs than normal). Also, Raptor 6 i correct. Right now the cIm module is required to make it all work. This will be fixed for the next update. Cheers

@Kremator: Not totally sure if I understand you correctly. You need to put down the modules (in editor) for them to work of course. CIM wont work in missions without the modules. But the 'Reaction Module' features will work without sync if you call them by command: The sync is only needed to check if players are close to "event markers". If you want a specific event on a specific location you can use the above command to call it from, say, a trigger. EDIT: I could of course make the addon without modules so it just works "out of the box", but that would drain computer ressources, and force people to turn the CIM on/off depending on the mission they want to play. That's why I went with the module approach, so I can have the addon loaded as standard without worrying about ressources.

The 'Interaction Module' does not have to be synced. Just put in down in the editor. The 'Extraction' module only has to be synced with one unit - to indicate player side. The 'Reaction' module needs to be synced with group leaders of any and all groups that should trigger civilian events. Only the group leader though. It requires clients to have the addon installed. (I will consider making a script version when the addon is closer to completion).

LoL.. x2 This is straight awesome... Guess I will have to start learning Java too.

@SmokeDog: Thanks dude. Appreciate it. Let it be know that your Sangin/hells Kitchen map is currently my favorite map. Everyone should make sure to try it out. (btw: Your screenshots are in the making I am told). Regarding your ideas: 1 & 5: Those are cool ideas. It would be another level of ambience. I'll think about how it can be implemented. It will probably take some time before I can implement it though. 2 & 3: I actually just implemented those last night. I have replaced the "evidence" feature, with a new feature that (re-)configures the ALICE module to make civs more varied. (i.e. they dont all carry maps and radios). With this, all ALICE civs will have a custom chance of being armed - though not hostile - and a chance to carry "evidence" items or explosives. 4: I like this idea, and as I have already made the FSM for the "massacre" feature, it is very feasible. But that would require a 'killed' eventhandler on ALL civilians. I'm not sure if that would result in a noticable performance hit, but I dont think it will be a problem. It should not be complicated to implement. I will give it some thought. @psvialli: I agree that would be a cool feature. It has ben tempting to make suicide bombers and VBIEDs, as they are obvious civilian-like hazards. But I need to limit the scope of the addon, and I do not want to encroach on the territory of other mods, that do these features much better. For now, I will leave the exploding parts to the EOD/IED mods out there.

@clements: Sweet! You guys rock. Looking forward to the game play footage! @yanhchan: Thanks man! I was'nt sure if people would like the concept of the 'Reaction module'. I just felt it would be usefull as quick ambience when making missions. Regarding a template. clements video above should help. I am a little worried that with a mission template people wont bother to read through the readme (who reads a manual if they can help it?), and they will end up having problems with it. But I know how concrete mission examples can be much more intuitive than commands in a readme. I'll make sure to do a quick template. On a general note I have realized that the CRM currently requires CIM to also be present. Otherwise some events wont work (see Raptor 6 above). I will fix this for the next update. Until then the CRM should not be run without the CIM.

The gathering thing is already planned :).. I gave some of them weapons without turning them hostile to give some tension. I figured it is a shame to have that weapons=kill all the time. It could be cool with a bit more strict ROE to create suspense. I plan on evolving the .FSM file for "gathering behaviour" to include a chance of weaponbearers turning hostile. That wont be hard at all. I will make sure it makes it into the next update. Regarding shooting around the crowd that is a bit more difficult (at least to me). I've allready experimented with it, to get civilians to flee to safety if you fire your gun. I thought it would be a cool way of dispersing the crowd in a pinch. But the "firednear" eventhandler that I used was really unreliable and did more harm than good imo. If I figure out how to make this work reliably I will make sure to make good use of it. ;) Regarding sending people back in their vehicles: Yes of course. Not sure why I have not done this already. Especially since the 'get out' command excludes them from reentering vehicles (else ALICE civs would get right back in and step on it). And since I've currently only got one command for vehicles it wont even clutter up the action menu. I'll make sure this i featured asap. Let me know if you get more ideas.

That's no bother at all! I really appreciate the feedback. Thats doing me a favour man. Please do report any bugs you find, and I will try to solve them. Regarding the ones you just posted: You are right about the female civs. They cannot go prone, and they cannot use male animations (keycuffs). Nothing I can do about it afaik. Gathering: Not sure about this one. I will look into it. I'm glad the stuff spawns at least. I'll check it out. Ambush & Intel: Well spoted. I think I know whats causing this. Earlier I corrected a (potential game-crashing) bug that related to houses not having path LODs. I think that a related issue is causing these errors too. That is why the problem shows up on Utes but not on Takistan. That should be an easy fix I think. I'll look into it asap. Massacre: None of those are CIM errors. Most of them are about ACE and CBA. The ones that do relate to the addon are not errors but just debug messages. Because the addon is still in beta it has a "debug-mode" enabled by default. This will throw diag_log to your .rpt telling you what's going on. (I check it continously while testing to make sure stuff has been spawned and such). ETA on update: I am extremely busy irl this week, so I cannot say for sure when I have time to fix this. Besides work it is my main priority though, so it should not take too long. Thanks a bunch for a detailed bug-report. Posting the settings and .rpt obviously makes it a lot easier to track down issues :). Regards, EDIT: Certainly. I plan on adding more events. All I need is time and ideas. Of course as long as there are bugs they will be my main priority, but I'm deff. going to add more stuff. If you've got some (more or less) feasible ideas I'd love to hear them. :)

Thanks for the feedback man. As long as you did not have problems with it, a "worked perfectly" is great feedback. That makes me less uneasy about the functionality, and lets me know that someone finds it interesting and/or usefull. If you encounter problems, or have ideas/wishes for further updates, dont hesitate to tell me. :)

0.22 is out with a readme that will actually let you use the new modules. I must confess that there were two more errors in the readme :o (Thanks goes to LAxemann for telling me about them). The OP has been updated to 0.22, which should have correct information on the CRM module in the readme. Sorry for the tripple update in a day. I try to save up the updates so the changelog actually has several entries, but alas, this false information in the readme was a "module-breaker". I think it is straightened out now though. :)

Looks great! Will check this out asap. Thanks for the efforts!

Thanks Foxhound! I just released a small hotfix update (v. 0.21). The command I wrote in the readme for setting the number of markers was wrong. Of course that would make the whole module break, so I would not suffice with stating the error in a post. That's why I've thrown up such a small update. The correct command for setting number of markers is:

New version 0.2 out! Updated the first post. As time irl is getting more sparse these next weeks, I thought I might as well release where I'm at with the addon right now. Some important bugfixes, and the addition of some new features are in this release. The new 'Reaction Module' still only has 4 types of events, and they prolly need some tweaking. I'll look into that when I have time. There has been some changes. Make sure to read the readme.pdf for instructions on how to use the new modules. And please let me know what you think :)

I just remembered. There are some general problem with resyncing on respawn. AFAIK the sync has to be done within the first .5 seconds of the mission, so the command is really useless. At least for modules like the SecOps manager. Check out this thread: http://forums.bistudio.com/showthread.php?t=81331

:bigglasses:

That is correct... However - to tell you a secret - the next update will take care of that too ;) Right now the "physical actions" are mostly usefull in conjunction with mission setups or Reezos EOD mod (to haul off triggermen).

Yes its the variable in the name line in the editor. But actually you can just use 'player' as that will return the local player/unit name. the eventhandler is local (afaik) so it will only fire for the local unit. I should have used that in the example, sorry. Assuming you dont mess around with dedicated servers, do the following. Put a module and name it myModule. Put the following in your init.sqf, or in any init field. player addeventhandler ["respawn","_this execvm '\respawnScript.sqf'"]; In the respawnScript.sqf, put: myModule synchronizeObjectsAdd [player]; That should do it I would think...

I'm glad others are getting some fun out of this too :) Yeah, my buddy is all into the russian stuff, so I cant really turn my back on that. But I will deff. look into making the chopper classname a variable. But I gotta put some work into that one, cause right now I spawn crew into specific positions and stuff, so gotta think about it. Hmm. Not sure about that one. That action still only "doGetOut" and "AllowGetIn = false", with a "doStop" for good measure. Not sure if the allowgetin makes them act weird, but that needs to be there. I've taken the doStop out for the next version, that might help. I'll prolly do an .fsm for it at some point. If you guys test it out on (relatively) big scale, I'd appreciate a word on bugs, but also if you had a smooth ride, so I know that it's moving in the right direction. :) EDIT: I'm getting tired. I thought I fixed the sound problem but I overlooked something. I'll look into it though!