Pete Dowson

I think that's the same as the one reported in the thread entitled "5.12 and display problem". This seems to be a result of the same error as ths main thread theme. I think I've narrowed it down enough now to fix it. Expect 5.12 to be replaced by 5.121 very soon ... Pete

I think this is basically the same problem as in the thread %.12 Space ... I'm working on it. Expect 5.12 to be replaced by 5.121 soon ... Pete

Which display? What happens when you click on it? Pete

What version of Flight Sim? Have you reported this to Majestic, as these sorts of things are often properties of the aircraft, not th Pete

I can reproduce this, but I'm stumped. FSUIPC itself is not interpreting the Space bar, nor is it setting the cursor position. The SPACE bar is, as it is defaulted in P3D, sends P3D the "MOUSE LOOK TOGGLE", as shown here in FSUIPC's logging: 1048218 KEYDOWN: VK=32, Waiting=0, Repeat=N, Shifts=0 1048218 .. Key not programmed -- passed on to FS 1048218 *** EVENT: Cntrl= 66734 (0x000104ae), Param= 1 (0x00000001) MOUSE_LOOK_TOGGLE 1048390 KEYUP: VK=32, Waiting=0 I've put traps in FSUIPC in all the places where the mouse might be moved (normally in one of the Mouse facilities enabled in the Misc Tab in FSUIPC options), but none are triggered. So it is something else in P3D which is somehow being affected by some small change in FSUIPC. I don't know how to locate it, though. I might have to ask L-M to help explain what is causing P3D to do this. One other nasty, which I'll need to report to L--M too. As part of my test I tried to change the assignment of the SPACE bar in L-M Options-Controls, but it crashes L-M with a great long error display! First I'll see if I can undo one change between 5.113 and 5.12 at a time, to see if I can identify the trigger, but it still looks like a P3D problem which FSUIPC is somehow triggering. This could take a while. :-( Pete

I've asked L-M to again consider making the fix I suggested to overcome the problems, which "FixControlAccel" does (but in a clumsier way). I'm sure they don't realise what tricks the add-on aircraft implementers get up to. Pete

It sounds like you have FSUIPC's mouse look option enabled on the Miscellaneous Page. FSUIPC doesn't read the keyboard. The space bar is usually pre-assigned to mouse look in the Sim but FSUIPC doesn't operate that facility unless enabled. Or maybe you mean that you ARE using the FSUIPC version of mouse look, but that it has gone wrong in 5.12? Pete

Unfortunately I cannot do it in P3Dv4. It was only my list of requests to L-M but I'm afraid they've not implemented any of those yet. It is normally due to the add-on aircraft in question invading the Windows' queue of requests with many repeats of its own, and these being interpreted as repeats of your one command. Pete

Well, that shows it is still recognised okay. It's no different that before. The log is still incomplete -- you didn't answer that question, about P3D hanging or crashing on closedown. Maybe it would help if you fixed or avoided that (as I suggested)? BTW you are still on an old version of FSUIPC. 5.113 was reeased a few weeks ago to fix some things, and 5.12 was released earlier today. Best to keep up to date -- you never know, it might help. Pete

Well, the INI file show so the pedals are detected okay, and assigned Joystick ID 2: 2=Saitek Pro Flight Rudder Pedals2.GUID={1344C6F0-02B8-11E4-8001-444553540000} and in all your axis assignment sections you have brakes and rudder assigned okay: 6=2X,256,F,66387,0,0,0 -{ TO SIM: AXIS_LEFT_BRAKE_SET }-7=2Y,256,F,66388,0,0,0 -{ TO SIM: AXIS_RIGHT_BRAKE_SET }-8=2R,65,F,65764,0,0,0 -{ TO SIM: AXIS_RUDDER_SET }- So there's nothing amiss in FSUIPC. Interestingly, though, the 13th August log shows 187 Device acquired for use: 187 Joystick ID = 1 (Registry okay) 187 1=Joystick - HOTAS Warthog 187 1.GUID={CAF866C0-9479-11E7-8002-444553540000} 187 Device acquired for use: 187 Joystick ID = 2 (Registry fixed) 187 2=Saitek Pro Flight Rudder Pedals 187 2.GUID={1344C6F0-02B8-11E4-8001-444553540000} 187 Device acquired for use: 187 Joystick ID = 0 (Registry fixed) 187 0=Throttle - HOTAS Warthog 187 0.GUID={AF6A9180-9479-11E7-8001-444553540000} with two device IDs presumably changed (maybe after installing HOTAS Warthog) and changed back automatically by FSUIPC to match your settings. (Previously this would have needed an external utility or registry editing). The logs don't show any use of the rudder or brakes, though (eg via axis logging), so apart from showing the devices being detected and assigned okay, they aren't really helpful. I do notice, though, that both logs end abrupty after calling SimConnect_Close. Is P3D hanging then? There used to be such a problem with SimConnect_Close in some of the P3D3 releases, and I stopped calling it and simply let P3D close untidily. I'd like to know if that problem has re-appeared, as it seems okay here. You can make FSUIPC bypass it by adding "CallSimconnectEnd=No" to the [General] section of the INI file. Back to your pedals, though: if they are not providing variable values in FSUIPC's assignments then they are not providing any, period. If it is just that they appear to work one moment and not later, it may be down to Windows USB power management letting them "go to sleep". Make sure power msnsgement is turned off on all USB hubs in Windows Device Manager. The only other suspects would be an external USB hub playing up, and of course the pedals themselves. Pete

It was in the wrong place. Luckily I just noticed it whilst doing some housekeeping and moved it here, the Support Forum itself. The subforums are really intended as repositories for reference information which stays readily svailable to all users. I'm really not sure what you mean by a "dial function". Flaps are normally controlled by a lever, with notches for the different positions. What aircraft has a dial (I don't know a "tfdi 717"), and what sort of dial do you mean? FSUIPC does include flap assignments for axes with calibratable areas for each "notch". Those can set set differently for different aircraft -- by using different Profiles. What "manuals" did you look at? For FSUIPC you really only need the FSUIPC User guide. There are chapters on Profiles, Axis Assignments, and Calibration. I think you need to refer to those, and probably in that order. Please just ask specific questions if something confuses you, but i won't reproduce what it says in the manual here. Pete

I've found and fixed this problem. It was a 32 to 64 bit difference in the structures used to ennumerate running programs. It will be fixed in version 5.12, which I will probably be able to release later today, otherwse certainly by the weekend. Incidentally, if a program won't CLOSE (and, yes, I know there are some like that), then the more ruthlss KILL option can be used. It's safe enough for most programs, assuming there are no settings to change. It's the same as using End Process in the Windows Task Manager. Pete

The FSUIPC options dialogue is a standard Windows dialogue. There is no handling of mouse of keyboard in FSUIPC for this, it is all standard Windows stuff. FSUIPC merely gets the results when you finally press OK or Cancel. So you have some problem with your Windows system, or some other installed program is interfering somehow. Pete

That's about threeb years old now, I think. Once your a bald I don't think much else notices. My wide is older than me, but looks youunger (and she's NOT even bald!) ;-) Now for this: #define EVT_CONTROL_STAND_ENG1_START_LEVER (THIRD_PARTY_EVENT_ID_MIN + 521) All you need to do is look at the top of the list where you will find the value for "THIRD_PARTY_EVENT_ID_MIN", then, as it says, add 521 to that value. That gives you the "custom Control" number, which you can assign in FSUIPC using the "<custom control>" selection, right at the top of all the lists. There will be a place where you can enter the number you computed, and a parameter. The parameter you need is more tricky. For the Start Lever, which is either on or off (idle or cutoff) it might just be 1 or 0, but I can't say. Others shoul be able to advise you. There are examples of using this stuff in the User Contributions sibforum above. Pete

Well, there were (almost) no such things as computers when I was a "kid" (I am 74 by the way). Tell me what you find relevant the the document I mentioned and we'll take it from there. As I said, it is only a matter of adding two numbers, which are given there. Pete

Possibly. If you've assigned keys for some other purpose then you can't really expect them to do something else just because you want them too. You need to make sure all your assignments are separate keypress combinations. they are not in short supply. Pete

Well, there it clearly says "Vector magnetometers measure one or more components of the magnetic field electronically.". I already told you that neither FS nor P3D simulate Earth's magnetism, or, if they do, it is certainly not exposed. Pete

At the end there is a list of controls you can assign in FSUIPC using the <custom control> assignment facility. Just compute the numerical value -- only a matter of adding up two numbers! Really you'd be better off in a PMDG support forum. I don't even use any PMDG aircraft, I just provided the Custom Control facility so folks can use additions made by PMDG (and others) to the range of controls FS provides itself. Pete

No point. What are you logging? By default the log is short. You must have many options set in the Logging tab. So, use the custom controls provided for that aircraft! It is much simpler! Mouse macros date back to older versions of FS and do not work very well, if at all, on most recent add-ons. Custom controls are listed in the .h document 9look at the end0 in the SDK folder for the PMDG aircraft. You compute the number as shown and use it in a <custom control> assignment in FSUIPC. Pete

Vectors of speed or acceleration? Both are available in offsets, relative to body or Earth. Did you look? Pete .

You seem to be using an add-on aircraft which does not support mouse macros. I notice you don't state which aircraft you are using, but these days very few do support mouse macros! You supplied the Install log for some reason, which isn't relevant. The FSUIPC4.LOG would at least have allowed me to see which aircraft was loaded. There are probably muchbetter alternative methods of assigning buttons or switches to operate switches in the cockpit. For example, all PMDG aircraft supply controls for all of their switches. Pete

Sorry, I don't really know what that means. "Late"? This is whilst creating a MOUSE macro (there are normal macros and Mouse macros)? You must have G set somewhere either as a Windows HotKey or in the add-on aircraft you are using which is taking priority. Because FSUIPC reads keyboard input directly before it reaches FS. Pete

Assuming it isn't just that you've not calibrated properly, or have assigned in the Sim, not in FSUIPC, and have some silly slider values there, then that's usually a Saitek installation bug. It is fixable in the Registry. I'm really surprisded they've not fixed that yet. Take a look at the FAQ subforum. There are entries about that. Sorry, that doesn't make sense. Where are you observing this "showing in FSUIPC as 16384 just above half way and -16384 just below half way"? And what exactly do you mean by "they do not show the whole range."? This from the LOG shows it is actually a Registry or installation problem. the two quadrands show totally different ranges for the two of them on the X and Y axes: Max=R0,U0,V0,X255,Y255,Z255Max=R0,U0,V0,X127,Y127,Z255 And the INI file shows you've not even calibrated any axis. They are all default values. You should ALWAYS calibrate when assigning direct to calibration, as you have. Pete

I've found the Window position problem. It was a mix-up between Screen, Window and Client coordinates. I'm going to have to restrict the Window position and size facilities to undocked windows and docked ones in full screen mode only. There are just too many variables and unknowns for me to deal with sensibly, otherwise. I've got a few other things to attend to, but it'll be in a release before the weekend. Pete

First try the interim update 5.113, available for three weeks now. Also the FSUIPC5.LOG file is required, not the install log. Your JoyScan file shows: Y, x1E, x06A3, x0763, Saitek Pro Flight Rudder Pedals, 3, 3, 0, {8EE9DBB0-7BB4-11E7-8009-444553540000}, {8EE9DBB0-7BB4-11E7-8009-444553540000}, {8EE9DBB0-7BB4-11E7-8009-444553540000}, Y, Y Y, x1E, x06A3, x0C2D, Saitek Pro Flight Throttle Quadrant, 1, 1, 0, {8ED6A1D0-7BB4-11E7-8005-444553540000}, {8ED6A1D0-7BB4-11E7-8005-444553540000}, {8ED6A1D0-7BB4-11E7-8005-444553540000}, Y, Y Y, x1E, x06A3, x0C2D, Saitek Pro Flight Throttle Quadrant, 2, 2, 1, {8EE017B0-7BB4-11E7-8006-444553540000}, {8EE017B0-7BB4-11E7-8006-444553540000}, {8EE017B0-7BB4-11E7-8006-444553540000}, Y, Y N, x01, x06A3, x0C2D, Saitek Pro Flight Throttle Quadrant, -1, 4, 2, {NULL}, {E2A751A0-8E7A-11E7-8008-444553540000}, {NULL}, N, N Y, x1E, x06A3, x0BAC, Saitek Pro Flight Yoke, 0, 0, 0, {8ED198C0-7BB4-11E7-8003-444553540000}, {8ED198C0-7BB4-11E7-8003-444553540000}, {8ED198C0-7BB4-11E7-8003-444553540000}, Y, Y So, THREE Saitek throttles, one of which appears to be an invalid Registry entry. The INI file sohws these detected and entered correctly. 0=Saitek Pro Flight Yoke 0.GUID={8ED198C0-7BB4-11E7-8003-444553540000} 1=Saitek Pro Flight Throttle Quadrant 1.GUID={8ED6A1D0-7BB4-11E7-8005-444553540000} 2=Saitek Pro Flight Throttle Quadrant 2.GUID={8EE017B0-7BB4-11E7-8006-444553540000} 3=Saitek Pro Flight Rudder Pedals 3.GUID={8EE9DBB0-7BB4-11E7-8009-444553540000} So what exactly do you mean by this? The two throttles are fine, which different assignable IDs 1 and 2. What "prop piitch lever" do you have on your throttles? Do you mean you assigned one? To an FS control or direct to FSUIPC calibration. For it to be full on or off it sould s like you've not bothered to calibrate correctly. Your INI file sohws no calibrations whatsoever, and only an Axis assignment to and uncalibrated Elevator assigned "direct to calibration". Pete