Fadi

Great work so far. The area has a very good balance of vegetation, height and open areas that should allow for a varied missions.

http://feedback.arma3.com/view.php?id=11943 as well.

Nope, it's not that his ALICE isn't configured correctly it's that that map is missing the defined city centers and neighborhoods needed for it. A bit more info here: http://forums.bistudio.com/showthread.php?94741-ALICE-not-spawning-civilians&p=1603763&viewfull=1#post1603763 Running a crb_locations test with ALICE debug on SMD vs. CAA1 with the patch in the above post... SMD: http://dl.dropboxusercontent.com/u/14592975/arma2oa%202013-11-09%2007-13-11-02.png CAA1: http://dl.dropboxusercontent.com/u/14592975/arma2oa%202013-11-09%2007-08-39-26.png With ALICE's debug on, the flags represent city centers that will spawn units and the circle the radius to activate that location. The colors and (0/0) aren't particularily important since it doesn't cache locations that haven't been activated at least once. The lines between towns show connected neighbors. The blue text shows the city center locations, although all of them in the example aren't used. There are more location types that aren't defined that would also help with certain types of missions.

It is. Here: https://dl.dropboxusercontent.com/u/14592975/arma2/vilas_aks_cfg.pboLEA's class generation works best extracting/analyzing from a pbo with config.bin inside it. More or less all I did was depbo the config file and repbo/binarize it with BinPBO. Make sure both that and vilas_aks.pbo are in the same folder... choose that folder as the source to extract/analyze with LEA and you're good to go. There should be a few items that don't have pictures because it doesn't associate them with default Arma pictures. All of those can be found in the LEA program folder under ...\LEA\resources\pictures\

Apparently this can also be done on the Marshall with the gunner/commander, the commander of the Marid, the commander the the M2A1, the commander of the Gorgon and all three MRAPs. I haven't tried any other vehicle.

Looks fantastic. Thank you and congratulations to all of you who contributed.

Alternatively have a set of modules that apply the patches by sync'd unit, group or side and leave it up to the mission makers.

I have had CTD issues as well. It's not very consistent however when it happens it tends to create a deadzone where any other players that enter that area will crash. Previously, the issue stopped coming up when the beta patch was run on the server but not the clients. With the CBA changes though that's no longer an option. Edit: Nevermind, I resolved my issue. Since I redid my servers .bat file I've been launching the wrong arma2oaserver.exe

Looks nice so far. What sort of size are you going for with the city?

Argument, that looks very nice. Keep up the good work.

Make sure INDFOR is set to not be friendly with OPFOR. By default, it's set so INDFOR and OPFOR will not attack one another. One could probably also add CDF to the enemies that will populate the map... In the files for the CAS and logistics module, you can also redefine what vehicles are used... you don't have to disable them.

https://dev-heaven.net/projects/mso/repository/revisions/f8de06237053f990b206c387d51c2d138b040a1f https://dev-heaven.net/projects/mso/repository/revisions/2bd7c066c46ae524a37694136598f8ebdbb49284 Those should be a good reference point to what you would need to change to add a new faction. You will have to know the faction and group class names for the FFAA terrorist units.

If you want to edit the weapons.yml in the support\modules\MGO folder, I have a few weapons done for a CDF version I've done. Here: AK74M_SET: ACE_AK74M: Iron Sights ACE_AK74M_1P29: 1P29-1 (UPO-1) ACE_AK74M_1P78: 1P78-1 ACE_AK74M_Kobra: Kobra (1S-03) ACE_AK74M_NSPU: NSPU-3 (1PN51) ACE_AK74M_PSO: PSO-1M2 ACE_AK74M_TWS: Goshawk AK74MFL_SET: ACE_AK74M_FL: Iron Sights ACE_AK74M_1P78_FL: 1P78-1 ACE_AK74M_Kobra_FL: Kobra (1S-03) ACE_AK74M_NSPU_FL: NSPU-3 (1PN51) ACE_AK74M_PSO_FL: PSO-1M2 ACE_AK74M_TWS_FL: Goshawk AK74MFLF_SET: ACE_AK74M_FL_F: Iron Sights ACE_AK74M_1P78_FL_F: 1P78-1 ACE_AK74M_Kobra_FL_F: Kobra (1S-03) ACE_AK74M_NSPU_FL_F: NSPU-3 (1PN51) ACE_AK74M_PSO_FL_F: PSO-1M2 ACE_AK74M_TWS_FL_F: Goshawk AK74MSD_SET: ACE_AK74M_SD: Iron Sights ACE_AK74M_SD_1P78: 1P78-1 ACE_AK74M_SD_Kobra: Kobra (1S-03) ACE_AK74M_SD_NSPU: NSPU-3 (1PN51) ACE_AK74M_SD_PSO: PSO-1M2 ACE_AK74M_SD_TWS: Goshawk AK74MSDF_SET: ACE_AK74M_SD_F: Iron Sights ACE_AK74M_SD_1P78_F: 1P78-1 ACE_AK74M_SD_Kobra_F: Kobra (1S-03) ACE_AK74M_SD_NSPU_F: NSPU-3 (1PN51) ACE_AK74M_SD_PSO_F: PSO-1M2 ACE_AK74M_SD_TWS_F: Goshawk GROZA762_SET: ACE_gr1: Iron Sights ACE_gr1sp: PSO-1M1 ACE_gr1sd: SD ACE_gr1sdsp: SD PSO GROZA9_SET: ACE_oc14: Iron Sights ACE_oc14sp: PSO-1M1 ACE_oc14gl: GP-30 ACE_oc14glsp: GP-30 PSO-1M1 ACE_oc14sd: SD ACE_oc14sdsp: SD PSO RPK74M_SET: ACE_RPK74M: Iron Sights ACE_RPK74M_1P29: 1P29-1 (UPO-1) MAKAROV_SET: Makarov: Standard MakarovSD: Silencer AK74_SET: AK-74: Iron Sights AK_74_GL: GP-25 AK_74_GL_kobra: GP-25 Kobra AKS74_SET: AKS_74: Iron Sights ACE_AKS74_GP25: GP-25 AKS_74_kobra: Kobra (1S-03) AKS_74_NSPU: NSPU-1 AKS_74_pso: PSO-1 AKS_74_GOSHAWK: Goshawk AKS74U_SET: AKS_74_U: Iron Sights ACE_AKS74_UN: SD AKS_74_UN_kobra: SD Kobra ASVAL_SET: ACE_Val: Iron Sights ACE_Val_Kobra: Kobra ACE_Val_PSO: PSO AKM_SET: ACE_AKM: Iron Sights ACE_AKM_GL: GP-25 AKMS_SET: ACE_AKMS: Iron Sights ACE_AKMS_SD: SD AKS_GOLD: Gold AKS74P_SET: ACE_AKS74P: Iron Sights ACE_AKS74P_Kobra: Kobra ACE_AKS74P_PSO: PSO-1 ACE_AKS74P_GL: GP-30 ACE_AKS74P_GL_1P29: GP-30 1P29-1 ACE_AKS74P_GL_Kobra: GP-30 Kobra ACE_AKS74P_GL_PSO: GP-30 PSO-1 Also the CDF version I'm running if anyone wants it... It does require ACE: https://dl.dropbox.com/u/14592975/arma2/CO51_MSO_ACEX_CDF_vs_TAK.takistan.pbo FOB by Koalasalad, used from here: http://www.armaholic.com/page.php?id=13865

That's one fine vehicle, great job. I also think a UN version would be good, they look quite nice [source] painted white.

Ah, that works for stock missions. Thanks. I'm having issues with edited missions though... Even making small changes they hang at a certain point loading depending on what modules are active; "Initialising: DRN weather" and if I disable that "Initialising: Ambient civilians" and if I disable ambient civs "Initialising: R3f logistics", etc.

Great work to the MSO team and those who have contributed. That said, I'm having some issues that I haven't experienced with 4.4 and 4.5rc3 on both stock and edited missions. When 4.5 was released I changed Arma2Net to the version linked on MSO's wiki on Dev-Heaven and I've dropped my old tables and imported the new schema. The missions loads initializes fine with NOMAD however using PDB it hangs at "Please wait setting up client". There's a ping in the background as though PDB set up a row for a new table and in the RPTs for both client host everything moves along as it normally should. It will take 15 minutes or so before though there are any logs generated by either Arma2Net or Arma2MySQL and when they start rolling in they look like: Arma2NetMySQL: https://dl.dropbox.com/u/14592975/arma2/New%20folder/11-19-2012_00-54-55.log Arma2Net: https://dl.dropbox.com/u/14592975/arma2/New%20folder/Arma2NET.log Would this be an MSO issue? Or should I report this somewhere else.

I've got it up on my test server running alongside MSO and it looks good so far. I'll definitely be keeping track on how this progresses. One error I've encountered so far... On death/respawn this comes up: Warning Message: Script gbl_advanced_interaction\scripts\interaction\modules.sqf not found

Very nice work with the police units.

I've been working on a version of Zargabad Insurgency using Vilas' Project '85 units and came across an easy work around while searching this board. I'm not sure what thread I found it in though. Essentially you can group units to the faction you want them to appear as (ex. OPFOR tethered to BLUFOR), set that units rank higher so they'll take command and set them to be unplayable with 0% probability of presence.