SkipperSMG

Strange. I have easy comms definetly off and VAICOM tells me i can't contact AWACS via UHF frequency. Looks like a should go for a fresh install at this point :lol: thanks for the headsup. Any idea on the SRS-mode related problem, though?

Btw i got another question out of interest that might have been asked already but i wasn't able to find an answer on: Why does VAICOM limits AWACS on the VHF band? From my knowledge they are even most of the time on UHF but I'm open for any elucidation :book:

Open the VAICOM config menu, switch to "about" tab and click on "List". It will display your license code, purchase ID and purchase email. Edit: Sorry, i overread that you are already on a new machine. I would suggest to to open a support ticket or contact info@vaicompro.com directly for license key support related stuff.

Thanks, that solved the problem. Is it VAICOM related or what could be the problem here? In the past this worked beautifully without problems.

Module is properly recognized but i tried it nontheless. No joy

Yes i noticed that and yes i did so. However, situation is still as described. Wenn I press TX1 for VHF, UHF is recognized by VA. After i pressed TX1 for like 3 times, finally UHF is shown in VA. However, its not functional

Howdy Folks After the recent update i encountered some problem regarding the Viper. VAICOM recognizes all my inputs as VHF altough UHF is activated. In the PTT menu it is correctly recognized but VA says im talking over VHF. After pressing the same key 2 to 3 times then UHF is recognized. And vice verse (UHF as VHF). In addition no radio recognizes the frequency dialed in in DCS (radio 0, 000.000 Mhz). Strangly enough, DCS itself recognizes all inputs as UHF however no response. I thought it might be related to the Version so i updated to 2.5.12.2 but the problem stil persists. Any ideas?

1) I would like to be able to combine conditions for triggers on a more globaly basis. Just one example: "altitude greater than" not only for one unit/group but for whole coalitions. Many useful trigger conditions are somewhat useles because every unit would have to be added to the list. Both options would greatly improve workflow. 2) draging selection boxes 3) there are a lot of excellent suggestions already in the thread. Pick as many as you like :music_whistling:

You need to update VAICOM. Version 2.5.12 does not support the viper and thinks you are sitting in the F-5. Use version 2.5.12.1

I let it run on the my dedicated server. And somehow, don't ask me why, it started working. I restarted my PC a couple of times and suddenly it was working. i haven't touched anything. This **** will drive me crazy some day :music_whistling:

Vaicom (2.5.12) recognizes the F16 as the F5 Tiger, so it limits you to one channel

SWAPR - SWeet Automatic Player Replacement script Thanks for the input, but unfortunately not the answer here. Everything is set up as it should and has been check more than 10 times i guess :noexpression:. As I said, I even got the files and the mission from somebody who got it working properly and that did not change anything. So it seems to be related to my system?! MP is set, hook script is in place and correctly modified, clients are properly recognized. I was able to not die like 2 times out of ~50 while hopping through the slots doing my different testings but i did not change anything and also was not able to reproduce that. Kind regards

Unfortunately, i am not able to get it working in multiplayer. SP is no issue but for MP everybody explodes when joining into a slot. I tried to exclude as many variables as possible, i even got all the files and the mission from a mate of mine which worked for him when hosting on DC in MP. But no joy. After a couple of hours i gave up. Any idea what could be the cause? Everything works but despawning of AI or the static object when the client enters the the aircraft.

not yet implemented

tried that. It messed up all the controls. Nothing was bindable. Suggestions? :book:

When ordering you get an estimated dispatch time. Proably 2 months or so. Thats pretty close.

Which does not affect the freedom or feeling of movement of the ministick or how to cursor travels. Its just your personal preference. I prefer the round one, since i want the cursor/ministick movement relation to be even in every direction.

My TGP does the some and always did.

Order received today, installation and calibration with the provided instructions was a walk in the park and only took 5 min. 10 of 10 would buy and wait for ages like a child for christmas again :thumbup:

Order #1986 shipped today :thumbup:

you know, some things receive an upgrade over the time of their service life

#1986, im dying right now

After an in-depth long-term study on feature release history regarding this module, I would rate the probability of the event you requested as tending to zero. TLDR: I do not think so

Already working on a future template :joystick: around 130 active and 120 inactive sam sites, speaking of syria alone. At the end it is intended to include all installations of military interest.

Thank you for your input. Much appreciated :)