I think I know my problem, does anybody use another drive for users files/appdata ? I have an ssd for my main programmes, as I do not want users files clogging up my ssd, I have users files on my conventional drive, I don't think vox is finding these files. ASN ask for the location of users files/appdata, Vox doesn't.

 

Your thoughts please.

"YMML (Melbourne default), ATIS is always correct on departure."

 

If VOXatc can get your DEP Wx it knows where to get ARR Wx.

 

Is your DEP Wx always ok?

"YMML (Melbourne default), ATIS is always correct on departure."

 

If VOXatc can get your DEP Wx it knows where to get ARR Wx.

 

Is your DEP Wx always ok?

That's a good point, yes it is always correct on departure. If I restart vox after TOD, it finds the correct destination weather ? I'm gonna reinstall vox into default location as I first planned and re-test. Thanks for ya help.

 

 

If VOXatc can get your DEP Wx it knows where to get ARR Wx.

 

This wasn't true in the past versions (haven't tested the latest version). This is because once you get airborne, ASN doesn't inject correct weather into FSX until you are 100nm away from your destinations (distance is configurable). VoxATC used the "default calm weather" to determine the ARR weather before the correct weather was injected.

 

This is also why the restart worked in past versions. So what I'm saying is that in the past, correct DEP weather didn't automatically mean correct ARR weather. Hence this thread asking about it.

Jarkko,

 

"This wasn't true in the past versions"

 

I was not talking about past versions.

 

I just quoted him as an example.

This wasn't true in the past versions (haven't tested the latest version). This is because once you get airborne, ASN doesn't inject correct weather into FSX until you are 100nm away from your destinations (distance is configurable). VoxATC used the "default calm weather" to determine the ARR weather before the correct weather was injected.

 

This is also why the restart worked in past versions. So what I'm saying is that in the past, correct DEP weather didn't automatically mean correct ARR weather. Hence this thread asking about it.

That's is a good point too, for me, the latest version is behaving the same as the last version. I am gonna reinstall and re-test today. How do you configure the distance ?

What have you found out?

What have you found out?

I think I have been too impatient. Im just gonna have to get quicker at configuring a 737 lol. Tegwyn was quick to respond with the below ( great service as always):-

 

You need to be within 60 NM of your destination for the simulator to start generating weather there and for VoxATC to pick it up. This has nothing to do with the appdata folders. If there was a problem, VoxATC would not be working at all.

I think I have been too impatient. Im just gonna have to get quicker at configuring a 737 lol. Tegwyn was quick to respond with the below ( great service as always):-

 

You need to be within 60 NM of your destination for the simulator to start generating weather there and for VoxATC to pick it up. This has nothing to do with the appdata folders. If there was a problem, VoxATC would not be working at all.

 

Is your arrival Wx correct and is approach getting you the correct runways based on current arrival ATIS (ASN)?

 

Or are you still getting your departure ATIS data when arriving?

 

Is ver 6.49 working with ASN for you?

Is your arrival Wx correct and is approach getting you the correct runways based on current arrival ATIS (ASN)?

 

Or are you still getting your departure ATIS data when arriving?

 

Is ver 6.49 working with ASN for you?

Havn't had time to test yet, possibly tomorrow.

 

Merry xmas

Havn't had time to test yet, possibly tomorrow.

 

Merry xmas

All works great, Destination weather is right on the money, must learn not to be so inpatient, 60 NM is the magic number, best flight yet. First time I have been vectored due to traffic.

 

Nice update Tegwyn

"All works great Destination weather is right on the money, must learn not to be so inpatient,"

 

Right.

All works great, Destination weather is right on the money, must learn not to be so inpatient, 60 NM is the magic number, best flight yet. First time I have been vectored due to traffic.

 

Nice update Tegwyn

Bingo, VOXATC it is, can't wait to try it out.

I love VoxATC.  It is my go to ATC program but lately it has been a real bonehead.  My last three landings have all been tailwind landings.    I'll read my weather updates from FSCaptain and ASN, setup for the correct runway and then as I am coming in to the control area VoxATC assigns me a tailwind or hellishly evil crosswind runway.   It is getting annoying, even if it that tailwind landing did save my life once when I had an engine flameout and was leaking gas.  The tailwind pushed me into the airport just as the gas run out and the batteries failed.  XD    This was not the intention of VoxATC.  It was just being crazy and not reading the weather file updates being made by Active Sky.   I hope they find a solution.   My solution now is to just turn off VoxATC altogether for landings if they don't match the REAL runway and go with the weather reports which sucks because I am missing out on all the fun arrival procedures and interaction for approach.

"It was just being crazy and not reading the weather file updates being made by Active Sky."

 

1. Was the VOXatc ATIS correct prior to your arrival vectors?

 

2. I thought the Beta testers all this was now working?