Sign in to follow this  
Dalton0190

Version 6.45 Released

Recommended Posts

Help AVSIM continue to serve you!
Please donate today!

It's at http://www.voxatc.com/Home.aspx/News

 

Changelog:

 

23 June 2014 Version 6.45 Released

This release greatly improves and fixes problems previous versions of VoxATC had with interfacing to FSX or P3D. There are therefore improvements to AI behaviour and problems with VoxATC spontaneously pausing or being stuck paused have been fixed

Share this post


Link to post
Share on other sites

...works great so far!  :wub:

 

smooth and reliable with Windows 8.1 and Prepar3d 2.2

Share this post


Link to post
Share on other sites

Great news! Just to double check:

 

1) 6.45 is a full installer, so the previous version must be uninstalled?

2) 6.45 no longer works with VoxPop server, so it has to be uninstalled?

3) Buy new voices to replace the VoxPOP voices?

 

Thanks for the help once again!

 

P.S reason for the questions, that I'm live streaming a FSX flight tomorrow and thinking of upgrading VoxATC before the flight.

Share this post


Link to post
Share on other sites

Hi Jarkko

 

1. Yes

2. I don't use it anymore. And it is not working either. So yes, remove it.

3. No idea at the moment. I use the free ones.

 

 

Best

Patrick

Share this post


Link to post
Share on other sites

Great to hear crashmax!

 

Following install instructions on the download page - yes uninstall current version before install. I didn't see the voxpop voice support issue, so would expect them to work also - after reinstalling them in new system perhaps?

 

I will install tonight or tomorrow and give it a spin.

 

John

Share this post


Link to post
Share on other sites

Ok, so I have now upgraded from 6.05 to 6.45 and did a flight from CYEG to KPDX. Some positive things and a handful of problems.

 

Good things first:

 

1) I got VoxPop working with 6.45.

 

After the install, the VoxPop server refused to start. Lucky for me, I had saved the working VoxATC folder before the uninstall.

 

After I replaced the voxpop folder inside the new installation folder (broken) with the one found in the old (working) installation folder, the VoxPOP came alive.

 

2) I like how the AI traffic is handled in the new version.

 

Next the not so good parts:

 

1) I wasn't given an initial altitude for the departure (vectoring). The problem is that there was no altitude info in the charts or the navdata. I decided to climb to 5000 and hope I got it right.

 

2) The radio ping-pong is still there: After contoller Y send me to controller X, the Controller X sends me back to Y after initial contact.

 

3) VoxATC becomes unresponsive for couple of seconds after reading back instructions. It wan't respond to any keyboard or joystick click commands.

 

4) Arrival to KPDX was a disaster. I was kept quite high. Once I requested lower for arrival, I was sent down to 6000ft. Five seconds later, I was told to descent to FL180... 

 

5) VoxATC ATIS for KPDX didn't work. It was reporting default "ISA" weather (temp 14, winds calm, baro 29.91, runway 3) even though the FSX ATIS was reporting the correct weather (winds from 110 at 4, baro 30.09, runway 28R) in the background.

 

6) Approach was even worse, than arrival: "Fly heading 145, descent to 2900ft". Then couple of seconds later: "Fly heading 360, climb and maintain 8000ft". ATC had me flying away from the airport, and froze. Once I had flown away from the airport, even crossed the start of the STAR (SEA VOR), and still no directions from ATC, I restarted VoxATC.

 

7) After the restart, all went fine until vectoring on the downwind for rwy28. I was told to descend to 2900ft. As I was flying in the dead of night, I wondered why the aircraft was telling me that my gear should be down.

 

I soon realized, that the radio altimeter was showing about 300ft even though I was flying at 2900ft. I was flying into a mountain! Had to manually climb like crazy, while ATC kept on telling me to immediately descend to 2900ft.

 

8) Taxi instructions were odd at KPDX. I was told to taxi to G26 via T to B6 and hold short 28L. The problem? Taxiway Tango would have taken me direct to gate G26. No need to cross any runway using B6.

 

So... The betting handling of AI, especially during cruise is great, but... there are still a lot of things, that can and do go wrong.

Share this post


Link to post
Share on other sites

Jarkko,

 

What was your full FSX flight plan and altitudes expected (e.g. SID/STAR whatever)?

Share this post


Link to post
Share on other sites

One flight from PAKT PAJN this morning in Majestic Dash-8 Q400.  Very pleased with results.  No Fatal errors, although I followed the ATC (dodging mountains as best I could) rather than selecting RNAV approach like I would normally do.  So...I'll see how it does on future flights - but so far I'm very pleased (no pause problem and no loss of connection in the middle of flight).  The only issue I had was on taxi for takeoff - vox window told me to taxi to the runway while the controller continued to ask me if I copied his last request.  I tried again - but it had already recognized that I was cleared to taxi per the message on the screen.  He continued to ask me if I copied until I was taking the runway - at which point I was given the message to state I was taking the runway - as one would expect to see.  So...in spite of this glitch - it recovered nicely and the flight went on without problem.


I found that it didn't want to install when I had disabled my UIAutomationCore.dll files (fix for fsx freeze on some systems).  The installer worked after I re-enabled those files.  I think I can disable them later if I get freezes during flight.  I've had freezes with Majestic (even with the new UIAutomationCore file), so have those disabled normally unless if have issues with other programs (like the newest version of Plan-G).

 

I would also suggest repeating the update process after install (rwy number update, indexer, and UT2 bridge if installed).  This might clear up some issues.  While I see that the indexer ran automatically on install, I don't think the rwy number updater did.  That's why I would redo this entire process.

 

John

Share this post


Link to post
Share on other sites

Jarkko,

 

What was your full FSX flight plan and altitudes expected (e.g. SID/STAR whatever)?

Here is the plan for CYEG to KPDX:

 

N0447F360 DCT YEG DCT YXC/N0446F380 J505 SEA HELNS5

 

This means that my FSX flight plan started from YEG and ended at SEA with cruise altitude of FL360

 

I think I was assigned DEVON1.20 departure and HELNS5.SEA arrival.

Share this post


Link to post
Share on other sites

John,

 

"I've had freezes with Majestic (even with the new UIAutomationCore file), so have those disabled normally unless if have issues with other programs (like the newest version of Plan-G)."

 

The problems with install and others you mentioned is not normal .. and you never really sort out what software is causing which problem. Unless, it is a widespread problem (many pilots reporting it)  and a vendor can duplicate it.

Share this post


Link to post
Share on other sites

Not sure what you're trying to say  Vonmar.  There were only two problems I specifically mentioned regarding Voxatc current version:

 

1.  Vox repeatedly asking if I copied last message after giving me "taxi to runway" message.  For this I think is a minor bug in current version.

 

2.  Install problem (failed after "select simulator", and wouldn't run runway indexer).  This I assumed was due to my disabling the file UIAutomationCore.dll.  My assumption was apparently correct because the install was successful after enabling those files on my system.

 

I post these for two reasons - The first is (with my problem number 1) that I think is a minor bug that might need tweaking by the vendor.  The second (with problem number 2) to alert others who may have the FSX tweak of disabling that dll file, that they can properly install Voxatc by restoring that file.  This is not a problem with the software for the vendor to deal with, but a 'heads-up' to other users who may have not identified the problem (same with the Plan-G app) that they need to restore their dll file to work these programs.

 

Overall my first test flight went very well with the minor exception of that noted - a great improvement over version 6.34.

 

John

Share this post


Link to post
Share on other sites

Jarkko,

 

You are not sure of the departure that was in your plan?

 

I seen that you also had some problems with the initial installation .. folders .. whatever ...

Maybe something got messed up?

 

You mentioned problems with the arrival ..... did you not use the HELNS5 STAR .. which has mandatory crossing altitude and route.

You did not mention exactly where you were at which (wrong) altitude / speed / waypoint(s) during the STAR ....

 

Maybe it would be a good Idea to do the Sample IFR flight .. then see if there are problems.

 

Are you away from your PC and cannot check on specific information while posting here?

Share this post


Link to post
Share on other sites

Hello Vaughn,

 

 

 


You are not sure of the departure that was in your plan?

 

I didn't have departure in my plan. Only DCT YEG. VoxATC dynamically assigned me DEVON1 from rwy 20. FWIW I have the whole flight recorded and can go over and verify these if need be.

 

 

 


I seen that you also had some problems with the initial installation

 

Only the same problems with VoxPop server that other users are having. Just wanted to report, that I found a work around.

 

 

 


did you not use the HELNS5 STAR .. which has mandatory crossing altitude and route.
You did not mention exactly where you were at which (wrong) altitude / speed / waypoint(s) during the STAR

 

Yes, I flew the HELNS5 with SEA transition. I was about 10nm away from the end of the STAR which has a hard altitude limit of 12000ft. As I was being kept at FL230, I requested a lower altitude.

 

I was then told to descent to 6000ft which work well for the approach vectoring. Only a few seconds later, I was told to descent to FL180  :huh:

 

 

 


Are you away from your PC and cannot check on specific information while posting here?

 

I was doing a live stream using ProATC, so I was unable to answer. The flight had the same ATIS problem and therefore wrong runway assignment. I will soon post more info.

Share this post


Link to post
Share on other sites

Ok, so here is a link to the flight I just did:

 

http://www.twitch.tv/virtualfreightdog/b/541451113

 

1) At 57:26 you can see me requesting the latest weather using TOPCAT. The winds were from 250 at 19kts.

 

2) At 01:09:52 I listened to the VoxATC ATIS for the first time. Winds were reported as calm and runway in use was 06L.

 

3) At 01:21:32 I listened to the ATIS once more. You can see the FSX ATIS in text format on the screen as follows: winds 250 at 19 (the same as TOPCAT) runways 24L/R in use, but... if you listen carefully. VoxATC ATIS was reporting the same info as before. Winds calm and runway 06L in use.

 

4) At 01:23:46 VoxATC clears my for ILS06L approach which would give me 19kts tail wind during landing. This is why I request ILS24L approach.

 

5) From 01:37:29 forward, you can see from the navigation display, that the winds stay locked at 250 at 19kts just as reported by TOPCAT.

 

So to me, this seems like a VoxATC problem, because FSX ATIS got the winds and the runway correct.

Share this post


Link to post
Share on other sites

Jarkko,

 

On this LXGB-LEPA .. was the Departure VOXatc Wx /ATIS and Dep RWY correct?

Share this post


Link to post
Share on other sites

Yes, at 03:25 I listened to the ATIS and it matched the FSX ATIS.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this