Jump to content
The simFlight Network Forums

Cruachan

Members
  • Posts

    17
  • Joined

  • Last visited

Posts posted by Cruachan

  1. Hi Pete,

    As ever, I take my hat off to you :)

    Prepar3D 1.4 still has considerable value for me as I have a number of Addons which, as yet, don't work fully in Version 2.0. Also performance is excellent in v1.4. Hopefully things will improve in v2.1 with the promised implementation of SLI. Fingers crossed!

    Probably not needed now, but answering your questions:

    1. Yes, UAC has been disabled.

    2. Yes, the FSUIPC installer was run as Administrator.

    3. Yes, as part of my efforts to achieve a clean reinstall I had deleted the content of the Modules folder in both Prepar3D v1.4 and Prepar3D v2. Prior to all this I did have a previous registered version of FSUIPC installed in Prepar3D v1.4.

    Of course, I will be only too happy to test should you wish me to.

    Regards,

    Mike

  2. Hi Pete,

     

    Please accept my apologies for not having come here first to request support. In my defence and being a creature of habit, Avsim has long been my first port of call for help. In fact, since the heady days of FS9 I have been a relatively infrequent poster. Also, when I started that thread, I wasn't aware that you had an FSUIPC Support Forum at simflight.com, nor did I believe I had in fact registered. However, here I am and have discovered I must have done so at some point in the distant past. Having said all that, it's easy to appreciate how idiots like me must at times seem, by throwing needless distractions your way, to threaten to be the bane of your very busy life.

     

    In case others are wondering what this is all about, I refer them to that aforementioned thread over at Avsim in The Prepar3D General Forum. Look for a thread with the same title as this one.

     

    In response to your request, Pete, here now is the content of my FSUIPC4 Install.log file which was created earlier today:

     

    Installer for FSUIPC4.DLL version 4.923

    Looking in registry for FSX install path:
         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
         Parameter"SetupPath"
    Not there, so looking in:
         HKEY_CURRENT_USER\FSX
         Parameter"AppPath"
    ... NOT found! ...
    Looking in registry for ESP install path:
         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0
         Parameter"SetupPath"
    Not there, so looking in:
         HKEY_CURRENT_USER\ESP
         Parameter"AppPath"
    ... NOT found! ...
    Looking in registry for Prepar3D install path:
         HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
         Parameter"SetupPath"
    ... >>>  OK! FOUND Prepar3D!  <<< ...
    Looking in registry for Prepar3D v2 install path:
         HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
         Parameter"SetupPath"
    ... >>>  OK! FOUND Prepar3D v2!  <<< ...
    ===========================================================

    INSTALLATION FOR Prepar3D:
    SetupPath="C:\Program Files (x86)\Lockheed Martin\Prepar3D\"
    Checking version of the Prepar3D EXE:
    ... Version 1.4.4747.0  (Need at least 1.0.677.0)
    Checking compatibility with installed SimConnect:
        Found SimConnect build 60905 (Original)
        Found SimConnect build 195 (ESP Orig)
        Found SimConnect build 61242 (SP1 May07)
        Found SimConnect build 61259 (Acc/SP2 Oct07)
    Checking if there's already a version of FSUIPC4 installed in:
           C:\Program Files (x86)\Lockheed Martin\Prepar3D\Modules\FSUIPC4.DLL
    ... No previous valid version found.
    Prepar3D Modules folder already exists.
    Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Lockheed Martin\Prepar3D\Modules\FSUIPC4.DLL"
    Looking for the current user's Application Data path:
    ... found as "C:\Users\Mike\AppData\Roaming"
    Now finding \Lockheed Martin\Prepar3D\Prepar3D.CFG for all users, including this one
    Looking in "C:\Users\All Users\AppData\Roaming"
     ... No Prepar3D.CFG there
    Looking in "C:\Users\Default\AppData\Roaming"
     ... No Prepar3D.CFG there
    Looking in "C:\Users\Default User\AppData\Roaming"
     ... No Prepar3D.CFG there
    Looking in "C:\Users\Mike\AppData\Roaming"
    Found Prepar3D.CFG in "C:\Users\Mike\AppData\Roaming\Lockheed Martin\Prepar3D\Prepar3D.CFG"
    Now checking DLL.XML ...
    ... There is a previous DLL.XML, checking for FSUIPC4 section.
    ... FSUIPC4_Loader section already exists but will be replaced.
         (for FSUIPC4, without Loader)
    ... FSUIPC4 section of DLL.XML written okay
    Now checking for a SimConnect.XML file ...
    ... There is a SimConnect.XML, checking for "local" section.
    ... "local" section already exists, file not modified.
    Looking in "C:\Users\Public\AppData\Roaming"
     ... No Prepar3D.CFG there
    "Modules\FSUIPC Documents" folder created okay!
    Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder:
       Installed "SimConnectP3D.dll" okay
    Now installing additional files into the "Modules\FSUIPC Documents" folder:
       Installed "FSUIPC4 User Guide.pdf" okay
       Installed "FSUIPC4 for Advanced Users.pdf" okay
       Installed "FSUIPC4 History.pdf" okay
       Installed "List of FSX controls.pdf" okay
       Installed "FSUIPC Lua Library.pdf" okay
       Installed "FSUIPC Lua Plug-Ins.pdf" okay
       Installed "Lua License.pdf" okay
       Installed "Lua Plugins for VRInsight Devices.pdf" okay
       Installed "LuaFileSystem.pdf" okay
       Installed "Example LUA plugins.zip" okay
       Installed "Offset Mapping for PMDG 737NGX.pdf" okay
       Installed "FSUIPC4 Offsets Status.pdf" okay
    ===========================================================

    INSTALLATION FOR Prepar3D v2:
    SetupPath="C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\"
    Checking version of the Prepar3D v2 EXE:
    ... Version 2.0.9448.0  (Need at least 1.0.677.0)
    Checking compatibility with installed SimConnect:
        Found SimConnect build 60905 (Original)
        Found SimConnect build 195 (ESP Orig)
        Found SimConnect build 61242 (SP1 May07)
        Found SimConnect build 61259 (Acc/SP2 Oct07)
    Checking if there's already a version of FSUIPC4 installed in:
           C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL
    ... No previous valid version found.
    Prepar3D v2 Modules folder already exists.
    Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL"
    Looking for the current user's Application Data path:
    ... found as "C:\Users\Mike\AppData\Roaming"
    Now finding \Lockheed Martin\Prepar3D v2\Prepar3D.CFG for all users, including this one
    Looking in "C:\Users\All Users\AppData\Roaming"
     ... No Prepar3D.CFG there
    Looking in "C:\Users\Default\AppData\Roaming"
     ... No Prepar3D.CFG there
    Looking in "C:\Users\Default User\AppData\Roaming"
     ... No Prepar3D.CFG there
    Looking in "C:\Users\Mike\AppData\Roaming"
    Found Prepar3D.CFG in "C:\Users\Mike\AppData\Roaming\Lockheed Martin\Prepar3D v2\Prepar3D.CFG"
    Now checking DLL.XML ...
    ... There is a previous DLL.XML, checking for FSUIPC4 section.
    ... FSUIPC4 section already exists but will be replaced.
         (for FSUIPC4, without Loader)
    ... FSUIPC4 section of DLL.XML written okay
    Now checking for a SimConnect.XML file ...
    ... No SimConnect.XML file found. This is okay.
    Looking in "C:\Users\Public\AppData\Roaming"
     ... No Prepar3D.CFG there
    "Modules\FSUIPC Documents" folder created okay!
    Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder:
       Installed "SimConnectP3D2.dll" okay
    Now installing additional files into the "Modules\FSUIPC Documents" folder:
       Installed "FSUIPC4 User Guide.pdf" okay
       Installed "FSUIPC4 for Advanced Users.pdf" okay
       Installed "FSUIPC4 History.pdf" okay
       Installed "List of FSX controls.pdf" okay
       Installed "FSUIPC Lua Library.pdf" okay
       Installed "FSUIPC Lua Plug-Ins.pdf" okay
       Installed "Lua License.pdf" okay
       Installed "Lua Plugins for VRInsight Devices.pdf" okay
       Installed "LuaFileSystem.pdf" okay
       Installed "Example LUA plugins.zip" okay
       Installed "Offset Mapping for PMDG 737NGX.pdf" okay
       Installed "FSUIPC4 Offsets Status.pdf" okay
    ===========================================================

    All installer tasks completed.
    Registration for FSUIPC4 was successful! (result code 00)

    *************** End of Install Log ***************
     

     

    Hope this helps. As I said in that thread over at Avsim, when I examined it, everything seemed to be as it should be and I could see no obvious explanation for the apparent failure to copy the FSUIPC4.log, FSUIPC4 Install.log and the FSUIPC4.key files into the Prepar3D v2\Modules folder.

     

    Kind regards,

     

    Mike

  3. Well, what do you know, I think I've found the answer/workaround:

    http://www.simforums.com/forums/forum_pEmma+Field

    For the moment, until I have more time to study the thread in detail, I've disabled the 'Enhance Streams' option in the UT-USA configurator and it works - Emma Loads fine!

    So, it appears that it wasn't Emma's fault after all.

    Still no joy with Ranger Creek, however. That might possibly be a scenery priority issue. I'll investigate further.

    Mike :)

  4. Hi Francois,

    Here's the list:

    Georender 1-6 (Flying M Ranch and Forks Minicipal appear to be okay) and all the 2004 versions. However, Ranger Creek fails to load the ground textures - I'm presently in conversation with Richard and others at the Georender forum.

    FSCargo v. 1.1 (installed 19/08/06)

    Sorry, please remind me what else could be included as it's perfectly possible I've missed some.

    Regards,

    Mike

  5. Hi Gary (or anyone reading this),

    I managed to carry out a separate install of EMMA on another drive to see exactly what was being installed and where. Unfortunately this hasn't helped much so far :(

    I downloaded a fresh copy of emma_patch_2004_100.zip and tried installing that - still no joy!

    So, we are back to the VistaMare dynamic link libraries. I note my intelliscene ViMaIScn.DLL file version differs from yours - mine is 2004.0.8.0. This is perhaps interesting as the version installed by emma_patch_2004_100.zip is 2004.0.3.0. Switching them made no difference, however.

    We both have the same versions of ViMaPlay.DLL (2.0.3.0).

    This leaves ViMaCore2004.dll. It's just possible that this might be the source of the problem , but I'm not holding my breath ..LOL

    Your version is 2.0.15.0 wheres my current version is 2.0.22.0 downloaded from the VistaMare site.

    Now emma_patch_2004_100.zip installs version 2.0.11.0 and the fact that I have still got version 2.0.22.0 in situ suggests that the installer does not overwrite files of a more recent version.

    Sooo, the only thing I haven't tried yet is your version of ViMaCore2004.dll: 2.0.15.0

    Any suggestions as to where I might be able to download it, or perhaps you would be prepared to e-mail me the file as an attachment?

    BTW, I don't know whether or not it is relevant, but I also noted that our version numbers of Glider.dll differ. Mine is 2004.0.4.0 whereas yours is 2004.0.5.0 .

    Regards,

    Mike

  6. Hi,

    I had to rebuild fair chunks of my >45GB FS9.1 installation following a MoBo failure and system rebuild. Most appears to be working fine, but on checking my scenery addons I've discovered that KEWL (Emma Field) no longer loads. Actually, it does load partially, but fails when the progress bar reaches 53%-56% (depending on the provided flight situation selected ) while loading terrain. I see the message: "Microsoft Flight Simulator has encountered a problem and needs to close, etc, etc"

    When I look at the error signature it tells me ModName: unknown, ModVer: 0.0.0.0 and Offset: 00000000 which means absolutely nothing to me.

    If I try to create a flight by going to KEWL, then the progress bar stops at 59%, also while loading terrain.

    I've tried starting from scratch by uninstalling and then reinstalling using the setup.exe file in the archive EMMA_Patch_2004_100.zip. The install seemed to proceed normally to completion.

    I've also ensured I have the latest files from VistaMare (ViMaCore2004.DLL and ViMaPlay.DLL) and all the functions which depend on these files appear to be working in my Georender (2004) series, etc.

    I would appreciate any suggestions as to what I should be doing to get EF working again. It's a strange one!

    Thanks!

    Mike

  7. Hi Holger,

    You mentioned in the UT for MSFS forum that you have sent an updated version of the UT-Alaska Cinematic batch files to Richard.

    I know I'm being impatient, but the only file currently available is still the ACV1Update1.1.zip posted 22 June 05. I think Richard must be busy or testing the file or asleep recovering from exhaustion. Surprised how you manage to keep going!

    Any chance you could provide us all with a temporary link to the update or perhaps you could upload it to Avsim for us?

    I know I posted this request over at the UT MSFS forum, but it was at the end of rather a long thread and I thought you might miss it ;) I can just hear you....what a chancer!! Sorry, but if you don't ask you don't get..lol

    Cheers,

    Mike (as he quickly runs for cover...)

  8. Stranger and stranger :?:

    After much experimenting I found the binding combo CTRL+SHIFT+R did the trick.

    I have to assume that there was a conflict between the chosen FSUIPC assignment and FS9's keyboard assignment for CTRL+SHIFT+W = Cycle Chase View Forward. However, deleting FS9's assignment made no difference whatsoever. After making the change I exited FS9 and then restarted to ensure that the changes were written to FS9.cfg.

    What is puzzling is the fact that I have always used CTRL+SHIFT+W for Clearing Weather and this change in behaviour has only recently become apparent.

    Ah well, at least I have managed to resolve the problem, albeit without having found a satisfactory explanation.

    In passing I noted that I have Powerstrip configured to use CTRL+SHIFT as the global modifier for several Hot key bindings. One in particular could have proven to be a bit of a pain while FS9 is running and that was the binding for restoring adapter defaults - CTRL+SHIFT+S. Not sure whether this has any effect in FS9 but I imagine this combo could be hit by accident with unexpected results!

    FS9 sure keeps us on our toes :wink:

    Mike

×
×
  • 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.