AJ.eightFive

Here is the mod I've put together to suppress the virtual pilot's speech and eliminate the delays between issuing a command and receiving a response. See this post: http://forums.eagle.ru/showthread.php?p=1345157#post1345157

To all those usng VAC, I have created a mod that suppresses the virtual pilot's speech and delays between issuing a command and receiving a response. See this post: http://forums.eagle.ru/showthread.php?p=1345157#post1345157

To all those usng VAC, I have created a mod that suppresses the virtual pilot's speech and delays between issuing a command and receiving a response. See this post: http://forums.eagle.ru/showthread.php?p=1345157#post1345157

To all those usng VAC, I have created a mod that suppresses the virtual pilot's speech and delays between issuing a command and receiving a response. See this post: http://forums.eagle.ru/showthread.php?p=1345157#post1345157

VAC Friendly Radio Mod by AJ.eightFive v1.2 Summary: - Supresses virtual pilot speech, leaving AI flight members, ATC, JTAC, Tanker, AWACS and Ground Crew speech intact. - Eliminates the delay between issuing a command and receiving a response. Dialog with AI feels much more natural. - Fixes several AI speech/audio bugs. - Includes detailed VAC profile designed for more realistic speech interaction with AI. - Restructures radio command menu, creating three static ATC recipient pages instead of a single dynamic one. This allows actual airfield callsigns to be used when building commands with VAC. Description: The purpose of this mod is to improve the player's experience when using the software VAC to issue radio commands. For an example of VAC being used in conjunction with DCS A-10C, please see Fish's post here. With an unmodified DCS A-10C, every time the player issues a command through the radio menu, scripts generate appropriate phrases which are then spoken aloud by the virtual pilot. Several VAC users have expressed a desire to supress the virtual pilot's speech in order to enjoy a more believable interaction with the AI entities. This was previously accomplished by deleting all sound files from the DCSInstallDir\\Sounds\Speech\Sound\ENG\DCS A-10C\Player\ folder (which I still recommend for this mod... just in case). Unfortunately, for long messages (such as the JTAC check-in message) this would result in a large delay between when the command was issued, and when the AI would respond. The speech scripts automatically generate a "buffer" to allow the speech audio to finish playing before the response is generated or new commands can be issued. The duration of the "buffer" is based on the length of the message subtitle string which is still produced even when the player sound files are removed. This mod eliminates the "buffer" by changing the speech scripts so that subtitles and audio messages are no longer generated for player issued commands. Now AI responses will begin almost immediately after the player issues the command. This mod also restructures the radio command menu, creating three static ATC recipient pages instead of a single dynamic one which sorts ATC recipients by distance. This allows actual airfield callsigns to be used when building a VAC profile. For example, with the VAC profile included, the user can say "Anapa One One, Enfield One One, Inbound For Landing" where previous VAC profiles could only use a generic callsign such as "Tower" or "ATC One" to issue the desired command due to the dynamic nature of the ATC recipients list. One of my goals for future versions of this mod is to extend this behavior to dynamic entities such as JTAC, Tankers and AWACS. Finally several problems with the default speech scripts that cause the AI responses to produce no speech audio have been addressed. Examples are the Tanker's "Cleared to pre-contact" message, and AWACS' "Vector to Tanker" and "Vector to Home Plate" messages. If you are aware of any other AI speech that does not correctly generate audio, please let me know and I will try to find a fix for future versions of this mod. This mod contains a VAC profile which I recommend using or basing your own custom VAC profiles upon when using this mod. Enjoy! Notes: - I realize receiving instant responses isn't a perfect solution either, as in real life there is always a delay while the other party thinks about their response. I intend to experiment with ways to gracefully create such a delay and will tie the delay length with the complexity of the response such that a simple response such as "roger" will be received almost instantly, amd a more complex response such as a 9-line briefing, will take considerably longer. - In order to allow the direct selection of ATC recipients, the default menu behavior whereby ATC recipients were sorted by distance is no longer enabled. However, in order to make all ATC recipients available, there are now three seperate ATC submenus accessed by function keys 5-7. The tanker submenu has been reassigned function key 8, AWACS function key 9, and Ground Crew function key 10. The "Other..." submenu previously displayed in the main menu has been moved, and is now a submenu of the Ground Crew menu. In the future I hope to be able to avoid this by creating a "Next page..." menu item in the ATC submenu to be able to access all of the ATC recipients without the need for three seperate menus. If anyone has suggestions as to how this might be accomplished please let me know as I've hit a brick wall trying to make this work. - This mod was tested only for DCS A-10C (v1.1.1.1) in a single player environment. Please advise if your own testing confirms the mod also works in multiplayer (somewhat likely) or for DCS:2 (unlikely). - This mod is likely to be broken by subsequent patches. If future patches do not improve the radio experience for VAC users I will attempt to release an update version of this mod that does. Changelog: v1.2 - ModMan 7.3 compatible. - Compatibility with DCS A-10C version 1.1.1.1. - Fixed wingman commands that were broken by v1.1. - Added several missing commands to included VAC profile (All ATC submenus, "JTAC 1-1" command). Note: Some player subtitles may still be generated now until I can find a safe way to remove them. Recommend disabling subtitles in DCS A-10C's audio options if you find this distracting. v1.1 - Fixed discrepancies in ATC recipient sorting between single player missions. - Modified "Other..." radio menu to be a sub-menu of "Main Menu > Ground Crew" so that missions that require it can still be completed. Added the VAC voice command "Other" to access the menu. - Removed the redundant word "callsign" from the menu text describing Kolkhi airfield. - Removed some additional player subtitles that were still being generated. VAC Friendly Radio Mod v1.2.zip

Got that one sorted Jona33, although not the way I had wanted... See this post: http://forums.eagle.ru/showthread.php?t=82444

Bug: After selecting Tanker Intent to Refuelt AI Tanker generates subtitles but no audio. Cause: \\Sounds\Speech\Sound\ENG\Common\Tanker\Numbers\7000-end.wav missing or speech generator not concatenating \\Sounds\Speech\Sound\ENG\Common\Tanker\Digits\7-continue.wav and \\Sounds\Speech\Sound\ENG\Common\Tanker\Numbers\1000-end.wav as desired. Fix: Quick and dirty fix (because I've been unable to solve it in a more desireable way) is to copy the .wav files from \\Sounds\Speech\Sound\ENG\Common\AWACS\Numbers\ to the \\Sounds\Speech\Sound\ENG\Common\Tanker\Numbers\ folder. The speech will sound a little disjointed because the voices are different, but it beats having to look at the subtitles (I intend to disable them once I get everything sorted out). Hopefully the next patch includes the missing sound assets (most desirable) or the scripts are rewritten to concatenate from the digits (least desireable because nobody calls out their altitude as seven zero zero zero, seventy-five hundred or seven-thousand five-hundred is the norm). If you don't care about this and you'd rather the digits be read out you can simply change lines 801-809 of common.lua: Old: Altitude = { make = function(self, alt, country, accuracy) base.assert(alt > 0.0) local altitudeUnit = countryUnits[country].altitude return self.sub.At:make() + ' ' + self.sub.Number:make(u.adv_round(alt * altitudeUnit.coeff, accuracy or 1.0)) end, sub = { At = Phrase:new({_('at'), 'at'}), Number = Number } } New: Altitude = { make = function(self, alt, country, accuracy) base.assert(alt > 0.0) local altitudeUnit = countryUnits[country].altitude return self.sub.At:make() + ' ' + self.sub.Digits:make(u.adv_round(alt * altitudeUnit.coeff, accuracy or 1.0)) end, sub = { At = Phrase:new({_('at'), 'at'}), Digits = Digits } } As a side note, making either of the above changes also allows you to increase the accuracy of the tanker's altitude reporting by editing line 147 of NATO.lua to read: self.sub.Altitude:make(message.parameters.altitude, message.sender:getUnit():getCountry(), #.#) Where #.# is the desired degree of accuracy, i.e. 100.0 will have the tanker report his altitude in thousands and hundreds of feet. The default is 1000.0.

Bug: After selecting AWACS Vector to Tanker and Vector to Home Plate the AI AWACS generates subtitles but no audio. Cause: BullseyeCoords defined on lines 789-798 of common.lua generates at random, the phrase "at bulls" or "at bullseye" which the speech/phrase module won't process for an unknown reason but likely a consequence of there being seperate at.wav, bull.wav and bullseye.wav files. Old: BullseyeCoords = { make = function(self, point, coalition, country) local bullsEye = base.Coalition.getMainRefPoint(coalition) local bullsEyeDir = { x = point.x - bullsEye.x, y = point.y - bullsEye.y, z = point.z - bullsEye.z } return self.sub.atBulls:make() + ' ' + self.sub.Direction:make(bullsEyeDir, country) end, sub = { atBulls = PhraseRandom:new({{_('at bulls'), 'at bulls'}, {_('at bullseye'), 'at bullseye'}}), Direction = Direction } } Fix: Instead of returning self.sub.atBulls:make() to generate "at bulls" or "at bullseye" messages at random, create a new sub "At" to produce the new phrase 'at' and a second sub "Bulls" to produce the random phrase 'bulls' or 'bullseye' as below: New: BullseyeCoords = { make = function(self, point, coalition, country) local bullsEye = base.Coalition.getMainRefPoint(coalition) local bullsEyeDir = { x = point.x - bullsEye.x, y = point.y - bullsEye.y, z = point.z - bullsEye.z } return self.sub.At:make() + ' ' + self.sub.Bulls:make() + ' ' + self.sub.Direction:make(bullsEyeDir, country) end, sub = { At = Phrase:new({_('at'), 'at'}), Bulls = PhraseRandom:new({{_('bulls'), 'bulls'}, {_('bullseye'), 'bullseye'}}), Direction = Direction } } Another solution might be to create an "at bulls.wav" and "at bullseye.wav".

I'm working on modifying the sound/speech files to remove player speech (subtitles and audio) for those that use VAC. Along the way I've come across a few bugs that I'm going to list here (along with my fixes if applicable) in hopes that they can be addressed in a more elegant manner in the next patch.

Nearly have this licked and will upload the modified files for everyone to test soon (it'll take me far too long to verify all the messages have been supressed on my own). In the meantime. Can someone confirm for me that in 1.1.1.0 the "Cleared to pre-contact" audio no longer plays after contacting the tanker with "intent to fuel"? I want to be sure that I didn't break it myself. I've tried restoring backups of the files I modified but the audio still doesn't play. Edit: Appears AWACS vector to tanker, vector to home plate audio isn't working in 1.1.1.0 either. Confirm?

Here's an example, which stops the script generating the player's callsign at the beginning of the JTAC check-in: From line 864 of NATO.lua Note that only the return statements are commented out as these are the ones that actually produce the messages. Commenting out the other statements within the toJTACHandler block still works, but produces a luascript error that appears on screen.

Torment, deleting the audio files in each of the subdirectories in \\Sounds\Speech\Sound\ENG\Player does what you are suggesting, that is, the commands are still sent, but there is no player speech. The problem, as Jinja discovered, is that the sim is still reserves a certain amount of time for the audio to play so that the player doesn't step on the transmission. With the player audio files deleted, checking in with JTAC results in a long pause before JTAC sends a response because the sim is still building that buffer. I've made a little more progress with this though. NATO.lua (amongst others I'm sure) contains several "handlers" that generate the player speech subtitles and by commenting these out one by one I have been able to stop the sim from generating the messages, and thus the big pauses. I haven't tried it yet, but I have a suspicion commenting these out means the audio files wouldn't be played either so there might not be a need to delete them.

Anyone think they can help with this? (Trying to eliminate player speech and the delay after "transmitting" a message for better immersion when using VAC) http://forums.eagle.ru/showthread.php?t=71121

Have been fooling about with some of the scripts and I've found a way to eliminate the delay after a player transmits a message. phrase.lua contains code which appears to concatenate the messages and calculates the total duration of the message based on the syllables it contains. The function getTextDuration takes the message string as an argument and returns the total duration of the message, creating the buffer which we are seeking to remove. Returning 0 is a quick and dirty way to remove that buffer but the problem is at this level it affects all speech and not just player speech, which causes some AI speech to overlap. For example, the JTAC 9-line briefing gets muddled up with the "advise when ready to copy remarks and further talk on" message. Changing the code to accomplish the desired result without this undesireable side effect might take a little more time than you think Jinja ;). Anyway, I'll keep working on it and hopefully others will see this and come up with some new ideas as well.

Need some new ideas on this front. With 1.1.1.0 renaming the \\Sounds\Speech\Sound\ENG\Player folder produces a lua error when trying to issue radio commands. Like Jinja, I've got VAC set up now and I'd like to remove the player speech as well as the delay after "transmitting". Edit: Changing the \\Sounds\Speech\Sound\ENG\Player folder name produces an error, but deleting the files within that folder and sub-folder works. I think someone else had already figure that out though.

Done! ...for now ;)

I picked up my iPad 2 and a copy of iControl DCS a couple of weeks ago and have my 'pit' set up nicely now. I tried a few different tools to get the job done (AirDisplay with Helios, iPadPit) but ultimately iControl DCS was the easiest to configure and also the best performing (in terms of CDU framerate) so nice job in that regard! It would be great to see some degree of customization added to the application if you release another version. For example, as you can see in the picture of my setup I've attached below, I have two physical MFCD's set up so it would be nice to be able to hide the MFCD bezels in iControl DCS when they aren't needed or replace them with an RWR or CMSP repeater instead. I've also noticed that radio tuning is a little hit and miss. I know I should be happy it's working at all now after patch 1.1.0.9 broke it but there's definitely room for improvement. It's very difficult to get the right ILS freqency set because it will often skip certain digits after the decimal. I was thinking an option to choose between the drag input method, or a popup with some numerical softkeys where the desired frequency could be entered might be an attractive option. Thanks again for the great app! It's well worth the money and if new features have to come with a price tag I'll gladly make another "in app" purchase!

Warthog stick and throttle connect to your system via independent USB cables whereas the Cougar throttle connects to the Cougar stick via gameport and then to the PC via USB so no, you can't have Cougar throttle with Warthog stick unless you also plug in the Cougar stick. The interchangeability refers to the stick grips. You can attach the Warthog stick to the Cougar base and vice versa. If you connect the Warthog stick to the Cougar base the push button on the countermeasures hat will not work however. Also, be careful tightening the large grey nut when changing the grips as the mechanism inside the Warthog stick is not as robust (it's made of plastic) as those inside the Cougar. I made the mistake of over tightening the nut and cracked the plastic ball joint and had to RMA the stick.

Were you using VGA or DVI cables before you switched to HDMI? I only ask because I thought VGA went the way of the dodo along with CRTs and if in fact you switched from DVI to HDMI and solved the problem, that might be something I try myself.

Can't wait to try it!

MASTER ARM = Safe? :P Do the GBU-38's show RDY status and highlighted in reverse video on the DSMS? Are you sure that the particular button you are using for weapon release is being held? If you are using a joystick profiler software it is possible that even though you are holding the button, the profiler is only sending a quick keypress when you first push the button.

Can't rep you again Headspace so thanks for the update. Really looking forward to the next release.

My 2 cents: I've owned CH ProPedals, used the Saitek pedals for a week or so and now own Simped F-16's. The CH pedals were very narrow and were unfortable to use for a long period of time. They were also very noisy. As well, after a few years the signal from the potentiometers became very erratic, opening up the pedals and cleaning everything out didn't help either. Toward the end of their life I had to set a 50% deadzone on the toe brake axis or hold the pedals back with my feet to keep the brakes from engaging constantly. I think I probably got 5-6 years of use out of them though. The Saitek pedals I am least familiar with having only used them a handful of times. They were much wider than the CH pedals and the adjustable friction was nice. They also felt more solidly built and were quieter out of the box but my friend complained they became sloppy and started creaking after a year of use. My Simpeds arrived about a month ago. Having read so many rave reviews I was a little dissapointed with the build quality. There is nothing stopping the toe brakes from flopping over the wrong way for example. I 've used cable ties to keep that from happening but I don't think I should have had to. There also seems to be a fair amount of play between some of the components so they don't feel as solid as I had expected. For the price I was expecting something more but I'm still happy with the purchase and have no doubt they are the best of the three by a long way.

Ewww, vinyl's worse than StarForce. I had LOMAC on vinyl and played so much I wore it out in a month! The fidelity of the flight model was incredible though. :pilotfly:

Video evidence or it didn't happen... ;)