Officermuffin

I am absolutely shocked this did not win. WLA is why I still play ARMA3. I have restarted the WLA mission on Altis, Chernarus, and Takistan countless times and not once did I care. The mission changes every time I choose to re-start and makes it all worth while. The constant updates and tweaking from the author show a huge amount of dedication and should have been rewarded.

I was running WLA at 57 FPS pretty consistently before the 1.40 update with a heavily modded game. I've lost 22-25 FPS after the 1.40 update and the latest SP WLA release. However, I have the frame drop whether or not I am running WLA and whether or not the mods are active. I am fairly certain that it has something to do with 1.40. Interestingly, I upped my graphics settings after the frame drop and have noticed that, although the settings are MUCH higher, the frame rate is the nearly the same 20-25 FPS. Unfortunately, that means 20-25 FPS consistently. It will not leave much room for an inevitable drop later on in the WLA mission as things heat up. I have not seen a bug report on the frame drop with 1.40 yet. I cannot get my head around why, since the changes in 1.40 don't seem too substantial on the surface.

Love the script Tophe. I've been using it for a bit and wanted to give thanks. Skål!

Thank you very much Tophe. I enjoy the script thoroughly.

Maybe the following will help you. You can lose the Simple Support Module now. 1. Place your unit. 2. Place an ACM module and a SOM module. Make sure they are NOT grouped to each other or to you. DO synchronise each of them to your unit. 3. Place the following text in the SOM Module initialization field. The text is in italics for clarity here. this setVariable ["settings",[["ambush","attack_location","trap","rescue","patrol","escort","defend_location","destroy","search"], true, ["Bravo 1-1", ["Bravo","one","one"], "Razor 2-1", ["Razor","two","one"]], 60, true, 30, 0.75, [500, 1000]]]; Notes on the previous text: You can remove some of the available missions("ambush","attack_location","trap","rescue","patrol","escort","defend_location","destroy","search") if they do not fit your mission setup. I like to get rid of the trap and search missions. The "true" after the missions represents that you wish to have radio chatter. I adjusted the callsigns to Bravo 1-1 and Razor 2-1 for fun. Obviously, not everything you enter for the callsign chatter will work. The "Bravo 1-1" is the text that will appear in the subtitles and the "Bravo","one","one" is the speech reference. The same goes for Razor 2-1 (formerly HQ). I am still working on finding a nice easy list of available speech. The 60 is the delay in seconds before the SecOps Manager attempts to task you out. The "true" after the 60 is the reference to reinforcements. If you lose a player in your squad the SOM will call you and offer reinforcement. You must accept the reinforcement via the communications menu. The 30 after the "true" is the amount of time in seconds that the SOM will wait before attempting to give you another mission after completion of the previous one. The 0.75 after the 30 is the percent chance that the SOM will offer that said mission after 30 seconds given completion of the previous one. The final numbers are the minimum and maximum ranges at which the SOM will offer missions. I have it set low in the example because I built the module for the example in the desert map. It seems to be only 2x2 kilometers. 4. Place a trigger. In the activation drop down select radio Alpha or another phonetic radio letter. Alpha is easy because tou can type 001 to quickly get the supports I will list below. Next to activation (to the right) select "repeatedly". In the TEXT field, call it SUPPORTS or whatever else you want. That will display on the radio LCD in the map screen. In the OnAct field place the following text. The text is in italics for clarity. [["artillery_barrage"], player, [[]]] call BIS_SOM_addSupportRequestFunc; [["transport","gunship_run","aerial_reconnaissance","supply_drop", "tactical_airstrike"], player] call BIS_SOM_addSupportRequestFunc; Notes on the previous text: The items in quotes, i.e. "artillery_barrage", "transport", and etcetera are the supports you will have access to. Like the SOM missions, you can remove some if you don't like them. If you remove the artillery barrage as in the above example, then you should remove the whole of the following: [["artillery_barrage"], player, [[]]] call BIS_SOM_addSupportRequestFunc; . I keep the artillery and other supports seperate because the artillery is customisable. I leave it as is so I have access to all of the artillery options. You can access all of the supports from one radio trigger (Alpha in this case), but you can also split them up into different triggers if you wish. Makes sense to keep them together in my opinion. 5. Save the beginnings of your mission as a "User Mission" and an "Export to single missions", then enjoy, I add a bit at a time to the missions until they suit me, but variations of the setup above can be quite fun. Typically I'll give myself a team of five to seven and then a vehicle or two in the event I don't want to use the support chopper. I almost always put the ambient civilians, ambient animals, and ambient civilian vehicles on the maps as well for ambience. If you want more enemies to fend off make sure to select that independents are friendly to OPFOR in the INTEL section of the main editor screen. It is there you can set weather, date, time, and etcetera. 6. To use the supports either click on the SUPPORTS text on the radio in the map screen or type 001 (Zero Zero One). It will show that the supports are now available in the top right. Then go to the communications menu via the spacebar and select "communication", then "request support". You'll figure out how to use all of the supports if you have not already done so. Have fun. :D