So today I almost completed a full flight from Houston KIAH to Kansas City KMCI in P3D. VoxATC 7.3 beta performed flawless, while flying a real time flight based on United flight 1433. By the way, I like the fact that you don't have to say your call sign number by number, and it sounds more realistic to real world when you can just say "fourteen thirty three", very cool. I was flying the Aerosoft Airbus A320, using AC16 for my real time whether. Took off from FSDreamteam's Houston KIAD, and landing at TropicalSim Kansas City KMCI. Visibility was less than 1/2 mile during landing.

 

My first issue was at my approach descent to 8,000 my Airbus speed kicked off and started to go crazy, it wouldn't react to any of my controls. Once I got a hold of the situation, it started to descent from 8,000 to 4,000 without a problem. Once I captured the glide slope and was given the clear to land by VoxATC, I got to minimum and still couldn't see the ground. I was thinking about testing to missed approach, but I didn't encounter any issue until I was about 100 feet off the ground, still couldn't see it, it was total soap out there, all of the sudden my airspeed increase, and I couldn't land. It was too late to hit the missed approach and I crashed on the ground. I was also using FS2Crew, which has always worked fine for me, but this time my co-pilot was not help during my approach commands. Never happened to me before, always been able to land this aircraft even in CATIII conditions, but I don't know what happened here. It was my first long distance flight with VoxATC 7.3 Beta. Could it be something to do with VoxATC? Can't say for sure, because indications were normal all the way to my landing clearance. I'm at a lost, but on this one I'm not blaming VoxATC, I'm just giving my initial flight experience with this latest Beta version.

By the way, this is not a bug, but a kudos. I have never been able to fly with P3Dv3 with more than 10% of aircraft traffic, and 0% GA traffic. However, I'm not sure if it has anything to do with VoxATC 7.3 Beta, but today I was able to set VoxATC at 40% traffic, and my airports were full of aircrafts, and not a drop in frames or loss of VAS. Not sure what's the trick, but I like.

That's because VOXATC doesn't worry about maintaining a cache of flight plans for all AI aircraft worldwide. It just creates and controls the AI aircraft within the user's  reality bubble. One can get even more performance  improvement  at big airports by using the FSUIPC traffic limiter  options.

5 hours ago, jabloomf1230 said:

That's because VOXATC doesn't worry about maintaining a cache of flight plans for all AI aircraft worldwide. It just creates and controls the AI aircraft within the user's  reality bubble. One can get even more performance  improvement  at big airports by using the FSUIPC traffic limiter  options.

Thanks for the tip, but what numbers would you input in the FSUIPC if you want to keep it around 40% traffic, do you say 40, or is it a different numeric value?

Use whatever setting that you want in VOXATC (40%). The main setting in the FSUIPC limiter is the maximum number of AI aircraft within the user's reality bubble (I tend to use 100-150). Read up on the FSUIPC traffic limiter, as it has a bunch of useful options. Most are locational (on ground, in air, etc.). But there is also an FPS setting which doesn't limit the AI traffic unless the frame rate goes belong a user specified value.

Finally, a flawless full flight from KIAH to KTPA, and not a glitch to report, with the exception of ATC asking me to repeat myself twice, and that's not bad at all. This was on P3Dv3, Aerosoft Airbus, FS2Crew, AS16, FSDT GSX, and plenty of traffic on the ground, weather was mostly overcast. Used a real world flight from FlightAware, United 1814 from this afternoon.

I decided to try the update to see if there was an improvement.  I managed to contact heathrow departure/director this time unlike before.  However, the moment I get the instruction from ATC to do so, my autopilot fails on the FSLabs A320 and will not turn on again (A/P d/c with the rudder pedals swinging wildly and the plane yaws hard when A/P switch is pressed again but will not stay lit).  Could be an conflict with these programs?  It is really strange. It seems to happen at some airports and not others.

P3D, FSLABS A320, Aerosoft Heathrow, AS16/CA, PFPX, LevelD navigraph data installed, ORBX Global, LC Europe, Vector, GSX.

it would be great it would work.  I tried another ATC program that works but just doesn't seem as realistic, especially because there is no control of AI and no voice.  Please help me use the bus with this program, thanks. 

 

 

It sounds like a SimConnect issue of some sort. Try some other aircraft to see if you can duplicate the issue. Since we now know that VOXATC is alive and well, I suggest that you use the official contact form for the beta:

http://voxatc.com/Contact.aspx

You may eventually need to submit a log file at some point, so if asked to do so you will need to enable logging in the VOXATC Advanced Settings utility.

I have beta 7.3 and it says the demo has expired. I download 7.3 yesterday, and uninstalled 7.2 today. I then rebooted my pc and installed 7.3. When I started p3d v3 I got the error message. 

 

Any sugestions? 

The 7.3 beta installation instructions  said to uninstall  the previous 7.2 beta version first. You probably  have a muddled up bunch of entries now in your Windows registry from the two versions. PM me and I'll try to walk you through  a cleanup.

6 hours ago, jabloomf1230 said:

The 7.3 beta installation instructions  said to uninstall  the previous 7.2 beta version first. You probably  have a muddled up bunch of entries now in your Windows registry from the two versions. PM me and I'll try to walk you through  a cleanup.

My 7.2 version expired. I had resumed flying 6.52. When the Beta 7.3 came out, I uninstalled the 6.52 (cleanly) and installed 7.3. It has been working fine on my end.

It's the 7.2 beta info that's still hanging  around in the cobwebs of  Damian03's Windows  registry. 

20 hours ago, jabloomf1230 said:

aIt sounds like a SimConnect issue of some sort. Try some other aircraft to see if you can duplicate the issue. Since we now know that VOXATC is alive and well, I suggest that you use the official contact form for the beta:

http://voxatc.com/Contact.aspx

You may eventually need to submit a log file at some point, so if asked to do so you will need to enable logging in the VOXATC Advanced Settings utility.

The NGX works OK no problem with A/P.  But the A320 Fslabs disconnects the a/p.  I've had the disconnect happen either on departure or approach at random times.  There is a slight pause and the FO stops controlling coms before it happens.

Another problem is that I had 3 TCAS warnings on my a320 flight to Dublin from Heathrow.  Isn't it supposed to keep planes separated?

I sent the message about the A320 A/P to the dev.

 

On ‎4‎/‎26‎/‎2017 at 3:31 AM, nam1394 said:

Do me a favor and start a flight at EHAM and listen to the ATIS. Let's see if you have the same problem as I do. This way we know if it is the scenery or my setup.

 

thanks in advance

I re-installed the product.  I'm having major issues with EHAM.  The VOX ATIS states two runways in use, one landing and one departing.  The P3D Atis has a lot of different runways.  That's not the issue though.  The thing crashes basically when I contact tower on arrival.  Fatal error later on when on the ground, no ground control recognition or service.  I also go OOM at EHAM all the time, so I always have to load up the landing from a saved flight.  I don't know whether VOX uses more VAS than usual, but the airport is very VAS intensive and I can't fly from heathrow or paris without going OOM on approach.  My settings are not high either, a bit higher than default but normal autogen.

 

25 minutes ago, Heathrow to Dublin said:

I re-installed the product.  I'm having major issues with EHAM.  The VOX ATIS states two runways in use, one landing and one departing.  The P3D Atis has a lot of different runways.  That's not the issue though.  The thing crashes basically when I contact tower on arrival.  Fatal error later on when on the ground, no ground control recognition or service.  I also go OOM at EHAM all the time, so I always have to load up the landing from a saved flight.  I don't know whether VOX uses more VAS than usual, but the airport is very VAS intensive and I can't fly from heathrow or paris without going OOM on approach.  My settings are not high either, a bit higher than default but normal autogen.

 

the ony way I believe vox will influence VAS is the amount of ai active

 

I discussed VAS with Tegwyn before and as far as I understand vox does not operate using any part of the sims 4Gb.

 

loading a saved flight for landing may be part of the cause, ive never done that.  It sounds as though vox is working fine though allocating one rw for use.

Edited May 1, 20179 yr by kevinfirth