Jump to content

sthompson

Members
  • Posts

    925
  • Joined

  • Last visited

Everything posted by sthompson

  1. Is there any chance that you are still starting DCS under an administrator account? If you did that it possibly would be loading code from the administrator account Saved Games folder rather than your own. And since VAICOM is patching the code in your own Saved Games folder this could explain a communications issue.
  2. Relatedly, I'd like to see hot mic status follow the in cockpit switch at the seat I'm sitting in on multi-crew aircraft. For example, if I'm flying as RIO in the Tomcat I'd like the VAICOM hot mic status to follow the switch in the RIO seat, not the one in the pilot seat.
  3. Why wait? You can do that now.
  4. You can't add to the VAICOM page on the kneeboard. Most people add checklists etc as separate pages in the DCS kneeboard. Keep in mind that the VAICOM "kneeboard" is actually just one kneeboard page with multiple tabs within the DCS kneeboard. You want to add pages to the latter, not the former, and you do that using the same methods you would use if not running VAICOM. Those methods involve dropping png image files into the appropriate kneeboard subfolder within Saved Games. I'm afraid I don't remember the exact details offhand. I used Kneeboard Builder to do it for me.
  5. It was this very issue with the comms menus that prompted Hollywood to abandon the original keystroke based implementation of VAICOM and switch to a method that communicates with DCS internals directly and not through simulating keystrokes. But obviously that requires getting into the guts of the relevant code, which may or may not be possible for George/Petrovich.
  6. That's not right. "Disable menu" turns off the menus that DCS would otherwise open. But VAICOM does not open them itself. So if you call the ground crew using one of the TX keys, and it is not bound to anything in DCS, then the menus are not supposed to open.
  7. This has been reported many times. It seems to be a byproduct of changes made when the kneeboard extension was rolled out. Hopefully @Hollywood_315 will fix it at some point because VAICOM really shouldn't be writing to a root folder.
  8. I can't really read the screenshot you posted. But my best guess is that anvil is defined somewhere else in the profile. Otherwise the profile is corrupted and you should probably build a new one.
  9. See statement from the developer earlier in this thread:
  10. I've sometimes seen trouble when people tried other VOIP modes then switched back to Broadcast Parallel without first clearing all of the other VOIP options. So I recommend that you turn on whichever VOIP mode you tried earlier and then make sure that all of the boxes on the RHS of that screen are unchecked before switching back to Broadcast Parallel. (They are greyed out so that you can't uncheck them when in Broadcast Parallel.) The every-other press issue seems like it could be related to earlier use of the TX Link mode.
  11. I've seen it show up when an update changed controller mappings for a module. And I don't run any mods.
  12. Another thought. Is your jet in the same coalition as Nellis? If not, that can cause an ATC to not be available. Also, what happens if you tune Nellis manually before giving the command? And can you give a command to Nellis using the communications menu instead of VAICOM?
  13. Do you have "Select Tunes Radio" turned on in options?
  14. Were you on TX Link before? That requires a different TX configuration from the usual. Details are somewhat complicated but are in the manual.
  15. I recommend also copying over the associated registry entries for Eagle Dynamics if you aren't going to install from scratch. These may need editing if the new install locations do not match the old. Curiously, DCS itself doesn't seem to care about these, but there are add on programs that look in the registry to find your DCS installation(s). (VAICOM PRO is an example.)
  16. You might check in the Eagle Dynamics folder of your Start menu to see if you have an icon for this. When I installed DCS it created such an "update" icon. I have one for the Release version and one for OpenBeta.
  17. You still haven't answered the question about where DCS is installed. One version of your log showed it on drive E and the other shows it on drive F. Which is it? In any event if you do not have the Release version installed then the problem is that you have somehow created a registry entry for the Release version and so VAICOM thinks you have that version installed. Since it thinks you have both versions installed in the same directory it is trying to edit the same files twice. Here is my recommended fix, assuming you know how to use the registry editor. (If you don't know how to use the registry editor then let us know so we can suggest workarounds.) 1. Shut down DCS and VAICOM. 2. Start the registry editor and navigate to the section [HKEY_CURRENT_USER\SOFTWARE\Eagle Dynamics\DCS World]. That is where information is held about the Release version. Since you don't have the Release version, delete everything in that section and the section itself. (Back it up first by exporting the section if you are cautious.) It is the presence of these entries that is confusing VAICOM. 3. The very next section in the registry is for the OpenBeta version. There is a key there for the path to your openbeta installation. Make sure it points to the correct location. 4. Do a full repair of DCS openbeta. 5. Delete the Saved Games\DCS folder. You don't need this if you don't have the Release version. It was probably created by VAICOM due to its confusion. 6. (Possibly not needed.) Backup, then delete all copies of export.lua in Saved Games\DCS.openbeta (including in subfolders). 7. Restart VAICOM 8. (Not essential) Uncheck the "Use custom path" option in VAICOM options, then restart VAICOM again. (If your registry entries are correct then this step isn't needed.) 9. Restart DCS Let us know whether this solves the problem.
  18. When you update DCS it reverses the edits to certain files that VAICOM makes when it starts. On the other hand DCS only looks at some of those files when it starts up. So it's important that you restart VAICOM with DCS not running after an update, and then restart DCS. That way VAICOM will redo the edits with DCS not running, and DCS will see them when it restarts.
  19. Honestly we could help you better if you followed directions and provided the information we requested. So please answer/post each of the following. 1. Which version of DCS are you running and where is it installed? VAICOM thinks you have both versions installed in the same directory. We need to fix that before worrying about the Saved Games problem or else the Saved Games issue will return. 2. Please provide a screenshot of your VAICOM options page that includes the "custom path" option. 3. And the text file that you were asked about is dcs_variant.txt, saved in the root of your DCS installation folder. See if you have that file, and if so what is in it. It should say "openbeta" if you are running the openbeta version, and the file should not exist if you are running the release version.
  20. According to the log, VAICOM thinks that you are running the Release version of DCS installed in folder E:\DCS World\OpenBeta. (It believes this because you used the "custom path" option to point it to that directory and indicated that you are running the Release version. ) It also believes you are running the OpenBeta version from the same installation directory. (It used the DCS registry entry for OpenBeta to get that information.) Notice the conflict? So the problem is that you have confused it by having conflicting settings about version and directory. You also appear to have two different Saved Games folders for DCS even though you point to just one DCS installation folder. To get this solved please identify whichever versions of DCS you have installed and where they are installed. Also post a screenshot of your VAICOM settings that includes the custom path settings. Then we can provide advice to sort this mess out.
  21. Not really a VAICOM question. Perhhaps @BIGNEWY could move this thread elsewhere.
  22. Kneeboard pages are not "just png files." Some have dynamic content. I don't know how these are implemented, but there are many examples.
  23. Is this new messages history available without pausing the game, say through a keybind? Seems like it would be a good idea to be able to pull it up similar to the MP player list so that you could keep flying while viewing it.
  24. For future reference Saved Games is a system folder. DCS and Vaicom find it using a Windows registry key. If you move the physical folder without adjusting the registry it will appear lost to DCS and VAICOM. The safe way to move it is to go into your profile where you will see the Saved Games icon. Right click on that and select Properties. There will be a "Location" tab. It will show you where Windows thinks the Saved Games folder is. If it is pointing to the wrong place, use the "Find Target" button to reset it to the correct location. Or if it is pointing to the right location but you want to move it somewhere else, use the "Move" button. Simply moving the folder using ordinary Windows move methods does not work! That does not fix the Windows registry key to point to the new location.
  25. Have you tried giving an "Overlord, SELECT" command first? That's required if you don't name Overlord in the other commands. And naming Overlord in your command should only work if you have "Instant Select" turned on.
×
×
  • Create New...