FSUIPC v4.923 (problems encountered)

[Cruachan]

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

[Pete Dowson]

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.

 

Hmmm. Nor can I at first glance (the FSUIPC4.LOG won't be copied in any case -- it isn't relevant, it's a run-time log of what FSUIPC does in the sim so it's specific to that sim).

 

There is one odd anomaly, but it might be explained: This part:

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"

shows an existing Modules folder (made by what? A previous FSUIPC4 Install?), but with no FSUIPC4 module actually in it.

 

Did you delete stuff in the Modules folder before running the Installer (again)?

 

Although you found your way past the failure to copy those files, I am concerned and would like to fix whatever it is which could cause this to happen, so I will undertake some experiments here. Could you tell me whether you have UAC turned off or not in your Windows setup? Did you run the Installer with the right-click "as administrator" choice?

 

I may have to add more logging to the Installer to show the copying of the files from the first through to the other folders, with results logged too. I might come back and ask if you'll test it for me. It would be with version 4.924. Not many changes from 4.923, but still.

 

Thanks,

Pete

[Pete Dowson]

I may have to add more logging to the Installer to show the copying of the files from the first through to the other folders, with results logged too. I might come back and ask if you'll test it for me. It would be with version 4.924. Not many changes from 4.923, but still.

 

Well, that was a daft thing for me to suggest. I'm copying an already created log file and expect to log things into it about it being copied? Duh!

 

Anyway, I found the bug whch caused those two files not to be copied over. It only happens when you have both P3D1.4 and P3Dv2 installed, but not FSX at all. Just a scenario which I'd not tested till now, in the rush to get P3Dv2 supported properly.

 

So it will be fixed in the next full install update. Thanks for your report, which allowed me to find this!

 

Regards

Pete

[Cruachan]

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

[n2airb]

Hi Pete,

I installed v4.923 into Prepar3d v2 everything works except mouse macro. I am not getting the window when I click ok and it puts me  back to the simulator,nor am I getting the macro in the pulldown list. any ideas? thanks Shawn.

 

Hopefully I just didn't talk about something that has been resolved and I didn't see it in the FAQ.

[Pete Dowson]

I installed v4.923 into Prepar3d v2 everything works except mouse macro. I am not getting the window when I click ok and it puts me  back to the simulator,nor am I getting the macro in the pulldown list. any ideas?

 

Sorry, but that is rather confused. What 'ok' are you clicking? The one in the option after selecting the macro starting button? Or the one after entering the macro filename?

 

Which window are you 'not getting'? If you mean the window which allows you to name the macro when you click the mouse on a mouse-macro-capable mouse spot on the cockpit? If this is what you really mean (thjough it's a long way from "Ok" clicking), then you should know that mouse macros are not possible on most cockpits because nearly all modern ones aren't written using the FS2004 C/C++ gauge SDK.

 

You say you are "not getting the macro in the pulldown list", but how can you expect to if you've not actually created and named one? The filename is not the macro name, just the name of the file in which all your created macros are stored. Its name is just the prefix for what you would see in the drop-down selection list. The names are in the form:

 

<macrofile>:<macroname>

 

Generally you'd have all the macros for one aircraft type in the one file.

 

BTW version 4.924 is now available.

 

[LATER]

Checking among the aircraft in P3Dv2, so far the only one I can find where mouse macros can be used in some areas is the Mooney Bravo. In the main panel view, for instance, you can make macros for the bitd on the VS/ALT gauge, the NAV/GPS switch, the Speed Brake and WARN indicators, the red BAT and ALT switches, even the Magneto switch. Maybe others.

 

Of course most of these have adequate FS controls in any case.

 

Regards

Pete

[Cruachan]

Hi Pete,

 

I note you have stated that FSUIPC4 4.924 is now available. Would you like me to run a test on my system?

If so, would you prefer I started from scratch by removing all existing content from the Prepar3D 1.4 and Prepar3D v2.0 Modules folders before running the installer?

 

The version number is still 4.923 on your website.

 

Regards,

 

Mike

[Pete Dowson]

I note you have stated that FSUIPC4 4.924 is now available. Would you like me to r

 

No, thanks, it isn't necessary. As I said earlier, I found and fixed the problem.

 

The version number is still 4.923 on your website.

 

I have no website. All my stuff is located in the Simflight servers and accessible in the Download Links subforum here. If you mean Mr. Schiratti's "Dowson" page, then I have no control over that. I do occasionally ask him if he will update the wording there, but it can take a while, perhaps days or weeks, because he is travelling and working elswhere a lot of the time. In any case, the links on his page point to the same downloads from SimFlight, so it is of no real consequence. Only the descriptions there are out of date most of the time.

 

Regards

Pete

[Cruachan]

Hi Pete,

 

Okay, understood.

 

Something else learned today :)

 

Regards,

 

Mike

[n2airb]

Sorry, but that is rather confused. What 'ok' are you clicking? The one in the option after selecting the macro starting button? Or the one after entering the macro filename?

 

Which window are you 'not getting'? If you mean the window which allows you to name the macro when you click the mouse on a mouse-macro-capable mouse spot on the cockpit? If this is what you really mean (thjough it's a long way from "Ok" clicking), then you should know that mouse macros are not possible on most cockpits because nearly all modern ones aren't written using the FS2004 C/C++ gauge SDK.

 

You say you are "not getting the macro in the pulldown list", but how can you expect to if you've not actually created and named one? The filename is not the macro name, just the name of the file in which all your created macros are stored. Its name is just the prefix for what you would see in the drop-down selection list. The names are in the form:

 

<macrofile>:<macroname>

 

Generally you'd have all the macros for one aircraft type in the one file.

 

BTW version 4.924 is now available.

 

[LATER]

Checking among the aircraft in P3Dv2, so far the only one I can find where mouse macros can be used in some areas is the Mooney Bravo. In the main panel view, for instance, you can make macros for the bitd on the VS/ALT gauge, the NAV/GPS switch, the Speed Brake and WARN indicators, the red BAT and ALT switches, even the Magneto switch. Maybe others.

 

Of course most of these have adequate FS controls in any case.

 

Regards

Pete

Pete,

 

Sorry I was running out the door this morning when I posted.

 

Your response: [LATER]

Checking among the aircraft in P3Dv2, so far the only one I can find where mouse macros can be used in some areas is the Mooney Bravo. In the main panel view, for instance, you can make macros for the bitd on the VS/ALT gauge, the NAV/GPS switch, the Speed Brake and WARN indicators, the red BAT and ALT switches, even the Magneto switch. Maybe others. Gave me my answer. I was clicking in Virtual Cockpit mode (Carenado C90B Payware Plane) buttons that are not macro enabled . Thank you for your reply and the heads up on version 4.924  .Shawn