Just A Heads Up: New Version Released, v6.52

[vp49p3 216]

I spent a few years learning how to flight Sim with the late Michael Greenblatt.  Here's a link to his AVSIM In-Memorium thread.

 

http://forum.avsim.net/topic/385092-michael-greenblatt-fs-has-lost-an-icon/

 

One of Michael's mantras was that when something looks like it's going to take a long time for the computer to get done, walk away away from it and wait, instead of sitting in front of the screen, getting impatient and doing something that wouldn't help.  I was prone to doing this and he would actually yell at me to quit that.  (Michael yelled a lot in general).

 

If the installs seem slow or seem to stop altogether, realizing my proclivity for mischief, I go somewhere else to wait rather than in front of the screen.   Just following Michael's advice. That's all.

 

So, I guess the sum of all my walk-aways was that I got everything to work.

[wanabflyer 53]

I meant that it would save Tegwyn numerous emails if he would take part in this forum and take note of the issues we have. For example, there was no mention on his webpage or any readme accompanying the download, that 6.51 would not work with P3D when it is the only sim installed. So when he annouced 6.51, I installed it. Got problems and then found out in his subsequent email that 6.51 was not made to work for P3D installed alone. Come On Man - provide instructions in the first place, save yourself some emails and better still save your customer headaches and wasted time!

 

For my 6.52 installation, I told him In my first email that the installer would not show the indexer popup nor the sim select popup. He replied with a generic email to run the VOXATC tool and send him the error. There's no FATAL ERROR in the VOXATC window. The installer just doesn't complete properly. I installed 6.52 yesterday again and found out it works, but the runway updater, simselector.exe and indexer don't run and give me the "This program has stopped working" generic windows message. He sent me another tool veryfying my sim install - I have only P3DV2 installed - no tools required. This is where we stand.

 

What bugs me in all this is the everlasting back and forth emails when problems arise. He's somewhere in the UK and I am in Western Canada. An exchange of info can take many days. I know it's a one man show, but he could either 1. provide detail installation instructions and/or 2. participate in these forums and get some customer feedback.

Poor old Tegwyn is taking a beating here, however I can see your point Mario. I did suggest a few weeks ago on this forum, that all of these problems and solutions be moved to a pinned thread on the first page of this forum. Not as good as developer participation but might save a bit of time and frustration.

[Gregg_Seipp 568]

 

 

Poor old Tegwyn is taking a beating here, however I can see your point Mario. I did suggest a few weeks ago on this forum, that all of these problems and solutions be moved to a pinned thread on the first page of this forum. Not as good as developer participation but might save a bit of time and frustration.

 

Not so much a beating as a plea.  As frustrated as I am with issues, it's still a really decent ATC.  It's important to clean up the small things, though.  One thing going wrong, depending on what it is, can ruin a flight if you can't recover from it.  E.g. being stuck somewhere receiving "Unable at this time" over and over.  Also, I'd imagine that the solution to some of the problems might be simple and come out of the community thus, perhaps, saving him some work. 

[MarioB 4]

Tegwyn wrote back saying that the issue was due to a registry entry for P3D 1.4 that is set to the same folder as P3D V2.5.  He asked me to change that.

 

My knowledge of registry entries is poor. I have never had anything less than 2.0. Maybe it was created by an add-on (I never used Estonia). The FSUIPC install log also indicates that a path for 1.4 was found.

 

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LockheedMartin\Prepar3D

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Lockheed Martin\Prepar3D v2

 

are the key names I found.

 

If I am to change that, what should I do, delete the LM folder that contains the key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LockheedMartin\Prepar3D ?

 

Why is the 1.4 entry in my registry and why did VOXATC 6.50 work correctly?

[harryw 0]

Delete the whole Prepar3D folder/branch, NOT the LockheedMartin folder! I had this causing an issue with the ORBX FTX central. No idea where it comes from - I never had Prepar3D 1.4 and have few addons besides ORBIX stuff.

 

Also, just in case, make a backup of the registry before you delete anything  (File->Export and select theLockheedMartin Branch).

[MarioB 4]

Delete the whole Prepar3D folder/branch, NOT the LockheedMartin folder! I had this causing an issue with the ORBX FTX central. No idea where it comes from - I never had Prepar3D 1.4 and have few addons besides ORBIX stuff.

 

Also, just in case, make a backup of the registry before you delete anything  (File->Export and select theLockheedMartin Branch).

 

Thank for this Harry.

 

After Tegwyn examined my add-ons, he found nothing suspicious. He still believes the failed 6.52 installation is due to that P3D V1.4 registry entry. He told me to use 6.50 instead for now since there are no major changes. Something has changed in the 6.52 installer (apparently "improved" for all P3D, FSX and FSX-SE sims) that prevents a correct install for P3D 2.5.

 

So, for all of you that have ORBX products and P3D2.5 as the only sim installed, the VOXATC 6.50 version may be the best option for now.

[Russjm 0]

seems more stable;  however I am using it with Ultimate Traffic 2 it is still giving weird taxi instructions for any departure from London Heathrow that requires a 09R in that it sends that both me and the AI to cross runway 9R and then to a holding point. Also London Heathrow is plagued by TAP Air but that maybe down to UT2. I have emailed Tegwyn about the taxiing issue 3 times without response which is a little diappointing.

[specialist 51]

Did you run your runway number update on your VoxATC settings? I know it use to give me weird taxi instructions on some airports, but after running it, helped keep up with the latest Navigraph data.

[MarioB 4]

In the end, deleting the 1.4 P3D registry keys did the trick, 6.52 installed correctly

[specialist 51]

That's good! I don't use P3D, so I'm not sure what it does, but when I do eventually migrate to it, that's good to know.

[harryw 0]

Something else to take note of: VoxATC will create folders for FSX, FSX Steam, Prepar3d V1 and Prepar3d V2 in your Documents folder, regardless of what simulator versions you actually have - at least that happens on my system with only Prepar3d 2.5 on it.  Don't delete any of those folders, or VoxATC will run the indexer again, recreate the folders and overwrite your configuration with the default one when you next open one of the tools!

Maybe that's well known but I've only been aboard since version 6.50. Took me a while to realize what was going on...

[MarioB 4]

Something else to take note of: VoxATC will create folders for FSX, FSX Steam, Prepar3d V1 and Prepar3d V2 in your Documents folder, regardless of what simulator versions you actually have - at least that happens on my system with only Prepar3d 2.5 on it.  Don't delete any of those folders, or VoxATC will run the indexer again, recreate the folders and overwrite your configuration with the default one when you next open one of the tools!

Maybe that's well known but I've only been aboard since version 6.50. Took me a while to realize what was going on...

 

Thanks for the info Harry; this is true, I also noticed the creation of these folders in my documents.

I got confirmation from the developer that MT6 did not create the 1.4 registry keys. So it's still a mystery as to how they were created.

 

Going to KLXV, Lake Co. CO, the highest airport in the continental USA.

[jaybird1nyc 24]

Wow, that is strange indeed.  I'd really like to find out how those registry entries got there.   Hope you find out and let us know, might be helpful.

 

Jay

[sleightflight 17]

Hi All,

 

Well, I have gone through several updates with this software now, and each time has thrown a few curveballs at me, but I have always managed to sort them out.

This one has me stumped.

I have now tried un installing and re installing twice, + un installing and re installing all my voxpop software and voices.

I even open and close FSX between un instaling and re installing, and I've tried removing all my trusteds out of my cfg and allowing them to re load.

Everything goes in ok on the installer, everything works with the indexer and the panel installer, but when I load FSx, either with or without a flight plan, open the vox atc panel it is just a black box with no text in it what so ever, I have tried clicking in different parts of the box but nothing works.

Anyone else had this, I am in DX10 mode with Steves fixer but it has worked fine before with the last three versions.