Jump to content
The simFlight Network Forums

Paul K

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Paul K

  • Rank
    Member
  1. Ah, thanks for that Ian. If I ever have to do yet another reinstall of P3D, I might come back to this thread and pick your brains on that. Its certainly reassuring to know I'm not alone. Thanks again ! By the way, a bit off topic, but thanks for doing RAF East Wretham. I used to drive past it every day going from Thetford to Watton. Its a neat little Army camp now, for troops using the nearby STANTA battle area. Much enjoyed it in FSX. :)
  2. Okay Pete, well, if and when I next uninstall P3DV2.1, I'll take some screenies of the registry before, during and after. I swear I uninstalled both v1.0 and v2 correctly - I don't suppose there could be a remnant of the 1.4 installer thats been left inside the 2.0 installer by Lockheed Martin, is there ? Something that reintroduces that spurious v1.0 folder when you install v2.0? Just a bit of uninformed speculation on my part. Anyway Pete, thanks again for your time and help. Very much appreciated. :)
  3. Pete, thanks hugely for the help. It really is appreciated. :) This business with uninstalling P3D v1... I had similar errors when installing FSUIPC into v2.0 last year, and read a thread here where someone had had the same problem. You advised him about the incorrect uninstall of v1, and so I decided to uninstall v2.0, ran Ccleaner, and then went through the registry 'by hand' so to speak, deleting every reference to Lockheed Martin that I could find, so ensuring ( I hoped ) that there was nothing remaining that referred to v1 or v2.0. At that time I deleted both the folders you see here, in HKEY_CURRENT_USER / Software. Both folders reappeared after installing P3D v2.1. Is that correct ...what I mean is, should there still be two Lockheed Martin folders as shown ? I know you are a busy bloke, and I don't want to put you to any further trouble on my behalf...but if having two Lockheed Martin folders is correct, could you tell me where else the references to v1 might be in my registry ?
  4. First off: Windows 7 Pro 64 bit P3D Version 2.1.9936.0 FSUIPC version 4.929 P3D has been run several times prior to installing FSUIPC During installation, I had several messages pop up, which I show below in sequence. At the end of the process, it appears that both P3D is working correctly, and the FSUIPC interface is available in the sim under the Add Ons menu. All appears normal, and pretty much as I remember it in FSX. However, there is still a gnawing doubt; why all the error messages ? Anyway, here's what happened after I right clicked on FSUIPC Installer.exe and ran it as administrator... Picture 1 I clicked on the OK button in the picture above, and then I got this in Picture 2. To reiterate what I said at the beginning of this post, I have run P3D several times prior to this installing of FSUIPC. Honest ! Picture 2 I clicked on the OK button in the above picture, and I think it was at this point that I was asked to find P3D.exe myself, which I did. Things proceeded from there, as can be seen in Picture 3 Picture 3 I clicked on YES in the picture above, and then I have this appear in Picture 4 Picture 4 After clicking on the OK botton in the picture above, I arrive at the usual registration option as shown in Picture 5 Picture 5 At the end of all this, I decided to run the installer once again, just to see if it went normally ( I think I got the same message in Picture 4 again ). Anyway, here is the Install log :- Installer for FSUIPC4.DLL version 4.929 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="D:\Lockheed Martin\Prepar3D v2" Checking version of the Prepar3D EXE: ... Version 2.1.9936.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) Checking if there's already a version of FSUIPC4 installed in: D:\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL ... Version 4.929 found. Prepar3D Modules folder already exists. Okay -- installed FSUIPC4 into "D:\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Paul\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\Paul\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No Prepar3D.CFG there Cannot edit the DLL.XML file to activate FSUIPC. =========================================================== INSTALLATION FOR Prepar3D v2: SetupPath="D:\Lockheed Martin\Prepar3D v2\" Checking version of the Prepar3D v2 EXE: ... Version 2.1.9936.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) Checking if there's already a version of FSUIPC4 installed in: D:\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL ... Version 4.929 found. Prepar3D v2 Modules folder already exists. Okay -- installed FSUIPC4 into "D:\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Paul\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\Paul\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\Paul\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 already exists. 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 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 "Offset Mapping for PMDG 737NGX.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay =========================================================== All installer tasks completed. *************** End of Install Log *************** And here is a copy of DLL.XML which is located in C:\Users\Paul\AppData\Roaming\Lockheed Martin\Prepar3D v2 :- <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <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> As I say, both P3D and FSUIPC seem to be running fine, so everthing might be okay and I'm worrying about nothing. All I need is a 'Yes, that all looks okay' ... or help with whatever might be wrong. Many thanks in anticipation
  5. Thanks Andy. I'll see what can be done using Saitek software once my X52 is back, but as I say, I really would like to keep it all within FSUIPC if I can.
  6. Pete, Kosta, thanks for the responses. Pete, yes, I'd already read the changes document, and it was this that informed me that the mouse look could be enabled while the wheel button was pressed down. Up until then I had been using the spacebar to toggle mouse-look on and off. What I'm asking is...can I make the mouse wheel button act in the same way as the spacebar, i.e. to toggle mouse-look on and off, rather than it only being active while the wheel button is held down. ( Actually, if you do toggle mouse-look on with the spacebar, you can toggle it off by pressing and releasing the wheel button, so in a sense we are half way there. ) Kosta, I'll have a look at your method, when my X52 Pro comes back. Its being repaired at the moment ( oh quelle surprise). However, I'd like to keep it in FSUIPC if possible.
  7. Quick question; is it possible to use the centre ( wheel) mouse button to toggle mouse look on and off, rather than have mouse look active only while the centre mouse button is held down ? The reason I ask is I'm finding it a bit awkward zooming the view in and out while holding the button down. A minor thing, but I thought I'd ask.
  8. Clive, I assume you mean the mouse wheel on the front edge of the Saitek 52 throttle, yes ? If so, uninstall the software that came with your stick, run a registry cleaner like Ccleaner and download the latest versions from the Saitek web site. I have an X-52 Pro, and after installing the latest drivers and software, I can use the throttle mousewheel for trim. With mouselook enabled, I can use the little thumb stick to look round but while in this mode, the throttle mousewheel will zoom your view in and out. Disable mouselook and you will be back to trimming as before. You will find that you can really finely adjust the trim, and of course it frees up two buttons that might otherwise have been assigned to trim up and down. :)
  9. Hi Peter, thanks very much. I kept it *-0.01,+163, and that seems fine, though I will tweak it a little. Please accept my apologies - I'm really getting places with the FSUIPC manual and tutorials now, but the reverse axis part obviously eluded me. I'm sure you have better things to do on a Thursday afternoon than repeat what you've already said in the manual, so I apologise again. Thanks once more for your help and this absorbing FSUIPC you've come with, Peter. The more I learn, the more amazed I am at what it's capable of. No flight simmer should be without it. :smile:
  10. Nico, Peter...thanks for all the information. I'm learning FSUIPC ( version 4.827 ) slowly but surely, and I too wanted to assign zoom view to the thumb slider on the Saitek X52 Pro throttle. Thanks to this thread, I have been able to. :) The entry in my fsuipc.ini file is exactly the same as Nico's... 6=0S,256,F,65701,0,0,0,*0.01,+163 Can I edit this to reverse the axis...so I zoom IN when I move the thumb slider to the right, instead of zoom OUT ? Sorry if its a stupid question. Regards Paul
  11. No complaint, Volker. I know that if it was possible, you and Sascha would fix it. :wink: I'll look at the two URLs you provided. I've also looked at an application called EasyNavs, but I think its a bit too technical for my tired old brain. Thanks again Paul
  12. Thanks for clearing that up for me, Volker. Its a pity, because the only way one can verify whether all the nav-aids used in an FSC-generated flight plan actually exist, is to load it into FSX and check along the route nav-aid by nav-aid. Thanks again for your help. Regards Paul
  13. Thanks, Volker. I guess the bottom-line question is... If I have FSC9 directly connected to FSX as instructed on page 112 of the manual AND if I have the flight plan loaded in both FSC9 and FSX..is there any way the nav radios in my aircraft are going to detect that extra FSC9-only VOR ? If yes, then I will return to the manual and study it more. If not, I might as well go back to using the flight planner inside FSX. Regards Paul
  14. Hi Volker, thanks for your answer. Then how can I create a flight plan in FSC9 using radio navigation aids such as VORs if I can not be sure that all those VORs exist in FSX ? For someone like me who prefers the older style of navigation, and not GPS or any type of 'moving map', we can not be sure that the nav. radios will detect our VOR or NDB way points. Surely it would be better that the FSC9 database manager relies only what actually exists in FSX, or at least have the ability to choose that option when the database manager is run. Alternatively, is it possible to update FSX's database of nav aids to match that in FSC9 ? Regards Paul
×
×
  • 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.