Goldrake

+1 - That was fun. Sent from my SGH-I337M using Tapatalk

+1 It all ties in with the willingness (and associated pains) to step out of the comfort zone. Manpads should have been an opportunity to teach new tactics (transport helis are forced to adapt and, as stated, that was their only AA). Just getting on Teamspeak or SRS in a great tactic, no need to think Top Gun manoeuvers. With your addition of new airfields/farps, I suggest increasing the number of JTAC crates. Would it be possible to incorporate some type of repair/restore crate for airfields and farps? It would be cool for a transport heli to resupply a damaged asset and it would force people to get on comms to ask for assistance. Fixed it. I share your frustration. We need you, with your glass full. Salute.

@BlacleyCole I mostly followed the manual for step by step checklist. I would not be able to improve the manual with a checklist. Sounds to me that the best way to help you get your VA going is to meet you on a public mp server and compare notes through Teamspeak. When I get back to my PC I am going to update to version 2.5.1. Let me know if you are on mp. Sent from my SGH-I337M using Tapatalk

@BlacleyCole Can you be more specific on what you are trying to accomplish with VA? Are you having problems issuing commands in the Huey?

You are correct. It does work with the F1.

I have been flying the Huey lately transporting troops and I can understand the jet fighters frustration with the Manpads. I am guilty as charged but I do believe it is fairly realistic. The name of the game, at least for me, is to avoid detection and infiltrate enemy positions with troops. If I do get spotted ... most, if not all, of the time I am dead before I can even react (Reaper6 :music_whistling::thumbup:). If a Heli transport pilot manages to drop troops, when attacked, please give the guy credit for being able to land (and not crash) under pressure (it is not as easy at it sounds). No warning device of any kind and all visual flying. Please keep this in mind. We don't get the stat for the kill but in a way it should be credited somewhat. If you attack a transport Heli and miss on that first pass then you should change your attack strategy for your second pass. You have time to tactically re position. Once deployed to the field I cannot pickup my Manpad team again. Is Red able to do this? I can confirm on Blue side that if you drop your troops too close to the Farp they will run back toward the Farp and position themselves around the center of the Farp and just bunch up for an easy target. If you deploy them even closer then, yes, they are returned to base but that means that you are within the Farp's pickup zone and should not drop them there. If you drop them at a Farp and they are returned to base, just load them up again without lifting off the ground and re position yourself further out. If you see them running back to the Farp, get another team and drop them further out until they stay in place. Then you know the min distance you should be from a Farp for surgical placement. As far as ammo, I have seen the Blue Manpads fire at least 2 per team so if the Red Manpads do not fire more than one than it is either a bug or night time. I would love to transport rearmament to an infantry team in the field, but I do not believe it is possible at the moment so once their ammo has been depleted they are sitting ducks. JTAC crates are limited (pretty sure 10 is the JTAC limit per side) so after you've exhausted your JTAC's (which I think if you crash with one JTAC on board it may count against your total) there is not much left to do in Op Longbow for a Huey pilot but to attempt to infiltrate Manpad teams into enemy territory. I hope that not far in the future they will add repair crate kits for Farps, or something like that, in order to keep transport pilots busy but for the moment, once Blue takes Gali and there are no more JTAC's, it is pretty much 'be a PITA with Manpad teams and infiltrate Sukhumi'. EWR crates need 2 crates to build it but, from what I am told, it does not aid in the detection of the enemy and, on top of that, once you manage to drop two crates next to each other and unpack them, the EWR is invisible so you can't even admire your work. CTLD has a lot of stuff for a transport pilot to drop and build but at the moment it is not scripted in Longbow. Most likely the limitations are for server stability, which makes sense, and thus why Heli's are a big PITA with their Manpads. :)

Thank you for the tip. After much testing... the sequence of combo keys RAlt | followed by F12 seems to take care of the root state issue. Still having issues when intercom mode is in PVT but I am pretty happy with it so far. Good to hear that you are working on a plugin. Looking forward to a much more elegant way of doing it.

Hi, I have manually added additional commands for the Complete Transport and Logistics Deployment communication menu under F10 (such as load troops and/or crates) when flying a Huey. The problem I am having is that I cannot find a ‘common ground/common key press’ to reset the communication menu to be ready to accept commands for both the VAICOM preset commands and the manually added commands. Example, I use my additional commands to load troops, load/drop crates … and it all works well but when I give a VAICOM preset command such as request refuel-rearm (which by the way works like a charm) I find that my communication menu does not reset to a state where my additional commands get recognized at first instance. I have to manually reset the communication menu by pressing the “\” key on the keyboard twice after every VAICOM preset command. Adding the two “\” key presses to the VoiceAttack command sequence does not work for some reason. I guess my question is very simple: is there a special key sequence (or something) to add in VoiceAttack so that the communications menu resets to a common default state after every command?

Great piece of software, surpassed only by your dedicated technical support. I am truly enjoying it. There seems to be a compatibility issue with SRS and the Huey. In the event that you are having issues, like me, running VAICOM and SRS in the Huey and your mike remains open when you press the TM HOTAS Throttle mic key, the following fix may help. Open C:\Users\**your PC name**\Saved Games\DCS\Scripts\DCS-SimpleRadioStandalone.lua In the following section: function SR.exportRadioUH1H(_data) Find and delete the following lines: if SR.getButtonPosition(194) >= 0.1 then _data.ptt = true end Restart the DCS Huey module If you update SRS to a new version, after you have modified the lua, then the 3 lines will reappear and you will need to take them out again (until properly fixed).