Pete Dowson

No offence taken at all! Why do you think that? Not from FSUIPC itself. I'm afraid I don't know SPAD so maybe that will do it. Sorry! I really don't know everything about other programs. If SPAD have no support, I think it best to post again with a question with SPAD in the title -- then folks who may know might answer when they spot it. Yes, I understand that, and i was trying to answer and help you help yourself. Did you not see the part where I said " there are no facilities in FSUIPC for driving display outputs"? Well, I am 75 and don't know anything about Facebook. i had to learn a bit about forums in order to offer technical support. But they aren't my creation. Join the club. I get very upset by some posts I get here. I'm sorry you took what I thought was a helpful and constructive post in reply to you. The only thing i told you off about was posting three copies of exactly the same text! Surely you can understand that makes no sense and only clutters things up and potentially irritates? I started replying to a second one before I realised it was the same as another I'd seen! Pete

Affirmative. Affirmative. "Auto" means do it automatically, but you can do it manually. If you think you might add or change controllers later, then set itto Yes. It wom't change your manually set ones but will then automatically add letters for new connections. You cannot change the IDs in mid-session. You need to let it do the assignment changes first. Pete

Ah, so if it starts off okay does it continue okay for that session? Can you try moving its axes back and forth before P3D is loaded, or whilst it is loading? Regarding my suggestions earlier: 1. Check the JoyNames section in the INI and make sure the IDs there are all unique. If necessary change them. I see your INI contains a good JoyNames section now. However, you do really need to change this line AutoAssignLetters=No to AutoAssignLetters=Yes Or, for more meaningful assigned letters than A, B, C, D, change it and assign your own letters, so: [JoyNames] 0=Flight Rudder Pedals 0.GUID={AF48AE50-3E72-11E8-8006-444553540000} 1=Plasma-MM2 1.GUID={AF48AE50-3E72-11E8-800A-444553540000} 2=Throttle - HOTAS Warthog 2.GUID={AF48AE50-3E72-11E8-800B-444553540000} 3=Saitek Pro Flight X-55 Rhino Stick 3.GUID={AF48AE50-3E72-11E8-800C-444553540000} R=Flight Rudder Pedals R.GUID={AF48AE50-3E72-11E8-8006-444553540000} Y=Plasma-MM2 Y.GUID={AF48AE50-3E72-11E8-800A-444553540000} T=Throttle - HOTAS Warthog T.GUID={AF48AE50-3E72-11E8-800B-444553540000} S=Saitek Pro Flight X-55 Rhino Stick S.GUID={AF48AE50-3E72-11E8-800C-444553540000} Then run P3D. FSUIPC4 will automatically change all number assignments to letters. After that we can change IDs without messing assignments up. THEN close P3D4 down and edit these lines: 0=Flight Rudder Pedals 0.GUID={AF48AE50-3E72-11E8-8006-444553540000} 1=Plasma-MM2 1.GUID={AF48AE50-3E72-11E8-800A-444553540000} changing them to 4=Flight Rudder Pedals 4.GUID={AF48AE50-3E72-11E8-8006-444553540000} 5=Plasma-MM2 5.GUID={AF48AE50-3E72-11E8-800A-444553540000} so that joystick IDs 0 and 1 are avoided. 2. Uninstall the device completely in Device manager (hopefully this will remove the Registry entries) then re-boot. when the device is seen again it will be added back, hopefully with better entries. I still think this is worth doing, as I'm convinced there's something wrong with the registry entries for the device. Pete

Okay. Thanks for letting me know. Pete

THREE POSTS all exactly the same, and two stupidly entitled "Les Trickett"? What on Earth is that supposed to mean? I've deleted one of them and merged the other two. Please behave more sensibly in the future! Pete

"led". Care to explain? What "led" exactly? If you are thinking that LED can drive displays or LEDs itself, then, sorry, no. there are no facilities in FSUIPC for driving display outputs. BTW, you say you are a "novice" in the title, but that is all you say! And you didn't post in a Support Forum at all! I have moved it for you. It you want to get relevant replaies you ALWAYS need to put a meaningful subject in the title. "Novice FSUIPC User" only gets my attention as the author of the programs supported here and I try to answer everything in any case. But giving it a meaningful title might attract folks who can actually answer your questions more helpfully. Okay? Pete

No! I meant that the Plasma-MM2 has three entries in the registry, as listed, but that two of them have joystick IDs assigned there: 0 for the "correct" connection, which clashes with the pedals, and 1 for the INCORRECT connection relating to some unkown function other than normal joystick operations! Please review again the extracts I showed above! So the CSV you sent earlier was different? Yes, that looks a lot better. Well it would puzzle me too. So what was the previous CSV file you uploaded? One AFTER you had the problem, or an initial problem? Do you know it is different each time? Or is is changing, somehow, later. I've still not heard about the settings in the INI file either! Have you asked ACE support, as it does seem a very specific problem to their device? Pete

Using FSX,. ok, but that's not a lot of information. An add-on aircraft? Saitek control software, or FSX assignments, or FSUIPC assignments, and in the latter case what to (i.e what control names)? BTW proper altitude control needs autothrottle engaged also. Pete

FSUIPC is just returning the error it received from Windows when it asked for the Product Name. as you can see, all the other details were accessible. I'm afraid i don't know what the circumstances can be for the Product name not being readable. I see later on that this did not occur. Ouch! I hadn't noticed that. That shouldn't happen. The first scan shows: 125 Device acquired for use: 125 Joystick ID = 0 (Registry okay) 125 0=Flight Rudder Pedals 125 0.GUID={AF48AE50-3E72-11E8-8006-444553540000} 125 Device acquired for use: 125 Joystick ID = 1 (Registry okay) 125 1=Plasma-MM2 125 1.GUID={AF48AE50-3E72-11E8-800A-444553540000} Looks like the disconnect/reconnection messes something up. what does the JoyNames section in the INI file show? Looking again at the CSV file, i think that's a registry issue: Y, x1E, x06A3, x0763, Flight Rudder Pedals, 0, 0, 0, ... Y, x1E, x12DA, x0920, Plasma-MM2, 0, 0, 0, ... N, x19, x12DA, x0920, Plasma-MM2, -1, 1, 0, .. N, x11, x12DA, x0920, Plasma-MM2, -1, -1, 1, ... Y, x1E, x044F, x0404, Throttle - HOTAS Warthog, 2, 2, 0, ... Y, x1E, x0738, x2215, Saitek Pro Flight X-55 Rhino Stick, 3, 3, 1, ... N, x11, x0738, x2215, Saitek Pro Flight X-55 Rhino Stick, -1, -1, 0, ... Ignore the RED entries which are not valid (readable) joysticks. With the Rhino I think the extra entry is a control interface to set it up or update firmware. not sure why there are two extra entries for the Planma-MM2. The important value to observe here is the second single digit number. That's the ID read from the registry. I've highlit those by Italic large font. The -ve numbers mean none assigned. Odd that one of the non-joystick accesses to the Plasma-MM2 has been assigned ID=1 in the Registry. I suggest two things: 1. Check the JoyNames section in the INI and make sure the IDs there are all unique. If necessary change them. 2. Uninstall the device completely in Device manager (hopefully this will remove the Registry entries) then re-boot. when the device is seen again it will be added back, hopefully with better entries. (If not there's another stage -- Registry editing. but let's leave that for now!). Pete

The Log shows that the device is continally disconnecting and reconnecting. FSUIPC is clearly receiving notifications of these events from Windows. I assume you've not installed any software for the device? Best not to. If you have, try using Windows' Device manager to completely uninstall it and any drivers, then re-boot the PC. Also, make sure that USB power management is disabled on all USB devices (hubs etc) listed in Device Manager. The only alternative answer really is that it is a hardware problem. Try a different USB connection, a different cable. If nothing improves it then I'd suspect the yoke itself. Pete

You'd need to use a user offset (anything between 66C0 and 66FF) to remember the state and use that as a condition on the action. This involves editing the INI file [Keys] section. For the chosenn key you'd use three lines: 1. one line which uses an FSUIPC Offset byte togglebits control to change the byte from/to zero 2. a line with an offset condition testing for zero, and doing one action 3. a line with an offset condition testing for non-zero, and doing the other action Offset conditionals are actually described in the Buttons section of the Advanced User's guide, with a reference to itfrom the Keys section. The FSUIPC Advanced User documentation details how overcome this, and do multiple actions, with buttons and switches, making actions conditional on offset values or other buttons being pressed. There are also flags which can be used to remember the state of one button or switch and using it as the condition on another, so they don't need to be pressed simultaneously. Folks have done a lot with the normal numbers of buttons on joystick type devices. Pete

You need ProSim support then. Sorry. ProSim should just recognise whatever button you choose! You don't have to give numbers! Or at least you didn't use to, surely? I use my own drivers for my 737 Cockpit, interfacing solely via FSUIPC offsets, so I don't really know about assigning joysticks in ProSim. Sorry. Pete

Interesting. I've never met that option! Thanks for the feedback. Pete

Actually, I did a couple of more tests. The symptoms go away not only going into the FSUIPC menu, but any menu which makes a dialogue. That was a really big clue, so i took a closer look ... Seems that in those two instances which you found, FSUIPC receives a "SIM START" state notification, but doesn't see a "SIM STOP" beforehand, so it assumes it is just a repeat of a previous notification. It is easy to fix as I just need to act on the SIM START in any case. It will be fixed in the next release, but there are other changes which depend on the next P3D update, which i hope is not far off. So look out for an update of FSUIPC at that time. Regards Pete

I've now had a chance to reproduce this phenomenon, and i still don't understand it. I shall have to look at adding extra logging to see what is going on. it's almost as if some essential SimConnect functions are suspended, but it certainly isn't getting a SimConnect time-out. Most Simconnect values are arriving normally, but USB events aren't seen. Not sure about AutoSave yet, as that's only dependent upon the time, whis is clearly updating. . Very odd indeed. I'm afraid i might not get to this straightaway. -- a bit tied up over the next few days. Pete

I think it depends on the function. The Sim's autopilot controls operate the Sim's autopilot, which isn't used by ProSim. When using ProSim it provides almost all of the 737 functions you need. For some (like radios) it "shares" the inbuilt sim function, but for advanced aircraft control facilities such as Autpilot and AutoThrottle, it provides its own. That's really the point -- ProSim is providing you with a much more realistic and accurate rendition of a 737 (or A320 if that's the version you are using). The same would apply to other advanced aircraft add-ons, like those from PMDG. I think you might need to read up more on Prosim and perhaps visit their Support Forum. Pete

That's "XPUIPC" by another author. Not me, no, sorry. i'm 75 this year and trying to do less not more! Yours is the first appeal I've received for this. Maybe my successor in FSUIPC development would be interested, but it won't be anytime soon. And then, who knows, you might be using XPlane-12 or -13 (or if Austin is superstitious, 14). Pete

If you assign the button, which is recognised, then when it is pressed FSUIPC will send that P3D4 control. But you say you are using ProSim, sodon't you need to assign in there? ProSim has these AP controls: Two for the Disengage bar on the MCP: MCP AP Disengage Normal MCP AP Disengage Disengage Two for the A and B A/P buttons on the MCP: MCP CMD A Pushed MCP CMD B Pushed And two for the AP Disconnect on the Yokes: AP Disconnect Yoke Capt Pushed AP Disconnect Yoke F/O Pushed Shouldn't you be using one or more of those? Pete

Well, there's some indication of a SimConnect overload, but only affecting the AI Traffic reading link: 3726032 Sim stopped: average frame rate for last 3315 secs = 20.5 fps 3726032 Max AI traffic was 229 aircraft (Deleted 0) 3736203 **** Restarting traffic scanning due to non-reception **** 4009032 Sim stopped: average frame rate for last 273 secs = 30.4 fps 4009032 Max AI traffic was 229 aircraft (Deleted 0) 4206625 **** Restarting traffic scanning due to non-reception **** 5810391 **** Restarting traffic scanning due to non-reception **** 6645907 **** Restarting traffic scanning due to non-reception **** If FSUIPC wasn't getting normal SimConnect events frequently enough it would log it and re-connect Simconnect, which would cause small pauses whilst everything is reloaded. And there's no sign of a joystick device rescan, so it isn't losing USB connections either. So, sorry. It is very odd. I think you'll need to do a process of elimination on your add-ons. Those simple mean that the normal P3D window lost the keyboard focus. It is only logged for information -- a facility added to find out which program was sometimes causing P3d to go into "background" mode whilst some other process ran. the logging of focus changes is just that, logging. It means nothing else. Pete

Mouse macros are supported in the current FSUIPC5 release!!! You must be out of date! Please always check you are using the current version. you can check this in "Download Links" subforum. Pete

How strange. I can't imagine what could cause that. When you say FSUIPC defined controls, do you mean all assigned to buttons or axes, or are you including keyboard? For USB controls like joysticks I can imagine perhaps a strange fault in Windows whereby they get "disconnected" -- going into the FSUIPC menu and out would force a re-scan -- but the AutoSave mechanism is based on a timer, so it really makes no sense. When this happens, and after using the Menu to make it start again, please get the FSUIPC5.LOG file from the P3D Modules folder and show it to me. BTW what's the " time preview window"? Pete

For axes, FSUIPC does nothing different whether in "instant replay" mode or not. FSIOPC doesn't know anything about it and cannot operste differently. What about if the axes are assigned in P3D itself? And is P3D4 ddifferent to P3D3? Sorry, that seems to contradict what you just said! Please explain. There's no such setting. Instant replay mode is totally irrelevant to FSUIPC operations. Check with logging -- FSUIPC logging tab. Enable axis logging and see. Maybe it's a function of P3D4? Perhaps you should ask in the L-M P3D support forum? Pete

Mouse macros from the "old version", whether "old FSUIPC" or "old MadDog", cannot possibly work! You MUST make new ones for P3D, and probably each time you update MadDog. Mouse Macros are closely related to the coding in the add-on aircraft! If it changes, you must re-make them. This is unavoidable and has always been the case! Pete

FSUIPC has no idea nor interest in your airports nor scenery. If anything, it could be a corrupt weather file where the corruption in only in certain weather records which relate to those airports or their vicinity. A sight of the FSUIPC5.LOG would have been useful to see where it gets to! NEVER omit that in any reports, please. The problem is that as soon as FSUIPC starts reading weather data from SimConnect, the latter refers to those files. And the files are in binary WITH NO CHECKING! Note that the Module which crashed was API.DLL, which I think is the one doing the loading. Delete the wxstationlist.bin file in your AppData\Roaming P3D4 folder, and all the .WX files in your P3D4 Files folder in the Documents folder. This loss of saved weather information won't matter if you are using an external weather program, but otherwise just set up new weather and save a flight. Pete

Well, the scan returns the same results for the Trim Wheel in both cases: Y, x1E, x06A3, x0BD4, Pro Flight Cessna Trim Wheel, 4, 4, 0, {627C8510-4FB6-11E8-8001-444553540000}, {627C8510-4FB6-11E8-8001-444553540000}, {627C8510-4FB6-11E8-8001-444553540000}, Y, Y so I really don't understand why it isn't functioning correctly like any other joystick connection. Weird. Pete