rusblag

Hi John/Pete, all good now. It was me missing a step in the installer. Don't let anyone kid you that getting older is good....it isn't. Regards, Russell

Hi, I've purchased FSUIPC6 from simMarket. In the install I put my name, email and key No. and it says it has installed successfully. When I start Prepar3D v5, it is there, but unregistered. It tells me to uninstall then reinstall to register. I've done this three times already with the same result. What am I doing wrong ?. Regards, Russell.

OK, 5.123b installed perfectly. No two ways about it, your support is second to none. I believe you are around one year younger than me, and it amazes me that your brain is still active and sharp enough to deal with, and cure, the constant stream of cries for help from all over the globe. It really is appreciated Pete. /Russell.

Hi Pete, That's strange, as I was unaware that P3d had ever closed with a crash, it's always appeared to close normally. I always run the installer as administrator. 5.123 is the first one that's given me a problem. Would it be a good idea to delete the 5.123 and install 5.122a again, which worked perfectly ? No, I don't use Linda. Thanks for your help anyway...much appreciated. I've deleted 5.123, installed 5.122 then updated to 5.122a. Everything is now back and working. Doesn't that point to a fault with 5.123 ? /Russell

Oh damn...I was looking in the wrong place. Here it is. Sorry about that. /Russell SimConnect0.Log

Hi Pete, I created the simconnect.ini and placed it in the Prepar3D files in My Documents, then ran the sim. It shows nothing. This is the simconnect.ini Have I done it right ? /Russell simconnect.ini

Sorry about that Pete. DLL.zip

Forgot to say...I downloaded it at 10.42pm today. /Russell

<?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>SSWF-104S</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-F104S-ASA\modules\zipper.dll</Path> <DllStartName>f104s_cvars_init</DllStartName> <DllStopName>f104s_cvars_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>SSW_NASARR21G</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-F104S-ASA\modules\nasarR21G.dll</Path> <DllStartName>nasar21_init</DllStartName> <DllStopName>nasar21_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>vACMI</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>.\vACMI.dll</Path> <DllStartName>vacmi_cvars_init</DllStartName> <DllStopName>vacmi_cvars_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>Traffic Toolbox</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>D:\Lockheed Martin\Prepar3D v4 SDK 4.1.7.22841\World\Traffic\traffictoolbox.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Visual Effects Tool</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>D:\Lockheed Martin\Prepar3D v4 SDK 4.1.7.22841\Modeling\Special Effects\Visual FX Tool\visualfxtool.dll</Path> </Launch.Addon> <Launch.Addon> <Name>SSW-F84F</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-F84F\modules\thunder.dll</Path> <DllStartName>f84_cvars_init</DllStartName> <DllStopName>f84_cvars_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>WebSimClient</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimSkunkWorks\WebSimConnect\modules\WSC_Client.dll</Path> <DllStartName>wsc_cvars_init</DllStartName> <DllStopName>wsc_cvars_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>SSW-PA200</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-TORNADO\modules\panavia.dll</Path> <DllStartName>pa200_cvars_init</DllStartName> <DllStopName>pa200_cvars_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>SSW_PA200_RADAR</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-TORNADO\modules\pa200radar.dll</Path> <DllStartName>radar_init</DllStartName> <DllStopName>radar_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>SSW_NASARR15</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-FRF-104G\modules\nasarr15.dll</Path> <DllStartName>nasarr15_init</DllStartName> <DllStopName>nasarr15_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>SSW-FRF104G</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-FRF-104G\modules\zipper_g.dll</Path> <DllStartName>frf104g_cvars_init</DllStartName> <DllStopName>frf104g_cvars_init</DllStopName> </Launch.Addon> <Launch.Addon> <Name>SSW.MIRAGEF1</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-MIRAGE-F1\modules\ssw_miragef1.dll</Path> <DllStartName>f1_cvars_init</DllStartName> <DllStopName>f1_cvars_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>MIRAGE_RWR</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-MIRAGE-F1\modules\F1rwr.dll</Path> <DllStartName>f1_rwr_init</DllStartName> <DllStopName>f1_rwr_init</DllStopName> </Launch.Addon> <Launch.Addon> <Name>SSW-AV8IIB</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-AV8B-HARRIER-IIB\modules\harrier.dll</Path> <DllStartName>av8_cvars_init</DllStartName> <DllStopName>av8_cvars_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>SSW-RBVSTOL</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>SimObjects\Airplanes\SSW-AV8B-HARRIER-IIB\modules\rbvstol.x64.dll</Path> <DllStartName>cvars_init</DllStartName> <DllStopName>cvars_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 5</Name> <Disabled>False</Disabled> <Path>D:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.dll</Path> </Launch.Addon> </SimBase.Document>

Hi Pete, Never ever had a problem updating before. Had ver. 5.122a and updated to ver.5.123 The install log says it installed OK...but no FSUIPC in the addon menu, but the log file and ini file stayed the same showing ver. 5.122. I deleted the log file and re-ran the installer. That put a 5.123 installer log in the modules folder, but still left the ini file showing ver.5.122, but still no FSUIPC in the addons menu, so it appears to be not actually installing. /Russell Installer for FSUIPC5.DLL version 5.123 Looking in registry for Prepar3D v4 install path: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4 Parameter"AppPath" ... >>> OK! FOUND Prepar3D v4! <<< ... AppPath=D:\Lockheed Martin\Prepar3D v4\ =========================================================== INSTALLATION FOR Prepar3D v4: AppPath="D:\Lockheed Martin\Prepar3D v4\" Checking version of the Prepar3D v4 EXE: ... Version 4.1.7.22841 (Need at least 4.1.0.0) Checking if there's already a version of FSUIPC5 installed as: D:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL ... Version 5.123 found. D:\Lockheed Martin\Prepar3D v4\Modules folder already exists. Okay -- installed FSUIPC5 into "D:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Rus\AppData\Roaming" Now finding \Lockheed Martin\Prepar3D v4\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\Public\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Rus\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\Rus\AppData\Roaming\Lockheed Martin\Prepar3D v4\Prepar3D.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC5 section. ... FSUIPC5 section already exists but will be replaced. ... FSUIPC5 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 "FSUIPC5 User Guide.pdf" okay Installed "FSUIPC5 for Advanced Users.pdf" okay Installed "The 2016 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 "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "FSUIPC4 Offsets Status.pdf" okay Installed "Profiles in Separate Files.pdf" okay Installed "FSUIPC5 History.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" 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 "Offset Mapping for PMDG 747QOTSII.pdf" okay =========================================================== All installer tasks completed. Registration dialog exit: selected FSUIPC CHECK Checking FSUIPC registration ... Registration check for FSUIPC5 was successful! (result code 00) *************** End of Install Log ***************

Go to the SimSkunkWorks web page and open a ticket on the help desk. /Russell.

Very well said Pete, I agree 100%. Russell.

Richard...reply is on SSW forum. I'm pretty sure it's not an FSUIPC problem.

I used the Saiteks for years, and there was ever only one SaiD0762.pro file in System32. With the X36 it was called SaiDo255.pro so I don't know how you have two in the same folder. It's been a year since I had the X52 installed, but am fairly sure that you should be able to programme the three switches on the stick, T1, T2 etc. with that file in place. Those same switches stopped working on mine, after my son spilled a drop of coffee on them, are you sure they are clean ? Removing that file will definitely allow you to programme the scroll wheel button, and in fact every button on the stick and throttle. I never used the saitek's programming software, I assigned them in FS9, then FSX, and now Prepar3D. Have you tried uninstalling / reinstalling the Saitek drivers ? Btw, after removing the SaiD0762.pro file, you MUST unplug/replug the X52 in order for the programming to work. /Russell.

Yes, as Andy says, go to windows system32 and remove the file SaiD0762.pro You will then be able to programme every button and switch on the stick and throttle. I don't know whether that includes the mode switch that Andy refers to as I never tried that one. I did this on my X36...X52.. and X52pro with no problems, but I've now moved onto the Warthog. /Russell.

Oh dear, I'm not having a good day...written this once, and my connection went down as I hit the send button. OK Pete, you deserve an explanation, and an apology. Having never used FSX before, I assumed FSUIPC4 had shipped with the sim. For over a year now 99% of my flying has been with a fighter jet being developed to ultra realism by a talented team, some of whom flew this jet when it was in service. As I'm involved (in a small way) with the development, I've been using all the beta models with absolutely no problems. They'ed just sent me the beta for FSX (hence my purchase of the sim) Yes Pete, I can see you nodding your head...the last thing on earth I would ever have suspected, brought it in. First off, I had deleted just the fsuipc4.dll Then ran the installer from Shiratti. I suppose the key file still in the modules folder was jigging it up. After clearing the modules folder completely, I now have fsuipc registered and running correctly. Pete, please accept my sincerest apologies. Russell.

Pete, never had FSX on my computer before, bought a sealed copy of FSx Gold Edition from Amazon.co.uk. When I installed FSX, that fsuipc4 was in the modules folder, but not showing in the fsx menu bar. I then deleted the fsuipc4.dll...downloaded and ran the 4.53 installer from SimMarket..then installed the latest update from your support page 4.551, then paid for it via SimMarket. I've been a registered user of fsuipc on fs9 since 2003. ABSOLUTELY no pirated stuff whatsoever. And no..I did'nt make a mess of anything..it appears a legitimate copy of fsx was shipped to me with this bloody thing already on board. When I start fsx and use the drop down menu to access fsuipc, the Register now button is greyed out, thats where the message to shut fsx down, and right click the start icon is. I'll now delete everything related to fsuipc (I only deleted the dll before) and start again from scratch, and see where that gets me. After doing everything above board and legitimate, it infuriates me for you to insinuate that I'm using pirated stuff, an attitude I could understand if I was trying to get out of paying..but I've paid..check with simMarket. Russell.

Hi Pete, just installed FSX for the first time. Have also purchased FSUIPC4. The documentation tells me to right clickthe FSX start icon and "run as" administrator. I am the administrator, but when I do this it give "error=28 Unable to run message filter." Then flight simulator has encounted a problem and needs to close. I can't choose another account, because mine is the only one. This is the log file...who the hell is Archie Scott ? I downloaded this dll from your support page. ********* FSUIPC4, Version 4.551 by Pete Dowson ********* Reading options from "D:\Program Files\microsoft Games\Flight Simulator X\Modules\FSUIPC4.ini" Trying to connect to SimConnect Acc/SP2 Oct07 ... User Name="Archie Scott" User Addr="archiescott369@aol.com" FSUIPC4 not user registered WIDEFS7 not user registered, or expired Running inside FSX (using SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed DebugStatus=0 172 System time = 28/11/2009 12:54:28 172 FLT UNC path = "D:\My Documents\Flight Simulator X Files\" 172 FS UNC path = "D:\Program Files\microsoft Games\Flight Simulator X\" 1188 LogOptions=00000000 00000001 1188 SimConnect_Open succeeded: waiting to check version okay 3813 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 3813 Initialising SimConnect data requests now 3813 FSUIPC Menu entry added 3875 d:\my documents\flight simulator x files\Rimini.FLT 3875 D:\Program Files\microsoft Games\Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR 38719 System time = 28/11/2009 12:55:06, Simulator time = 12:54:31 (11:54Z) 39391 Advanced Weather Interface Enabled 70391 System time = 28/11/2009 12:55:38, Simulator time = 12:54:42 (11:54Z) 70391 *** FSUIPC log file being closed Average frame rate for running time of 11 secs = 25.9 fps Memory managed: 7 Allocs, 7 Freed ********* FSUIPC Log file closed *********** Regards, Russell.

Ooops, sorry...yes...KEY file, sorry, I used the wrong word. Russell.

Pete, I cut the Reg. file out of my own fs9 modules folder, and put it in a spare folder, before I uninstalled fs9. After reinstallig fs9, I put the SAME Reg. file back in the modules folder, then ver. 3.8.7.4.dll It's the ONLY FSUIPC Reg. file on my computer. I simply moved it from one place to another..then back again. I have now got it correctly registered in my name. I SHOULD have thought of doing this before. I deleted the Reg. file, restarted fs9, then was able to register it in my name. Trouble is, it's that sort of unexplainable ( and what you would think was impossible) thing that makes, for me, the process of getting everything back up and working such a bloody nightmare. Thanks for your incredibly fast response. I'll get that reg. file out the bin and send it to you. Regards, Russell.

Hello Pete, after re-installing fs9, I placed the FSUIPC Reg.file in the modules folder...then downloaded the latest FSUIPC dll and put that in the modules folder. It works perfectly..but..it's registered in someones name I've never heard of, complete with unknown email address. I've just notified Sim Market, but thought I'd better let you know too. Regards, Russell.