Anybody got news on whether the above will be included in VOXATC??

John

john

the only need one has (to use any plane) is to install the voxatc gauges in the panel.cfg for that aircraft ....... not sure about the NGXu, but that file is in the -800 for the full suite of NGX aircraft.

run the indexer to see a list of aircraft "panel.cfg's" or copy the entries from an existing vox configured file.

Thanks for the reply John. Previously VoxAtc has worked with the old 737 NGX so I went into the sim P3D/SimObjects/Airplanes/PMDG 737-NGX/panel/panel.cfg where I found:

[Window28]////VoxATC
visible=1////VoxATC
size_mm=400,200////VoxATC
window_size=0.3,0.3////VoxATC
window_pos=0.05,0.05////VoxATC
background_color=0,0,0////VoxATC
ident=14077////VoxATC
zorder=5////VoxATC
alpha_blend=0.65////VoxATC
gauge00=VAGauge!VoxATCPrompt,0,0////VoxATC

[Window29]////VoxATC
visible=0////VoxATC
size_mm=400,600////VoxATC
window_size=0.3,0.7////VoxATC
window_pos=0.65,0.05////VoxATC
background_color=255,255,255////VoxATC
ident=14078////VoxATC
zorder=5////VoxATC
gauge00=VAInfo!VoxATCInfo,0,0,400,600////VoxATC

------------------------------------------------------------------------

I openned the panel setup in VoxAtc, removed and reinstalled the VoxATC panels, then I went into the equivalent PMDG 737-800 NGXu panel.cfg file - there were to references to VoxAtc panels. I could copy the above into the NGXu panel.cfg but am afraid to do this without consulting expertise! Do you think doing this would help?

John

You will also have to copy in the section[Window Titles]

Window28=VoxATC////VoxATC
Window29=VoxATC Recent Comms////VoxATC

Richard.

That did the trick. Thanks for your help. I now have VoxATC for the 737 NGXu

John

16 hours ago, jsmcwilliam said:

That did the trick.

good to hear ... surprised it didn't show as "available" in panel install after "indexing".

 

I spoke too soon! The VoxATC panel appeared but I did not test run it untill today. Clicked on enable and got the following message:

Startup failed, unknown FS aircraft type PMDG 737-900ERNGXu PMDG House Blended Winglets (N739 ER | 2019)

followed by:

Fatal Error disable VoxATC

I realised I had not run the indexer so I restarted my computer followed by the VoxATC indexer. The indexer hung on D:\Prepar3D v4 \Weather\themes. Went back to mu old PMDG 737NGX to see if it was working with VoxATC - it was, however, I got the same result when I tried to run the indexer, it hung on ...Weather\themes!

Any suggestions?

John

Edited December 11, 20196 yr by jsmcwilliam

john

uninstall all panels using panel setup (from start menu), then check the aircraft.cfg's to confirm gauges removed (& only then delete any not removed in the first step) 

run indexer & if successful, reopen panel setup & install to the listed aircraft (yours).

hope that works for you.

My problem now is that I uninstalled VoxATC and ran the setup.exe again. The process hangs on the indexer at D:\Prepar3D v4 \Weather\themes and removing backup files. I have even tried removing Internal Workings before reinstalling but the result is the same and I cannot reinstall VoxATC

2 hours ago, jsmcwilliam said:

My problem now is that I uninstalled VoxATC and ran the setup.exe again. The process hangs on the indexer at D:\Prepar3D v4 \Weather\themes and removing backup files. I have even tried removing Internal Workings before reinstalling but the result is the same and I cannot reinstall VoxATC

How long did you wait with the indexer before you said it was definitely blocked?

Richard.

There's an old thread here somewhere that covers this issue, which dates back to around when the P3d4 version of VOXATC 7 was first released. I'll keep looking for it. In the mean time, when the Indexer hangs at ..\Weather\themes it almost always indicates an error in your scenery library. Unfortunately, there's no easy way to troubleshoot this situation except by disabling scenery library entries one at a time until you see what the problem is. The most common cause is having the same scenery file active in both scenery.cfg and as an add-on.xml file. You should first download the Lorby Add-on Organizer:

http://www.lorby-si.com/downloads.html

Then run the Organizer and see if it shows any errors in your scenery library. You could upload a zip file here containing your scenery,cfg and the two add-ons.cfg files but I don't know if anyone could figure out what is happening on your end from just looking at those files.

I followed the suggestion that the problem could be with the scenery files and having Lorby installed I was able to deactivate my last scenery addition, a freeware rendering of EDDF which I had installed because ORBX had got all the taxiways wrong and there was a missing runway. This proved to be the solution perhaps because EDDF was present in my scenery.cfg as a duplicate (Freeware + ORBX). I could run the indexer and after that activate EDDF again. VoxATC now works better that ever with my new PMDG NGXu which delights me.

The lesson learned was - always run the indexer after changes in the scenery, navdata.or addition of new aircraft. Doing this brought the NGXu into the VoxATC panel setup containing the list of available aircraft. Furthermore, Lorby Addon Organiser is a good app when it comes to finding errors in scenery configuration something which VoxATC seems to be sensitive towards.

John