sthompson

Those messages are normal when you start VAICOM before you start DCS itself. Except for one thing. It's a bit strange that your older messages are at the bottom of the list instead of at the top. Do you have the most recent version of VoiceAttack? EDIT: When writing the above I had forgotten that there is an option in VoiceAttack to put the newer messages at the top vs. the bottom of the log.

Do the static menus show up for you correctly? What do you mean when you say you can only talk to Sochi? What happens if you call ATC at a different airfield? Can you confirm that Voice Attack is correctly identifying the recipient? It's possible that the new mod has caused a change in the static ordering of airfields, which would affect interaction with VAICOM. I would not expect that, but realize now that I did not check that. I can try to look at it this weekend.

Static ATC Mod for 2.0.5 and 1.5.6 All: I have created a new version that seems to work in 2.0.5 and 1.5.6. See post https://forums.eagle.ru/showthread.php?p=3090920#post3090920. This may also solve some issues that others have had with helos since some of the newer lua code involves helo support that was not present when the original mod was created. But I don't fly helos and can't confirm that. Thanks to Whartsell for the brilliant original! sthompson (Softball in MP)

Static ATC Mod for 1.5.6 and 2.0.5 Hi all. I've spent some time working on modifications to the Static ATC Mod and now have a version that seems to work in both 1.5.6 and 2.0.5. I mostly fly 1.5 so have not done extensive testing in 2.0.5, but have tested enough to know that it no longer crashes DCS and that the static menus work. The support for VAICOM ATC communications in the Nevada map could use some work since none of the Nevada callsigns or airbase names seem to be coded in the F-15 module, and I presume not in the others as well. You need to call them by number. For example "Nevada 3". The "nearest" function works just fine, however. FYI, it took quite a while to track down why the static mod wasn't working on the Nevada map. It turns out that the built-in call getCallsign was crashing when applied to some of the smaller air strips and airports that have no tower communications. This doesn't happen in the Caucusus or on the older Nevada map. To work around this I had to modify both files of the Mod. To install, drop in the two attached files in place of the files of the same name in the original Static ATC mod. Let me know if there are issues, but this seems to be working for me. Vote me some reputation if you find this helpful! sthompson (Softball on MP) RadioCommandDialogsPanel.lua ATC.lua

New features in VoiceAttack 1.6.2 Hey Hollywood. Thanks for all of your work on VAICOM. It is awesome! I just installed the latest version of VoiceAttack and noticed in the changelog description of new features that it now supports including multiple other profiles in the current one, so that you can have multiple profiles active simultaneously. See "Include commands from other profiles'" in the documentation for 1.6.2, which also describes how priorities are set when this leads to multiple definitions of the same command within the profile. It occurs to me that this feature would permit a much more modular design for VAICOM (VAICOM 3?). You could have default profiles for VAICOM admin tasks, ATC, Tankers, Flight, JTAC, etc. all included in a profile, with only the aircraft specific commands at the top priority in a profile. I realize I'm talking about a major redesign but it would make VAICOM much more modular and make it easier to add new aircraft. It might also facilitate testing and debugging because you could turn modules on or off rather easily without having to do major surgery on profiles. Full disclosure: I haven't tried this feature myself yet! Anyhow, I'd be interested in any reactions you have to this. --sthompson ("Softball" on MP)

ATC Static Mod for 1.5.6 and 2.0 I recently was working on an update of the file I circulated previously that made the ATC Static Mod work again under 1.5.5. I had the new version working under 1.5.6 and 2.0 but I never got around to circulating it, and the recent updates to 2.0 may have killed it. I will try to work on this again later this week. Hoping that 2.5 will have ATC static menus built in as an option! --sthompson, ("Softball" on MP) please upvote my reputation if you found the previous work on this valuable.

If the ball is not centered then your plane may be pointed directly at the runway but that is not the direction in which you are traveling. Instead you are slipping slowly to one side. Use rudder (or rudder trim) to compensate until the ball is centered. The degree of side-slip depends on RPMs so you may have to change the amount of rudder you are using as you adjust power and RPMs. You may also be slipping due to a cross-wind. That requires a different kind of adjustment.

I purchased the Albatross package today based on glowing reviews here. I didn't realize there were two models. Are there any differences other than the cannon on the ZA? Also, now that I've configured controls for the C model can I just copy those settings over to the ZA?

I have figured out how to use chat in MP but there is no way I'm going to be able to type messages while flying. Yet other people seem to do that routinely. How? Third hand? Assistant? voice recognition software. What do you do? Somewhat relatedly, is there a way to ID other players. Last night someone on AerobaticsOnline server kept locking me up and the tone was driving me nuts to the point where I quit flying. Seems like there should be a way to PM another player, or at least figure out who is doing it.

If you mean the Static ATC mod then version 1.5.5 broke it. However you might take a look here to see if the fix I made works for you. https://forums.eagle.ru/showpost.php?p=2986946&postcount=499

I'm trying to bind the printscreen function to HOTAS keys in the profile for several birds. The binding appears to work fine, and printscreen works fine if I use the keyboard. But the bound HOTAS function does not work at all. DCS recognizes it because if I push it when I'm in the controller options menu DCS highlights the correct function. Any suggestions will be welcome. This is in 1.5.5, using CH hardware and the CH control manager software configured to generate DirectX button presses when I press a physical button. The setup is working fine for all other functions.

I'll try that, but I still consider it a bug. Using the mouse to zoom works just fine in other parts of the game. Sitting in the cockpit, for instance. It's only a problem when viewing the map, either in the ME or in the F10 view. And its frustrating that there does not seem to be any other option for adjusting the zoom level on the map.

I'm hoping to bump this issue. I too cannot reliably zoom the map view using the mouse wheel in Mission Editor in 1.5.5. If it zooms at all it only does so with a very long lag (most of a minute, if not more, definitely not just a few seconds). And since there is no immediate feedback as to how far I have zoomed I frequently find myself zoomed all the way in or out and can't do anything useful in either case. Definitely a bug. Mouse drag and clicks work without any problems. Mouse zoom worked fine pre 1.5, if I recall correctly. Hoping 2.5 has configurable keybindings for the mission editor, but I can live with mouse zoom only if this problem gets fixed.

Static ATC Mod I've been trying to get this working in 1.5.5 and think I've succeeded. If you want to try it out for yourself, download the attached file, and use it to replace the file of the same name in the original Static ATC mod. I created this by comparing the file line by line to the one installed with 1.5.5. Most of the differences appeared to be due to the "under the hood" changes in comms that ED has been working on, but it seemed fairly easy to identify the static ATC mods and copy them into the 1.5.5 version of the file. The other files in the mod do not appear to have been updated by ED recently, and so I left them alone. For me this allows the ATC static menus to appear, and they appear to work as expected. Now if I can just get VAICOM 2.0 working. Or more precisely, get Windows to not mangle everything I say before passing it to VoiceAttack. EDIT: Files attached here are for 1.5.5. For a version that works with 1.5.6 and 2.0.5 see https://forums.eagle.ru/showthread.php?p=3090920#post3090920. RadioCommandDialogsPanel.lua

Disabling easy comms makes communication impossible in the FC3 planes as nearly as I can tell, because the radio is not manually tuneable. If that's the only solution then I consider this a bug.

Speed to waypoint in the SU-27 is the designated speed for the flight plan. This may or may not be the speed needed to arrive on schedule, depending on whether you are deviated from the plan already, or not. Best approach is to study the flight plan in the mission editor and know when you are due at each WPT. Then watch the clock and distance to WPT and adjust speed accordingly.

I've found that if it's really dark finding things initially is a challenge. But there is always the flashlight function to help you get started until you can power up the other lights.

I've been trying a bunch of night missions lately and find that often I can't see the comms menu items that are rendered in a dark font because they are invisible against a black background. Is there a workaround?