Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

6 Neutral

About Hippo

  • Rank

Profile Information

  • Gender

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. I have just installed and very briefly tested but looks ok. I was able to install without issue, get and respond to a clearance. Not flown yet. Oh, and the VoxATC panels are now viewable in VR!
  2. Sorry to hijack the thread somewhat (as this isn't a 4.3 issue as such). But I wonder if anyone has encountered the following: just sitting on the runway, when I look around the cockpit, intermittently around every 5 seconds, the display will stall (i.e. stop moving for less than a second). This was actually happening to me with 4.2 recently, but I had been away from P3D for months previously and I'm sure it wasn't an issue before then. Maybe a new driver from the past couple of months or so? Appreciate any responses as this makes the sim unusable for me. I had completely uninstalled all traces of 4.2 so was hoping this issue would not be there. This is on a completely clean install of 4.3. The only other thing I have installed is fsuipc. I am testing by loading the aircraft from with the default flight. Do not see this issue with the other aircraft (f22). In answer to the original question, I can only say that it installed without issue and appears to work as usual.
  3. I always uninstall everything and start again from scratch. I know the update is supposed to be perfectly fine, but still I'm always left wondering. A bit like "did I leave the gas on". Sorry, if all you've got from that is that I'm a bit odd.
  4. I feel a pithy comment coming. No, better not...
  5. Point taken, no lazy way around this then. IOM installed ok for me into P3Dv3. Have since installed Guernsey, all ok, except that the autogen is missing? As I mentioned I had already installed Orbx scenery. Does it matter which is installed first (ES / Orbx)? Does the order in the scenery.cfg matter? I notice in IOM that I can "crash" into invisible objects. Is anything known about this? After looking at the sdk I had a play with the autogen tools (ac2scan, ac3scan). They throw up LOTS of warnings and errors. Is this to expected with old sceneries? Some of the errors referenced Orbx stuff.
  6. I've just installed IOM into 3.4. I have previously installed Orbx Global, England, Wales, Scotland, EU LC and Vector. I notice that the file Autogen/default.xml was replaced / amended during the installation. Can anyone tell me what this file is for, and if there are any implications of it being changed by the ES installer? Should I put the backed-up version back? At first glance it appears to have installed ok. I did have to put a copy of scenery.cfg into the P3D folder beforehand, and copy it back to %programdata%. I'm trying to work out what you're (Kevin) doing in your posts with the xml stuff. I'm guessing it's some new method of dealing with add-ons. Any chance of a quick pointer as to where this is explained in simple terms?
  7. Installed this today (into 3.4 no other version on my system) without issue. Using the installer offered here: https://www.pilots.shop/Cms/Ui/Pages/Products/MainPage.aspx?id=f414426b-3149-4102-a422-c812f1bbcb10 I found the instructions in the included readme file to be quite understandable.
  8. Ok, here goes. Good luck. The method is to create a series of linked folders so that it appears that an installation of P3Dv2 is installed on the computer. When VoxATC runs it is "tricked" into thinking it is reading from a P3Dv2 installation, when it is actually reading the P3Dv3 files. Carry out the following to set this up. Please read the notes at the end before proceeding. The first step, though, is to check the registry. I believe that VoxATC locates the P3D installation from the following key (the following is taken from an export on my PC); my installation is at D:\P3Dv3. --- Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Lockheed Martin] [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Lockheed Martin\Prepar3D v2] "SetupPath"="D:\\P3Dv3\\" --- There should already be a corresponding key for v3. You must create the key above for v2, but make sure it is referencing your v3 installation folder.** One way to do this is to amend the text above within the dashes to point to your installation folder then save it as a text file with a *.reg extension. Double-clicking that file should then import the entry into your registry. The folders we need to create links to are %userprofile%/Documents/Prepar3D v3 Files %localappdata%/Lockheed Martin/Prepar3D v3 %appdata%/Lockheed Martin/Prepar3D v3 %programdata%/Lockheed Martin/Prepar3D v3 Run a command prompt with admin priveleges**, and type the following commands: cd %userprofile%\Documents mklink /d "Prepar3D v2 Files" "Prepar3D v3 Files" You should find, if you look at your Documents folder, that a new folder "Prepar3D v2 Files" (the link) has been created, with a little shortcut symbol in the corner of the icon. The Prepare v2 Files folder acts as a kind of shortcut to the "real" v3 folder (the target). Whenever you or an app accesses files within the v2 folder you / it is actually accessing files in the v3 folder. It is safe to delete the link folder (i.e. it will not delete the target folder files) if necessary; however, deleting individual files in the link, WILL delete the files in the target. Then do the same for the other folders: cd %localappdata%\Lockheed Martin mklink /d "Prepar3D v2" "Prepar3D v3" cd %appdata%\Lockheed Martin mklink /d "Prepar3D v2" "Prepar3D v3" cd %programdata%\Lockheed Martin mklink /d "Prepar3D v2" "Prepar3D v3" On my PC, at least, after doing the above, VoxATC works. I would recommend you do a fresh VoxATC install at this point. NOTES ** if I am assuming too much Windows techie know-how here, please let me know, I can explain further. - v3 is the only version I have installed, if you also have v2 installed then this will not work. - for ages I have had an issue where (sometimes) if I run the programs using the shortcuts the installation creates in the start menu, it goes into an install routine instead of running the program. I don't know if anyone else has this issue, and I have no idea what causes it. What I do is to create a shortcut on my desktop to the VoxATC installation folder and run the *.exes directly from there. - SimulatorSelection.exe now crashes on my machine. Doesn't really matter to me too much as VoxATC works, and I'm only running one version of P3D anyway. - Run the following (from the VoxATC folder)if the installation fails, or when necessary: Registrar.exe (to register VoxATC with your key) AdvancedSettings.exe (config) JoystickSelect.exe (config) VoxATCSettings.exe (config) VAPanelSelect.exe (to select which aircraft to add panels to) VoiceConfig.exe (to configure voices) VoxATCIndexer.exe (to index scenery, aircraft, etc. you should run this any time you make scenery changes or add aircraft) - I believe all this to be perfectly safe, but you tinker with the registry and make the changes above at your own risk... etc, blah. Please don't blame me if something breaks. - Superficially, it appears to work for me. I have not tested in depth, and problems may still crop up. - Other addons will think you have a P3Dv2 installation on your PC. I would just select to install to v3 (where offered), or just let it install to v2 if not. Most addons now recognise v3, but for those that don't I don't think there should be an issue. - I am running Windows 10 64-bit. Folders / registry keys might not be exactly the same for other versions. - I believe that this is doing manually (some of) what the migration tool does for you. If you are using the migration tool already, it's possible there could be unintended issues.
  9. I've been able to get voxatc working in v3 using the old symlinks (mklink) workaround. Haven't tested in depth, but so far it appears to work (I've been away from my PC for a few months). I can explain in more detail if you're not familiar with mklink.
  10. Hi, Just wondering when video number 13 (shared cockpit full flight) from the the FO course will be released. It was shown on the website as due within a few weeks or so when I bought the course, then got pushed back, and more recently was described as "coming soon". Now it appears to have been removed. I hope that this is just a mistake, and that the video will still be delivered (I have paid for it, after all). Thanks.
  11. https://www.gog.com/game/falcon_collection $2.49 Includes Falcon 4, so a cheap way to get hold of a legal copy of that, if you're into that sort of thing (BMS, etc).
  12. Thank you so much to everyone for your replies; wonderful videos backed up by an excellent forum. I hope you won't mind too much if I slip in another quick question: What is the (two position?) button on the far left of the control column for (not the elevator trim)? I suspect it's a PTT (one position for radios, the other for intercom)? Thanks.
  13. I believe that in the (cadet) videos you use the AP button on the panel to disengage the autopilot at the end of the approach. I have mapped to control column A/P disc button (pro version) to my joystick and noticed that when using that button the effect is not the same (there's beeping and flashing). I push the button twice (to cancel the alerts?). The control column button seems more natural to me, and I was just wondering which button is usually used (IRL) to disengage at the end of the approach. Also, what is the difference between using the control column button and the panel AP button?
  • Create New...