Jump to content
Bohemia Interactive Forums

kirkherbstreit

Member
 View Profile  See their activity

  • Content Count

    20

  • Joined

  • Last visited

  • Medals

Posts posted by kirkherbstreit

  1. Posted · Edited by kirkherbstreit

    Second question now that everything seems to be working: What is the proper script for erasing ALL OPFOR's knowsAbout levels with regards to the player?

    I'm a little stumped here. The natural solution is something like [opfor units] reveal [player, 0.0]; However, my OPFOR units are all randomly spawning using ACM. Basically what I'm trying to create is a circular area that says "If no OPFOR are present, then all OPFOR on the map have 0 knowledge of player." Hard to reference every OPFOR on the map when they're constantly changing.

    This was the closest I got:

    Created a circular trigger area radius 5, slaved to the player. Activation is OPFOR not present.

    Condition: time == time and {side _x == east} count thislist > 0

    On Act.: detected = false; hint = "Hidden";

    However as soon as OPFOR were present in the trigger area, it activated! Exactly the opposite of the Activation requirement!

  2. Posted

    Rather than search the whole map could you use a smaller trigger attached to the player so there would be less units to check.

    ...

    Unfortunately there is no way to reduce what another unit knows about another apart from time.

    It's a real pain when doing a stealth mission also there is a bug with dead bodies, they can be seen through objects and the enemy will become alert to you.

    Maybe a small, 1-2 meter bubble around the player that checks detection? It would artificially solve the trigger problems and the whole remaining stealthy issue.

  3. Posted

    Here's what I'm working on: On any map, the player starts as a single BLUFOR unit with setcaptive true. When the OPFOR's knowsAbout level on the player is 0, the player is "hidden." However, when knowsAbout increases to any number other than zero, the player is "detected." The player can run around and do anything without the OPFOR shooting at the player, regardless of being detected or hidden. However, if the player commits any hostile act against an OPFOR while detected, the player's setcaptive becomes false and OPFOR are free to shoot. If the player can successfully evade and become undetected, the player becomes "nefarious," basically meaning the player's setcaptive is still false and OPFOR are actively hunting him, and will shoot on sight, forcing player to remain undetected. After a given amount of time, the OPFOR stop searching for the player who will become anonymous once again. Think Assassin's Creed ;).

    Anyway, I've got it going pretty well so far, and I need help fine-tuning things now because the scripting is getting more challenging. The setup is basically this:

    Player init field: player setcaptive true; detected = false; nefarious = false;

    First trigger (called 'hidden') (size covers entire map):

    Activation: OPFOR Present, repeating

    Condition: round (time %1) == 1 and {_x knowsabout player == 0} count thislist > 0

    On Act.: detected = false; hintSilent "Hidden";

    //This is the default setting, as I've been testing in a blank map with player spawning behind 2 OPFOR looking the opposite direction. Everything works fine with this part so far. How does the condition field look? Could it function better with a different script?

    Second trigger (called 'detected') (size covers entire map):

    Activation: OPFOR Present, repeating

    Condition: round (time %1) == 1 and {_x knowsabout player > 0} count thislist > 0 and rating player == 0 //important that player's rating is 0; indicates no hostile act has been committed

    On Act.: detected = true; hint "Detected"; //global variable 'detected' prevents me having to constantly re-use the bulky knowsabout script ;) and also creates a constant dinging noise so player knows he's detected :D

    //This trigger works alright. It activates as player is within visual sight of any OPFOR, dinging noise commences. A problem here is when I try to get out of visual distance, I remain detected. Not sure, either the trigger is just constantly activating or the AI just has unreasonable detection ranges (I try hiding behind mountains and buildings, nothing works). Any way I can fix this/ make it better?

    Third trigger (called 'hunted') (Size irrelevant):

    Activation: none, repeating

    Condition: detected and rating player > 0

    On Act.: player setcaptive false; hint "Hunted";

    //This one works fine.

    Fourth trigger (called 'notorious') (Size irrelevant):

    Activation: none, repeating

    Condition: !detected and !captive player

    On Act.: nefarious = true; hintSilent "Notorious";

    //This is merely an indication to the player that he's no longer detected, however...since I can't escape detection (see my notes for 'detected' trigger) I can't verify if it works or not. Not really a huge problem if this doesn't exist, but it will help the player a little bit.

    Fifth trigger (called 'anonymous') (Size irrelevant):

    Activation: none, repeating, 120 second countdown

    Condition: !detected and nefarious

    On Act.: player setcaptive true; nefarious = false; hintSilent "Hidden"; player addrating -abs(rating player);

    //Resets player rating to 0 because player is now officially 'anonymous' again. As before, I can't verify if this works because of the detection problem.

    Sixth trigger (last one, I promise :P) (called 'successful kill') (Size irrelevant):

    Activation: none, repeating

    Condition: !detected and rating player > 0

    On Act.: player addrating (-abs(rating player)); hint "Successful Kill";

    //Simulates killing an OPFOR while anonymous, player rating remains 0 allowing player to remain hidden

    That's what I've got. I suppose my main issue at this point is the detection logic. Does anyone know a better way to exploit this for my purposes? Thanks for any help in advance!

  5. Posted

    So lately I've been having a ton of fun knocking around in single player with some really simple yet really fun missions that I've created. Thought I'd share my method with anyone who's looking for simple yet fun missions to play solo.

    For example I've been playing a lot on the Takistan map. I'm simple a 5-man unit of US Army SF operators. I operate out of the empty base near Rasman which I've complemented with H blocks, gates, and sentry towers with a few infantry units acting as gate guards. Now I get creative with Ambient Combat module, placing one with a wide area around the base synched to one of my nonplayable gate guards that only spawns US Army units that are constantly moving/flying around the base and Rasman (http://community.bistudio.com/wiki/Ambient_Combat_Manager for tips/options). Feels and looks a lot like Bagram Air Base (which I was at for a month, haha).

    Next comes more ACMs which I've located in the various villages and towns around Takistan. Each of these ACMs are synched to triggers in each individual town. The triggers are operated by the presence of a civilian Takistani that I've placed in each town (http://community.bistudio.com/wiki/trigger#Activation). So long as the civilian is within the trigger radius (default, 50 meters) the ACM that is synched to that trigger will constantly spawn only Takistani insurgent units in the town and the immediate vicinity (http://community.bistudio.com/wiki/Ambient_Combat_Manager#Configuration). Once the civilian is removed (either via force or death) that particular ACM is deactivated (http://community.bistudio.com/wiki/trigger#On_Dea.28ctivation.29).

    The only things I use are ACE2 and the Civilian Interaction Module/Civilian Reaction Module made by Nielsen (http://www.armaholic.com/page.php?id=15664). Highly recommended as it adds a unique layer of depth to these missions and is easy to use. That and he Ambient Civilians/Ambient Civilian Vehicles modules add an ROE element to each mission that can sometimes be challenging, plus it adds some cool random events and lets me take down my civilian target nonlethally if I need to! I'm also using the SecOps module for the easy air support/artillery/transport options, with the default helo switched to a CH-47 (http://community.bistudio.com/wiki/Secondary_Operations_Manager#Quickstart and http://community.bistudio.com/wiki/Secondary_Operations_Manager#Replacing_the_Default_Vehicles for how-to's).

    All of this, no joke, can be done with some of the simplest scripting imaginable. Just read those links carefully and you can get to making missions like these, too. Of course it's very sandbox-style, so no directives or objectives unless you want to make those yourself. Honestly each time you load and play is different.

    So what do you think? Suggestions to make it more immersive? Improvements? Hopefully this will bring as much enjoyment to some of you as it has to me. Thanks for your time.

  6. Posted

    Hope I'm not out of line bumping up this thread, but I'm stuck.

    I used the tool perfectly one time for a test run, but I've been working on another mission of Russia (player) vs CDF (AI). I set up everything the exact same way but NO units spawn anywhere even though I've scattered bases all over the map. Also, I never see the dialog box in the upper right stating the total number of groups. Did everything according to the video, and nothing is happening. Is it because I'm trying to play as OPFOR?

    Second question: is there a way to raise the air drop altitudes? Everybody dies during the initial drop because the chutes don't have time to deploy.

  7. Posted

    Couldn't find anything about this problem, as it seems fairly unique...

    I'm using the WICT tool and one of the weird things it does it change the ambient time, as in the speed that the clock moves, the clouds, sun, etc. However it doesn't change the actual game speed, so movement/ballistics/etc. remain at normal speed. I wanted to make the ambient, environmental time go to normal instead of at light speed because that's REALLY annoying. I tried SetAccTime = 0.1 and it slowed the ambient time back to normal, however it reduced the game speed as well.

    What if anything can I change to make the ambient time go at normal pace without affecting the game speed? Anyone familiar with WICT knows what I'm talking about?

  9. Posted

    I just read in the editing wiki that radio triggers never have a deactivation field. I have one radio trigger - it begins a countdown, then sets the Ambient Combat Manager settings to highest intensity with my preselected spawn groups, basically just turning ACM "on" - and I thought I could put a script in the "on deactivation" field for the same trigger that simply set all ACM settings to zero, basically turning ACM "Off" so I could do other things. But now that I know that won't work, I tried a second radio trigger that switched all ACM settings off when I activated it. However, this led to an error message during gameplay; I think it had something to do with ACM trying to force-spawn groups when the spawn frequency and intensity were both zero. So I ask, can I trick the editor into switching off a previous radio trigger?

  11. Posted

    "The random minimizing issue"? Never heard of this. Also, it doesn't sound like it's game related, since the game doesn't generally minimize itself.

    Games can be minimized by other Windows programs that are trying to get your attention though. I've experienced it, for example, when people sent me messages over certain IM programs like Google Talk.

    So you might want to look for a program that could be doing this. Try shutting down all applications you're not using before running the game and see if the problem persists.

    https://www.google.com/search?q=arma+2+minimizes&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a

    Seems to be a fairly common bug that many are reporting. No processes are running in the background. Also, I took the liberty of installing CPUID to see if maybe my video card was overheating, and my max temp on the card was 73 C, so it's definitely not a heat issue.

  16. Posted

    There doesn't seem to be a topic regarding this anywhere...

    Below is my script that I tried in ACM once today. So far the module has been pretty good at spawning a lot of units that I didn't ask for in the script, as far as I can see. There have been many BMP-3s, Helicopters, Su-25s, and such. However there have also been several units that I did ask for. I don't know why the other units are spawning too, as air patrols are set to 0. 

    waitUntil {!isNil {BIS_ACM getVariable "initDone"}};  
waitUntil {BIS_ACM getVariable "initDone"};  
sleep 5;    
[1, BIS_ACM] call BIS_ACM_setIntensityFunc;  
[bIS_ACM, 500, 1200] call BIS_ACM_setSpawnDistanceFunc;  
[["BIS_US", "BIS_CZ", "BIS_GER", "BIS_UN", "BIS_TK_INS"], BIS_ACM] call BIS_ACM_setFactionsFunc;  
[0.1, 0.5, BIS_ACM] call BIS_ACM_setSkillFunc;  
[0.55, 0.85, BIS_ACM] call BIS_ACM_setAmmoFunc;  
["ground_patrol", 1, BIS_ACM] call BIS_ACM_setTypeChanceFunc;  
["air_patrol", 0, BIS_ACM] call BIS_ACM_setTypeChanceFunc;  
[bIS_ACM, ["US_RifleSquad", "US_WeaponsSquad", "US_TeamMG", "US_MotorizedSection", "US_DeltaPatrolHMMWV", "ACR_InfantryPatrol", "ACR_SpecialForcesPatrolLandRover", "KSKTeam", "TK_INS_Group", "TK_INS_Patrol", "TK_INS_Technicals", "TK_INS_MotorizedGroup", "UN_Patrol", "UN_MotorizedPatrol", "UN_MechanizedPatrolM113"]] call BIS_ACM_addGroupClassesFunc;

    Are my units wrong?

  17. Posted

    Tried with build 92767, didn't work, big surprise.

    If anyone would like to try to replicate this, all I'm doing is going into the editor and 1.) placing a player unit as a forward air controller, 2.) placing an OPFOR tank some distance away, 3.) placing the Simple Support Module somewhere on the map, then going into the mission, looking at the tank with the laser designator, requesting an air strike through the Communication menu, and waiting. Sometimes the A-10 shows up and does nothing, sometimes I can hear the sound of the A-10 in the distance but it never shows up. All other support options work.

  18. Posted

    I had same problem but never used any beta patches,now installed only the ARMA 2: OA beta build 92767 and now simple support module for me works great, never had one failure yet calling in air strike, A10 comes in destroys target, im using US army FAC guy,on any map good luck kirkherbstreit.

    Beta build 92767 - so I take it you don't use patch 1.60? Are you using any addons/mods as well?

  20. Posted

    I've noticed complaints about the SSM air strike not working with 1.6 beta. I thought updating to the full 1.6 would solve this problem but I guess not. Is there any script or ANYTHING that can make the air strike portion of the simple support module work? Right now all that seems to happen is either A) A-10 shows up, doesn't even bother to fly in the vicinity of the target, then gets shot down, or B) no A-10 shows up at all.

    For what it's worth, I've also been mainly using the laser designator while using SSM, but the same issues persist no matter what targeting method I use.

    Would changing the aircraft/payload fix anything? Would writing anything in the init field fix anything? Is there ANYTHING that can be done?

×