Greyman

im getting a fair bit of technical VAICOM Pro stuff wrong atm, so I can't be certain, but I'd guess that this folder and file only exist for the duration of the auto-update and will only exist if the process hasn't completed properly. Whether the time since your last use of VP is a factor has contributed, I can't say, but if you have manually brought the files up to date, just keep an eye on things when the next update comes. It'll probably be fine.

@Snacko - take a look at post #2465 (and #2464 that prompted the response) for something that might help.

In the viper, you would press Comm2 and enter the frequency, 13300, into the DED, followed by a press of the enter button. You don't need the decimal point and i am fairly certain that the "Tune Radio" command, if you have AIRIO, will only work in the F14. Then you would use, press and hold, whichever switch you have set for TX1 on the PTT screen and say "inbound", "request startup", "request takeoff" or any other message for the Lochini tower, as appropriate.

So whereas @dax post would explain what might be causing the "bounce" your post would suggest that the square bracket should not move like that at all. If that is the case then it looks like this will need to be addressed, at some point.

I wasn't aware that VAICOM had any control over that, as all it does, in very simple terms, is follow the DCS comms menus that have been fed from the mission file. Maybe check the .miz file or possibly the briefing, for the mission in question, and see what frequencies have been allocated to the AWACS aircraft. I'd be surprised if VAICOM won't work with those frequencies.

It's the creativity that's my problem. My elder sister got all of the creative genes in my family's gene pool. ;) I have more of a logical mind, so the mechanics of using the mission editor don't scare me, it's just thinking up what should go where on the map. I've amended a few mission files before and will probably have another go at creating new ones, probably just the "simple" ones that would allow me to test new weapons/features. Thanks for the encouragement.

Now that does make some sense, if the square image stays where it is until a new scan redraws it back where it should be. If the aircraft moves relative to the target between scans, this is probably what it would look like. So does a fully locked target get scanned more frequently then, as that would explain the smaller "bounces"? Thanks both

Thanks @Hollywood_315. I was struggling

Looks like the F-5 really will be the next aircraft in my "hangar" then. I had been looking at this module for a while and this, along with the sale, has probably just clinched it.

You are right, in that it definitely becomes more stable with a full lock, but it feels like it is still trying to follow the aircraft's nose, but is more restrained in some way, than it was in SAM mode. If this is how it is in RL, then fine, but it just feels a little odd.

thanks @Wags. Much appreciated. My mission editing skills are, shall we say, not good.

When i lock a target, using Radar, the square bracket that appears on the HUD does not seem to be stable and appears to follow my own joystick movements, rather than stay over the target aircraft. It appears to return to where it should be on the HUD, ie over the target, when i point my nose at the target aircraft. I did save a track, but on replaying it, the target aircraft did not get locked, so there didn't appear to be any point. By the way, if you need to reproduce, i was flying RedKite's refuelling mission, starting behind Texaco and then heading straight for Shell, using TACAN channel 22Y,

I've just tried and it appears to be working. Do you have the latest version of VAICOM Pro, 2.5.12.2? This is a very recent new update Have you reset the 'Use custom DCS path' if you have DCS installed in a non-standard folder? this can lead to some odd behaviour, which i had once, but i'm not certain it was like yours. Just press the SET button and select your main top-level DCS folder. For both of the above, i don't think that a restart of VA is necessary, but it probably wouldn't hurt to do so. You will be able to tell that i'm no expert, but these should be worth trying, until someone else dives in, if you are at a loss.

ooo, had to post another one to get off the dreaded 666 :)

did you delete the export.lua file after you updated DCS? that normally shows by not displaying the module name in the PTT window and not getting the PTT buttons right, but still worth asking

you have probably noticed that the VHF channel, Comm2 in the viper, sits on TX1 in the VAICOM PTT tab and that the UHF channel, comm1 in the viper, is on TX2. That shouldn't stop them working, but you do need to press the TX1 button for VHF and vice versa.

It might be that he has nothing to say on a perfect approach. Not that I'd know, of course.

Is there likely to be a hotfix for the "pickle" button issue or is that more likely to be fixed at next Friday's patch?

undesignate maybe?

Is there any chance of a pre-made Walleye mission, preferably air-start, or will we need to make our own?

Have any TM WH users been able to check whether the alternate TDC slew option works or not? I know that option was implemented for MavF, IIRC, but surely the Walleye TDC should be the same?

There is a setting in DCS to simulate the muffling effects of wearing a helmet.

Apparently, and this comes from the top, "you have to let kids fight sometimes"

Good point. As ED has just released an update, don't forget to delete your export.lua file and restart VA and DCS or your PTT dialogue will look like that screendump, even with an aircraft active

Not a problem. Someone will have helped me when I had a problem(s) and I am sure that you will help others when you can. I have a Thrustmaster Warthog HOTAS, and there is a 4-way/push-button MIC switch on the throttle, that is used predominantly for the comms buttons. I have that set up with VHF on the forward button and UHF on the down button. The other 2 directions are also set up but aren't used by the viper