Pete Dowson

Because the weather control and filter facilities in FSUIPC were very seldom used since so many add-on weather control programs were developed, They do a much better job. Pete

Oh, right! Having long been an FSX/FSX-SE user before P3D I already had several versions of the separate SimConnect DLL installed, so I'd never have thought of that! Presumably ProSim uses the FSX "SP2/ACC" version? That seems the most commonly used. Thanks Pete

Something is very wrong then. I'm using MSFS mode all the time. I think Andras ("Lapi") does too. Pete

I use ProsimV2 and keep it up to date with the latest Beta releases. My controls are assigned and calibrated only in FSUIPC, not in ProSim, and work fine. So, sorry, I don't know. I have ProSim set to "MSFS" not "SimConnect". I think there may still be problems with the SimConnect option, but I've not tried it here. All my controls and, in fact, most of my cockpit, are non-standard hardware items, or ones which ProSim doesn't support directly in any case (e.g. PFC serial port controls, centre console, MIP and MCP), so I use all my own software for the hardware and connect to ProSim via FSUIPC offsets for everything -- except the Sismo aft overhead, which is supported directly by ProSim. I think you should check the ProSim forums and post questions there about what you are seeing. Pete

If you mean that the flight controls are erratic, then the most likely thing is that you have them being handled in more than one place -- maybe in ProSim, in FSUIPC, and in P3D? You should only assign in one place. if ProSim is handling them, then neither FSUIPC nor P3D should. And so on. Really, since this is ProSim related you should be posting in the ProSim forums, not here. It evidently is not an FSUIPC matter, because, as you said "all works fine with FSUIPC 5.124 but if i start Prosim ..."

Version 5.124 was released and is the main current version, available in the usual places! Pete

If you are talking about FSUIPC5 for P3D, then version 5.124 is released and you should be using that. Pete

No, not at all. Why do you think that? BTW Version 5.124 is released. You need to update now. Pete

Yes. FSUIPC5 is a different product to FSUIPC4, just as FSUIPC4 was different to FSUIPC3. There are separate purchase pages for each at SimMarket. Pete

I've tested here, and it works fine with FSUIPC version 4.974, the current release. If you still have problems, please add these lines to the FSUIPC4.INI file's [General] section: Debug=Please LogExtras=x20 Then run P3D and try to create macros again. Please then show me the FSUIPC4.LOG file. Pete

Please, have you replies to my previous questions? Just delete the DLL. Nothing else. Why? Do you not want it registered? Anyway, I'll be looking at the problem now. I could do with answers to my questions though. Pete

Okay. I'm not sure why that should be. Have you made any other changes? Is it just a FSUIPC change? You've mentioned 4.966, 4.968 and 4.971. Which ones worked for you and which not? Why wereen't you using 4.972 before 4.974, as that was the 'current' version for a long time? Anyway, I'll check it later today. But I'd lke to know when it changed for you. Pete

PMDG aircraft (737, 747, 777) have custom controls, which are a much better solution. I didn't think they responded to Mouse Macros in any case. The FS9 versions used to, but not FSX/P3D. What is the actual symptom? What do you mean by "map nothing"? Pete

Yes, there's no difference for mouse macros. What are the actual problems you have? Are you trying to create new macros? If so, bear in mind many add-on aircraft do not support Mouse Macros. Pete

5.123e has no problems. If your P3D4 isn't behaving you need to look elsewhere. There are lots of assorted new problems with it which you'll see if you visit the L-M forums. If you only updated the Client then that could be the source of some of the problems, as it seems this update needs the Content updated as well. Pete

Dowload and install FSUIPC 5.123e from the Download Links subforum above. That is the latest version. Pete

Go to the Download Links subforum above, find FSUIPC 5.123e.zip (the latest version). download it, and copy the FSUIPC5.DL from there into your P3D Modules folder. Pete

fsui is part of FS, nothing to do with FSUIPC. As you have no FSUIPC.LOG nor an FSUIPC.INI, the FSUIPC you've installed has never been run. I think you've been running a different copy of FS9, not the version reagisted and which FSUIPC has installed into. Instead of clicking on your shortcur for FS9, go to and double click on the FS9.EXE you find there. C:\Program Files (x86)\Microsoft Games\Flight Simulator 9 and double click on the FS9.EXE you find there (or is is FS2004.exe. I don't recall, it's so long ago now!) Pete

What action? Please be specific. What are you assigning to and what do you expect to happen? BTW your thread title is wrong. It says "not recognizing buttond/switches, yet you just said it was recognising buttons! Pete

If the Lua library documnet, in your FSUIPC Documents folder. The ... part is explained there, of course. Why not follow on with the continuation on psge 18 then? The Handle must have been obtained in the Lua plug-in using any of the methods defined for obtaining a program handle. in the EXT library. (It is actually a Window handle, which should be the main program Window). I'm not sure off-hand whether Handle is local to the particular Lua plug-in, or can be passed over using ipc.Set and ipc.Get. You'll need to try it. Pete

I wonder why the positions weren't recognised in P3D then? Glad you got it all sorted. Pete

Please download the new WideClient, version 7.02, from the Download Links subforum above. Pete

Okay. For the Helicopter profile you have these axis assignments: [Axes.Helicopters] RangeRepeatRate=10 0=0X,256,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }- 1=0Y,256,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }- 2=3Z,1,F,65697,0,0,0 -{ TO SIM: THROTTLE_SET }- 3=3R,256,F,66291,0,0,0 -{ TO SIM: AXIS_PROPELLER_SET }- 4=5X,256,F,66387,0,0,0 -{ TO SIM: AXIS_LEFT_BRAKE_SET }- 5=5Y,256,F,66388,0,0,0 -{ TO SIM: AXIS_RIGHT_BRAKE_SET }- 6=5R,256,F,65764,0,0,0 -{ TO SIM: AXIS_RUDDER_SET }- The "THROTTLE_SET" control is the old FS98 generic single endine one, which I'm pretty sure assumes a simple throttle without reverse. Try assigning to AXIS_THROTTLE1_SET and calibrate that. I also note that although you have 7 axes assigned there, you have calibrated none of them. Oddly there are calibration entries for the Elevator Trim and the Flaps, neither of which are assigned! I've not checked any other entries, but they probably need looking at. So Hat switches are broken in 4.2 as well? You need to report that to L-M for sure. To test, then, you need to try other button or keyboard assignments, or simply use the keyboard numeric keys 1 and 7 which Your FSUIPC Hat trim Up/Down button assignments are fine. FSUIPC can do no more than send the assigned controls to P3D and expect it to obey them. [LATER] Just tested here on 4.2. The default assignments work (numpad 1 and 7), as do the same controls assigned in FSUIPC. So I certainly think you need to test with other button assignments and if they work, blame your Hat switch. And, as always, test with a default aircraft in case your add-on has a problem with 4.2. Pete

No. FSUIPC provides methods for accessing things by name via offsets too -- Macros and L:Vars are both identified by names! If you search for L:Var in the offsets list I mentioned you will find details of how to read them and write them via offsets, using the L:Var name (NOT a number). Only the values of L:Vars are numbers, their identities are names! Pete

No. The Install log is the log from the Installer. The FSUIPC.LOG is generated when FSUIPC is run. If there is no such file then FSUIPC has never been run. Look in the folder C:\Program Files (x86)\Microsoft Games\Flight Simulator 9\Modules There will be 4 (FOUR) files named FSUIPC: The DLL, an INI, a LOG and the KEY file you found. If there’s no log and no INI file then you have never actually run the Sim with FSUIPC installed. When you run FS9 make sure you are running the EXE file in C:\Program Files (x86)\Microsoft Games\Flight Simulator 9. Maybe you have an old installation still and are running the wrong EXE. If you purchased the key in 2004, I assume you have used it before, successfully? FS9 hasn't changed. FSUIPC registration hasn't changed. FSUIPC might have been updated, but the registration check is no different. The only registration problem with the earlier versions of FSUIPC was that they had an earlier expiry date on the key validity, so keys purchased after about 2015 would not work with those earlier versions (no one seriously expected FS9 to still be in use 12 years later, let alone folks still buying FSUIPC! I'm afraid I don't have FS9 on any of my PCs these days. Made room for FSX, FSX-SE, P3D1-3 and the 64-bit P3D4. I still need to see your FSUIPC.LOG file, please. Pete