Chris Death

correct ;) ~S~ CD

afp - try playing around with guard waypoints and guarded by triggers maybe you'll find something there. Place 3 guarded by triggers (no syncronisation needed) and place let's say 5 groups on guard mode. 3 groups will go to the 3 triggers (can't remember how to determine which is going where but you'll find that out easy me thinks) and 2 groups will stay at their starting position. Setdammage one group to death or do it the rambo way and use a pkm on a jeep :) and you'll see one of the 2 reserve groups enter the scene - they might go directly to the now empty guarded by trigger or a group of another guarded by trigger does and the reserve takes their place instead. Such a guarded by trigger on top of the players helmet could make one get really nervous. Ah and btw - i saw in your first post something about the sentry wayoint. Waypoint SENTRY does nothing else than let a unit wait to pass it until it detects an enemy unit. So in case of them not noticing that you are there - it wouldn't have helped at all - it doesn't make them get knowledge of someone else it's more like you say "sit" to a dog and the dog has to get up once you release him (in that case once he knowsabout an enemy unit). ~S~ CD

Well i got ARMA2 a week ago so forgive me if i'm not common with anything that came after patch 1.08 for ARMA1 (because that was the time when i started having a break here). I think there are the modules in ARMA2 which can help here but as i said there might be others knowing more about that. What i can tell you is the way which worked in OFP and will work in ARMA2 aswell. It's pretty simple - this is where the SUPPORT waypoint comes to it's strength; Place an ammo truck or a medical vehicle (or soldier) or a repair vehicle or a fuel vehicle or put them all into a group (up to you) and give them a SUPPORT waypoint. Whenever any unit of that side requests ammo/medic/fuel/repair, they gonna go there to support (maybe even of a friendly side but i've never tested that). Note that the SUPPORT waypoint is an obsolete waypoint aswell so syncronise it to a switch trigger if you want to send them somewhere else when the action on that location has ended. Basically it doesn't matter where the support waypoint is placed - they will come but you might not want them to drive through another part of your mission, where they shouldn't at that time, so you should play around with waypoints to get them where they are required. I would also not let them have an active support waypoint while a fight is going on since they burn faster than they drive. ;) Let's say you place a group of ammo-truck - fuel truck - repair truck; Now give them a normal move waypoint (behaviour careless so they don't get the idea to become heroes) and syncronise this waypoint (or use it's condition-field) to an event where it is safe to let them do their job. Their next waypoint will then be the SUPPORT waypoint somewhere near to where you need them (behaviour: anything but not careless but be aware that safe would be the only way to make sure they are using roads). Syncronise this support waypoint to a switch trigger which you can set to whatever you want - maybe even a radio alpha/bravo/etc. so you get more controll on the scene. Everything behind that support wayoint is now up to you - they are ready to go. ;) ~S~ CD

There seems to be a lot of confusion about waypoints me thinks. Syncronising a trigger with a waypoint will cause a unit/group not to pass this waypoint until the trigger gets triggered. Trigger type Switch is used to force a unit/group to follow the next waypoint after the one the trigger is syncronised to. Trigger type Switch is REQUIRED to make a unit/group pass an obsolete waypoint which are for example: HOLD, GUARD Waypoint CYCLE is an obsolete waypoint in some way since the unit/group will not move to the next waypoint in logical order but to the closest waypoint next to the cycle waypoint. This comes in handy when creating a patrol with a few waypoints followed by a cycle waypoint close to where the patrol should start again (usually the first waypoint of the patrol but doesn't need to be the first one). Now syncronising a switch trigger to that cycle waypoint will make the unit/group continue to the next waypoint after the cycle in logical order - usually i made that a GUARD waypoint since this one will make them engage automatically to where they are needed. Waypoint type SEEK & DESTROY is NOT an obsolete waypoint - the unit/group will run around like chicken for a while and then continue to their next waypoint. SENTRY is an interesting waypoint since it makes a unit wait at the waypoint until it detects an enemy unit - after that the unit will continue to it's next waypoint. DESTROY works somehow like SEEK & DESTROY if i remember right - didn't use this one too much so i'd have to investigate again. I know there are a few more but these above are the ones fitting into this thread me thinks. ;) ~S~ CD ---------- Post added at 09:13 PM ---------- Previous post was at 09:12 PM ---------- You have to group them - F2 and drag a line from trigger to unit or vice versa. ~S~ CD

hmm - maxmem = 2047 and that's it - everything above will get downgraded automatically to 2047 Maybe one more gig to make windows happy but ArmA 2 won't touch anything above 2047 - at least that's how i understood the description of the maxmem startparameter in the biki. ;) ~S~ CD

ProfTournesol - pardon if this is now wrong at all - i just came back after a 3/4 years break but i seem to remember from old ofp that arraya = arrayb would cause that if you change arrayb afterwards arraya was changed aswell then. I really can't say anything for sure about that now but it's just that feeling i got that there was something about this 4/5 years ago. ;) ~S~ CD

I can't believe it - i got the game running on my older one pc from year 2002. P4 2.8 ghz (single core) MoBo: ASUS P4S800 RAM: 2 x 1024 mb sdram pc3200 GPU: Sapphire Radeon HD 4650 1gb AGP The game is running at 1280 x 960 (not sure exactly if it's now 900 or 960 but it's somewhere in the 9xx range) - everything on NORMAL and a few options even on HIGH - postprocessing off (didn't like that at all) and no shadows. The shadows i don't really need to enjoy the game and tbh i disabled them right from start without testing the performance with shadows on. Viewdistance 1600 FPS (taken from the result of the two FPS missions) The first one was about: max 35 - min 12 - avg 23 and the second one mission: max 27 - min 7 - avg 17 I remember when ARMA 1 has been released and i had an FX 5700 ultra with 256 mb in that pc - there was a slideshow going on in the desert with most settings down to almost nothing. That HD4650 turned this pc into a monster which doesn't stop impressing me - Crysis Modern Warfare 2 - Grid - Pro Evolution Soccer 2010 - Medi Eval 2 total war - HAWX ARMA 1 (everything on high) - Men of War - Theatre of War ..... nothing could stop it yet but that i got ARMA 2 running on it made me already a little bit scared of that pc. :) :edit - btw there's that one rig which makes me really wonder how a game like ARMA 2 would look like on it. FASTRA II ~S~ CD

Yeah you're right - a space costs only 8 bits (or 9) but that's the same number of bits, anything else costs. Well, two simple textfiles created with notepad - both contain the same text but one contains no spaces and the other one does have spaces inbetween. bacdfeeeeeeeeefasdetffedghjjktgdcgjjgrghjgdd b a c d f e e e e e e e e e f a s d e t f f e d g hj jk tg d c g j jg r g h j g d d The file with no spaces ends up with 44 bites while the one with the spaces is 87 bites - that's double the size and a quite drastical way of wasting spaces if there's no need to. I understand and i'm fine with that it is better to use the spaced version to get a better overview - but i thought that it's at least worth to know that spaces are not "nothing" but also "something". ;) And when i see an array posted like this: ["xxx", "yyy", "zzz"] i feel the smell of mixing up grammar with syntax. And to be honest: the spaces after the coma in that array above do not give any better overview at all. I'm not talking about the structured setup of the array i'm talking exactly about the example i've posted and seen in the first post of this thread aswell. Anyway i think there's enough forum space lost for talking about spaces :) ~S~ CD

Just a sidenote: ["xxx", "yyy", "zzz"] is the same as ["xxx","yyy","zzz"] just different because of the spaces after the coma which is gramatically correct but not important for the system. ;) All that the spaces are doing is: increasing filesize - well some people would be proud about that fact but i believe that when you're using arrays you're doing so because you want to reduce filesize and usage of resources. ~S~ CD

What about setting the policemen to: setcaptive true and combatmode neverfire? this setcaptive true: in a unit's init field will cause that the unit is captive and thus no threat anymore so noone will fire onto them. The never fire combatmode is very selfexplaining imho. Can be made with a waypoint or with the setcombatmode command, using the right colour (i don't know the colour right now but to find that out shouldn't be a prob anyway). ;) ~S~ CD

While "marker" should be replaced with the name of your marker and thislist will only work when executed from the trigger itself - from anywhere else you have to name the trigger and use instead: list trigger_name. ;) ~S~ CD

I'm not so common with new features behind OFP due to ARMA 1 not impressing me at the start so i've skipped it and hopped back in to ARMA 2 last weekend. The technique i showed above is if you want to have quick a few men into fixed positions and to remount them automatically without having to make too much extra work. AnimalMother92's solution does look much more like what you need in that case. ;) ~S~ CD

Here's a quick one i've been always using in ofp. Have a few men to build a group (4/5 or so) - place them near the empty gun and give them a GetIn waypoint attached onto the gun - open fire - combat. Now when the gunner gets killed, remaining men of the group will remount the gun until no one left. Those who are not in the gun will fight the enemy aswell - it's always the group leader unit who mounts the gun - so no worries about the others moving too far away. ~S~ CD

hmm not sure if you meant that: when a waypoint is attached onto a unit you can: dbl-click it to open the waypoint's box or use shift-click to go for the unit below the waypoint. If you hover the mouse over the waypoint+unit and press delete, you will delete the waypoint because it's the let's say top layer. As long as it's one unit and one waypoint it's easy to mess around with, things start getting more tricky when there are two waypoints of two different groups attached onto a vehicle - no way to change lot of without having to delete and recreate it. :( ~S~ CD

Well then do a googlesearch on Blue screen of Death and have a read at the BSOD wiki to convince yourself that the BSOD comes from what i mentioned already above. The BSOD happens to you only in ArmA, because none of the other games did touch the faulty zone. Ya know it's like a person who cannot swim. As long as this person doesn't go into deep waters, he will not sink - but if the low water is full and he needs to go further: blubb blubb blubb Just because you have exchanged the dll file doesn't mean that you should have fixed the problem. It just can tell you (if the error still exists), that the dll file itself wasn't the problem. There are lots of other components in your pc which can cause those troubles, but i doubt that the game developers can help you out here. I'd take a look into a hardware forum or summit like that. Lots of guys there usually do know way more than any of those who sold you your pc. ~S~ CD

hmm let me guess: ati3duag.dll you got an ATI graphics card Blue Screen of Death usually indicates faulty hardware or driver. Have you ever tried a google search with that error? Well, i did and there are popping up lots of links showing this error in relation to lots of different games. Some inner voice tells me that your BSOD has nothing to do with ArmA. ~S~ CD

Nice work there As soon as looking at the pictures there comes the feeling that this is one thing that should be already hardcoded into the game, depending on time of year and weather settings. This would be an awesome change to the atmosphere and could give every mission it's individual taste. But sure there were lots of other troubles, BIS had to deal with when developing ARMA. ~S~ CD

If you count your brackets { and compare them to the brackets } you will find out the: <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE"> }; }; showTitles=1; showRadio=1; }; these 3 brackets at the end are too much. I'm not into this stuff anymore that i could clearly tell you where this part has to go, but there's the fault. ~S~ CD

paradox - give them rice, they want bread - give them bread and they want rice. By not releasing it as a beta, we would still be beta testers only without somebody telling it official. Like the first release of ArmA. The mass of the comunity didn't like that way - they wanted to have beta's, so that they could be prepared hardware wise for the real thing. Now when BIS has changed their approach back to beta before official release, ppl comming along begging for no beta's. weird ~S~ CD

Do you mean you can't place markers during a running game or are you talking about placing markers by the editor? ~S~ CD

Your sys-specs and ingame settings would off course be very helpful to people trying to give you any advise. ~S~ CD

Noone asked that yet Can he play on other servers? ~S~ CD

Did you also check for chipset / BIOS updates? Also various different drivers for sound or gfx could prolly help out. It might be software related if a BSOD occurs, but then this is just because the software hits a region where no other softwarez was before. Sounds very logic for both: ArmA and Stalker - so maybe the other proggies which are running fine for you don't touch the faulty adress spaces, where the BSOD is comming from. ~S~ CD

This is normal ~S~ CD

Still wondering about when the first one arrives who understand what DarkFenix did post clearly imho. Â I will help you guys (sorry @DarkFenix - i can't help you directly but maybe others can once they understand). DarkFenix pays for a dedicated server (not at his home) Other people can join and play on this 'external' dedicated server but DarkFenix can't 'join' the server. Now explaining him how to login as admin will not help that much since he does not even get that far - he simply cannot 'enter' / 'join' / 'access' this server. Â :edit - ah yeah i almost forgot; DarkFenix can join other servers led by other ppl - just not the one he rents and pays for. ~S~ CD