Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Content count

    33,419
  • Joined

  • Last visited

  • Days Won

    99

Pete Dowson last won the day on November 28

Pete Dowson had the most liked content!

Community Reputation

165 Excellent

About Pete Dowson

  • Rank
    Advanced Member
  • Birthday 08/27/1943

Contact Methods

  • Website URL
    http://

Profile Information

  • Gender
    Male
  • Location
    Near Stoke-on-Trent, UK
  • Interests
    Flight Simming, Steam Railways, Table Tennis

Recent Profile Visitors

23,059 profile views
  1. TQ6 ADV- A/T disengage

    AT Arm means ARM the A/T. You need A/T disengage the one operated by the buttons either side of the throttle handles. Oh, exactly as Thomas found for you. :-) How did you miss those? Altough there are two (one button either side) the should do the same thing. Pete
  2. TQ6 ADV- A/T disengage

    Most PMDG aircraft have their own systems, and do not use FS controls. The PMDG 737 has its own list of controls ("Events") which can be assigned via FSUIPC's "<custom control>" selection. You need to work out the number from the comprehensive list towards the end of the .h document in your 737's SDK folder. Pete
  3. Please don't append to this thread again. I shall close it. The subject is different to your question. Did you read the Changes document included in the ZIP which clearly stated that it needs P3D4.1? There are other threads too on exactly the same subject. You need to update your P3D! Pete
  4. Thanks. I don’t see any reason for problems there. The only other thing I can think of is that the GUID that FSUIPC obtains from the registry is actually allocated to another non-Joystick type of device, so accessing it with joystick type requests causes the crash. If that is the reason then it does imply a mess in the Registry. If you have a restore point from before you first installed the unit, now’s the time to use it. Or even just a Registry backup. Otherwise I’d need even more, as the only way I can tell is to look at the relevant part of the Registry, the part under the key "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput”. If you don’t know how to export that to a file for me to look at let me know and I’ll provide some instructions. If you do, don’t try attaching a .REG file or it'll fail. Rename it as a .txt file first. Eeither way, I can’t get to it till tomorrow now. Sorry. Pete
  5. I see the crash is in a Windows DLL. It would be worth your while Googling that DLL for information. It rings a bell but I can’t recall the details. Also, run my HidScanner program and attach the log you get from that please. You’ll find in in the Useful Additional Programs thread of the Download Links subforum. This will show if there’s some conflicting device, which I suspect after looking at the log you attached. When you deleted the drivers and device, I assume you re-booted so that the device would be seen as a fresh USB HID device, which is all it needs. However, I’m not sure that gets any mess in the Registry cleared out. But that would be another step. Pete
  6. FSUIPC 5.103

    Only the current version of FSUIPC is ever available. You must update your P3D to 4.1. Why do you want to go backwards when things only improve Pete
  7. First, a clarification: there is no "demo version". The only version is either registered or not. In its unregistered state t just offers an interface to applications, and none of the user facilities. Second, without more information I cannot help. Did you re-enter the Registration details correctly, or copy the correct files from a backup you made before re-installing Windows (the FSUIPC5.INI and KEY files are important)? Anyway, please show me the Install log and the FSUIPC5.LOG files from the P3D Modules folder. Pete
  8. Problem with FSUIPC 5.122

    You don't mention what version of P3D you've installed, but it sounds like it is 4.0. as stated in the changes notes in the FSUIPC 5.122 download, it is not compatible with 4.0, you MUST update P3D to 4.1. Pete
  9. FSUIPC5 Problem

    FSUIPC5 is no longer compatible with P3D version 4.0. You MUST update to P3D 4.1. It does tell you this in the Change notes included with the FSUIPC downloaded installer! And you are lucky I found your post! There are others, more recent, on exactly the same subject which you should have looked at first, but in any case, please NEVER add a new post to a very old thread or it will often simply not be seen, being hidden way down many pages deep! Pete
  10. FSUIPC 5 under Prepar3d V4

    Is that DLL.XML file exactly as you found it? Because the 4th line is incorrect <Filename>dll.xm</Filename> should be <Filename>dll.xml</Filename> and the iVap entry cannot work, and the error there probably means the whole file is ignored: <PathC:\Program Files (x86)\IVAO\IvAp v2\Ivap_fsx_bootstrap.dll</Path> missing the > after <Path. Did you test iVap before installing FSUIPC? If it doesn't work after correctingthe mess (which i suppose the iVap installer made), then I need to see your Install Log file as well. That's the main reference and the reason it is produced is specifically to help resolve such problems. Also, check the P3D Modules folder. C:\Program Files\Lockeed Martin\Prepar3d v4\Modules If there's an FSUIPC5.LOG file, show me that too. BTW there's no option "Modules". That's the name of the folder. FSUIPC appears in the Add-Ons menu, once P3D is ready to fly. Pete
  11. P3D V4.1 not starting with FSUIPC 5

    That seems a bit muddled. "starting Win10 Pro"? "Win10 Pin". And you get a message about P3D without even trying to start it? Anyway, certainly FSUIPC has absolutely nothing to do with screens and starting either Win10 Pro or P3D. It doesn't even get loaded until P3D starts! You'll need to look elsewhere. Probably the L-M P3D support forum is the correct place for such an odd thing, unless you do really mean Win10 Pro in which case you need Microsoft support. Regarding FSUIPC5, the Install Log for FSUIPC shows you are installing FSUIPC 5.122 but that you are still using P3D version 4.0. From the Log: Checking version of the Prepar3D v4 EXE: ... Version 4.0.28.21686 (Need at least 4.0.20.21316) You MUST update your P3D to 4.1. Version 4.0 is not supported. This was made clear in the change notes for FSUIPC! Pete
  12. $400.00 Dollar Paperweight

    I thought from your earlier messages you were already running fSUIPC, or have you only just installed it? Say YES, get the crash, then show me: 1. The Windows crash details from the Windows Event viewer, and 2. The FSUIPC4.LOG file from the sim Modules folder. Pete
  13. $400.00 Dollar Paperweight

    As DaveG says, uninstall the software which came with it. In fact, best to go to the Windows Device Manager, select the device and right-click, and uninstall. Select drivers to be uninstalled too when the option arises. Then re-boot the system and let the device install with default USB drivers. Pete
  14. Mouse Yoke Rudder Control

    But it was killed in the normal process of closing down the Sim, as clearly shown in the Log! All threads started by FSUIPC must be closed to allow P3D to close down tidily! If you want the thread to continue running, then so must FSUIPC and P3D! Pete
  15. P3D V4.1 not starting with FSUIPC 5

    Are you running P3D version 4.1? What version of FSUIPC did you install? 5.122 (or later) is not compatible with P3D4.0 so you would need to update P3D. And regarding this Error 1332 is documented as meaning "No mapping between account names and security IDs was done.", whatever that means. So my questions would be: 1. Did you run the installer "as administrator" as instructed? 2. Was the end result effective? i.e are there FSUIPC5.INI and FSUIPC5.LOG files in the Modules folder? 3. What does the Security tab in the modules folder properties show? Is "Everyone" included as a user name, and if so, when selected, are there ticks below against "Full control" and "Modify"? If not you will need to set it yourself. If there is a FSUIPC5.LOG file in the Modules folder, please show it to me. Why delete the folder? That means re-installing each time. If you must stop FSUIPC loading, just rename FSUIPC5.DLL to FSUIPC5.DLX (or anything different) and it won't then load. Pete
×