Jump to content
The simFlight Network Forums

Adamski

Members
  • Content Count

    33
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Adamski

  • Rank
    Advanced Member

Contact Methods

  • Website URL
    http://www.nzfsim.org

Profile Information

  • Gender
    Not Telling
  • Location
    Auckland, New Zealand
  • Interests
    Growing old gracefully ...
  1. Thanks, Volker. I hadn't set the "Follow" option, so missed your post (above). Now rectified. I've managed to add FSC to the new Aerosoft database site (no problem there) ... but the D/L link is still 9.7.0. I'm sorry, but I'm a little confused (easily done at my age!!) ... is 9.75 available for P3Dv4 - or is my current 9.7.0 the only/latest version that is able to work with P3Dv4 (for legal reasons)? Thanks for all your help! Adam.
  2. Hi! I'm trying to update my FSC to 9.75 - but my only option for downloading at PCAviator is for v10 - which I can't use as I'm on P3Dv4.3. Should I be contacting PCAviator - or can I download it from somewhere else? Many thanks, Adam.
  3. Thanks, Pete - welcome back!!! I hope you had a good break - straight back in the saddle, I see! Looking forward to 5.123d! Adam.
  4. Hi Volker, Thanks for the quick reply! I'll repost with all the info as required/described in that link. I don't think I've ever had to report a problem with FSC before, so was unaware of the correct procedure. Adam.
  5. FSC 9.7 Build 26 July 2017 I have all my paths set up correctly in FSC, yet I always get this "error in writing pmdg plan (9)" error when trying to save with the PMDG box ticked. The dialog box says that PMDG will read from the default P3D folder for routes - but that isn't true. In P3dV4.1, PMDG flight plans are stored in [...]\Prepar3D v4\PMDG\FLIGHTPLANS or [...]\Prepar3D v4\PMDG\FLIGHTPLANS\NGX. Also, PMDG plans are in RTE format - which FSC no longer seems to create (possibly because of the above error) <??>. HELP!! Adam.
  6. There's our problem, then LOL!!! I'd still be keen to hear if anyone else out there shares my problem. I can't be the only one, Shirley? Adam.
  7. Thanks, Pete. Out of interest (it's all news to me): https://support.microsoft.com/en-gb/help/305097/how-to-view-the-system-registry-by-using-64-bit-versions-of-windows Maybe there's some mixup in the installer between the two versions of the HKLM keys (64/32-bit)? It does seem a coincidence that it's the HKLM path that's going weird. Adam.
  8. OK ... here's the batch file code (you can try it on your system too): @echo off echo. REM echo Checking Prepar3d V4 location. reg query "HKEY_CURRENT_USER\Software\Lockheed Martin\Prepar3d v4" /v AppPath >nul 2>nul for /f "tokens=2*" %%a in ('REG QUERY "HKEY_CURRENT_USER\Software\Lockheed Martin\Prepar3d v4" /v AppPath') DO SET "P3Dv4_Path_HKCU=%%b" echo ------------------ echo HKCU: %P3Dv4_Path_HKCU% echo ------------------ reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4" /v SetupPath >nul 2>nul for /f "tokens=2*" %%a in ('REG QUERY "H
  9. Yay!!! See my comments after the log (P3D fires up OK and FSUIPC reports 5.103g): ===================================================== Installer for FSUIPC5.DLL version 5.103g Looking in registry for Prepar3D v4 install path: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4 Parameter"AppPath" ... >>> OK! FOUND Prepar3D v4! <<< ... AppPath=H:\Program Files\Lockheed Martin\Prepar3D v4\ =========================================================== INSTALLATION FOR Prepar3D v4: AppPath="H:\Program Files\Lockheed Martin\Prepar3D v
  10. Thanks, Pete. I've just rung a buddy (with P3Dv4). He has exactly the same as me: \... on the end of the HKCU entry (not on HKLM).. I'll remove the redundant P3Dv3 and P3Dv2 entries then run a registry defrag. Then I'll have another go ;) Adam. EDIT: No luck after the registry defrag/cleanup, I'm afraid. Same error, exactly as before. Over to you, Sir!
  11. I must admit it's odd. I've never had it do this to me before ... ever! Sorry - I should have said .... it was from HKLM. In HKEY_CURRENT_USER, I only have "AppPath" - which has the same path as in HKLM (except it has three periods after it: H:\Program Files\Lockheed Martin\Prepar3D v4\...). This appears to correspond to what the installer is expecting (going by my successful 5.102). I appear to have entries in HKCU for P3Dv2 and P3Dv3 (but not in HKLM)... should I remove them? Adam. EDIT: Wait a minute. If you check my (successful) 5102 log, it says it couldn't find the pa
  12. Pete - thanks for taking this on! Here's the error window. Hard to screengrab, as Windows takes focus on the 2nd error window: The registry entry: The FSUIPC log itself appears to be fine - and updates itself everyu time I run P3D. The install log (also in "Modules") is the old 5.102 one - and doesn't seem to have been updated by the [failed] 5.103 install. Here it is anyway, just in case it's useful. Installer for FSUIPC5.DLL version 5.102 Looking in registry for Prepar3D v4 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4 Paramete
  13. Hi Pete! I'm sorry to say that I've also been struck by some installation weirdness ... after so many years of using FSUIPC with no problems. I tried to install 5.103 and the installer pops up the familiar install window, gets as far as querying the P3Dv4 registry entry, then crashes every time. This is P3Dv4 with Hotfix1. 1) The zip is properly extracted (no errors). 2) Win7x64. I'm logged in as "Admin" - and have also tried "Run as Administrator". 3) Comodo Firewall and Avast A/V temporarily disabled. 4) The install log never gets created. 5) I checked my registry entry for
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.