Jump to content
The simFlight Network Forums

quink99

Members
  • Content Count

    21
  • Joined

  • Last visited

Community Reputation

0 Neutral

About quink99

  • Rank
    Member
  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://

Profile Information

  • Gender
    Male
  • Location
    San Miguel de Allende, Mexico
  1. Old Texas expression from my childhood............ "Even a blind hog gets an acorn now and again..." In a rage of frustration, for the third time, I deleted FS-SE and everything I could find relating to FSUIPC, and the VRS F18 and followed up with a defrag and shutdown and restart and the only thing I did different this time was to run a complete registry cleaning and.........Voila........upon firing up this third iteration of FXS-SE with FSUIPC and the VRS F18 reinstalled everything worked perfectly. The ADDON menu was present in the flight sim with entries for both FSUIPC and the VRS F18 present and functioning as they should. The files that were missing before such as FSUIPC.log and the various Simconnect.log files were all where they belonged. What happened? Damn'd if I know, because the only thing I did differently on this re-install was to run the CCleaner registry cleaner prior to reinstalling the above mentioned items. Pete, please my accept sincere thanks for all you have tried to do! I most appreciated all of it. At least now you've got me out of your hair and I can use my favorite tool, FSUIPC, to go set up all my flight controls, keys, buttons and switches, Frederick
  2. Prior to going flying I checked in the Flight Simulator X Files to verify that the Simconnect.ini file was still present and in the correct form from the FAQs as shown here; [simConnect] level=Verbose console=No file=C:\Program Files(x86)\Steam\steamapps\common\FSX\Modules\SimConnect%01u.Log file_max_index=9 ........................and it was. After the flight I checked BOTH of my MODULES files for ; - SimConnect1.log and/or SimConnect2.log and neither were present. - FSUIPC4.log files and neither had one had present. - During the flight the ADDONS menu tab was still not showing. Sorry for the bad news! Fred
  3. Got me on the first one, Pete......you're absolutely right! As I said, I am a beginner when it comes to exploring the neurons of a computer's brain but with your help slowly I'm getting better. "No. Not only does it look completely wrong (the same path is there TWICE!), but it doesn't contain a filename! There is no way a SimConnect.log file can be produced because you've not told it what the filename should be! The filename is the name of the file you want to see. The path only tells it where to put it. You can put it in C:\ if you like!" Here is the corrected file that I placed in the My Documents\Flight Simulator X files based on the FAQ as you mentioned. ===================================================================================================================== [simConnect] level=Verbose console=No file=C:\Program Files(x86)\Steam\steamapps\common\FSX\Modules\SimConnect%01u.Log file_max_index=9 ===================================================================================================================== Did you not actually read the FAQ thread I mentioned. Look now. See the "file=" line? Yes, Pete, I did read every word of it, several times in fact, but I apparently didn't understand it based on what seem to be two installation of FS Steam in my FSX folder each with it's own Modules folder. I won't bore you with the details unless you're interested but if so, just let me know. At any rate I think it is now done correctly! "Your entry appears to be two copies of just the "path to fsx" stuck together". .....and that's how it appears in my FSX folder tree. "You also appear to be using / characters instead of the correct \ characters." Thanks again, Pete. I sincerely never knew the difference. With luck maybe we can whittle it down to zero errors this time. I'll go for a flight now and see if it made any difference. Fred
  4. The " quotation marks" appear in the actual original DLL.MXL exactly as you pointed out; -<SimBase.Document version="1,0" Type="Launch"> "Is VRS_TacPack supposed to provide a menu entry too? does it?" During all the time I have had it the VRS TacPack has always been accessed by an icon in the start menu or from a desktop icon. "Try renaming the DLL.XML file and re-running the FSUIPC Installer so it makes a fresh one just with FSUIPC4 loading. Renamed the DLL.XML and then re-ran the FSUIPC Installer and, sure enough, it showed only FSUIPC (I think) as loading; <?xml version="1.0" encoding="WINDOWS-1252"?> -<SimBase.Document version="1,0" Type="Launch"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> -<Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> </SimBase.Document> I then opened FS Steam and checked the MENU but ADDONS was still not shown. "If that doesn't work then I need to see a SimConnect log file -- see the "FSX HELP: logging Simconnect" thread in the FAQ subforum for details." Here is the file that I placed in the My Documents\Flight Simulator X files based on the FAQ as you mentioned; [simConnect] level=Verbose console=No file=C:/Program Files(x86)/Steam/Steamapps/common/FSX/Steam/steamapps/common/FSX file_max_index=9 I then flew two flights and after finishing I then checked in in the modules folder of the path shown above for Simconnect1.log and/or Simconnect2.log and they were not present. To verify that they were not present I did a backup search using Start>Search programs and files and nothing was shown anywhere in my computer. Obvious (?) conclusion...........I don't have these files. In the Simconnect.ini file above look at the convoluted address to reach my main FSX folder! Is this normal? That's the way Steam installed it. Fred
  5. Pete, I'm sure by now you've become as frustrated with me as I have become confused. On the theory that today some people going into flight sim have never had FSX and start right out with Steam. I've tried to return to that less complicated state by again uninstalling FSUIPC, the VRS F18, and FS Steam. I had previously thought that I had uninstalled FSX using the MS UNINSTALL function but it left the whole FSX folder tree on my C: drive and that I have just tried to erase every trace of using the DELETE function. It is now no longer there. Following this I re-installed FS Steam and then FSUIPC but not, yet, the VRS F18 until FSUIPC is taken care of. FS Steam functioned as desired but without the ADDONS menu as before. I have here posted all of the logs as requested before but only with today's date, 20APR16. ============================================================================================== Installer for FSUIPC4.DLL version 4.949p Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX Looking in registry for FSX-SE install path: HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX Parameter"Install_Path" ... >>> OK! FOUND FSX-SE! <<< ... SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX\steamapps\common\FSX Looking in registry for Prepar3D v1 install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v3 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3 Parameter"AppPath" ... NOT found! ... =========================================================== INSTALLATION FOR FSX: SetupPath="C:\Program Files (x86)\Steam\steamapps\common\FSX\" Checking version of the FSX EXE: ... Version 10.0.62615.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 62615 (Steam) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07) NOTE: This is actually FSX-SE masquerading as FSX-MS Checking if there's already a version of FSUIPC4 installed in: C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL ... Version 4.949p found. FSX-SE Modules folder already exists. Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\User1\AppData\Roaming" Now finding \Microsoft\FSX-SE\FSX_SE.CFG for all users, including this one Looking in "C:\Users\Administrator\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Backups\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\User1\AppData\Roaming" ... No FSX_SE.CFG there Looking for the current user's Application Data path: ... found as "C:\Users\User1\AppData\Roaming" Now finding \Microsoft\FSX-SE\FSX.CFG for all users, including this one Looking in "C:\Users\Administrator\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Backups\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\User1\AppData\Roaming" ... No FSX.CFG there Looking for the current user's Application Data path: ... found as "C:\Users\User1\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\Administrator\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Backups\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\User1\AppData\Roaming" Found FSX.CFG in "C:\Users\User1\AppData\Roaming\Microsoft\FSX\FSX.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. "Modules\FSUIPC Documents" folder already exists. 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 and P3D 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 "ASN WX Radar facilities in FSUIPC4.pdf" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "Offset Mapping for PMDG 777X.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay Installed "Profiles in Separate Files.pdf" okay =========================================================== All installer tasks completed. Registration dialog exit: selected FSUIPC REGISTER Providing FSUIPC registration dialogue ... Registration for FSUIPC4 was successful! (result code 00) *************** End of Install Log *************** ===================================================================================================================== The most recent FSUIPC4.log that I could find was dated 04/07/16. Since every thing has been changed several times since then I've not bothered to send it. If you want it just ask. Here is the most recent DLL.xml file ==================================================================================================================== <?xml version="1.0" encoding="WINDOWS-1252"?> -<SimBase.Document version="1,0" Type="Launch"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> -<Launch.Addon> <Name>VRS_TacPack</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\VRS_TacPack\VRS_TacPack.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> </SimBase.Document> ==================================================================================================================== Both FSUIPC and the VRS TacPack now show up in the MODULES folder of Steam. I'm sorry this whole thing has been so complicated, If I can just get access to my beloved FSUIPC then I can begin to program all the dozens of flight controls and buttons and switches on the F18. Its's complexity makes it almost impossible without your fantastic utility. Hope this is what you need.
  6. Pete, After my last message above I; - did a shutdown and restart - Ran CCleaner - Defragmented - Emptied the recycle bin and I'm sorry to report that the results are the same. FSUIPC still does not show in the ADDONS dropdown window, only the VRS entries still do. Fred
  7. Pete, Hopefully I've got the DLL.xml done now in an easy readable, manner this time! I'm not sure what happened before. ===================================================================================================================== <?xml version="1.0" encoding="WINDOWS-1252"?> -<SimBase.Document version="1,0" Type="Launch"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> -<Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>VRS_TacPack</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\VRS_TacPack\VRS_TacPack.dll</Path> </Launch.Addon> </SimBase.Document> ===================================================================================================================== I've also re-installed FSUIPC4 again and re-updated it to FSUIPC4.949n after renaming the DLL.xml to DLLrename.xml VRS Tac Pak is not installed in either the FSX or the Steam module folders. It's path is; C:\Users\User1\Downloads\Programs\VRS_TacPac_FSX_1.4.2.8.exe and upon clicking the desktop icon for it it functions as it should. FSUIPC is not mentioned in the FSX.cfg [TRUSTED] section after the reinstall. I have modified the Simconnect.ini file and it has now been saved according to the FSUIPC FAQs. With fingers crossed, Pete Thanks, Fred
  8. Pete, Hope you enjoyed your weekend. Color me red with embarrassment over the double posting!. I must have used the wrong finger when hitting the SEND button. All my attempts to edit out the second one went for naught, . "Sorry to disappoint you, but you are most certainly running GSX, not FSX-SE." I'm sure by "GSX" you meant FSX and your right. The old FSX folder tree can still be found at C:/FSX. All the folders and icons are still there except FSX.exe. I find this a bit mystifying because prior to installing FS Steam I deleted FSX using CONTROL PANEL>.PROGRAMS AND FEATURES to delete it and afterthe deletion it no longer appeared in the PROGRAMS AND FEATURES. I double checked the deletion using CCleaner. FS Steam Edition is definitely installed. On my desktop There is an icon labeled Microsoft Flight Simulator Steam Edition. When I click it a small box appears saying something like..."connecting to your steam account" followed by the usual Microsoft opening screen with STEAM EDITION printed in large black letters and each of the flight setup pages likewise have Microsoft Flight Simulator Steam Edition printed on them. The simulator using Steam operates completely normally except that the FPS is much better than it was on FSX. The path to the FSX folder is C:/FSX After considerable searching I finally found the path to the FS Steam.exe. It is; C:/Program Files (x86)/Steam/steamapps/common/FSX It is here, finally, that I found the missing FSX.exe. While there is a whole FSX-like folder tree with many of the same folders as FSX-SE.exe file. There was, however, one intriguing file named FSXSEConfig.exe but I just didn't have the nerve to push it. "Is that when you last tried? Are are you fishing out old files to show me? If you removed FSX how are they still there?" The old FSUIPC4Install.log and FSUIPC4.log files that I sent you are from MODULES in FSX. I sent them prior to your latest email which got me on the hunt for the STEAM MODULES file which I just found today. In this folder is a more recent FSUIPC4 Install.file with the date of 4/20/16 but there is no FSUIPC4.log file in this folder or any other one that I can find other than the one I already sent you in my last posting. I will install the interim update 4.949n as suggested as soon as I finish posting this. The version of FSX I show is 10.0.62615.0 and the version of Steam I show is 62615 By now you have come to realize that I'm not exactly a "rocket scientist" when it comes to finding my way around computers and I want you to know your help and patience is most appreciated. Thanks, Fred P.S. No matter how I try I can not prevent theDLL.xml file from losing it's format when I try to copy and paste it here. I've tried both WORD 2013 anD Notepad but nothing works for me here. ==================================================================================================================== Installer for FSUIPC4.DLL version 4.949h Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX Looking in registry for FSX-SE install path: HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX Parameter"Install_Path" ... >>> OK! FOUND FSX-SE! <<< ... SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX\steamapps\common\FSX Looking in registry for Prepar3D v1 install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v3 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3 Parameter"AppPath" ... NOT found! ... =========================================================== INSTALLATION FOR FSX: SetupPath="C:\Program Files (x86)\Steam\steamapps\common\FSX\" Checking version of the FSX EXE: ... Version 10.0.62615.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 62615 (Steam) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07) NOTE: This is actually FSX-SE masquerading as FSX-MS Checking if there's already a version of FSUIPC4 installed in: C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL ... Version 4.949h found. FSX-SE Modules folder already exists. Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\User1\AppData\Roaming" Now finding \Microsoft\FSX-SE\FSX_SE.CFG for all users, including this one Looking in "C:\Users\Administrator\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Backups\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No FSX_SE.CFG there Looking in "C:\Users\User1\AppData\Roaming" ... No FSX_SE.CFG there Looking for the current user's Application Data path: ... found as "C:\Users\User1\AppData\Roaming" Now finding \Microsoft\FSX-SE\FSX.CFG for all users, including this one Looking in "C:\Users\Administrator\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Backups\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\User1\AppData\Roaming" ... No FSX.CFG there Looking for the current user's Application Data path: ... found as "C:\Users\User1\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\Administrator\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Backups\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\User1\AppData\Roaming" Found FSX.CFG in "C:\Users\User1\AppData\Roaming\Microsoft\FSX\FSX.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. "Modules\FSUIPC Documents" folder already exists. 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 and P3D 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 "ASN WX Radar facilities in FSUIPC4.pdf" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "Offset Mapping for PMDG 777X.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay Installed "Profiles in Separate Files.pdf" okay =========================================================== All installer tasks completed. Registration dialog exit: selected FSUIPC REGISTER Providing FSUIPC registration dialogue ... Registration for FSUIPC4 was successful! (result code 00) *************** End of Install Log ***************
  9. Pete, Attached you will find the requested files. My FS Steam is a stand alone system. I no longer have FSX installed. Thanks for your prompt reply and enjoy your weekend ==================================================================================================================== Installer for FSUIPC4.DLL version 4.949 Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=C:\FSX\ Looking in registry for FSX-SE install path: HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX Parameter"Install_Path" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\DovetailGames\FSX Parameter"AppPath" Not there, so looking in: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v1 install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v3 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3 Parameter"AppPath" ... NOT found! ... =========================================================== INSTALLATION FOR FSX: SetupPath="C:\FSX\" Checking version of the FSX EXE: ... Version 10.0.61637.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) 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:\FSX\Modules\FSUIPC4.DLL ... Version 4.949 found. FSX Modules folder already exists. Okay -- installed FSUIPC4 into "C:\FSX\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\User1\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\Administrator\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Backups\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\User1\AppData\Roaming" Found FSX.CFG in "C:\Users\User1\AppData\Roaming\Microsoft\FSX\FSX.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 ... ... There is a SimConnect.XML, checking for "local" section. ... "local" section already exists, file not modified. "Modules\FSUIPC Documents" folder already exists. 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 and P3D 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 "ASN WX Radar facilities in FSUIPC4.pdf" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "Offset Mapping for PMDG 777X.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay Installed "Profiles in Separate Files.pdf" okay =========================================================== All installer tasks completed. Registration dialog exit: selected FSUIPC REGISTER Providing FSUIPC registration dialogue ... Registration for FSUIPC4 was successful! (result code 00) *************** End of Install Log *************** ==================================================================================================================== ********* FSUIPC4, Version 4.949 by Pete Dowson ********* fsx.exe version = 10.0.61637.0 Reading options from "C:\FSX\Modules\FSUIPC4.ini" Running inside FSX on Windows 7 Module base=673F0000 User Name="Frederick D. Coleman" User Addr="quink99@yahoo.com" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 234 System time = 07/04/2016 20:47:11 234 FLT path = "C:\Users\User1\Documents\Flight Simulator X Files\" 234 ------ Module Version Check ------ 234 acontain.dll: 10.0.61637.0 234 api.dll: 10.0.61637.0 234 controls.dll: 10.0.61637.0 234 fs-traffic.dll: 10.0.61637.0 234 G3D.dll: 10.0.61637.0 234 sim1.dll: 10.0.61637.0 234 visualfx.dll: 10.0.61637.0 234 weather.dll: 10.0.61637.0 234 window.dll: 10.0.61637.0 234 ---------------------------------- 312 Trying to connect to SimConnect Acc/SP2 Oct07 ... 327 FS path = "C:\FSX\" 1061 ---------------------- Joystick Device Scan ----------------------- 1061 Product= Saitek Pro Flight Combat Rudder Pedals 1061 Manufacturer= Saitek 1061 Vendor=06A3, Product=0764 (Version 2.1) 1061 Serial Number= 1061 Product= Pro Flight X65 Control System 1061 Manufacturer= Saitek 1061 Vendor=06A3, Product=0B6A (Version 1.100) 1061 Serial Number= 1061 ------------------------------------------------------------------- 1076 LogOptions=00000000 00000001 1076 ------------------------------------------------------------------- 1076 ------ Setting the hooks and direct calls into the simulator ------ 1076 --- CONTROLS timer memory location obtained ok 1076 --- SIM1 Frictions access gained 1092 --- FS Controls Table located ok 1092 --- Installed Mouse Macro hooks ok. 1092 --- Wind smoothing fix is fully installed 1092 --- G3D.DLL fix attempt installed ok 1092 --- All links checked okay 1092 ------------------------------------------------------------------- 1092 SimConnect_Open succeeded: waiting to check version okay 1092 Trying to use SimConnect Acc/SP2 Oct07 28174 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 28174 Initialising SimConnect data requests now 28174 FSUIPC Menu entry added 28220 C:\FSX\FLIGHTS\OTHER\FLTSIM.FLT 28220 C:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 190695 C:\FSX\SimObjects\Airplanes\VRS_FA-18E\FA-18E-6.8_SE.AIR 242644 Weather Mode now = Theme 322469 Aircraft="VFA-143 "Pukin' Dogs" CAG" 322485 System time = 07/04/2016 20:52:34, Simulator time = 12:25:37 (19:25Z) 323265 Starting everything now ... 323359 ASN active function link set 323359 Ready for ASN WX radar 326744 Advanced Weather Interface Enabled 1657292 Sim stopped: average frame rate for last 1334 secs = 18.4 fps 1873307 Sim stopped: average frame rate for last 41 secs = 16.9 fps 1893587 System time = 07/04/2016 21:18:45, Simulator time = 12:38:54 (19:38Z) 1893587 *** FSUIPC log file being closed Minimum frame rate was 9.9 fps, Maximum was 20.0 fps Minimum available memory recorded was 2547Mb Average frame rate for running time of 1389 secs = 18.3 fps G3D fix: Passes 10120, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 628 Allocs, 628 Freed ********* FSUIPC Log file closed *********** ==================================================================================================================== <?xml version="1.0" encoding="WINDOWS-1252"?> <SimBase.Document version="1,0" Type="Launch"><Descr>Launch</Descr><Filename>dll.xml</Filename><Disabled>False</Disabled><Launch.ManualLoad>False</Launch.ManualLoad><Launch.Addon><Name>Object Placement Tool</Name><Disabled>True</Disabled><ManualLoad>False</ManualLoad><Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path></Launch.Addon><Launch.Addon><Name>Traffic Toolbox</Name><Disabled>True</Disabled><ManualLoad>False</ManualLoad><Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path></Launch.Addon><Launch.Addon><Name>Visual Effects Tool</Name><Disabled>True</Disabled><ManualLoad>False</ManualLoad><Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path></Launch.Addon><Launch.Addon><Name>VRS_TacPack</Name><Disabled>False</Disabled><ManualLoad>False</ManualLoad><Path>Modules\VRS_TacPack\VRS_TacPack.dll</Path></Launch.Addon><Launch.Addon><Name>FSUIPC 4</Name><Disabled>False</Disabled><Path>Modules\FSUIPC4.dll</Path></Launch.Addon></SimBase.Document>
  10. Pete, Attached you will find the requested files. My FS Steam is a stand alone system. I no longer have FSX installed. Thanks for your prompt reply and enjoy your weekend ==================================================================================================================== Installer for FSUIPC4.DLL version 4.949 Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=C:\FSX\ Looking in registry for FSX-SE install path: HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX Parameter"Install_Path" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\DovetailGames\FSX Parameter"AppPath" Not there, so looking in: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v1 install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D v3 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3 Parameter"AppPath" ... NOT found! ... =========================================================== INSTALLATION FOR FSX: SetupPath="C:\FSX\" Checking version of the FSX EXE: ... Version 10.0.61637.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) 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:\FSX\Modules\FSUIPC4.DLL ... Version 4.949 found. FSX Modules folder already exists. Okay -- installed FSUIPC4 into "C:\FSX\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\User1\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\Administrator\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Backups\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\User1\AppData\Roaming" Found FSX.CFG in "C:\Users\User1\AppData\Roaming\Microsoft\FSX\FSX.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 ... ... There is a SimConnect.XML, checking for "local" section. ... "local" section already exists, file not modified. "Modules\FSUIPC Documents" folder already exists. 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 and P3D 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 "ASN WX Radar facilities in FSUIPC4.pdf" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "Offset Mapping for PMDG 777X.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay Installed "Profiles in Separate Files.pdf" okay =========================================================== All installer tasks completed. Registration dialog exit: selected FSUIPC REGISTER Providing FSUIPC registration dialogue ... Registration for FSUIPC4 was successful! (result code 00) *************** End of Install Log *************** ==================================================================================================================== ********* FSUIPC4, Version 4.949 by Pete Dowson ********* fsx.exe version = 10.0.61637.0 Reading options from "C:\FSX\Modules\FSUIPC4.ini" Running inside FSX on Windows 7 Module base=673F0000 User Name="Frederick D. Coleman" User Addr="quink99@yahoo.com" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 234 System time = 07/04/2016 20:47:11 234 FLT path = "C:\Users\User1\Documents\Flight Simulator X Files\" 234 ------ Module Version Check ------ 234 acontain.dll: 10.0.61637.0 234 api.dll: 10.0.61637.0 234 controls.dll: 10.0.61637.0 234 fs-traffic.dll: 10.0.61637.0 234 G3D.dll: 10.0.61637.0 234 sim1.dll: 10.0.61637.0 234 visualfx.dll: 10.0.61637.0 234 weather.dll: 10.0.61637.0 234 window.dll: 10.0.61637.0 234 ---------------------------------- 312 Trying to connect to SimConnect Acc/SP2 Oct07 ... 327 FS path = "C:\FSX\" 1061 ---------------------- Joystick Device Scan ----------------------- 1061 Product= Saitek Pro Flight Combat Rudder Pedals 1061 Manufacturer= Saitek 1061 Vendor=06A3, Product=0764 (Version 2.1) 1061 Serial Number= 1061 Product= Pro Flight X65 Control System 1061 Manufacturer= Saitek 1061 Vendor=06A3, Product=0B6A (Version 1.100) 1061 Serial Number= 1061 ------------------------------------------------------------------- 1076 LogOptions=00000000 00000001 1076 ------------------------------------------------------------------- 1076 ------ Setting the hooks and direct calls into the simulator ------ 1076 --- CONTROLS timer memory location obtained ok 1076 --- SIM1 Frictions access gained 1092 --- FS Controls Table located ok 1092 --- Installed Mouse Macro hooks ok. 1092 --- Wind smoothing fix is fully installed 1092 --- G3D.DLL fix attempt installed ok 1092 --- All links checked okay 1092 ------------------------------------------------------------------- 1092 SimConnect_Open succeeded: waiting to check version okay 1092 Trying to use SimConnect Acc/SP2 Oct07 28174 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 28174 Initialising SimConnect data requests now 28174 FSUIPC Menu entry added 28220 C:\FSX\FLIGHTS\OTHER\FLTSIM.FLT 28220 C:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 190695 C:\FSX\SimObjects\Airplanes\VRS_FA-18E\FA-18E-6.8_SE.AIR 242644 Weather Mode now = Theme 322469 Aircraft="VFA-143 "Pukin' Dogs" CAG" 322485 System time = 07/04/2016 20:52:34, Simulator time = 12:25:37 (19:25Z) 323265 Starting everything now ... 323359 ASN active function link set 323359 Ready for ASN WX radar 326744 Advanced Weather Interface Enabled 1657292 Sim stopped: average frame rate for last 1334 secs = 18.4 fps 1873307 Sim stopped: average frame rate for last 41 secs = 16.9 fps 1893587 System time = 07/04/2016 21:18:45, Simulator time = 12:38:54 (19:38Z) 1893587 *** FSUIPC log file being closed Minimum frame rate was 9.9 fps, Maximum was 20.0 fps Minimum available memory recorded was 2547Mb Average frame rate for running time of 1389 secs = 18.3 fps G3D fix: Passes 10120, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 628 Allocs, 628 Freed ********* FSUIPC Log file closed *********** ==================================================================================================================== <?xml version="1.0" encoding="WINDOWS-1252"?> <SimBase.Document version="1,0" Type="Launch"><Descr>Launch</Descr><Filename>dll.xml</Filename><Disabled>False</Disabled><Launch.ManualLoad>False</Launch.ManualLoad><Launch.Addon><Name>Object Placement Tool</Name><Disabled>True</Disabled><ManualLoad>False</ManualLoad><Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path></Launch.Addon><Launch.Addon><Name>Traffic Toolbox</Name><Disabled>True</Disabled><ManualLoad>False</ManualLoad><Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path></Launch.Addon><Launch.Addon><Name>Visual Effects Tool</Name><Disabled>True</Disabled><ManualLoad>False</ManualLoad><Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path></Launch.Addon><Launch.Addon><Name>VRS_TacPack</Name><Disabled>False</Disabled><ManualLoad>False</ManualLoad><Path>Modules\VRS_TacPack\VRS_TacPack.dll</Path></Launch.Addon><Launch.Addon><Name>FSUIPC 4</Name><Disabled>False</Disabled><Path>Modules\FSUIPC4.dll</Path></Launch.Addon></SimBase.Document>
  11. After many years of happily using FSUIPC with no problems of any kind I now have one though I suspect it may be self- inflicted. After uninstalling my old FSX and then cleaning and defragmenting it I installed FS Steam which worked as it should using a default airplane. I then installed one of the only two airplanes I ever fly, the VRS F18F. Following this I then installed FSUIPC 4.949 which seemed to install normally as it always has in the past. Upon restarting the flight sim I immediately went to the menu bar>ADDONS to check for FSUIPC and although there were several links for various addons associated with the VRS F18 the usual FSUIPC link was not present leaving me with no way to start and use that program. I've found several threads here on the forum pertaining to this same problem but with Prepar3D but none that I could find involving FS Steam.With out FSUIPC availability. I feel like a small child who has lost his nanny! Any help will be most deeply appreciated. Thanks, Quink
  12. Pete, I am running FSX Gold on Windows 7 64 bit with all controls assigned and calibrated through FSUIPC. These controls consist of a Saitek X65F stick and throttle quadrant and Saitek Combat rudder pedals. All has functioned well until about a week or two when I have run into a problem very similar to that of the originator of this thread. In attempting to program the throttles with reverse I suddenly became aware that both of the dual throttles would go from idle to full throttle if they were even touched. The only way they could be returned to idle was to use the FSX F1 key. If manually moved they would return to full thrust. As of yet I've have not found any functional solution to this problem though I've found it has happened to others in the various forums. The only two aircraft I normally fly are the VRS F18E and the PMDG B737NGX. This problem affects both of these as well as any of the FSX default aircraft I tried. Not being "the sharpest knife in the whole drawer" when it comes to the registry I was hoping that you might be able to expand a bit on your quoted statement as to what it is that we should do within the registry to alleviate this problem. Otherwise I may have to throw my very expensive Saitek control set out the window and then open my veins. Please accept my thanks in advance for any assistance with this matter Fred.
  13. Pete, Even after several years of using FSUIPC I have come to realize that the learning with this extremely versatile utility never stops. In this case you were, as usual, absolutely right, The serendipitous part of my problem was that it forced me into the Advanced Users Guide where after a couple of hours of struggling with what, at first, seemed to me to be totally incomprehensible computer gibberish eventually began to become clear enough to allow me to translate the button lines in my FSUIPC. ini and, thus, resolve my problem of the double inputs to one of my buttons. All works as it should now. You're a stern task master and it is much appreciated.......I learned a lot. Thanks again, Fred
  14. As I did in FS9, I have set up in FSX a four way button on my CH PRO THROTTLE (USB) to raise and lower my flaps in increments. Raising the flaps works as it should but when I attempt to extend them while in the VC cockpit they will extend but I also begin to cycle through all the following views; OUTSIDE VIEW - LOCKED SPOT TOWER VIEW - NEAREST TOWER AIRCRAFT VIEW - LANDING GEAR COCKIT VIEW - VRS COCKPIT The end result is that I always get full extension on the flaps which I don't necessarily always want. I can, of course, retract them to the position desired after returning to the VC cockpit but that's a bit unnerving on final approach or during a close in carrier approach. After trying everything I have read about in the FSUIPC documentation I'm at a loss. If anyone could advise me as to how to eliminate the view changing so I only have flap extension when the button is pushed I would be most appreciative. Thanks
  15. Thanks for the prompt reply! In my ignorance I must admit I don't understand the difference between "digital" and "analog" mode as it pertains to flight controls or how I can tell which mode I might be in. I am also not aware of any "switch" in either FS9, FSUIPC, or on my CH Pro Pedals that I might have inadvertantly altered to change from one mode to the other; certainly not in the last four days or so since this problem began. You mentioned that one of my brakes appeared to be calibrated correctly and the other not. How could I tell which one was done correctly so that I won't attempt to recalibrate the correct one? Once both are calibrated correctly I will remove the slopes from the brakes. If you concur that, prehaps, the best solution might be to start fresh I wonder if you might advise me exactly what to remove from both FS9 and FSUIPC to begin with a clean slate from a flight controls assignment and calibration standpoint. Thanks again
×
×
  • 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.