Pete Dowson

Do the other add-ins load ok -- PMDG Options? The one for ActiveSky? Show me the FSUIPC4 Install log please. Pete

You've made a mess of the DLL.XML file. Delete it and re-run the FSUIPC installer. It will make a new correct one. Use the latest FSUIPC4 installer (4.966c) available on the Schiratti site (ignore the text there, it's out of date) or in my own Download Links subforum above. You then might need to re-run a PMDG installer, or just add the following to the DLL.XML BEFORE the first <Launch.Addon> line: <Launch.Addon> <Name>PMDG Options</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGOptions.dll</Path> </Launch.Addon> Pete

Just enable "Mouse Look", in the Miscellaneous tab in FSUIPC Options. Pete

Okay. In that case, here's what your log clearly shows: Your stick is working, and as you have two button assignments to that it is being scanned all of the time, even when you are not in the FSUIPC Options for Axes or Buttons. That fills up most of the log. The rudder isn't assigned so that doesn't appear except when you enter the options. After you entered the Buttons assignment dialogue, all possible joystick numbers were scanned (I must fix that -- it should only scan those detected before hand -- i.e. in your case 0, 1, and 2, the Stick, Throttle and Rudder. Oddly, 3 gave a valid response too, but I think that must be a fluke. it gave an error later. Here's an extract showing valid responses for 0-3: 153218 *** Entered Buttons option page *** 153218 Read joy 0, Buttons=x00000000, POV=-1 153218 Axes: X=33444,Y=32524,Z=0,R=0,U=0,V=32751 153218 S=0,T=0,P=-1,Q=-1,M=-1,N=-1 153218 Read joy 1, Buttons=x00000000, POV=-1 153218 Axes: X=0,Y=0,Z=0,R=0,U=0,V=0 153218 S=0,T=0,P=-1,Q=-1,M=-1,N=-1 153218 Read joy 2, Buttons=x00000000, POV=-1 153218 Axes: X=0,Y=0,Z=0,R=0,U=0,V=32383 153218 S=0,T=0,P=-1,Q=-1,M=-1,N=-1 153218 Read joy 3, Buttons=x00000000, POV=-1 153218 Axes: X=0,Y=0,Z=0,R=0,U=0,V=0 153218 S=0,T=0,P=-1,Q=-1,M=-1,N=-1 You see the X, Y values for the Stick (Joy 0), near max. Those values wobble a bit, typical jitter probably ignored by FSUIPC with the default Delta value left set. The readout for Joy 1 is basically a default. But it is most certainly coming from the device (or rather from DirectInput and the device's driver). Here, Joy 2, the rudder, has an interesting non-default value for the V axis (probably not used), but otherwise the input from that seems stable at zero. Oddly, though you were supposed to be checking the buttons on the Throttle, you pressed buttons on the Stick instead: 159640 FirstButtonChange res=00000008 (0.0, 8) 159656 Read joy 0, Buttons=x00000100, POV=-1 159656 Axes: X=31852,Y=32206,Z=0,R=0,U=0,V=32751 159656 S=0,T=0,P=-1,Q=-1,M=-1,N=-1 Later the same again for buttons 8, 6, 7, 8, 12, 10, 13, 11, 4, 12, in that order. Surely you saw these coming up in the dialogue, for your stick? Did you actually press any buttons on the throttle? Then, at about 235 seconds (3m 55s) into the session, something wierd started happening. Your X-55 devices were disconnecting themselves (unless you did it), or losing power. This happened with both Stick and Throttle. maybe this is when you pressed buttons on the Throttle, precipitating the problems? 235156 *** JOY ERROR: GetDeviceState for Joy #0 returned 'Input Lost' 235156 *** JOY ERROR: GetDeviceState for Joy #1 returned 'Input Lost' 235156 Read joy 2, Buttons=x00000000, POV=-1 235156 Axes: X=0,Y=0,Z=0,R=0,U=0,V=32383 235156 S=0,T=0,P=-1,Q=-1,M=-1,N=-1 235156 Read joy 3, Buttons=x00000000, POV=-1 235156 Axes: X=0,Y=0,Z=0,R=0,U=0,V=0 235156 S=0,T=0,P=-1,Q=-1,M=-1,N=-1 235156 *** JOY ERROR: Poll for Joy #0 returned 'Input Lost' 235156 *** JOY ERROR: GetDeviceState for Joy #0 returned 'Input Lost' 235156 *** JOY ERROR: Poll for Joy #1 returned 'Input Lost' 235156 *** JOY ERROR: GetDeviceState for Joy #1 returned 'Input Lost' Interestingly the Rudder and the mysterious Joy 3 continued okay. This went on for a great portion of the log until 238 seconds (only 3 seconds, but a lot of log!) when another USB device was added! 238093 ***** A device has been attached! 238093 ***** HID USB device reconnected: re-initialising FSUIPC connections 238093 #### Initialising Dlrectinput Axis Scanning ... 238093 EnumDevices: 0.GUID={B15E4040-937C-11E5-8002-444553540000} 238093 EnumDevices: 1.GUID={B160B140-937C-11E5-8006-444553540000} 238109 EnumDevices: 2.GUID={B15E4040-937C-11E5-8001-444553540000} 238109 EnumDevices: 3.GUID={3C3B5D00-9DAB-11E5-8001-444553540000} A "real" device 3 after all! Not the ghost scanned earlier. And see what this turned out to be: 238125 Joy#3: Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_068E&PID_C010\" 238125 Joy#3: OEMName = "CH Control Manager Device 1" 238125 Joy#3: GUID = {3C3B5D00-9DAB-11E5-8001-444553540000} Now what is that for? Why are you running the CH control Manager at all? Maybe this is the cause of all the problems? It not only did this, but appeared to reconnect the device many more times (over 6, I lost count), and in the process also got the Stick moved to device 4! Not only that, but subsequently Joy 3 stopped returning any values, even though as a "ghost" device it did! So, conclusions: 1. Uninstall CH Control manager and re-test. 2. It looks possible that the USB port for your X-55's, and especially the Throttle, is playing up. Try moving them. If using a hub try plugging them direct into the PC. As far as I can see, apart from the excessive scanning (all 16 initially), FSUIPC is doing everything right. Pete

Did you send me a log by email, from someone called "Ron" (you NEVER seem to sign your posts here so I've no idea who you are or where the email is from)? Pete

Yes, but only in the assignments dialog. Sorry, yes, I see what you were trying to do. but it didn't look like the sim was ready to fly (I was looking for the "Starting Everything Now" message in the log -- that's when FSUIPC is fully ready for normal use. It might be a few seconds after the sim appears ready. I'm looking at shortening anydelay there -- I'm trying to detect the end of the sim's loading progress bar. Ready to fly should be when you can do things in the menus, as you are. but I think, especially with P3D, this can occur later -- maybe 10-12 seconds or so. The reason for this delay is that I was trying to avoid doing things when the scenery/traffic etc progress bar is still running. I didn't find a way to detect that, so estimated a time. On my system the progress bar isc still going for quite some time after my delay, so FS starts everything too early. Yors may load stuff a lot faster (less scenery, AI traffic, lower settings, etc). That's why at present I'm trying to find a way to detect the progress bar. Pete

I've checked, and in fact the logging I need is already in place. It logs the results from the actual polling of the joysticks, at first and then whenever they change. It will make a BIG log, especially with your working device in place, so please, not only keep the session short (though not so short you don't get to operate buttons or move levers when the sim is ready to fly), then ZIP it up and send it to me at petedowson@btconnect.com. To get this logging as well as the earlier stuff, change the LogExtras line n the INI to LogExtras=x201000 Please don't forget to remove the extra copies of the two added lines. Oh, and to keep the log size down, it might be best to temporarily disconnect the working devices. Otherwise I'll have to add an INI parameter to select which devices to log. [LATER] Another thing I now realise: you have no assignments to the axes or buttons in question. I sort of assumed you were carrying over an INI file from an earlier install. FSUIPC does NOT scan devices where there's no need because no assignments, so the new logging I'm asking for will ONLY occur whilst in the Axis or Button assignments dialog. So you can keep the session and log shorter by keeping those visits short. Thanks, Pete

I've checked, and in fact the logging I need is already in place. It logs the results from the actual polling of the joysticks, at first and then whenever they change. It will make a BIG log, especially with your working device in place, so please, not only keep the session short (though not so short you don't get to operate buttons or move levers when the sim is ready to fly), then ZIP it up and send it to me at petedowson@btconnect.com. To get this logging as well as the earlier stuff, change the LogExtras line n the INI to LogExtras=x201000 Oh, and to keep the log size down, it might be best to temporarily disconnect the working devices. Otherwise I'll have to add an INI parameter to select which devices to log. Another thing I now realise: you have no assignments to the axes or buttons in question. I sort of assumed you were carrying over an INI file from an earlier install. FSUIPC does NOT scan devices where there's no need because no assignments, so the new logging I'm asking for will ONLY occur whilst in the Axis or Button assignments dialog. So you can keep the session and log shorter by keeping those visits short. Thanks, Pete

Well, yes. But when / where did you get time to operate any buttons or move any axes? I see you went into the Buttons Options right near the beginning (why?), but you terminated the session before the sim was even ready to fly, just 147 seconds after you started it and about 80 seconds after leaving the Button options page. Live the other X55 problem report here (from OldPop, near this thread), there are an excessive number of Joystick Scans and re-writes of JoyNames shown in your log. OldPop has a working X-55 stick but problems with the throttle. There's a common these through pretty much ALL of the threads about joystick problems here: the X-55 (and the X-56 once, a close relative I believe). If it wasn't so expensive I'd buy one just to find out what a mess Saitek have made! If you can make a log with the buttons and axes used just a little bit before shutdown -- but AFTER the sim is completely ready to fly please, then I'd like to see such a log. Keep it short, but not this short! Meanwhile I'm looking at adding extra logging to get closer to the coalface, so to speak. I might post a link to a test version today or tomorrow. Pete

Okay, the JoyNames section is now correct: [JoyNames] AutoAssignLetters=Yes A=Saitek Pro Flight X-55 Rhino Stick A.GUID={B15E4040-937C-11E5-8002-444553540000} B=Saitek Pro Flight X-55 Rhino Throttle B.GUID={B160B140-937C-11E5-8006-444553540000} C=Saitek Pro Flight Rudder Pedals C.GUID={B15E4040-937C-11E5-8001-444553540000} 0=Saitek Pro Flight X-55 Rhino Stick 0.GUID={B15E4040-937C-11E5-8002-444553540000} 1=Saitek Pro Flight X-55 Rhino Throttle 1.GUID={B160B140-937C-11E5-8006-444553540000} 2=Saitek Pro Flight Rudder Pedals 2.GUID={B15E4040-937C-11E5-8001-444553540000} There's one very odd thing that the log shows straightaway: the initial Joystick Scanning which FSUIPC does even before connecting to the sim, is actually repeated later, after the connection, after the aircraft is loaded, but before the sim has completed loading: 150453 #### Initialising Dlrectinput Axis Scanning ... etc Then, odder still, is the repetition of the section writing the JoyNames details, here 163812 ---------- Making INI JoyNames Section ---------- and here: 264328 ---------- Making INI JoyNames Section ---------- You closed the session shortly after that last, apparently without leaving the starting dialogue so never reaching the "ready to fly" stage. There's no mechanism in FSUIPC for repeating the scan except: 1) on detecting a USB device connecting or re-connecting. however, that would be logged by ***** HID USB device reconnected: re-initialising FSUIPC connections (This can be turned off by changing "AutoScanDevices" to 'No' -- but it is 'Yes' as standard and is better left enabled.) 2) When you go in and out of the Axis options tab, and you certainly couldn't have done that in the 16 ms between the first two instances, but I'm not sure about the full rescan later. Surely you didn't (couldn't) enter the options before everything had settled and "ready to fly"? 3) When an aircraft is loaded which invokes a change of profile. However, the log shows only one aircraft loading, right at the beginning: 21906 Aircraft="VFA-31 "Tomcatters" 101" So, I've no idea what's so odd with your system at the moment, and it certainly is odd, very odd. Even odder if exactly the same thing is happening on two separate systems -- unless you made one as a copy of the other. Now, I don't think any of this above is really directly connected to the unresponsive throttle. It's all just an indication of something awry. I'll think about how to work out what it is -- aybe even more logging needs to be inserted to track the paths to these incidents. To glean a bit more about the throttle quadrant, concentrating just on the buttons for now, could you please enable button logging in FSUIPC's Logging options, then operate some buttons (maybe once each, in sequence). Then show me that log. Incidentally, you have those additional lines i asked for in the INI twice: Debug=Please LogExtras=x200000 Debug=Please LogExtras=x200000 This won't do any harm, but you might forget to remove both copies when all this os over. I'm afraid it might not be the weekend now before I can do more on this. Pete

The Log is the first doesn't have button or axis event logging enabled. though I see you enabling them in that log before then immediately closing the session anyway. No idea why you thought that might be of interest. And you din't bother to add those two lines to the INI as I asked either. Furthermore, it is rsther bewildering why you also supplied a log in a zip (7z) file which is exactly the same one again, but compressed from a mere 8kb to a minscule 3kb ! Why supply two the same with no more information in than before? The INI shows nothing useful excpt that you enabled button and event logging, as shown in the two identical logs, and proves the omission of the two important lines. :-( I'm going to bed ... Pete

Odd. It must be very big. Please keep the session very short -- i really don't want to have to wade through pages and pages. Try ZIPping it first. It's only a text file and will be a lot smaller. If ZIP isn't accepted, rename the ZIP to TXT -- but tell me, so I name it back. Pete

So, you are now saying that FSUIPC is seeing the X-55 stick? You programmed 2 functions on the hat on that stick? And you say it shows as "A". If it can read 2 buttons, it can read 32. They all arrive together, along with the axis values, in one data bundle. You can't get just buttons or just axes or just parts. The data structure in USB and the DirectInput software provides the lot every time the software asks. So the only problem device is the X-55 Throttle? Only buttons not working? what about the levers, the axes? The INI file is odd. The JoyNames section: [JoyNames] AutoAssignLetters=Yes A=Saitek Pro Flight X-55 Rhino Stick A.GUID={B15E4040-937C-11E5-8002-444553540000} B=Saitek Pro Flight X-55 Rhino Throttle B.GUID={B160B140-937C-11E5-8006-444553540000} C=Saitek Pro Flight Rudder Pedals C.GUID={B15E4040-937C-11E5-8001-444553540000} shows no devices detected at all. There should be lines for each of those giving the actual ID, equating the sames and GUIDs to real devices! And the log shows there WERE real devices detect. So when was this INI from? It couldn't have been AFTER your last test session, the one for which the Log is provided! FSUIPC doesn't change the letter assignments. They have to match the names and GUIDs on the numeric values. The log shows Stick as 0, Throttle as 1, and Rudder as 2, though the Registry was fixed to make the last correct. Apparently it didn't have an ID. Anyway, the Log shows these lines being written to the INI: 140 ---------- Making INI JoyNames Section ---------- 140 Joy#0: Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_2215\" 140 Joy#0: OEMName = "Saitek Pro Flight X-55 Rhino Stick" 140 Joy#0: GUID = {B15E4040-937C-11E5-8002-444553540000} 140 Joy#1: Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_A215\" 140 Joy#1: OEMName = "Saitek Pro Flight X-55 Rhino Throttle" 140 Joy#1: GUID = {B160B140-937C-11E5-8006-444553540000} 140 Joy#2: Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0763\" 140 Joy#2: OEMName = "Saitek Pro Flight Rudder Pedals" 140 Joy#2: GUID = {B15E4040-937C-11E5-8001-444553540000} So why give me an out of date INI? The log shows nothing else useful FSUIPC is certainly doing the right things. Funny, though, in all the reports of X-55 problems it seems to be the Throttle more than the Stick. Perhaps you could answer the question posed above about the levers on the throttle, and also try logging with Axis and Button logging enabled. Did you do the research into problems with the X-55 -- and Win10 If we get no further after this I'll look to see what other logging I can invoke to get at the truth. Pictures don't help, so please don't send any more. i believe you if you tell me what oyu do and see. Pete

Well, it was the Mindstar chap, Stasi, who tested it. I don't have the software. Check you don't have more than one of those settings in the INI, and that it is in the [General] section. You could also try the more extreme one, eliminating all AI reading by FSUIPC, "ProvideAIdata=No". Other than that I'm afraid I've no idea -- you have to get Mindstar support to sort it. It is their software. Pete

I'm not sure it works on the process in which it is running, but even if it does I don't think it will if P3D is running in full screen mode. Are you using it in Windowed mode so that Max/Min operate? Pete

It was the FSUIPC4.LOG I needed, not the install log! The INI file definitely shows they have been detected with Joystick IDs as shown here: [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Combat Rudder Pedals 0.GUID={A86269B0-067D-11E7-800D-444553540000} 1=Saitek Pro Flight X-55 Rhino Stick 1.GUID={A8617F50-067D-11E7-8007-444553540000} 2=Saitek Pro Flight X-55 Rhino Throttle 2.GUID={A8613130-067D-11E7-8005-444553540000} Apart from this, the INI file looks like it's almost all default. Surely you haven't been deleting your INI files? If so, why? When you say: what EXACTLY do you mean? No buttons seen on the Buttons & Switches tab with ANY of the 3 attached and detected controllers? No axes recognised in the Axes tab when you move any levers or pedals? A couple of days back you said: and when I pointed out that you must have had controllers enabled still in the sim you said they weren't, that they were disabled there. This certainly indicates something else was sending the controls, not FSUIPC or the Sim. So what? Is this still the case, the axes work in the Calibration tab even though no one is sending them? An impossible situation. If you do send a proper FSUIPC log (not the Install log), please first, before running the Sim, add these lines to the [General] section FSUIPC4.INI file Debug=Please LogExtras=x200000 Also, go into the FSUIPC Options and enable the Button/Key and Axis logging. Then operate a button or two and move an axis. Keep the session short as the log will get large IF it sees these things. Pete

The facility I mentioned is still in FSUIPC of course. I'm surprised this wasn't made public by MindStar. I don't know what you think you'll find in the L-M forum, it's MindStar support you want. Pete

What Saitek software are you using? I have strong doubts over software which does anything with these devices, especially from Saitek. I'd try first shutting down such software -- yes, by uninstalling the devices then reinstalling BUT without installing ANY software at all. To uninstall properly, do the usual uninstall from the Windows control panel "Programs & Features" facility, and then go to the Device Manager (in "System") and uninstall them there too. Re-boot and just let Windows discover the devices and re-enable them. Check in the Device Manager that they are there and don't have a funny mark on them saying they won't work through lack of drivers. Only if they do, proceed to install drivers, but not any other Saitek software. Then try that. Pete

WHY did you post this Support Question into the FAQ subforum? You are lucky I saw it! Please ALWAYS post support questions to the Support Forum! The only problem i know with Mindstar (only -- no other program has this problem) is crashes the sim or causes other problems when it tries to file a plan with no destination airport selected. I have no idea why it does this, but it usually makes the sim, or at least SimConnect, crash when FSUIPC is reading AI Traffic data including their departure and destination airports. I think L-M were notified of this and said they'd fix it. I don't know if it's been fixed yet, but in the mean time I added an option "ProvideAIairports = No" to stop FSUIPC doing this. Try it. It is in all recent FSUIPC releases (you should be on 4.966c). I thought Stasi has published this workaround for his users. Pete

Please never say that. It means different things to different people. Tell me if it is 4.966c or not. I don't want to wade through a huge log! Please either keep the session short, or take a typical extract! You only had to load up, try using throttle 3 in any one way which you say doesn't work, then terminate the session. Also, it is a pure text file. ZIP it, it will be much much smaller then. With a small sample, illustrating just the problem, not a whole session, you could paste the extract into a message here. that would be much more convenient to both of us. Pete

Apart from the Logs being rather odd, showing re-scans during the short sessions for no apparent reason (not logging USB reconnections, for example), you did not enable the extra logging as instructed so they are not really useful at all i'm afraid. :-( They do show your "X55 Rhino Throttle" detected as Joystick device 2 when you ran P3D, but changed to 1 when running FSX a little later (and the Registry amended to match). Without seeing your INI file for the two I don't know why, but I'd guess that's how you had them defined from before. You'll need to see what you've assigned them too. Maybe you should consider using Joy Letters so your assignments are independent of Joystick ID. Did you research the other threads on the X-55 problems? The X-55, or the drivers Saitek install, do seem rather problematic. Probably the majority of requests for help with joysticks are for the X55 (and similar models, like the X56). Pete

FSUIPC simply copies the throttle values over. Try with a default 3 or 4-engined aircraft first. Also 1-> 1,2,3,4 mapping and Throttle Sync (hotkey or assignable FSUIPC control) Enable axis logging in FSUIPC's Logging tab to see that the appropriate values are being sent. Show me the log if you want me to help check. Please make sure first your FSUIPC is version 4.966c, released today. Pete

You've not made a log yet with joystick diagnostic logging enabled. That might be useful for me to see what is happening. To do this add these two lines to the [General] section of the FSUIPC4.INI file. Please update to 4.966c (now released) first: Debug=Please LogExtras=x200000 Then show me the log please. I don't need any other files at this stage, but the next step might be examining the registry. BTW there are other threads showing problems with the X55, especially if you've installed the Saitek drivers. Here are some instances which were resolved successfully There are a few others if you do a search. Pete

But whether you send a series of keypresses which, as you can see from the logs, just make the Sim look up the keypresses (every time) in the assignments list THEN send the same controls you could have sent in the first place. or send those controls directly yourself, is surely no difference regarding one button or not. Okay. So we confirmed it is a problem with FSX/SP2, as it has always worked fine here with both FSX/ACC and FSX-SE -- as well as P3D. Yes. I never said you could use a mask for the command -- that's only for the FS offset. The Toggle Aircraft Exit takes the door number as parameter. Same here. BUT BUT BUT, as you can see from the logging for the keypresses with Events, those simply send the Toggle Aircraft Exit which you say works. The command equivalents ot your "Shift+E, 1, 2, 3" keypresses are "Toggle Aircraft Exit, Select 1, Select 2, Select 3" -- as you can see if you go back and look at the log! Yes, I get the same here. I cut them out of my log posts here. I don't know there they are coming from. Unless they are being Sent (rather than "Posted") I don't have much chance of finding out either. I just ignore them. I might change FSUIPC so it won't log them, ut folks might sometimes need to see such a log. Anything else now outstanding? With so many posts from you I might have missed something. Pete

Good. I've now released 4.966c which does that repair automatically! Pete