Evil_Echo

WP is mostly for marking locations and providing instant dense smoke as concealment. It's not meant to be used for mayhem. While WP can be used also as an incendiary, thermite is far better for that.

Very nice document, FreeFire! FYI - the documents for ACE2 and ACEX currently on the BI wiki will have to move to a new server in the next couple of weeks. The exact details will be announced when the migration is complete. Once that is done, there should be more detail in those documents as well since we won't be subject to as many restrictions in content. I do plan to include the link to your guide in the "see also" section if that is ok with you.

Not going to answer that. I wrote that it's not recommended. A human can drop the B61 very reliably. The BI AI is unreliable. It will either miss the target or get itself killed. Until that AI can be programmed in a way that gets it's act together I will not discuss a technique doomed to fail.

I had one for my missions in ACE1. Should be quite doable. Just have to find the correct function calls.

Kestrel is in the tools list in the ACE2 classlist wiki page.

Kind of - for one thing the various packs allow you to carry different amounts of stuff. The repair ability is mission-dependant - i.e. Xeno made that feature.

DU armor and fast neutrons = bad day. Spaced armor or even RHA is more healthy for you in that situation.

That depends on your definition of survive. I wrote the nuke code before the M1A1HC was finished, so used the stock T-90 for my tests. A near miss with 5.0 kt did not kill that tank, but it was so trashed that any surviving tank crew would have bailed out. Then there is the fallout coming down later.... FYI - now that some other chores are done I do plan to go back and add some more features to the nuclear weapons code. Expect crew damage to go up in certain AFV's due to interaction between armor and prompt-neutron flux.

*choke* Lack of documentation? I know there are still some gaps - but there is more documentation out for ACE2 than there was for ACE1 on the BI wiki. Enough data that we got yelled at for "abusing" their wiki ( status still pending ). I'm writing as fast as I can and still have a life. And at some point I may have to write it all over again if we move to a different site and different format. Not that anyone will bother to read it. But the information is out there if anyone cares to look.

More documentation on the way on the BI wiki. Getting class lists, etc, and then some how-to sections for various things. In the meantime... 1. Rucks. Added a small section to the ACE2 features. More on the way. Will be releasing documents on an API for mission-makers once the code for those is done and released. 2. Explosives like trip flares, claymores... Place one like a satchel charge. Then you will get action options to aim it ( clays ), attach a trip-wire, etc. 3. Goggles, mask. Documented in the FAQ. Once you register your player profile with ACE via the config, you should get extra actions to change headgear if you have at least one goggle/mask in your inventory.

The key binding list wiki page was correct. I fixed the entry in the ACE2 Features wiki page. Sorry for the confusion.

Have a trigger to detect the destroyed target, then delete the invis target.

Just be aware - you might want to sample the wind for an average value. People using ACE have noticed that the A2 game engine shifts the wind direction and speed fairly often. Another idea would be to impliment a wind-sock.

All for it, but would like to get a list of the weapon modes. Then just do a select 0.

Definitely use the modules and other documented switches to control what features are active. Do not remove .pbo files in an attempt to disable ACE functions! The interconnections between the various .pbo files are complex and subject to change without notice. Zapping files can/will lead to very bad surprises. You'll get absolutely zero support if the ACE is tampered with. Not to be petty or cruel, it's just not worth the time and effort to diagnose a hacked configuration.

Stamina. You can't win this argument. People will rant no matter what you try to impliment. So we are just baselining the upper limits using various documents including papers from the Uniformed Services University Department of Military & Emergency Medicine. You still have to fine-tune the system to match up how ArmA2 does things, but that is why ACE2 is in beta. Wind. ACE2 does not touch the weather, just makes it apparent. BI is making the wind shift around. One of my IRL hobbies is shooting benchrest rifle. When at the nearby rod and gun club the wind routinely shifts 45 degrees in seconds, gusts changing the speed by 10 knots also. Makes creating a small 5-shot group a challenge on some days, but I like challenges. I was asked to help test the new wind system when it was ready. 5 guys spread over 60m @480-500m away with very stormy weather going on. ACE's lead developer was my spotter and had the Kestral-4500 to get an average wind reading for me. I used a M-24 bolt-action rifle and fired up the arrow mode to monitor the wind as I adjusted my scope. Repeatedly did rapid-fire, 5 shots, 5 dropped men. Each shot, holding off on a different spot according to wind at that moment. Estimate I had a 95% one-hit rate aiming for center of mass, about 80% when I tried for head-shots. Not trying to sound condescending, but a good sniper needs to understand ballistics and practice a lot. There is a guide to markmanship for ACE - more will be added about doping the wind when I have time. In the meantime there are plenty of other resources out on the net for this topic. Read and then make a practice mission to hone your skills.

Actually - I, Sickboy, Pufu, Scubaman3D, and others do read the official ACE thread. You're lucky I saw this posting - don't count on that happening though. The info on usage is correct - pack/unpack button will transfer between the ruck and gear slots. Also the right arrow on ruck list will unpack too. Still under development, more to come as I have time.

Be sure to use the built-in options to disable stamina if you must. Removing files from ACE is "a bad thing". Not warranty that ACE will be stable if you start zapping files. Also there may be some API-like functions in the future for things like that. Using setVariable directly is not forward compatable, you are skipping safety checks right now. Until I document the ruck system, be careful or be ready for sudden changes in how it works.

Ok - that gives us a bit more detail then. TY. Could you file a bug report for that ( how-to in the FAQ ), specifying as much info as you can so we can try to reproduce that and fix? It would be very appreciated.

Just like it says in the wiki document, "Features of ACE2". Please people - read the "manual" before asking the same questions over and over again. There is even a FAQ that covers issues like the updater and goggles. Repeating questions or "bumping" is just wasting space and time we could be spending on making ACE even better. Those documents are constantly being improved with more info. So it's worth checking now and then for new data.

It's going in as fast as I can type and format it. Weapons for ACEX are done, other stuff on the way.

I will talk to you on Skype today, norrin, with the details. Some of the functions mentioned are internal and low-level. So you need to add some wrapper logic to use them externally.

If it's nuclear/biological/chemical, that would likely be my domain. All I can say right now is maybe - lots of work going on right now.

DRTB will certainly use ACE. Easy for us to keep up with the changes.

I used cloudlets for mine ( ACE ). It certainly can be tuned more. But a lot easier than the loop used in the original Gigan nuke and a lot less laggy.