June 27, 201510 yr I have the Airbus X A320/321 Extended. My VoxATC was working fine, until I decided to install FS2Crew. VoxATC was occupying window15 and window16 on the Airbus panel configuration file. However, when I installed FS2Crew, it took them over for FS2Crew Main Panel and Configuration Panel. Now if I try to open FS2Crew panels, VoxATC windows are what pops up. I guess my question is, have anyone here had this issue before, and how can I fix it? Should I manually erase VoxATC entries from the panel configuration file, or is there a way to uninstall VoxATC from the VoxATC configuration window, and put it back so that it accepts the next available window entry? I just don't want to mess something up. Johnny Rosario
June 27, 201510 yr I think you could just edit the panel.cfg and change the window numbers for the VoxATC entries to [window17] and [window18]. That has to be done in 2 places, as you probably know. Alternately, I also believe that if you uninstall and re-install VoxATC it would have the same effect. However, that requires you to uninstall the entire program, so I would just edit the panel.cfg. Seems easier to me. Jay Current Build (02/2024): AMD 7800X3D | Asrock X670E Steel Legend MB | Noctua NH-U12S Chromax | 32gb GSkill Trident Z5 DDR5-6000 CAS 30 | Samsung 990 Pro 2tb NVMe Gen4 (OS) | WD Black 4tb NVMe Gen4 (MSFS) | Corsair RM1000x Shift Series PS | ASUS RTX 4090 Strix ROG | LG 55" C2 Display
June 27, 201510 yr Author I ended up uninstalling the Airbus, and reinstalling it. I then installed FS2Crew before adding VoxATC, which turned out to be a good thing, since I didn't realize there was an update to FS2Crew itself. Any way, it's working now as It should. Johnny Rosario
Create an account or sign in to comment