psimester

Hi vadriver. Sorry, long time user of VoxATC from the days of DVD with four voices included and I still think of them as the 'default'. Although I've upgraded to 7.42 I kept the voices from the DVD which I believe are AT&T Natural Voices. I think the suggestion is probably correct that I'm hearing verb and noun pronunciations of the word wind, where what I think is 'line' may actually be 'wined'. It's just strange that it's one common word that I don't remember ever having had a problem with until recently. I've briefly read a section in an AT&T manual about creating User Dictionaries for AT&T voices. If the pronunciation gets to really annoy me I may investigate further.

An update in case anyone else hits this issue. I've done further flights using the default VoxATC voices and found the mispronounciation of 'wind' to vary; there appears to be no logical pattern to which voice gets it right or wrong, and whether it's Tower/Approach/ATIS. It just mystifies me why this has suddenly started happening after having used the program for years.

Yes, VoxATC 7.42 and Windows 10. I spent some time sitting at my usual departure airfield, setting one voice at time, listening to ATIS and trying to pinpoint where the problem is. I went through each individually and they all pronounced 'wind' correctly! I then switched them all back on and still ATIS was coming through correctly with each voice. I then tried a short flight with my usual settings; ATIS at departure and arrival pronounced 'wind' correctly, but both takeoff clearance and approach pronounced 'wind' as 'line'. Not sure where to go from here!

I just use the original VoxATC voices together with the downloaded VoxPop voices, as I've done for years. They've not had any trouble pronouncing 'wind' until very recently, but I can't think of anything I've done which would have changed the sound of that one word.

Something very strange has happened. I've been content to put up with the occasional odd pronunciation in VoxATC; re-addback instead of readback, glid eslope instead of glideslope etc. - at least they're consistent. I've read a couple of posts that give some instructions for changing pronunciations but I've not taken the plunge yet. However, suddenly the word 'wind' has started being pronounced 'line'. Not the end of the world as I know the order of information from ATIS and from tower on approach so I know what is meant, but it's a little annoying that it's suddenly changed to a completely different word. Even when I'm expecting it, I find my brain is so busy trying to figure out why I'm hearing 'line' that I miss the bit that matters! Presumably a tiny glitch in a file somewhere has changed the pronunciation. Has anyone any idea how this has happened and can recommend the easiest/best way to correct it? Thanks.

Thanks so much for the informative reply - what would this site do without you??!! I must admit that I'd assumed VoxATC, being primarily communication software, would be pulling radio frequencies from FSX when the Indexer was run. It didn't occur to me that it would already have frequencies included. Having got to grips with .bgl files I've now discovered the joys and potential of .xml! For someone who started flightsimming with his first ZX Spectrum that's no mean feat 😄 I'm aware of Navigraph et al, but I only get to fly two or three times a month so it's really not worthwhile for me at the present time. I'm very happy to have reasonably realistic radio comms with VoxATC and a radio panel; if one or two frequencies are not current 'real-world' I can live with that. In fact, many of the paper charts I've accumulated are old enough that I can use them with FSX 🤣 I just needed to get VoxATC and Plan-G singing from the same hymnsheet. Thank you again for your reply.

OK, this may sound a daft question, but where does VoxATC look to get its radio frequencies? I use Plan-G for flight planning, which is pointed to the FSX Scenery.bgl, and decided on a short VFR flight to Shoreham (EGKA). Plan-G gave me an ATIS frequency of 125.3 for Shoreham, however VoxATC told me to use 130.97. I was able to listen to ATIS on both frequencies. 125.3 is the 'old' FSX frequency, 130.97 is the current real-world frequency, so they're both 'right'. I'd like to have a single frequency that I can look up with confidence prior to my flight but I can't figure out where VoxATC has got the 130.97 frequency from. I've used ADE to check the ATIS frequency for the airfield, but every .bgl file I can find gives only 125.3 - nowhere can I find any mention of 130.97! I've used Windows search to find all .bgl files that have Shoreham or EGKA in the name and none has a frequency of 130.97; I've even looked at the .bgl files that I've switched off. Clearly I'm missing something, but can anyone tell me what??? I could simply use ADE to set the ATIS frequency to 130.97 so Plan-G agrees with VoxATC, but that rather skirts the issue and I could well come across the same problem on future flights. I'm using Orbx Shoreham, Orbx England, Orbx Global, UK2000 VFR Airfields, MyTraffic.

I've tried at various airports, using IFR, VRF and no flight plan. I've also run the Indexer a number of times. I did notice on latest trials that VoxATC is briefly reporting 'unknown aircraft' before throwing up the Fatal Error. I'm not sure how it becomes an unknown aircraft when I'd previously used the VAPanelSelect.exe to add the panel to the aircraft. I've again checked the panel.cfg against other aircraft and all the relevant VoxATC lines and windows appear to be there. Thanks for your interest and suggestions, Minister. I may try again from scratch one day and see if I can get VoxATC working with the DLC aircraft, but for now I think it's going to remain one of life's little mysteries 🤔

Many thanks for the reply. I confirm that the panel.cfg file does have the correct VoxATC entries. I've looked through the error log and can only immediately find known 'oddities' (mentioned in another post): Exception while initializing Asti - Cannot find AstiInt.dll Exception while intializing iFlyInt - Cannot find iFly.dll Object reference not set to an instance of an object. Here are the last 10 lines as requested: 19:53:39.8186061 BGLFILE 78833.vidx 19:53:39.8186061 BGLFILE 78877.vidx 19:53:39.8186061 BGLFILE 78850.vidx 19:53:39.8186061 BGLFILE 78901.vidx 19:53:39.8196032 BGLFILE 78723.vidx Object reference not set to an instance of an object. at com.intworkings.voxatc.Dispatcher.SetLocalFSFlightPlan(FlightPlan fpIn) at VoxATCServer.VoxATCServer.SetupLocalFlightPlan() at VoxATCServer.VoxATCServer.InitVoxAtc() 96563124 Ins Text set : FATAL ERROR! disable VoxATC As I mentioned in my previous post, all other default and third-party aircraft appear to be OK and I've tried a number of add-on and default airfields. Any observations or ideas greatfully received! 🙂

Hi. Many thanks to those who've posted in the past with suggestions for getting Vox panels to appear in FSX Steam DLC aircraft! I only have one DLC aircraft, but it's one I like to use for training and it would be great to get it working with VoxATC v7. Sadly, whilst I have no trouble getting the panels up and the voices to go through the initialisation process, it always pauses at the end and then gives the ominous 'Fatal Error'. I've tested various default and add-on aircraft at different airfields and they all work fine; it's just the Carenado DLC that trips it up. On that basis I don't think it's the voices - more likely something to do with the DLC. However, no-one else seems to have a problem with DLC aircraft once the panels are loaded so I'm at a bit of a loss. The aircraft .cfg looks OK and the speech marks seem to be in the right places. Anyone else had this problem?

I, too, have tried to upgrade this great bit of software from v6 to v7 and been confused with the different websites and companies. I purchased on the RC Simulations site and swiftly received an email from carol@rcsimulations entitled 'Your files for download' with a link to download a file. However, the link went to a page which is no longer working. Over the next hour or so I received further emails from Carol advising that my order was ready for dispatch and then that it had been dispatched, followed by an email from RC Simulations saying that my order had been invoiced. Each email appeared to be basically a copy of the invoice. I then received a a further email from Carol with three attachments; two further copies of the invoice and my Right to Withdraw. I did email Carol just before Christmas asking for clarification on what I needed to do next but was merely told to enter the code. The RC Simulations site clearly states 'Original Serial no Required. Serial no Are Not Automated' so I assumed that at some point I would need to re-enter my old v6 code, but I have never been asked for it. I have since noticed that there's a Registration page on the VoxATC site which does ask for your v6 serial number before taking you to the PayPal site. Only this morning have a looked again at the two identical invoices attached to Carol's email and noticed an additional line with a code. Duh! I've tried this code to register and it worked immediately. Moral of the story - when you receive multiple emails with multiple copies of an invoice, study each one and look for an extra line!

Hi Josh, Did you ever sort your issue? I'm having the same trouble - I used to have VoxATC on Vista and it worked fine, but I've recently transferred it to Windows 8.1 and now I keep getting the 'fatal error' message. I vaguely remember doing something with the language when I had it on Vista but it was sooo long ago I can't remember what I did! Paul