sthompson

The problem is not development of new tech but rather lack of support for older tech. As long as ED can rake in the money by releasing lots of modules that then lose support they will not have a financial problem. But they also will not have a financial incentive to provide support for older modules. The proposal is about changing incentives, not solving a financial problem. With the current model ED will lose (and probably has already lost) customers who are disillusioned with support levels on existing tech. At the very least, such customers are less likely to continue to shell out for new modules if they are unhappy about bugs in the old ones.

New F-16 campaign from @Reflected might be enough to get me to purchase the Kola map since he has an excellent track record of keeping campaigns up to date. But I'm not inclined to buy the companion FA-18 campaign by @baltic_dragon until there is some progress on his completely broken campaign for the MiG-19 Farmer. The Crime and Punishment campaign included with the paid MiG-19 module is currently unplayable. The bug was reported more than two years ago, with intervening promises to fix it. The last promise was made more than a year ago, but no action has been taken. I'm generally not a complainer, but my patience is at an end. ED really should fix a business model that prioritizes new content and features over game-breaking bugs. The bug report thread is here:

Only the functions that use the modifier stop working. The mapping for those functions will disappear until you re-enable the modifer mapping. They may show up with unexplained red triangles. If you don't use modifiers then there will be no device IDs in the modifers.lua files and so you don't need to edit them.

Renaming may not be enough. If you use modifiers you will also need to edit the modifiers.lua files and change the device IDs within those files.

None of this makes any sense to me. I stand by my original statement: Make spotting dots optional, with servers able to force them off for PvP if the server owner thinks using them is not sufficiently "equitable."

Please consider that a lot of players are using 2D not VR and fly mostly SP missions. Better to make spotting dots a server setting so that competitive servers can turn if off for competitive PvP MP without killing it for everyone in every kind of mission. The AI will still have superior vision in SP and in PvE MP environments even if the dots are turned off.

VAICOM knows "Shell" but it does not know "Shell 11" or "Shell 21." Furthermore, there is no difference And it ignores the radio and frequency settings when choosing recipients. (Wish that could be fixed!) If the radio tuning changes when you call for the tanker, but Easy Comms are OFF, then that implies you have "select tunes radio" turned on. In that case VAICOM is tuning to whichever tanker is selected when you call the tanker. If you haven't given a Select command then it tunes to the default tanker recipient, which is the tanker that was closest to you when the mission started. If you use an explicit "Select Shell" command first then it will try to find and tune to a Shell tanker, but not necessarily the one you want. To fix this, rename one of your tankers "Texaco" or "Arco." The easiest fix is to turn off "select tunes radio." You still will need to use a "select" command, however, that matches the tuned recipient. Unfortunately, VAICOM doesn't figure this out for itself. Ideally there would be an option to automatically select a recipient based on radio tuning and the named recipient in the transmission to the AI when easy comms are OFF.

I had this problem more than once. In addition to what @draconus said I've experienced it when I replaced one joystick with another one where the original joystick had a modifier button assigned that was used for other devices. If the modifier no longer works then you won't get an error when you hover. Remapping solves the problem in that case.

It would be unrealistic for DCS to support inputs for third party software, and I'm not sure I would call the VAICOM interface to DCS as an "input." What is needed is for track files to record events that are triggered via calls to a standardized API. DCS could provide an API for radio communications, for example, so that third party apps such as VAICOM would not need to mess around with DCS's internal code and would only need appropriate entries in the export.lua file. And then if tracks recorded calls to the API as events that could be played back then tracks would work again.

The FAQ. I've been subscribed to the Discord for a long time.

This. I'm trying to get back into DCS multiplayer, and when I connect to the HB CWS I'm strongly recommended to read the FAQ on their discord. But I'll be damned if I can find it.

RSBN and ATC are posted inside the cockpit, RHS, at least for Caucasus.

sthompson

Unfortunately there are other deal breaker commands that are needed to fly a mission but have no keyboard commands other than through the comms menu. Any module that requires interaction with the ground crew is in this category. In addition to wheel chocks there are also the ground air supply and ground power commands. And others for specific modules. (The update data cartridge command for the JF-17 is an example.) Of course tracks are unreliable as a general matter in my experience, and I guess I'm less worried about the immersion than your post suggests you are. So this hasn't been a big deal for me. On the other hand, I would love to have the track system fixed, and if so, having an API integrated that permits third party apps to interact with the AI would do the trick. That might even be a better option than having ED take over VAICOM.

If reinstalling Windows at the same time you might want to find and backup the Eagle Dynamics registry entries too. DCS doesn't use these, but some 3rd party auxiliary software uses these entries to find DCS. VAICOMPRO for example.

LOL. I posted essentially the same instructions in this thread months ago.

Before I upgraded my system with larger SSDs I tried this solution and found it didn't work for me. The problem is that the updater will refuse to update DCS unless there is enough free space on the SSD where DCS is installed, even if you have implemented junctions so that you know that many of the files will reside elsewhere. So if you try to install a new map, it won't install even if you have set up junctions for the download folder and for the appropriate DCS folders where the map will live. In short, this works only if you are willing to move so much of DCS off the SSD so that there is enough space on the SSD to do the install on the SSD.

If you use modifiers then you might also need to edit the modifiers.lua file since the device ID's appear there as well.

I don't understand some of the info in the briefing. For example, in Mission 3 the slide for the first leg has an annotation KN 224/16 in addition to the magnetic heading, altitude, and distance. In the next leg the code is GN 077/24. What do these designate?

Seriously? I have a lot of these conflicts, and I didn't change any key bindings. They just showed up. Fixing them all via that method is going to be very time consuming.

A bunch of these red badges showed up in various modules recently after I installed 2.9.6 and bought the FC4 upgrade. While a few show the conflict when I hover, most do not. Is there any way to determine what is causing the issue? Some of the red badges appear in places where I apparently have no assignment at all.

Permissions problem possibly? If you are running VoiceAttack as administrator, does your administrator account have full permissions on drive X? Administrator rights on one machine does not necessarily give full permissions on a different machine (the NAS).

Because sometimes you want to create a fixed view in order to save it as a snapview or other default. You can't do that while TrackIR is reporting head position updates to DCS. Some of the view commands are also helpful even when using TrackIR. The zoom commands for example. Or the commands to rotate the F2 view. It would help if you would provide more detail. What are your enabled TrackIR hotkey assignments? And which view commands don't work for you when TrackIR is running. Since view commands are often module specific, identify the module too.

There is no toggle for "off." I assume you mean "pause." The TrackIR software is still active in Pause mode but it isn't sending position updates to the game in that mode. I often pause TrackIR when I'm trying to create a particular view to memorize using one of the DCS snap views. I do not experience the lack of camera control that you mention. But perhaps that is because I do not use the default bindings in TrackIR. I map the pause function to the Keypad minus key. I map the "center" function to a joystick button. And I disable the other TrackIR bindings. Your inability to control the camera suggests that you have duplicated key bindings.

This showed up on my system today. I notice that all of the affected modules in this thread are from Razbam.