Thanks all, I'm running 12gb of memory so there shouldn't be a shortage there. I've found that cutting way back on the additional voice packs used reduces the VAS use considerably. I haven't yet had a recurrence of the OOM since rebuilding the cfg file, that may if course be down to the automatic setting of LOD radius to 4.5!

 

Mike, the exact phraseology can be worked around as stated, but some of the procedural errors at present can't be until they are fixed by the author. There is a specific problem around Liverpool and Manchester where airspace is not recognised as the correct class and consequently Vox gives you unrealistic instructions. For me the issue is resolved by only flying around Liverpool when there's a vatsim presence

 

K

Vox seems (shoot me down in flames here if I'm wrong!) to use part of FSX's 4gb virtual address space. It seems to be that with heavy addons and scenery like the NGX being used, I get OOM errors using Vox, following investigations using Process Explorer. The amount of VAS Vox takes seems to vary depending on the number of voice packs I have active. I invested a lot of money in every voice pack I could get my hands on, and when they are all in play Vox uses over 1gb of VAS!! Add in the 2.2gb fsx uses just with the NGX on the ground and there's hardly any left for scenery etc. So I can't fly the NGX in heavy scenery with demanding weather and use Vox with all my voices :( If Vox could be altered so that it runs as a standalone prog outside of FSX and therefore didn't use any of FSX's 4gb VAS then it would be a much more useable product for me. I've emailed Tegwyn tonight about it so when I get an answer I'll update this post. I may be entirely on the wrong track - we'll see!

 

Reply from Tegwyn:

"Sorry about the delayed reply. I've been stranded away from the office for a couple of weeks with no way to get my messages.

 

VoxATC runs as a seperate process and as you are running win 7 64 should not be using any of the VAS allocated to FSX.

 

VoxATC does have its own gauges in FSX for the prompt screen and recent comms whic run in FSX, but these should not use a lot of memory.

 

VoxATC does generate its own traffic in FSX which may take up more memory than the inbuilt traffic and push FSX over the edge if it's already loaded with other add-ons."

 

On the basis of this I'm going to do some testing with different traffic levels to see what if any discernible impact there is on memory use.

K

Any news on the next version of VoxATC?

I recently asked Tegwyn for status of the next version and here is the response.....(looks promising)

 

 

Hello

 

It's good to know you enjoy VoxATC.

 

The next release of VoxATC is in the final stages of beta testing. It will improve ground handling mainly. Hopefully it should be available in a month or so if we don't find too many bugs in the mean time.

 

Regards

 

Tegwyn West

Fantastic, just got the DVD and find that it's a lot better than the demo, lots of voices loaded and really like it. I bought it to help train me up for VATSIM and I notice the difference already as am focusing on what's being said and not how.

<br />It will improve ground handling mainly.<br />

 

Hmmm... This is a good thing, no doubt about that.

 

Personally I have no problems with current ground handling. Area where I would like to see "improvement" is the altitudes used when being vectored. To give you and example:

 

Yesterday I did a short hop from KBLI to KSPB. There is some terrain surrounding the KSPB area. While being vectored for LOC runway 15 approach, I was told to descent to 1100ft (1000ft above field elevation).

 

I was in the clouds, when I noticed that the radar altimeter was telling me that I was very close to the ground. This was soon followed by a terrain warning.

 

Now then. How could this be "fixed"? I checked the Navdata that VoxATC uses. The first waypoint for LOC15 approach has an altitude restriction of 2300ft or above (real world charts have an additional 3200ft or above that is missing from the Navdata).

 

If VoxAtc would have requested my to maintain 2300ft, I would have been fine. Now I had to avoid the terrain without visual on the ground.

I believe the developers are about to release a large or fairly large update anytime in the coming days or weeks.

 

Xplane version is about a year away.

 

Sent from my HTC One X using Tapatalk 2

Is VOXATC being supported by the developer? ... doesnt look like it to me ... which is a shame. Too may developers place too much hope on other users helping out others with questions or problems.

 

FS2Crew and OpusFSX (along with many others, just the 1sr twi to spring to mind) give A1 developer support.

 

I love VOXATC but the developer support is NIL which does not seem right for something which costs nearly £100.

I asked about Windows 8 support a week or so a god and got a prompt reply saying yes it was from the developer so he's still about, just not on these forums so often maybe?

Any time I've sent Tegwyn an email, he has responded promptly. As far as I know, he doesn't frequent this forum.