bonesvf103

I get what you are saying, but I guess from reading the manual I was under the impression that if you speak the TACAN tune command, whether you are in the Tomcat or another plane, that the sim would tune it for you and save you the trouble of having to do it with your mouse. So that’s why I was perplexed that I would speak that command and it would accept it but my TACAN up front would not change. v6, boNes

I also tried using "TACAN Tune Xray 074" and it would accept it but the TACAN wouldn't change. If in the Tomcat I have the TACAN set to pilot, shouldn't this command change the TACAN for me? Or is it reserved exclusively for the RIO and in which case I have to set TACAN to NFO? v6, boNes

Yes, I had the Tomcat was the loaded module. But, I got it to work again. The problem was I was asking it to scan a sector that apparently is not in the parameter range. For instance, based on the command as set up with VA/VAICOM PRO, you can't ask to scan an altitude higher than 14000. Or a range of more than 30 nm: "Scan Sector, Angels [0..14,5] [at; for;] [0..30,5]" I'm not sure how to read that line of commands exactly, but I think from looking at it I was asking to scan at angels 20 and range of 100 (IIRC)...both of which are outside of those parameters. What does that line above mean exactly? v6, boNes

I take that back. This time when I tried it it did nothing at all. I gotta tell you, VA and Vaicom Pro sure are consistent at giving consistent results. This time also, I started VA with Viacom Pro and for some reason AIRIO was turned off upon startup. Again, consistent at being inconsistent. I dunno. v6, boNes

I think I got fed up and said scan angels [] for [] and it worked! Just drop the "sector". I think because it at least recognized "angels" and "for" and figured it out from there. v6, boNes

Thanks! v6, boNes

I noticed in the manual that there are commands that are not listed in the dropdown list of commands that you train. So if I say a command that is in the manual, it's not recognized and thus doesn't execute. For instance, for AIRIO, "scan sector <angels> for <range>." Or, there are commands listed in the manual but they are different from what's listed in the dropdown menu. For example, the manual says "Enable grid" but the dropdown says "grid enable." Which, when I say "grid enable" Jester says OK, but he does nothing. Same with changing the NavGrid heading or sectors or what have you. Then there are commands that are listed, such as TACAN tune, and VAIMCOM PRO recognizes it but Jester does nothing. Any ideas? Thanks! v6, boNes

Thanks for all the tips guys, I appreciate it. v6, boNes

I was training the VAICOM PRO with the phrases that you are supposed to speak, and some didn't work so I skipped it, I want to come back to it later...but then it occurred to me--Will I ahve to rerecord all 870 phrases, or can I just do the ones that I skipped? Also, when I was recording the phrase "Select...", the Microsoft app wouldn't take note of it, instead it would say "Selecting..." and then hang. Any tips on that? Thanks! v6, boNes

Seems pretty random... Sometimes it works, other times it doesn't. Error message varies too. v6, boNes

I got it to work but now it isn't... v6, boNes

AS of this morning July 1st, when I start DCS, a DCS Login window pops up looking for Steam authorization data. It fails then tells me that all of my modules are not authorized and will be disabled. DCS continues to load and sure enough when the main screen comes on, all of my modules are deactivated. They were working fine yesterday. I checked my steam licenses in my account and they are all still there. Anyone know why they won't authorize and how to fix it? Thanks! v6, boNes

Thanks but yes it was in 4a. If I had it in 4c, I don’t think the datalink contact would not have shown up at all like it eventually did. v6, boNes

I was following calls from the E-2 and had the datalink on. I never saw the contact on the TID. I kept flying toward his bra calls. Eventually I picked the contact up 120 miles away, but still no datalink contact. A minute or so later the datalink contact appeared well after I had him on my own Radar. Why is that? I had the datalink on and tuned the whole time and didn’t change anything on it. v6, boNes

I also get the same. When I start, I lock a target with the laser, switch to the Mav MFD. As soon as I do that, it automatically uncages and goes right to where the TPOD is locked and lazing. But every Maverick shot after that it does not automatically uncage and lock on. In fact, it starts out as caged and when I switch to the Mav MFD it stays caged, then if I uncage, it wanders around looking for a laser, then if I cage it, it cages right to where the laser is locked. I hold the pickle, it fires the laser,it launches. I also found you can tap the pickle once to turn on the laser then tap it again to launch. But the cage uncage thing is inconsistent. v6, boNes

What is the procedure to bolter in Case II and III? Do you have to go back to Marshall, or do you just reenter the pattern...? v6, boNes

Just so you know, the ebracket is ratchety and inaccurate, even real Tomcat pilots don't even use it. v6, boNes

I know the patch from last week caused worse problems for lighting in general, however, even before that patch, the AOA indexer was really dim. Ever since the start. Can anything be done to brighten it up even more? Thanks! v6, boNes

Now, did anyone notice that if you choose MAVF standalone and your TPOD is on in the other MFD, that you can't slew the MAVF around, even if there is no designated target? I think the only way I was able to do so was to put the TPOD into standby or off. v6, boNes

THAT did it! PTRKing is not enough. You also have to designate with the TPOD. Or alternatively, just use the Maverick stand alone. Thanks! v6, boNes

OK, so I changed FOV to narrow before locking it on. On this run, I tracked with the TPOD with PTRK. The TPOD followed the target as it moved and the MAVF uncaged automatically and slewed to the target. I switched to the MAVF MFD and attempted to launch when it was in range. THere was the X on MAVF in the HUD and it did not launch. Now, I think I have done it before without designating with the TPOD after PTRKing it. But this was before the update. So maybe the update changed things? I am enroute to try it again this time with TPOD designation. AND RECLUSE! Let's fly sometime for old time's sake! Email me, my address is still the same. Me and the guys I fly with will be flying tonight. v6, boNes

PM sent... v6, boNes

Yes on both counts v6, boNes

My issue is I have the TPOD locked on the target in PTRK and designated. I hand it off to my MAVF. The MAVF automatically uncages and points to the target and locks on. "IN RNG" is in the HUD, but the crossout on the "MAVF" in the HUD never goes away and so I can't fire. Anyone know what's wrong? v6, boNes

Well they did use NAS Fallon during the 80s for some TOPGUN training so... v6, boNes