I contacted Tegwyn on November 4th to inquire about the update. He responded that he was making progress and that it might be ready in about a week or so. Such is the life of a software developer.

Looking forward to this update. I think a few things went wrong with the last one (v6.46).

Looking forward as well. I don't have any issues with v6.46 like some, (must only like certain pc configs), I guess thats why Tegwyn provides a generous trial version, hope he can fix it for the poor souls missing out. My only concern, destination weather ?

The destination weather issue is definitely fixed in the beta version that iam testing. Maybe it's me, however I have also noticed a Suttle improvement in the voice recognition also. Hopefully it's realesed to everyone soon.

The destination weather issue is definitely fixed in the beta version that iam testing. Maybe it's me, however I have also noticed a Suttle improvement in the voice recognition also. Hopefully it's realesed to everyone soon.

Not for me, (ASN) destination forecast 130/12, Vox 330/0 ? Tailwind landing on RWY 34, should have been RWY 16. Clean install of v6.49, no other probs ? Anyone else ?

 

Cheers

Its a bit shaky my end as well

"Tailwind landing on RWY 34"

 

Which airport?

 

A default airport?

 

FSX or P3D?

 

What did airport ATIS report during your descent ? And, was it a current report (accurate) Zulu time?

YSSY (Sydney default airport),FSX, ATIS 330/0 (fsx default weather), ASN 130/12, very disappointed.

P3D or FSX?

 

What was your Departure airport?

 

Was your departure ATIS = ASN weather ?

 

 

 

What did airport ATIS report during your descent ?

And, was it a current report (accurate) Zulu time?

YMML (Melbourne default), ATIS is always correct on departure. Reported fsx default ATIS 330/0 on decent, as per usual (current zulu time). FSX

Does it happen on all flights or how many fiights has this happened to you?

This is my first flight with v6.49, don't have that many opportunity's to fly these days. The 2 hr flight went perfect untill decent.

So, during descent when you knew you had the wrong Voxatc ATIS (because ASN was different) you did not try the old "fix" to Disable/Re-enable Voxact to get correct ATIS?

 

Actually, ASN report for your plan should show dep and arr winds before you depart ... did you see that repoer for your flight plan?

Did not try the old usual fix (disable/ re-enable), I thought that was the whole point of the new version. Yes, arrival meter reported 160/10 upon departure and changed to 130/12 later in the flight, I set up my fmc at departure on the ground, in anticipation of R16L.

"I thought that was the whole point of the new version"

 

If it installed properly ........ did you uninstall the old version first then go thru the whole setup on the new version?