PVT Watt.J

Lets not get worked up over it. Whether it is part of a helicopter pack or a fixed wing pack is irrelevant, either is fine.

Very exciting to see!

In missions where the player starts out as a gunner in the helicopter, it will not allow me to use the Gunner's optics. This is fixed by either 1) saving and reloading the mission 2) Exiting the helicopter and getting back in. Repro: Create a mission with AH-99 Blackfoot flying at 50m, playable as gunner. Test mission and set pilot to AI and gunner to player. Using optics key does not open up gunner's optics. **EDIT** Already been posted, nevermind! http://feedback.arma3.com/view.php?id=15059

Yes, I started having problems with that recently too, but fix is coming along with a rewrite of the code for missile guidance that fix some other issues as well!

Hey guys, I just received permission to bring you guys one of the best pieces of user-made content in the history of the Arma franchise. I'm very much indebted to the authors of this content for being so generous as to let me use it. I'm not ready to divulge specifics at this time, but something big is coming. It might take a while, but it is in the works, so stay tuned for more cryptic info!

Glad to help!

Are you sure you have enabled in optional file RWCO_HAFM.pbo? I know on my development version of RWCO the Apache works just fine. I can't think of any reason why the recent patch would break only the Apache/Cobra. Can anyone else confirm this?

Fold action would be great, but I'll take it any way I can get it!

Host the game as a dedicated server. You can run the arma3server.exe and arma3.exe on the same computer. This means that when your arma3.exe crashes, the game will not end.

This is actually complicated. For config stuff, it tends to matter based on the locality of the thing in question. Weapon mods will work if installed only on client (though other players will see them as invisible). Scripted mods will work clientside as long as the functions don't have locality issues.

Not exactly. It has fixed wings AND rotor wings. It would not be much more out of place in a heli pack then in a fixed wing pack. Not like there are any other aircraft for a tilt-rotor pack! In any case, I would love to see MV-22 or some EAST helos.

Deletion doesn't necessarily involve identification. It can simply be based on location. Define each segment by its endpoints. Then, when the user hits delete: 1. Get coordinates of mouse 2. Loop through all line segments, if line segment passes through a box of arbitrary dimensions centered on the cursor, then delete that segment. Of course, this is more complicated for anything other than nice straight line segments.

I don't know anything about the syntax difference between sqs and sqf. I've only worked in SQF. In any case, if you'd like to talk more message me on steam and I can try to help.

Hi Konyo, Script to turn on radio chatter could look like this: Script to turn off radio chatter could look like this:

Fair enough Goblin, thanks again.

If there is a simple way, perhaps, but this is really not on the radar in terms of priorities.

It can't fail. Not ever.

Hi Goblin, Thanks for your work on this. I tried it out and it was a totally different experience from the typical boring Arma HALO drop. My one suggestion would be to change the configs a so that this does not create a new faction. After a few faction mods, the list of factions can get fairly cluttered and if mods like this are creating new factions as well, the clutter starts to be a real problem! Might I suggest putting the HALO units under a separate class (rather than faction)?

Hi Konyo, Very exited about your MH-47. In the config, the condition for the useraction is a variable attached to the MH-47 using getvaraible. In your script, nowhere do I see setvariable being used on _heli to set it's "kyo_Chatter" variable to true. Hence, the chatter off action will never appear because this getvariable["kyo_Chatter",false] will return false. Perhaps I am missing something, but I believe that is the issue.

The primary audience of this mod is MP coop. Some features of the mod simply will not be fully accessible to AI, thus defeating the purpose of the mod in the first place. However, I am in the progress of working out some minimal level of AI compatibility. This is already accomplished with the Kajman. With the Blackfoot/Apache/Venom, the likely solution will be this: 1) Give missile trajectory usersactions to player, even if he is pilot. 2) If AI is in gunner seat, switch out version of DAGRs/Hellfires used by players to an AI-friendly version. Switch back if a player enters gunner seat. 3) Find some way to make AI not automatically fire at laser designators. My goal is to make UI elements cause as little disruption as possible to both mouse and joystick users. BTW, If you guys would like to have some fun with RWCO, grab a friend and do air-to-air combat vs. the Kajman. The key to winning? Don't sit still and don't fly directly at it. The Kajman's missiles are lousy at hitting moving air targets and its AI gun accuracy has been decreased to seem less robotic.

Would love to know how to calculate if there is good LOS between two points in a way that takes into account smoke? As far as I know, neither of the terrainintersects and lineintersects class of functions will handle this case (though I would be happy to know if I am wrong!).

Glad you like it, much more to come. Announcement: I'm looking for participate in RWCO who has experience with GUIs and PiP in Arma. There is a lot in this area that I would like to implement (Proper HMD, usefully MFDs, GUI for entering laser codes) and I have my hands tied up with the rest of the mod.

Thanks for this Olds. I see that this documentation has come a long way! Something like this has been needed for quite a while. You might want to add this to the list of documentation. It has proven highly valuable to me in working on RWCO. ***EDIT*** 10 minutes looking at Olds' references and I have already found a likely solution to a an issue I had where vehicle weapons were improperly aligned with optics. His reference links very quickly allowed me to identify three relevant parameters: https://manuals.bisimulations.com/vbs3/3-0/devref/#Config_Manual/CfgVehicles/P_cpp/cpp_parallaxCorrection.htm%3FTocPath%3D4%20Configuration%20Manual|CfgVehicles|_____355 https://manuals.bisimulations.com/vbs3/3-0/devref/Content/Config_Manual/CfgVehicles/C_cpp/cpp_canLase.htm https://manuals.bisimulations.com/vbs3/3-0/devref/Content/Config_Manual/CfgVehicles/C_cpp/cpp_compensateRange.htm

New release up with a number of fixes. Known issues: 1) Actions are available for using remote guidance/broadcasting lasers. This is just placeholder, it does nothing. 2) Lots of tuning required for guidance scripting. 3) Laser designators are still out-of-alignment.

I'd like to work on HMD-based nightvision/thermal view for attack helicopters where the center part of the screen is NV or thermal and the periphery of the screen is standard visual. Has anyone done this before? Have any information that might be useful? Either would be much appreciated.