Hellride

Hi Hollywood, I just tried the new .dll and for me at least, the config window still needs to be open. Everything else has been updated as per your 2.5.3 update. Not a huge deal since it does work - but for your information.

The way it works for me is to keep the config menu open. If I do not, I can't get ATC or wingmen, et al to respond but oddly, mission specific responses do happen. This works on the fly as well - start DCS, start VoiceAttack. Call ATC for clearance to startup - nothing. Pause game, go to VoiceAttack, open config menu - try again and ATC responds promptly. I have rebuilt the .lua files as well, as directed and from scratch with DCS repair. I updated VoiceAttack and am using the release 2.5 in VR.

Well... First go didn't work that well. I removed the old install, replaced with the new one and even retrained with the new key words. But, still had trouble calling up the F10 menu and JTAC callsign Uzi will not respond. Using nearest works but selects the wrong JTAC. Trying to use the menu to call up Uzi still will not get a response either. Only way to get Uzi to respond, is by reassigning the HOTAS mic buttons to the radios then use the menu option in Vaicom Pro. The F10 menu sometimes works but mostly calls up the options so not sure if it's just having trouble recognizing "mission" or "server" first. Didn't have trouble in training these though. Thoughts? I'll keep trying.

Wow! Thanks Hollywood that was fast!

Just finished the mission. ...and it occurred to me. If you have Vaicom running Uzi will not respond. Turn Vaicom/VA off completely and re fly. Uzi should respond as well as the remainder of the JTACs.

I had something similar. Chatter worked, could hear the squelch, and menus appeared but no response. Then I checked the menu. For VHF AM, it was choosing Interphone. So, restarted VA, Ctrl Alt C for config and refreshed the PTT page (make sure the game isn't paused but actually running) and that fixed it for me.

I have two questions as well (after reading the manual and reading these 35 pages) - any way to call a JTAC by a name that isn't a key word? I.e. mission has Axeman and it works just fine, then switches to Uzi - which is a keyword for a flight member - thus, no response. I tried just using Patrol, or Operator with the proper frequency (different than Axeman's) and the call still goes to Axeman. All JTAC operations are in a similar area. Is there a solution? - Is it recommended to open up the configuration menu before play? If I don't, I notice VA doesn't register my username into a mission with my callsign for that mission. Don't know if that matters at all but have noticed by opening and refreshing the PTT at the start of a mission it can help resolve some weird behavior. Thanks. Appreciate your help here and this stuff is great for VR.

Haha. Not sure what may be causing your Uzi issue - I finally had success last night, but the repair didn't do it. Had to reinstall the entire beta and now it works as advertised - except for the ATC granting permission for take off but I can live with that. At first Uzi didn't respond and I felt gutted - only to realize I hadn't used the 124AM freq. Then he did come on and gave me my target but be prepared with pen and paper... All I'm saying. :) I didn't fly back to Beta though. Maybe that's the difference?

Well, I guess I'm getting some progress. Axeman answered after my initial check-in today, but then disappears and never provides the 9-line. I wait. And wait... Nothing. So I check-out. He says I may depart. Cool. Check-in again, he's back - "ready to copy." Nothing. Try that a few times, then check out and he says I may depart. By the time I get to Charlie, I fail the mission for leaving the area. Which I figured would happen. ...when I get some time, I'm going to try on 1.5 next. Something is definitely up or I'm doing something wrong. It kind of reminds me of requesting take off at the hold short. ATC grants permission to taxi, but if I hold short and request take-off they disappear. If I just storm straight through to the runway - they announce unable to clear, with an immediate follow up of cleared for take-off. Started happening in the advanced campaign at Kobuleti and continues here. Never happened at Batumi during basic.

Thanks for the quick reply. I try calling him several times around Bravo, but only had him come back that one time and then he disappeared again. Is there a trigger point somewhere that I may be missing? I'll try again, will also see if 1.5 will work. If it takes some time for him to respond I can try waiting but I've already waited a long time circling and playtime is only 15 mins. Thanks for the radio clarification. I was wondering how he talked to me at mission start-up on the same freq as the tower, then pushed to 124 unless he was over UHF until the push. If he's not in our flight makes sense he'd be under TAD 12.

Hi all, So graduated to the TTQ and cannot get past the first mission - can't get the JTAC "Axeman" to respond. I have tried about a half dozen times so far, and today I finally got him to respond but then he disappeared and wouldn't come back after I reported "ready to copy." I have no idea what else to try? I'm using the FM radio on TAD 60 - 30.0MHz. Thought maybe we were checking into the area early so circled at WP1 for a while to check in by 7:15 but didn't work. Not sure what I'm not triggering and not sure why it kind of worked today then didn't. Any thoughts? I'm flying 2.5 Beta on VR but otherwise nothing different. Thanks for any help - was looking forward to the campaign but this is getting a little frustrating. PS - as an aside, when responding to the FE do I use the AM radio on TAD 12? The briefing says our flight is on TAD 15 (IIRC) which is the typical UHF for wingmen. He responds either way, but wasn't sure what was expected. Thanks again.

That's exactly the mission I was referring to. Finally finished it today. Frustrating to say the least using the H on that first tank, then knowing I'd have to use another for the convoy. Spotty at best but turned out epic as after I gunned down the rest of the convoy, all I had left was that last tank and an H on deck. Pressure. Didn't want to waste time with the TGP and have him escape into the darkness so made a quick circle to gain distance, lined her up on the HUD, got almost an immediate lock and quick pickle to finish him off. It was pretty cool and really close range -- no one in the house here cares, so feels good to share it here. :laugh: So, in the end it worked but I'd steer clear of H for sure.

I'm experiencing this very thing, but only with the H variant maverick. The contrast on the seeker CCD is pretty bad but I can barely see the target when i get pretty close. Even then I cannot get a lock, though. Today I noticed I finally could get it to lock, but way outside the range staple - within 1.5 miles. Missile does fire and hits the target so I guess that's good. Don't know why it only locks so close and outside the range staple but at least it worked. May be of note the mission is at night, but the target area is lit up bright with flares. I'm also using 2.5 beta in VR.

Holy cow. Thank you for this. Seriously.

Thanks for the help, but I did eventually get past this PO. I do have 2.5 and restarted the campaign, but I couldn't get him to stop running into me and moving only when I moved - so instead I called for taxi approval and let him rip by me to the hold short, then I took the other taxi way to the runway. That seems to keep 2 holding short until I'm wheel's up. I'm now on my way through the Advanced campaign...