Pete Dowson

No, it won't. There's no relation. Each keeps to its own Modules folder within its own simulator. Pete

Buy and install FSUIPC5, the 64-bit version, then do as Thomas says. P3D doesn't "find" FSUIPC's file: FSUIPC does! Pete

As Thomas says, check the Download Links subforum. That's where all my software is found. There are actually two separate 64-bit PFC drivers, just as for 32-bits -- 64 bit equivalents of PFCFSX.DLL and PFCHid.DLL. The new ones are called PFCcom64.DLL and PFCHid64.DLL. Both have been available both here and on the usual Schiratti "Dowson" page since last June 12th! Pete

Good! Happy flying! Pete

Sorry, but I don't see where I've been "rude". And there's no SHOUTING at all -- shouting is always denoted by all capitals. Emboldening is only an attraction for attention, and in this case it was just a "By The Way", so that next time you might provide a title which attracts those other users here which know more about the specific subject. This is particularly important for when I'm away, which is quite often. The other folk here are generally very helpful, but do need to be attracted to your post by some idea of the subject. I think your reaction to such advice is rather extreme and it is really unwarranted and hurtful. Should I put this down to your malady? Please take a good look through othere threads here to see my prompt and useful support which is generally appreciated. I'm not sure how much longer this will continue, mind. I am 75 this year and look forward to a bit more time off in my remaining years. (BTW according to the SPAD website, it uses FSUIPC in any case. ;-) ) Pete

This is a well known problem which is a combination of Windows marking the DLL as unwanted, and SimConnect, par of FSX, ignoring the error Windows returns when it tries to load the DLL. SimConnect actually assumes the DLL is loaded and jumps to where its entry point should be -- result, crash. When a program crashes, as your FSX-SE did, then Windows marks the last DLL left stuck running memory as "bad" which stops it loading next time. Re-run the FSUIPC4 Installer. The installer clears the Registry flag which tells the system not to load it. Pete

Got it. Thanks. I'll upload it and link it today. [LATER] Okay, "FxmlToFlt" is now available in the Download Links subforum, in the "Useful Additional Programs" thread. Pete

It is still the same sim control. There's no separate "axis" operating the parking brake, as it is a simple toggle switch in the sim. What would be the point of all the intermediate positions? The parking brake is either on or it isn't. There is an example in the documentation for assigning a GGear Lever axis to operate the gear switch (which is also a simple switch, except that the Sim provides separate UP and DOWN controls for that, which it doesn't for parking brake). BTW, it makes no sense at all entitling a question here as "John" as you have done. Next time you post please use a subject title which does describe the subject NOT the person posting it. Pete

The letters are what you assign too, so it doesn't matter if they change Joystick numerical IDs. The only thing that matters then is the unique device "GUID" which is attached to the joy letter. The GUID will only change if you reinstall Windows or move to another PC. Oh dear. You miss the point completely. Using the letter assignments deals with changes in the joystick numbers assigned by Windows which can change if you unplug devices, or if Windows sees them in a different order, or if a Windows update occurs. Once all of the assignments are associated with a letter rather than the Windows-assigned number, it no longer matters if Windows changes the numbers! Pete

That's the best way, yes. There is another way too: enable Event logging in FSUIPC and operate the control in the normal Flight Sim way -- keyboard or mouse click. the control being used, if there is one, will be logged. So then just look in the log file (FSUIPC4.LOG or FSUIPC5.LOG, in the sim's modules folder). Pete

Didn't you try "Parking brakes"? Seems pretty clear to me! Not obvious enough for you? For the slightly more obscure names you could try searching in the List of Controls document supplied for you in the FSUIPC Documents folder, but that is hardly necessary in this case! Almost all of the names are those originally chosen by Microsoft. Pete

Assuming you are talking about FSUIPC, which I support, then I need to see these files from your FSX Modules folder: FSUIPC4.INI FSUIPC4.LOG FSUIPC4.Joyscan.CSV You can either attach them as files, or paste their contents in a message using the <> button above the edit area here. Pete

If it is freeware, I can host it here in the Download Links subforum, or you could post some notes on it in User Contributions. I'll upload the file itself and add the link if you email me the file (petedowson@btconnect.com). Pete

Good. Pete

That's strange -- most perople complain the other way, that is isn't as sensitive as the P3D implementation. Both are actually doing exactly the same thing, sending the same P3D control. sorry, don't know how to make it "less sensitive" except by changing your mouse options in Windows' control Panel. Pete

I've moved your support request from the "User Contributions" subforum, which is a library repository for user contributions, to the correct Support Forum. Please always post support questions here if you want answers! Since the "memory left" is useless in P3D4 why not just replace the offset (24C) read there by the one for the AI count (25C), also a "UD", and change the text label accordingly? Pete

If FSUIPC is not registered, there are no weather features available to users other than logging it, so you can't change anything. There is no way it is influencing the weather unless there is an external program using its interface to do this, and you can't "set it off" if so. even in a registered install. The relationship between airspeed and mach is complex, but depends very much on air density which in turn relates to the pressure (hence altitude). Check the QNH when this happens -- it it probably rather low (but I might need correcting on this). If the problem is solely with the QW B757 then you'd probably need to ask in their Support Forum. Pete

Sounds exactly as if you have not disabled controllers in P3D and so its assignments conflict with FSUIPC's. You have no flaps assignment in FSUIPC. Pete

I've moved your post to the SUPPORT FORUM. Please ALWAYS post support questions for FSUIPC here! Otherwise they'll probably be missed! You are running P3D 4.0. You need to update to 4.1 in order to use FSUIPC 5.122. This is clearly stated in the release mntes in the ZIP. Pete

Error 267: ERROR_DIRECTORY 267 (0x10B) The directory name is invalid. Try: 1. No "" at all. 2. "" just aound first part 3. "" just arouund second part 4. Make second part just ivap_fsx.dll, no path. I wouldn't have thought the path was needed. Pete

Oh dear. Didn’t you read the Installation document included in your downloaded Zip file? All FSUIPC documentation, plus many other ‘goodies’ are in the FSUIPC Documents folder within the sim’s Modules folder, right next to FSUIPC itself! Pete

What happens? Is there any indication? Is there any log entry in the FSUIPC log file? Try omitting the "", or just having them on the first part. Pete

I don't even know what "PLC"s are! If they can emulate a USB joystick type device then you don't need any programming. If they look like another type of HID ("Human Interface Device") then you could program their actions in FSUIPC by relatively simple plug-ins written in Lua, a simple scripting language for which you'll find details on the main Lua webste. For any other type of device you've got to learn not only how to program the PLCs but also the interface into FSUIPC. All I can offer is examples, I cannot teach programming. This is not the place for learning languages, sorry. If you aren't a programmer and are not already learning programming, why are you using PLCs? Pete

Well "HID" stands for "Human Interface Device", but I've no idea otherwise. Action Star do make hubs, but also some other USB things like USB-VGA connectors for screens. If it is a hub with nothing connected other USB devices connected to a hub would show up as disconnecting and reconnecting too I think), then just try disabling it in the Windows Device Manager. If you are using it for anything then you should soon find out what, otherwise it should stop the reconnections. Alternatively, if it isn't affecting anything you are using then you can tell FSUIPC not to re-scan devices on connection. Just change Yes to No on this [General] parameter: AutoScanDevices=Yes Then, if you want a newly-connected device to be recognised by FSUIPC you'd have to go into the Axis or Button assignments tabs in FSUIPC Options. Pete

I've just checked, and in the version of FSUIPC you have you can enable extra logging which will identify devices disconnecting and/or re-connecting. You can enable it by adding: Debug=Please LogExtras=x200 Then the log sequence you'll see before the re-scanning entries will be (for example): 548608 ***** A device has been attached! 548608 Device at "\\?\HID#VID_16C0&PID_05BA#7&2620a131&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 548608 HID: Vendor=16C0, Product=05BA (Version 1.37) 548608 Manufacturer= Leo Bodnar 548608 Product= BU0836A Interface 548608 Serial Number= B59115 548608 ***** HID USB device reconnected: re-initialising FSUIPC connections 548608 ---------------------- Joystick Device Scan ----------------------- I think I'll add some of that without needing an extra option enabling. Pete