Pete Dowson

Well, that would be excellent, as then if there is a problem I can run it in debugging mode! Thanks! Pete

You must install the main release, 5.10 first, using the Installer. Then just replace the FSUIPC5.DLL module with the update. The changes since 5.10 are documented in the Download Links subforum. This is always the way with TEST releases, of which there have been 12 in 10 days! The full Changes document will be provided with the next full Installer update, 5.101, early next week. Ah, for WideFS registration? Sorry, yes, that question is actually being answered on request, here, at present, until the next main release, 5.102. Here's what you need to do: In the P3D4 Modules file, find and open FSUIPC5.KEY with an ordinary text editor like Notepad. Do not double click on the file, becase REG files change your Registry! If there are any WideFS lines already there, remove them and add these lines with your registration details, as follows: NameForWideFS=your registered name WideFSAddress=your registered email WideFS=your registration key I'll put this detail in a sticky thread at the top of the Forum. Pete

Yes. A "ModuleUser64.lib" is done but untested. I won't have time to make a test DLL for it until I get back off a short vacation in about 10 days time. But I'd be delighted if you'd please try it and let me know (before I go, on Wednesday). The changed are relatively trivial. You'll need the latest FSUIPC interim update (FSUIPC 5.101m, just released). I will be building a new full release of FSUIPC (5.102) for Monday or Tuesday, latest. Link to download LIB and all the source: ModuleUser64.zip Pete

That wasn't a good idea. Should have only uninstalled the joystick devices. Some wireless devices work fine with later versions of Windows out of the box, some need their own drivers installed. You'd probably need to find those (the pair would have come with a disk) or go to their website. Good. Pete

FSUIPC5 is now already up to version 5.101k which you can get from the Download Links subforum above. It is a busy time and it is being developed all the time. You are unlikely to get many addons working with 5.10. If your PDC Quadrant needed the PFChid.DLL on earlier 32-bits sims, it needs PFChid64.DLL for P3D4, because 32-bit DLLs will not run in a 64 bit process! Please do keep an eye on the Download Links subforum. Both FSUIPC and P3D4 are still being developed and there will be frequet changes. Now you confuse me. If the throttle quadrant is a genuine USB device then it will either work directly with simulators, or it will need PFChid64.DLL, On the other hand if it is one of the original serial port devices from PFC it will need PFCcom64.dll instead. Don't you know what you've got? Did you not get ANY information about the PFC stuff you have? Have you never used it before? I cannot support the hardware myself. I support my programs. Pete

And .. where is the log please? Those lnes were so that it would log more about what it saw in the Registry! That was the point. Sorry if I wasn't clear. Which part of "what was listed" there? Some of that is specific to a particular device makers, ones with VID_06A3 or VID_0738. The 06A3 is Saitek. (your 6 listed Quadrants are all VID_06A3). Your CH devices have VID_068E. Pete

Yes, PMDG have admitted it. Apparently, and unbeknownst to me, they do make calls into FSUIPC but using my 17-year old 32-bit ModuleUser library code! I think the problem is actually occurring in that code which must be compiled in one of their modules. FSUIPC 5.101k actually provides 64-bit application and modules support now, but only with programs compiled to use it correctly. There aren't any yet -- I have to write something to test it with. I'll put an option in to try to fend off any such calls, though that might not help if my theory is correct. Meanwhile, PMDG did say they'd release a fix. Have you looked? It may have only gone out to those who;ve reported the problem to them so far, so they can prove it. It'll be in the morning now ... Pete

From the JoyScan results it looks like your registry is rather severely corrputed in its registration of your devices. It have 6 entries for the Quadrant -- on 3 different GUIDs with one which looks as if it should work except that it has the same exact GUID as your Pedals (!!), another with 2 identical GUIDs (which is really wrong) and another with 3 identical GUIDs! (Even worse). How all this happened I don't know. GUIDs are supposed to be guaranteed to be unique. It looks like something has really trashed that area. Although I agree with Thomas that reconnecting the Quadrant to a different USB port might help, I think more needs to be done. First I'd like to see what is going on in the Registry in more detail. To that end, please re-run the test with FSUIPC, but first of all edit the FSUIPC5.INI file (in the P3D Modules folder) by adding these two lines to the [General] section: Debug=Please LogExtras=x200000 Then you could try uninstalling both the Quadrnt AND the pedals from Windows. Do that in the Windows Device Manager, and include the drivers too if it asks. Then just re-boot the system. Windows should find them and reinstall them, hopefully cleanly. If things still need tidying up after that I can fix the Registry for you. I'f need to give you instructions on using the Windows RegEdit program to extract the section to be fixed so you can send it to me. I'd tidy it up and send it back, or alternatively give you instructions on how to do that. [LATER] I've just seen you newer post, after the one from Thomas. The JoyScan shows that all moving them around has done is given the Pdals and one of the 6 listed Quadrants the same GUID. In fact now there are no unique GUIDs. I think it really will need manual intervention in the Registry. But first try uninstlling all three items in the Device Manager and re-booting. Don't worry about where they are plugged in. I'm off to bed now, but I'll catch up in the morning. Pete

THere's no difference between the J and Kversions in anything but 1. Adding a facility for 64-bit programs and modules to use the C/C++ interface to read and write offsets. This would only affet other add-ons not yet availalbe. 2. Allowing the Kneeboard to be invoked without preventing FSUIPC assignments working throughout and subsequently. I see your INI file is defayult again. Why do you delete your INI file every time you install an updated DLL. Please do NOT!!! Just copy the new DLL over the previous one! Otherwise all your reports of such oddities, changes that cannot have happened, are just meaningless. Pete

It isn'tFSUIPC doing this. You have no assignments to keys at all in your INI file so it isn't itseflf tpching your keyboard. You say so I would guess it is either one of those, or some other program you are running or have automatically started in P3D which is doing it, whether through FSUIPC or not. Pete

Just clicking on the GPSout tab to display the options? As well as the Log asThomas requests, the Windows crash details from it's event viewer please. Also, you miss out all the other vital information, like version of FSUIPC, version of FS. Pete

FSUIPC Installer does absolutely nothing else but install files in the Modules folder and add itself to the DLL.XML file so that P3D knows to load it. So you have somethnig else going on there, maybe coincidentally around the same time. But sorry, it is NOT related to FSUIPC. I cannot help you with your problem. If I were you I'd uninstall the sound scard and driver in the Windows Device Manager, and re-boot. If Windows doesn't re-install the drivers, get updates from the web and install them yourself. Pete

And what functions are you assigning to which don't appear to be working for you. (I did ask you this before!). Your INI shows that the ONLY buttons you've assigned are: PollInterval=25ButtonRepeat=20,102=U0,17,C0,0 -{Custom control: <0>}-4=R1,0,C65588,0 -{BRAKES}-5=P1,4,C65599,0 -{FLAPS_2}-6=P0,10,C66513,0 -{ATC_MENU_OPEN}-7=P0,9,C66514,0 -{ATC_MENU_CLOSE}-8=P0,8,C65752,0 -{PARKING_BRAKES}-9=P1,3,C65752,0 -{PARKING_BRAKES}- You have an odd custom control of 0 which can't possibly do anything. If you've loaded one of these aircraft: 1=PMDG 747-406 KLM Royal Dutch Airlines (PH-BFN | 2017)2=Lockheed Martin F-16C - USAF Gray you also have this button to use:0=P1,4,C65792,0 -{AUTOPILOT_ON}- replacing your FLAPS 2 assignment, or for other Boeings: [Profile.Boeing] 1=Boeing [Buttons.Boeing] 2=P0,4,C65751,0 -{LANDING_LIGHTS_TOGGLE}- No others. A rather odd lot of assignments really. Very few "normal" assignments I would expect you to use, and two separate assignments to "PARKING BRAKES". So which don't work? Without seeing the log I can't help further. Pete

Surely the name they use is the name you provide for your account? How do they work out differently? You are under a misunderstanding. You won't find ANY of my software on SimMarket. They only sell the Registrations! They do provide a link for the current Install package, but that links back to the Download Links subforum here, and it is in there you will find the latest interim updates and lots more useful stuff. The current update is 5.101j but version k will be released by tomorrow morming. Pete

For many things you can normally assign to for default and less sophisticated aircraft, PMDG implement their own controls. These are llisted in their SDK. They can be assigned if you work out the number and use the <custom control> facility in FSUIPC. Aircraft functions such as? Perhaps you should show me your FSUIPC5.INI file. You'll find it in the Modules folder. Looking back, you said: By "bind" do you mean "assign"? Because if you cn't assign them how did you assign one to opening and closing the ATC menu? Surely that shows that they are being received and sent on. You could enable Event logging in the FSUIPC Logging menu and see if the correct controls are being sent when you press buttons. Pete

FSUIPC really just consists of the FSUIPC4.DLL which is in the Modules folder. If you remove that or just rename it it cannot run. You don't need to restore anything in P3D. Pete

Are you sure you aren't trying to use functions which are implemented differently in the PMDG aircraft. Please test with a default aircraft. The state of buttons is read at the same time as the axes. FSUIPC can't get on without the other. Pete

Yes, I can reproduce this. Very strange. FSUIPC doesn't know a "Kneeboard" from a lump of wood, it is just an event it sends to P3D4. You don't need to clear the assignment to make it work again. Just enter FSUIPC options and cancel out. I'm investigating. [LATER] Found it. Seems it thinks it is still in a dialog. In version 5.101k, which I'll release this evening or in the morning, FS controls will continue to operate whilst the kneebnoard is showing as well as after, as they should. I now better check what happens in FSUIPC4. I think that bit of code is the same. Pete Pete

I didn't say that! I said "P3D improvements to ground friction will possibly make these facilities reducndant". Maybe it was pure hope, but L-M have said they were working on improved flight modelling and so on and I would assume they'd look at frictions too. But maybe no one has ever asked them, has never pointed out the need. Or maybe improvements are to follow. Pete

Or the fix which PMDG may put out. Keep an eye out for that. Pete

First please see my last post in this thread, just before yours. Pete

I think PMDG may have located the problem. It seems they DO use FSUIPC, and have used the old ModuleUser.lib code which dates back about 17 years and which is not compatible with a 64-bit prrocess like P3D4. They've only just told me they use this, and it really surprised me. I will temporarily make FSUIPC ignore module user calls until I work out a 64-bit implementation. That change will be in FSUIPC 5.101k, later today. Pete

Good. Thanks for the confirmation. I'll probably put together a proper Installer release for version 5.102 over the weekend. there a just a few little things for me to see to first. So expect one by Monday. I am away from next Wednesday till the following Tuesday. This is why I've been nearly killing myself working to solve the asorted problems as more and more FSUIPC users do more and more things with it. Next Tuesday was my last "deadline" to resolve serious problems, including receiving confirmation. I have still got MakeRunways to sort out. That's complex when folks add sceneries from folks like DreamTeam and FlightBeam. Makes things much more complicated. AND there's a "ModuleUser" interface, used for FSUIPC offset reads/writes by DLLs and GAUges within the 64-bit process. The change from 32- to 64-bit pointers makes that a bit messy too. Pete

The Traffic controls in FSUIPC are working in version 5.101j, now available in the Download Links subforum. Pete

You posted this exact request twice!!! (I deleted the other). I cannot pass out private email addresses without permission, and I am certain that would not be given. If you give me your email address I can ask my SimMarket contact. That's all I can do. Did you forget your password? That isn't "losing" it, so what do you mean by "loss"? Pete