Pete Dowson

Well, the numbers came from some time it was there when you closed FS. I wouldn't worry about it. Delete it ccmpletely if you like -- when the sim isn't running though. Pete

15, not 16. 16 is 0x10, more that 4 bits! ;-) Pete

I've had to move this into the support forum, which is where support is provided. Please do not post support questions into the reference subforums. As you found by setting normal defaults, FSUIPC itself does not interfere with anything your aircraft is doing. So something you are setting is the problem. That button changes some of the the settings (mostly those on the Miscellaneous tab) which are saved and used thereafter all the time until you change them again. Just press OK to exit the options when you've pressed it, and it is saved. The settings go into your FSUIPC4.INI file which is loaded each time you run FS. I don't use any PMDG aircraft and I don't know what option(s) you selected which your addons didn't like. However, I have to say that there really is nothing FSUIPC can do to prevent LNAV, VNAV, AT and LVL CHG operations. The worse you might have done is set reversed trim and zero elevator options on the miscellaneous page. Why not just be careful what you select and only use the settings you need and understand? Pete

No. C is 12, the max in 4 bits is 15 which is F so bright yellow would be 0x0FF0 . In 24 bits your 255,255,0 would be 0xFFFF00. If you don't understand hexadecimal please review the FAQ subforum thread "About bits, numbers and hexadecimal". Pete

It is RGB, but the colour is encoded as 12 bits per pixel, not 24, so only 4 bits each, not 8 which your 255 would need. So 6C0 = 6 of Red, 12 of Green, no Blue. Pete

Version 4.959 itself (not the later interim updates) did have an error in one of the Version fields still saying it was 4.958. However, that was corrected in all of the subsequent interim updates (the DLLs only, no installer). Pete

Hi Bob, Any success with that q version of FSUIPC 4.959? I'd like to know before releasing 4.96, hopefully later tomorrow. Thanks, Pete

Not according to the crash report -- or is your system date set incorrectly?: Look: Source: Application Error Date: 23/01/2017 09:09:10 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: CathalsPC Description: Faulting application name: Prepar3D.exe, version: 3.4.18.19475, time stamp: 0x5851bfd2 Faulting module name: FSUIPC4.dll_unloaded, version: 4.9.5.8, time stamp: 0x5857240f I cannot support LINDA myself. Crashes in LINDA.exe have to be dealt with by their support. This might be the DX problem already reported in the L-M forums. I suspect LINDA crashing left some device or other in a strange state. Loading with the n version can still fail if the previous session crashed. Precisely how and why this happens is still unknown, but by all reports if the crashes at the end of session which were occurring with 4.959 + LINDA are fixed, then it is okay ever after. Sometimes crashes on exit go unnoticed. The crash you reported in your first post was actually before FSUIPC was loaded ("FSUIPC_unloaded"), not the crash on exit. To find those you'd need to look further back still in the logs list, and those would certainly be before the n release because even this morning's was, as shown above! Pete

You are not actually testing with FSUIPC 4.959n according to the crash report which is dated 3 days later than the n release -- by then the incorrect version 4,9,5,8 shown in such reports was corrected to show 4,9,5,914, the 14 signifying n. Please replace the DLL with the later version before testing! Pete

Thanks for the feedback. There are definitely others with similar problems. Pete

Oh, I use ProATC/X too. What messages are too long? If it's the clearance or taxi instructions, which obviously vary in length, then this isn't part of the menu but its it the normal test window , w2 = wnd.open("FSX Text", WND_FIXED, 0,0,1024,100) wnd.backcol(w2, 0xfff) wnd.textcol(w2, 0x000) wnd.font(w2, WND_ARIAL, 10, WND_BOLD) I see you already have the font much smaller than that for the other two windows (10 rather than 17), so i suppose you don't have scope to reduce it further? Why not try changing this parameter, so it splits the line earlier? x = 80 --my example of how many characters you want, max After all, this was only my 'example'. If you want to split it further you need rather more complex code, maybe, for three lines, replace this: mycopy = msgs[1] --make a copy for me to use len = string.len(mycopy) if len > x then --need to split mycopy = string.sub(mycopy,1,x) .. "\r" .. string.sub(mycopy, x+1) end by this: mycopy = msgs[1] --make a copy for me to use len = string.len(mycopy) if len > x then --need to split mycopy2 = string.sub(mycopy, x+1) len = string.len(mycopy2) if len > x then --need to split again! mycopy2 = string.sub(mycopy2,1,x) .. "\r" .. string.sub(mycopy2, x+1) end mycopy = string.sub(mycopy,1,x) .. "\r" .. string.sub(mycopy2, x+1) end I haven't been able to test this (my cockpit is not up at present), but it looks okay. If not you should be able to see what it is trying to do and fix it yourself. Scrolling is possible, using code which keeps displaying from one later in the string, via another timer in another function. but that's even more complicated. If you fancy that, why not have a go? Pete

Your FSUIPC is way out of date! Download and install the latest version. Please always check you are using a current version before asking for support! Pete

The messages are just as they are. If they don't fit, they don't fit. What GSX messages are the problem? I have never had a problem reading them. Is your window very small. BTW you seem to have quoted something from me completely disconnected from your question, and there is no "code above". Pete

It's there on my system. FSUIPC gets the list from FS or P3D. What version of FS/P3D are you using and, more importantly, what version of FSUIPC? Pete

Surely it doesn't look "obscure", it is pretty well self-expnatory, and similar to the similar window entries you get in FSX.CFG and Prepar3D.CFg. It saves the position of the last Lua plug-in display window you had showing. At some stage you had some plug-in creating such a window -- LINDA maybe? Or something else you used? And if you want to change them you'd need to do it before starting P3D, and even then they'll probably be overridden by the display plug-in, especially if they are invalid like all 0's. Pete

Assuming the flight you are loading actually was saved with a more 'usual' view, it sounds like you have some incorrect assignment somewhere. Mate you using CH's control program, or are the CH devices only acting directly into FS/FSUIPC? Try enabling event both button and event logging on FSUIPC's Logging tab. You'll need to do that then restart FS so that the log starts off with those set. Show me the log after, and also your settings (the INI file). Both are in the Modules folder. Pete

I found one little suspicious bit of code which I've "fixed", or so I think (the code is old and so am I!). Can you try this test version please? FSUIPC4959q_TEST.zip Pete

You'd need to re-create the file every time, doing the open, write and close all together. Pete

Hmmm. I'll have another look, but the code has simple comparisons. Can you show me a HidScanner log, please? (HidScanner is in the Download Links subforum, in the additional programs thread). Also a Log with this preset in ithe INI file [General] section: Debug=Please LogExtras=x200000 In problems reported before with multiple Bodnar boards, we found that the GUIDs are not permanently associated with a specific one, but more a specific connection (i.e. USB port), so swapping two connections over was completely undetectable by software. I assume it is Windows assigning these according to socket or order of detection This sort of destroys the point of having letters assigned. I'll get back to you when I've looked at the code again. Pete

Also look at this thread, which seems to be about X56 in its later parts. http://forum.simflight.com/topic/82573-fsuipc-button-assignment-not-working-for-all-devices/ Pete

I really don't know. It seems very odd that things can change of their own accord. Really only hardware can do that, so when I hear of such things I always first suspect the hardware. I know you can have self-modifying software, and that settings files can be changed, but FSUIPC most certainly doesn't do either. Settings are made by the user and simply saved. The most interference FSUIPC does is annotate the assignment entries to make them more understandable. Of course,as I understand it, Windows 10 is under continuous change and you can't stop it (or can you?). I've avoided Win10 completely except on my Surface Pro, but that's used only for Internet and Documents. I did have Windows 10 installed on a new PC recently, because the supplier wouldn't install Win7, but after several days of difficulty -- various drivers for my cockpit not working, crashes left right and centre, I went back to Win7, which in my opinion is the best O/S Microsoft ever produced. Pete

Weird. The constant reconnection in your last posted log was worrying though. Make sure the device is plugged into a USB port on the PC itself, not a hub, and probably a USB2 one, not USB3 as many devices do seem to have problems with USB3. I have seen various issues reported with the Saitek X range - X52, X55, X56. I think you maybe you should seek out the respective threads. One I just found is on the P3D website forum, here: http://prepar3d.com/forum/viewtopic.php?t=120515 It might be useful too to visit Saitek's support forum. One thing I find useful is to view the parameters logged by my HidScanner program, which you will find in the Useful Additional Programs thread in the Download Links subforum above. Pete

Re-downloading and re-installing exactly the same meterial really accomplishes nothing at all. Deleting the Settings merely rmoves whatever you already managed to set up. The thing here is that you did say So something has changed since then -- and it isn't the software, obviously. This part of the Log you submitted above definitely shows a bad hardware problem: 863860 ***** HID USB device reconnected: re-initialising FSUIPC connections 863985 ---------------------- Joystick Device Scan ----------------------- 863985 Product= Saitek Pro Flight X-56 Rhino Stick 863985 Manufacturer= Mad Catz 863985 Vendor=0738, Product=2221 (Version 0.20) 863985 Serial Number= 863985 ------------------------------------------------------------------- 864000 ***** HID USB device reconnected: re-initialising FSUIPC connections 864016 ---------------------- Joystick Device Scan ----------------------- 864016 Product= Saitek Pro Flight X-56 Rhino Stick 864016 Manufacturer= Mad Catz 864016 Vendor=0738, Product=2221 (Version 0.20) 864016 Serial Number= 864016 ------------------------------------------------------------------- 864047 ***** HID USB device reconnected: re-initialising FSUIPC connections 864047 ---------------------- Joystick Device Scan ----------------------- 864063 Product= Saitek Pro Flight X-56 Rhino Stick 864063 Manufacturer= Mad Catz 864063 Vendor=0738, Product=2221 (Version 0.20) 864063 Serial Number= 864063 ------------------------------------------------------------------- 864079 ***** HID USB device reconnected: re-initialising FSUIPC connections 864079 ---------------------- Joystick Device Scan ----------------------- 864079 Product= Saitek Pro Flight X-56 Rhino Stick 864094 Manufacturer= Mad Catz 864094 Vendor=0738, Product=2221 (Version 0.20) 864094 Serial Number= 864094 ------------------------------------------------------------------- 864110 ***** HID USB device reconnected: re-initialising FSUIPC connections 864110 ---------------------- Joystick Device Scan ----------------------- 864110 Product= Saitek Pro Flight X-56 Rhino Stick 864110 Manufacturer= Mad Catz 864110 Vendor=0738, Product=2221 (Version 0.20) 864110 Serial Number= 864110 ------------------------------------------------------------------- 864141 ***** HID USB device reconnected: re-initialising FSUIPC connections 864141 ---------------------- Joystick Device Scan ----------------------- 864141 Product= Saitek Pro Flight X-56 Rhino Stick 864141 Manufacturer= Mad Catz 864141 Vendor=0738, Product=2221 (Version 0.20) 864141 Serial Number= 864141 ------------------------------------------------------------------- 864172 ***** HID USB device reconnected: re-initialising FSUIPC connections 864172 ---------------------- Joystick Device Scan ----------------------- 864172 Product= Saitek Pro Flight X-56 Rhino Stick 864172 Manufacturer= Mad Catz 864172 Vendor=0738, Product=2221 (Version 0.20) 864172 Serial Number= 864172 ------------------------------------------------------------------- 864188 ***** HID USB device reconnected: re-initialising FSUIPC connections 864204 ---------------------- Joystick Device Scan ----------------------- 866297 Product= Saitek Pro Flight X-56 Rhino Stick 866297 Manufacturer= Mad Catz 866297 Vendor=0738, Product=2221 (Version 0.20) 866297 Serial Number= 866297 ------------------------------------------------------------------- 876547 ***** HID USB device reconnected: re-initialising FSUIPC connections 876563 ---------------------- Joystick Device Scan ----------------------- 876563 Product= Saitek Pro Flight X-56 Rhino Stick 876563 Manufacturer= Mad Catz 876563 Vendor=0738, Product=2221 (Version 0.20) 876563 Serial Number= 876563 ------------------------------------------------------------------- 876594 ***** HID USB device reconnected: re-initialising FSUIPC connections 876610 ---------------------- Joystick Device Scan ----------------------- 876610 Product= Saitek Pro Flight X-56 Rhino Stick 876610 Manufacturer= Mad Catz 876610 Vendor=0738, Product=2221 (Version 0.20) 876610 Serial Number= 876610 ------------------------------------------------------------------- 877813 ***** HID USB device reconnected: re-initialising FSUIPC connections 877829 ---------------------- Joystick Device Scan ----------------------- 877844 Product= Saitek Pro Flight X-56 Rhino Stick 877844 Manufacturer= Mad Catz 877844 Vendor=0738, Product=2221 (Version 0.20) 877844 Serial Number= 877844 ------------------------------------------------------------------- 877875 ***** HID USB device reconnected: re-initialising FSUIPC connections 877891 ---------------------- Joystick Device Scan ----------------------- 877891 ------------------------------------------------------------------- 877938 ***** HID USB device reconnected: re-initialising FSUIPC connections 877954 ---------------------- Joystick Device Scan ----------------------- 877954 ------------------------------------------------------------------- 878000 ***** HID USB device reconnected: re-initialising FSUIPC connections 878032 ---------------------- Joystick Device Scan ----------------------- 878032 ------------------------------------------------------------------- 878079 ***** HID USB device reconnected: re-initialising FSUIPC connections 878094 ---------------------- Joystick Device Scan ----------------------- 878094 ------------------------------------------------------------------- 878125 ***** HID USB device reconnected: re-initialising FSUIPC connections 878141 ---------------------- Joystick Device Scan ----------------------- 878141 ------------------------------------------------------------------- 878172 ***** HID USB device reconnected: re-initialising FSUIPC connections 878188 ---------------------- Joystick Device Scan ----------------------- 878188 ------------------------------------------------------------------- 878219 ***** HID USB device reconnected: re-initialising FSUIPC connections 878219 ---------------------- Joystick Device Scan ----------------------- 878219 ------------------------------------------------------------------- 882813 ***** HID USB device reconnected: re-initialising FSUIPC connections 882829 ---------------------- Joystick Device Scan ----------------------- 882829 Product= Saitek Pro Flight X-56 Rhino Stick 882829 Manufacturer= Mad Catz 882829 Vendor=0738, Product=2221 (Version 0.20) 882829 Serial Number= 882829 ------------------------------------------------------------------- 884469 ***** HID USB device reconnected: re-initialising FSUIPC connections 884610 ---------------------- Joystick Device Scan ----------------------- 884610 Product= Saitek Pro Flight X-56 Rhino Throttle 884610 Manufacturer= Mad Catz 884610 Vendor=0738, Product=A221 (Version 0.21) 884610 Serial Number= 884610 Product= Saitek Pro Flight X-56 Rhino Stick 884610 Manufacturer= Mad Catz 884610 Vendor=0738, Product=2221 (Version 0.20) 884610 Serial Number= 884610 ------------------------------------------------------------------- 884641 ***** HID USB device reconnected: re-initialising FSUIPC connections 884657 ---------------------- Joystick Device Scan ----------------------- 884657 Product= Saitek Pro Flight X-56 Rhino Throttle 884657 Manufacturer= Mad Catz 884657 Vendor=0738, Product=A221 (Version 0.21) 884657 Serial Number= 884657 Product= Saitek Pro Flight X-56 Rhino Stick 884657 Manufacturer= Mad Catz 884657 Vendor=0738, Product=2221 (Version 0.20) 884657 Serial Number= The USB connection, or the device itself, or even maybe the USB hardware in the PC, is playing up. You cannot get such frequent re-connections of a USB device except by something being wrong. I count 21 re-connections in the space of 21 seconds, and at one stage they were so short that even the identify couldn't be read. Surely neither Windows Game Controllers or P3D itself can handle a device doing this either? Have you checked? Pete

FSUIPC stores your settings in a file called FSUIPC4.INI, and reads that again next time. It also logs those joysticks it sees in its Log file, FSUIPC4.LOG. Those two files might help you understand what is wrong. Other X55/X56 users have found that the units recognition in both FSUIPC and Windows is variable. There are other threads on this subject. If you want further help, show me those two files. I would also need to know whether this is always with the same aircraft, and whether it is an add-on or not. Pete

Good. I won't release 4.959p generally, as I'm close to releasing a full build 4.960, probably Monday or Tuesday. Please just replace it then. Won't be any difference unless something else crops up over the weekend, but I hope to do the few documentation updates before then. Pete