Pete Dowson

Hmm. There's nothing there which even interacts with FSUIPC. I assume you aren't starting any other FS programs outside of FSUIPC? Just in case it's some FSUIPC setting, could youtry with the FSUIPC4.INI file renamed or removed before loading P3D, please? P3Dv3 does tend to hang during closing if FSUIPC (or other add-ons) use the "SimConnect_Close" function when tidying up at the end. For this reason FSUIPC for V3 now, by default, does not do this tidy. But yours isn't even getting that far, because it logs this fact. I know the PMDG aircraft uses SimConnect a lot too, so I wonder now if its the PMDG call to Simconnect_Close which is aggravated by FSUIPC also using SimConnect. However, so far there have been no other reports of this particular problem even though there are a lot of users with both FSUIPC and PMDG aircraft. Pete

FSUIPC does nothing with Mouse buttons, except optionally the centre one if you enable Mouse Look or one of the other two mouse use options on the Miscellaneous page. It sounds like something else is interfering. If you think it must be an FSUIPC setting, somehow, then try removing or renaming your FSUIPC4.INI file before loading, so that it sets all options to default. Pete

No Pete

Please see the pinned thread on this P3Dv3 problem at the top of the forum. Pete

Why do you post here? Do you think it is anything to do with FSUIPC? Have you checked the PMDG forums? Pete

It looks like it isn't running at all. Is there even an FSUIPc menu entry in AddOns? I've had no other such reports, so I'd guess it's some clash with some other add-on. I'd need more information on that. Pete

What was happening then? Are they constantly jittering? There's a way round that, as documented and as mentioned above. Er, this is additional to what you said earlier? "My problem is with my assignment of Axes in FSUIPC" (i.e. not PFCFSX). Have you used the PFCFSX menu to set and calibrate them? Anyway, I've noticed that Lockheed-Martin are not only aware of many issues with control inputs but are actively dealing with them. I suggest that since you said that your setup was okay with FSX and P3Dv2, you simply copy over the same FSUIPC and PFCFSX settings (both INI files in the Modules folder), and stay calm until L-M do the business. I am tempted by P3Dv3, but I won't be switching until all this stuff is sorted out. Pete

There's no DLL in the SDK. You mean the LIB? Why are you posting in the SunForum for Paul Henty's library if you are not using it? You don't need a specific example. Writing to any offset is the same as any other. You need to open the link, first, then, when connected, any time you need to write you use FSUIPC_Write, either once for both offsets together (8 bytes) or twice, first for 3114 then for 3110 (4 bytes each), And an FSUIPC_Process call to make it happen. Repeat when needed. Any example containing a Read or a Write would do. The only real different between a Read and a Write is the command itself, and the only difference between offsets, as far as these commands are concerned, are the numbers of bytes. I am at a loss to understand what it is you fail to grasp. Have you done any programming before this? If not then this is probably not the place to start. Pete

Hmm, why? Was one of the others jittering too much and interfering? You can tell it to stop scanning an axis -- there's a button. It's only a temporary action. FSUIPC doesn't distinguish between axis inputs, apart from naming them of course, so the assigning action should be the same for all. Pete

Your re-formatting of the INI file settings makes things really difficult to read and understand. Why mess about with the file? Please just show me the file as it is. Er, WHY? Why do you want the Sim to only be able to set the top half of the throttle range? All FS's normal control axes use a complete range from -16384 to +16383. For the single generic throttle control -16384 is IDLE. The value 0 would be half way! Why do you think you should only be getting 0-16383? Sorry, I don't understand much of that. I don't know the aircraft you are using, but the FS throttle control axis, the one called "Axis throttle set" (which is what FS would assign to) runs from -16384 IDLE to +16383 max thrust. It has no intermediate positions. If an add-on aircraft uses intermediate positions for something special and you want to be able to set those you'd need, after calibration, to mark those positions on your lever's housing. There are no "detentes" on an FS throttle like flap positions. Again I don't understand what you are saying. First, why are you using offset 3B78 rather than the FS control itself? Is this just so you can program it as a latched switch rather than a button? Second, what control are you supposed to use for this function in this specific aircraft? If it doesn't change when using the proper FS control, I presume they've implemented something different? I'm afraid I really find it pretty impossible to support specific peculiarities of complex add-on aircraft which do their own thing. Some add-ons simply ignore FS controls altogether and you have to resort to L:Vars or Mouse Macros or try to find other ways. Each add-on aircraft seems to be implemented in its own odd way with no thought as to how hardware connections might drive them. There are usually ways of doing things, but you have to find them yourself or wirth the help of other users or maybe even the aircraft add-on makers themselves. If you actually explain what it is you need FSUIPC to actually do, without describing the aircraft switches and so on, then I can tell you if it is possible and how to approach it. Pete

Are, so it;s more like a rotary encoder with "up" and "down" detection, not a 32-way multiposition switch with 32 different macros, one for each position. For such a control you'd really be far better off with a rotary encoder yourself, which is what I use. They work really well with Bodnar boards. Then you just program one direction as INC and the other as DEC. As it is, with an analogue input, I think your only sensible way is to use a Lua plug-in. Assign the axis directly (on the left hand side) to a Lua plug-in, so it receives the analogue input value as the parameter, then when you see it increase by more than x (1/32nd of the range) execute the INC Macro, and vice versa when you see it decrease. You need to keep the previous value in a Global variable (set by ipc.set and retrieved by ipc.get. Pete

Thesel external programs are all wanting to receive keypresses you assigned to buttons? I don't know how they receive them in any case if they don't have keyboard focus. It shouldn't work whilst in any version of FS, UNLESS they are reading them from FS, which sounds unlikely. Or perhaps they define them as hotkeys? If that is the mechanism then I can only think that P3Dv3 is somehow stopping hotkeys stealing keypresses from itself. Pete

You are writing this thread in a SubForum dedicated to the use of Paul Henty's library for interfacing to FSUIPC -- look at the title FSUIPC Client DLL for .NET The FSUIPC SDK also contains a much more basic Library to interface to FSUIPC in C/C++. There may be others for the other languages included in the SDK (I don't know C# or the other languages, only C and ASM). Or maybe you are writing your own functions to do the interfacing? All ways are different for the code you write, but all you need to know is how to write an offset. There must be examples for whichever method you use. Have you looked? If you are starting out writing your very first program to iinterface to FSUIPC, then examples are going to be useful. Check the SDK and look again through the SubForum you are currently using. Pete

There isn't anything I'm aware of which keeps track of the user aircraft "flight phases", only AI traffic. Normally the pilot is aware of what he is doing. You can tell from offsets when you are on the ground, whether you are moving forward or backward, whether you are climbing, flying leveel or descending. I suppose you could read all the necessary values and deduce what you are doing. Pete

So it was okay with FSX or p3Dv2, and you've nt changed anything else? If the keypress is assigned to the button normally in FSUIPC, that keypress to sent to the program which currently has the focus, so it would normally always go to FS./P3D. I don't know how TeamSpeak gets them in that case. Do you know? Can you ask Teamspeak support what is needed? Pete

FSUIPC doesn't actually offer any "VAS Monitor". It simply updates a value in an offset regularly to indicate the amount of free memory. left to the FS Process, as described in the Offsets Status document. 024C 4 Available FS memory in kilobytes (updated every 1 0 seconds There is a VAS Monitor plug-in written in Lua which may be what you intended to refer to in your link above (which doesn't work for me). The Lua plug-in can be changed, expanded, whatever, to only record it every minute and to write to a file or even (using 3rd party graphics libraries for Lua) actually do the graph. You can also change the timing of the free memory check and offset update via a parameter in the FSUIPC4.INI file -- see item 38 in the current Changes Document included in the download Zip. Pete

FSUIPC can't do anything that FS cannot do. It is only an interface. Does the model you are using allow this? Pete

Yes, but there are at least 4 ways of doing that. Unless you are specific I cannot really advise. You weren't forced to do anything in previous versions of P3D because it worked either way. Not currently in V3 though. Please read the pinned thread on the subject at the top of this Forum. Pete

So, what is the questio?. I don't find one. Pete

Please see the Pinned thread on this subject at the top of the Forum ( IMPORTANT: FSUIPC calibration of axes in P3D version 3 . It does tell you exactly what you need to do and why. At present P3Dv3 will not allow FSUIPC to see controls assigned in P3D whilst it is in the dialogue. If you have calibrations from P3Dv2 or FSX you can copy them over -- just copy over the FSUIPC4.INI file. Pete

You need to send the Keypress code into 3114 and then the keypress control to 3110. Please see the FSUIPC Advanced User's guide. The correct numbers and format are given on page 31 -- control number 1070 does a press then release. The C# or C++ would depend on what library you are using, but it is just calls to write to FSUIPC offsets. Pete Pete

Why are you posting here? Do you have some question relating to FSUIPC or WideFS? There's a crash subforum for FS over on AVSIM. Have you looked there? Pete

Sorry, I don't understand 2not USB"? Are these the older serial port devices, then, which need y PFCFSX.DLL driver? The PFC Yoke is a standard USB joystick device? Another matter to which matter? I've not seen a question from you yet? Is there a problem? If you disable controllers in P3D or FS you would need to assign in FSUIPC. FSUIPC cannot calibrate things which it doesn't see! Pete Alex

I assume the INI file you attached is not the one you are using, because that shows no real axis assignments at all in FSUIPC. If you've disabled controllers in P3D and not assigned any in FSUIPC you canbnot really expect to see them in the Calibrations tab! Here's your total axis assignment section: which shows axis X on joystick #0 sending the non-axis control 65615 which is "ELEV TRIM UP". Not even an Eleve trim down assignment? Pete

The normal method is to round to the nearest integer: i.e. add 0.5 and take the integer part. Pete