Jump to content

mthomas904

Members
  • Content Count

    4
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    Yes
  1. Using the above suggestion as a starting point I have got VoxATC working in P3D v5. I have also got the Indexer and the Panel tool to work by tricking them into thinking they were still looking at v4. I achieved this by creating a folder junction/symbolic link between an empty 'Prepar3D v4' folder and the new 'Prepar3D v5' in each of the following locations: C:\ProgramData\Lockheed Martin C:\Users\Chris\AppData\Roaming\Lockheed Martin I:\Lockheed Martin I must say so far I'm very impressed with the performance of v5, it is leaps and bounds ahead of v4. Using this method, I too have gotten the indexer to run successfully and have managed to enable and initialise the VoxATC gauge in-game. Haven't had chance to try a flight but all seems to be working so far. Currently only have a few ORBX airports installed on an otherwise clean v5.
  2. Hi everyone, I was wondering if anyone else seems to notice the distinct lack of variety in the squawk codes assigned for IFR flight? Every single time it's '3 0 * *'. It's not a huge issue, but I was wondering if it's something to do with my setup or is it a common thing in Voxatc? Is there anything that can be adjusted in the config file to change it? P.s. I use P3Dv4 and Voxatc 7.1 Many thanks for your time! Mitchell Thomas
  3. Okay, so there seems to be an issue with my P3D V4 addon folder. I renamed the folder so that the indexer would bypass it and now the indexer continues. There something in there it doesn't like, but I need to work out what...
  4. I've uninstalled 7.4 and tried to install 7.41, but the indexer is hanging at C:\Lockheed Martin\Prepar3D v4\Weather\themes. This is the final folder in the P3D directory, which implies that it's struggling to work out what needs to be indexed next. I tried moving the folder in question out of the P3D directory temporarily and the indexer then hangs at the previous folder instead (In my case, a UK2000 folder), so it must be stuck trying to work out what to index after the main folders. Anyone else having this issue?
×
×
  • Create New...