HeathenHedgehog

During a flight yesterday I found odd behavior in regard to HARM POS mode. Usually I create a steerpoint where a known SAM is and lauch on that, which has always worked. But on this occasion my original target was destroyed, and I switched to targeting a Patriot battery. The attached screenshots where taken back to back with no changes made. Jet did not have TGP or HTS equiped. Instead of creating an entirely new steerpoint, I used the FCR to slew my SPI to directly over the site location. Here's where things get wierd though: as you can see in the HUD image, the ASL, TD box, and FCR ranging data (B034.1) all indicate launch and cueing data for the SPI directly off my nose. However the HARM Launch Scale indicates a target much closer that 34 miles, and the carat was actually moving UP the scale as the STPT was at my 5 o'clock and getting furrther away. I tried cycling POS sub modes, TMS up to FTT the target, and cursor zero + re-slewing the FCR to the Patriot. Unfortunately I did not get a screenshot of the FCR, but the SPI was on the Patriot site as shown by the TD box on HUD. There is no HARM FOV box visible in the image, because my screenshot captured in between flashes, it was present and flashing indicating in parameters for launch. When I launched the HARM it pulled hard to the right and went to the steerpoint behind me. null My question is whether HARMs in POS modes can only go to the original STPT, regardless of SPI from other sensors or offsets placed into the system. If so, I completely understand, but in that case I'd ask if the HUD symbology is correct, since the ASL and TD box seem to correlate with SPI/FCR data. I would attach the trackfile but it was 2+ hours and I dont have a time stamp. null

The Emergency Gear release binding doesn't work correctly, if I lower the gear handle, then press what I've bound to Emergency Gear release, it just raises the gear. Happened to me in multiplayer last night landing with no hydraulics, just tested and confirmed in SP on a fresh jet, track file attatched. Tried binding it to other peripherals and same result. The emergency extension can still be done by right-clicking the handle with your mouse, but I'm in VR and trying to fish around for the cursor on an emergency approach is not fun. EmergencyGearProblem.trk

Coaster & Tako Blue F-14B Pilot/RIO NO SC

Coaster F-18 (SC) Tako F-18

Hi guys! First time doing an event like this, wingman and I can fill the last two Hornet slots if avaiable: Coaster 1-1 | F/A-18C multi ,Supercarrier: Yes Tako 1-1 | F/A-18C multi ,Supercarrier: No

FYI, I had this bug happen occur last week on my second takeoff from the Forrestal, both me and my wingman's controls locked after launching. I own the Super Carrier (Steam Edition), he does not. So I don't think it's tied to SC module ownership, but which carrier you are launching from. Sorry no track.

Was just playing the Harrier and setting up Winwing MIP panel. Noticed that the bindings for HUD Reject NORM and REJ 2 are swapped in the controls. Sorry don't have a trackfile right now but if someone could check maybe its just me.

SRS/Vaicom Hi @soupyc, I actually suggested a solution for this problem to Hollywood, post #5186 on the main VA thread: https://forums.eagle.ru/showthread.php?p=4317315#post4317315 Hollywood seemed interested, but he's understandably busy adding a lot of features/fixes so it might be a while before we see changes to the SRS/VAICOM interaction.

SRS/VAICOM Synthesis Hey Ciribob and Hollywood , Prelude: I’m cross-posting this because I think you’d both like to see it, and I think it will take both of you to implement. The SRS update this week bringing MIDS functionality is really awesome, and it couldn’t have come at a better time since I’m spending most of my time in the hornet these days and we’ve got Super Carrier coming (fingers crossed). However, it did exaggerate a problem that I think I and anyone else who uses VAICOM has run into; buttons, or the lack thereof. In the past you guys have done some collaboration to try and make an integrated system to make unified SRS/VAICOM setups possible, I’ve played around with this but found various disadvantages in certain situations, the current method of holding the desired radio TX node, giving an AI command, then speaking on SRS can cause problems on frequencies that have both AI and human recipients like AWACS and ATC if you are trying to say something to players and don’t have a preceding AI command. It is convenient that it can detect frequencies that have no AI and will go straight to SRS transmission, except if I’m trying to tune that radio with the select tunes radio feature, in which case other players will hear me. So up till now I’ve been using the more direct method of mapping my VAICOM and SRS buttons separately. On my 4-way + Push comms switch, I have up/down on SRS 1/2, fore/aft on VAICOM TX-1/2, and push as VAICOM TX-5 INT. But with the introduction of MIDS I’m out of luck, no way I can fit two additional radios on the same hat, unless... Idea: I think that a large portion of users have their comms mapped to 4-way + Push hats as found on the TM Warthog and VPC throttles. The problem is that these hats are gated and can only output a single button at a time, my idea is for the SRS+VAICOM software to get around this and allow for the push function to inhibit one program's transmission/listening. Basically, the user would push in the hat, and then move to one of their 4 directions, the software(s) would be monitoring button inputs and detecting whether the hat had been pushed in first before going in one of the 4 directions, and depending on this, transmitting over SRS or listening in VAICOM. To be clear, the push in on the hat isn’t “toggling” which program is used as in back and forth (although that could work, though I think it would be less intuitive), rather you would always push in and then pick a direction when issuing VAICOM commands, and SRS would be triggered by just pressing the same direction without a preceding push in. I’ve tested with my throttle and found that pushing in on the hat, then moving to one of the directions, there is no delay between it switching output, it goes directly from the push to the directional, but maybe there should be small (adjustable?) delay for different hotas kits or worn out switches. I know this sounds very similar to using a modifier button but differs in a few key ways: -As stated before, many 4-way + Push hats are gated (only one output at a time) and cannot use the push as a modifier. -In this implementation the SRS/VAICOM software is monitoring if the directional press was preceded by the push in on the hat to determine behavior. -Compared to simultaneous broadcast, this implementation would actually inhibit transmission over SRS when talking to AI or VAICOM listening and trying to parse speech directed towards other players. Example: Let's say I have the push function set to inhibit SRS transmission, and I’m tuned into ATC frequency that has both AI and people; if I simply press my comms hat in a direction, I will be transmitting over SRS, I can make my calls for example taking the runway, coordinating with human ATC etc. When I want to talk to the AI, I just push the hat in, then go in the same direction, no SRS voice transmissions are made, and VAICOM starts listening so I can give commands to the AI ATC (or whatever is on the frequency). A example of near-universal mapping would be as follows: (no push in)/(push in first) SRS/VACIOM Up: Radio 1/ TX1 Down: Radio 2/ TX2 Fore: Radio 3(MIDS A)/ TX3 Aft: Radio 4(MIDS B)+SRS Intercom/ TX INT (double binding SRS radio 4 (MIDS B) and SRS’s intercom channel is for compatibility in the Tomcat, since it has no radio 4 it shouldn’t be an issue) Maybe it could also be configured by user preference the reverse way so that AI transmission was the default (no preceding push in), and pushing in would switch to SRS broadcasting. It could even do this automatically in singleplayer or if SRS was off. If it is set up so that the push in action triggers VAICOM commands, I think it could maybe be even be set up so that just pushing in and not going in a direction could be used as a general Voice Attack command PTT for functions outside VAICOM, or DCS voice chat, giving a grand total of 9 individually addressable voice channels. Compared to the current implementation of holding the TX button, giving AI command, then speaking on SRS, I think this method allows for much greater speed, and user control, as you no longer start with an AI transmission, you can go directly, and exclusively; to whichever frequency and program you want. OK sorry for the wall of text, I know I repeated myself a lot. Spent a while thinking about this and just wanted to make sure I was expressing the idea clearly. To me this would be the absolutely ideal comms setup. Maybe I’ve missed something, maybe people have already thought of this or it's technically impossible due to the limitations of Voice Attack or how windows handles buttons. I hope we can someday have a universal system like this, let me know what you guys think!

I am going to pile on to those struggling with the muted AOCS. It has been muted for me since the previous VAICOM version, I was hoping that this patch would fix it, but it is still muted. I have played around with all the settings there are and confirmed windows TTS functions normally and I have no other issues with sound redirect. Additionally, this patch seems to have changed the way you interact with Jester and the radios in a negative way (at least for me). My setup is as follows, a five way hat, with up, down, and right assigned to TX1+SRS PTT1, TX2+SRS PTT2, TX3+SRS ICS, respectively. Left is assigned to TX4 AUTO and TX5 ICS. Prior to this patch, holding left I could say "Stennis select" and Jester would tune his radio to the Stennis frequency, I could also issue any AI commands to tanker, ground crew, ATC, regardless of which radio was tuned and it would all go through to the proper recipient. Following this patch, the select command can only be used if I am pressing the TX node for the corresponding radio, but all other commands issued through ICS still work fine. So to get Stennis I have to press down and use the select command through that channel before issuing any commands via left button, which means I broadcast "Stennis select" on SRS, obviously not ideal. I think it would make the most sense if commands issued to Jester (via TX5 ICS) for radio tuning all targeted his radio, the new behavior makes sense at least for the pilots radio since you are the one interacting with it, and I can get by just on the preset channels. TL;DR: Select command no longer works through Jester via ICS PS. Still love this program, keep up the good work.

@TinyUK, the keys were emailed to you when you purchased, so I would just go to your inbox for whatever email you linked to the purchase and search for Viacom, they should still be valid.