Nytehawk

Definitely not feeling correct. The stick feels like I could use it for a chin rest. :-) I do the lean forward trick in VR to get it right, but it takes some fiddling around with head position.

Just for curiosity, is there somewhere we can donate to help with ongoing module costs? I've wondered about that before, and figured now is a good time to ask. :-)

PM sent GT, a couple of them really, but I'm not sure it made it. No confirmation on the PM from the forums, and they're not in my sent items. I'm trusting the digital postal service here. :-D

Sorry, I don't think I was being very clear on what I was saying... see below... This is what I was wondering, if they're applying a realistic filter curve when you check that box that simulates headset use, or using a different sound file, or just damping down things by adjusting gain or something.

There is a checkbox in the audio options to simulate wearing a helmet that I use when I'm wearing headphones. I wonder if that uses a different sound bite, or if it just attenuates the sound levels a bit.

Bah, I'm definitely not angry here. I'm tired today (on call for work, dealing with some insomnia, etc.) and maybe my sarcastic humor is showing through a little more abrasive than it usually does. Trust me, I'm deadpan and slightly amused at the moment, and was when I wrote my response. Sorry if it came across wrong. I'm a bit weird, so not everyone gets me. I just don't play as well on the public playgrounds as I used to when I was a younger biomass. :-D

Yes, you're correct. I'll admit that, which I thought I already did when replying to Snoopy's post correcting me the first time. You don't need to hate to break it to me, you're not upsetting the balance of my delicate little world here. :huh: Snoopy pointed out that the sound was recorded while sitting in an actual A-10C, so that's definitive enough for me. I've never had the luck to even see one in person, let alone hear the sound from outside or inside. I wasn't thinking the engines were different, I was pondering the possible lack of sound insulation between the two plane styles; regional jet being more civilian and commercial where a military jet might not focus so much on sound insulation as armor, systems, etc.. I was strictly going off the way it sounded before the patch and after the patch. Now that I know, it's no big deal. I can even turn the volume sliders way back up and hear everything else in better detail, since the old engines drowned out so much of everything. Anyway, I was pondering the whole fiasco that started with my ATC and Betty chatter. I wonder if the whole thing was brought on by Vaicom Pro. I still have not had anyone confirm or deny the existence of symbolic links named "redirect" inside the A-10C and ATC sound file directories. I'm interested in if this was a DCS or Vaicom issue, and where the bug originated. __Redirect sounds like the sound redirect to second sound card switch inside Vaicom, and the "disabled_player" directory sounds like how Vaicom disabled the player pilot calls.

OK, just for completion in case someone else comes looking for this same issue. I have everything working now. The symbolic link redirects are in and that solved the ATC and Betty issues. I looked into the "sounds\speech\sound\eng\common\disabled_player" and that is how Vaicom Pro is disabling the player speech, so those are expected error messages. All else seems to be working fine now. Now I'm experiencing the same thing other people have reported; Betty telling me to pull-up when I'm 1,500 in the air and flying level. Seems it's locking onto objects in the distance when it happens.

OK, I think I have most of it working now. I was able to create symbolic links (mklink /d) "sounds\speech\sound\eng\common\redirect__atc" and "sounds\speech\sound\eng\a-10c\redirect__a-10 vmu" pointing to "Sounds\Speech\Sound\ENG\Common\ATC" and "Sounds\Speech\Sound\ENG\A-10C\A-10 VMU", and now I'm hearing speech again. I'm still missing some sounds though, and looking through the logs it's still saying things like "ERROR SOUND: can't load wave: "sounds\speech\sound\eng\common\disabled_player", so there is that to track down now. But symbolic links worked, if someone can confirm this is how it's set up on your load.

Can anyone with a working ATC and Betty voice confirm something for me? In the DCS log file it's telling me it can't load sounds located at "sounds\speech\sound\eng\a-10c\redirect__a-10 vmu\messages" and "sounds\speech\sound\eng\common\redirect__atc". I have folders at \Sounds\Speech\Sound\ENG\A-10C\A-10 VMU\Messages and "\Sounds\Speech\Sound\ENG\Common\ATC", but nothing for redirect. Is this just a Junction Point redirect to the same folders listed? Looks like something didn't fully work on the last patch process.

OK, tracking down the problem, in the dcs.log file I see a ton of "ERROR SOUND: can't load wave: "sounds\speech\sound\eng" messages for pullup, altitude, begin/end PTT, etc. Now I just have to figure out why.

Maybe I just got used to the internal cockpit sound when it was "wrong"? I have no basis for comparison as I've never sat in the real thing. It just seems so quiet now compared to before the patch. I can deal with all that, really. The real focus right now is trying to figure out why B1tching Betty and ATC won't work audibly anymore.

The problem I'm having is, since the update, I can no longer hear the BIT Test "pull up, pull up" voice. I can see the text on screen, but nothing voice happens. Also, the radios aren't working at all anymore. They're on T/R and tuned to correct frequencies, but when I push the PTT hat I get nothing. If I try using VoiceAttack + Vaicom, no chatter and no mic PTT radio sound, just that "bloop" sound that usually happens if I don't have radios on or on correct frequency, yet I'm on correct frequency. The ATC talks to me when taxing around and taking off / landing, but all I get is text on the screen, no longer getting anything voice based anywhere. Is there a new setting I need to find and turn on? And yes, the sound is way different. Something definitely sounds odd when spooling up the engines, like I'm sitting in a nice, plush, business jet instead of a beast of a weapons platform.

Found the fix, I wasn't opted into openbeta, so the models weren't there and the planes in those spots were defaulting to A-10C as the first option in the list. Opt in to openbeta, and everything is working without modification now. I left details over on the Persian Gulf thread.

So yeah, found the fix to the invalid frequency issue Found the issue with my installation. I downloaded the new version today, and this started happening when trying to load or save. [CAP] F-14B - (Carrier) 1: Invalid frequency 124 MHz [CAP] F-14B - (UAE - Al Minhad) 1: Invalid frequency 124 MHz [CAP] F-14B - (UAE - Al Minhad) 2: Invalid frequency 124 MHz [CAP] F-14B - (Iran - Bandar Abbas) 1: Invalid frequency 124 MHz [CAP] F-14B - (Iran - Bandar Abbas) 2: Invalid frequency 124 MHz [CAP] F-14B - (Carrier) 2: Invalid frequency 124 MHz [CAP] MiG-19P (UAE - Al Minhad): Invalid frequency 124 MHz [CAP] MiG-19P (Iran - Bandar Abbas): Invalid frequency 124 MHz So that MiG-19P issue has multiplied to include the F-14B. They're defaulting to the A-10C as the first plane in the slot since my version of the game doesn't have those models. Then I realized that my Steam version wasn't opted into the open beta. Set that to openbeta - Public beta versions, and the error went away. So yeah, dummy me, forgot to opt in. :music_whistling::smartass::pilotfly:

What I started doing is finding MiG-19P in each mission and setting the radio to 251. That fixes it while leaving it as a client playable craft.

Mission cannot be saved due to errors - MiG-19P Invalid Frequency Hey DeadlyFishes, thanks for the hard work. I'm new to DCS, and new to TTI, just trying the single player stuff before jumping into MP so I can get used to how it works and I don't get in anyone's way. I've grabbed the (until today) most recent version of the single player files, 1.50, and I'm having trouble going from mission briefing to play. So far I've tried Nevada and Persian Gulf, and it's throwing an error at me saying the mission cannot be saved due to errors. [CAP] MiG-19P Invalid Frequency 124 MHz. I found that in the Nevada file, changed the MiG-19P plane (A-10C) from client to an AI level, and was able to get into the mission. I've searched around for a few days and I can't find any info on this, so I'm wondering if I have something set up incorrectly. Any ideas I can try without having to modify this craft in mission editor? Thanks!