Pete Dowson

It is limited to the number of virtual buttons available for assignment in FSUIPC -- 288. I fear you misunderstand something. The button functions are defined by how you assign them in FSUIPC, not by anything in WideClient. You can use bigger buttons with multiple labels on each (eg two lines on each label). The assignment of the functions in FSUIPC can be profile specific, so change function according to profile. For all FSUIPC cares you can simply number the buttons in WideClient and refer to a book to see which does what. Pete

This is a regular occurring problem with Saitek devices. It is a problem with the way it gets installed and I think it has to be corrected by a Registry hack. It is nothing to do with FS or FSUIPC and can't be corrected in either, as it affects the values being supplied from Windows before either FS or FSUIPC sees them. I'm afraid i don't know what the Registry fix is. You'll probably have to head over to the Saitek support forum and search there I'm afraid. Don't limit your search to trim wheel -- the problem has been reported with other Saitek axes too on other devices. Pete

Rudder deflection is a function of the aircraft design, not of input settings -- you might want to look at the AIRCRAFT.CFG file for that, though the designer should have made it as realistic as possible already. Proper calibration of surface controls will ensure that you can get to both extremes of movement allowed by the aircraft model. Using the 'slopes' facility you can make the effect more or less pronounced near the central area, according to your wishes, but of course you pay for that by the opposite effect further out -- whatever you change, you still always need to be able to reach all possible positions of the control surface. You can of course calibrate in such a way that you get to the extreme rudder positions with a shorter movement of the pedals, but all you are really doing then is wasting part of the range of the pedals and reducing the resolution. For best results follow the calibration steps as documented in the user guide carefully and accurately. You should then end up with the aircraft behaving as the modeller intended. If that isn't as real as you think it should be, it is a matter of tinkering with the model itself, not your controls. Regards Pete

Okay. Till the next set of questions, good flying! ;-) Pete

Thanks for testing. I'll release it as it stands, I think. Next major release will probably be for P3D version 2.3, but I've no idea when that'll be. Probably when I'm next on holiday -- it's happened that way every time so far! Pete

Yes, please do. But it sounds highly likely that F1 have done their own thing for this function. Pete

I think PMDG use their own systems for pretty much everything. As, in fact, do I in my B738 cockpit -- Project Magenta does the MCP and Autopilot, and a mix of third party software, including my own, takes care of all the other subsystems. The autopilot switching is done in several places and ways: 1 The engage buttons on the MCP for left and right A/P (there are three of course on a 747. Not sure about the T7). 2.The A/P disconnect bar, below the buttons on the MCP 3. the A/P disconnect button (red one) on the yokes of both Captain and First Officer. The A/P disconnect button does not also operate to connect the A/P, at least not in the 737, but, yes, when used to disconnect the horn will sound and you press it again to silence it. The horn also sounds if the A/P disconnects for any other reason, like an inability to cope with severe turbulence, or extraordinary trimming requirements. Regards Pete

But you get the same facilities no matter how or where you assign. All of the control surface axes go to calibration, just by different routes. The "direct to calibration" assignment is only different in that it bypasses FS completely.before calibration. Calibration and all the facilities you want to use there was a feature of FSUIPC long before there were ever any assignment facilities. All normal axes which are worth calibrating can be calibrated NO MATTER HOW OR WHERE YOU ASSIGN THEM! Heading bugs aren't calibratable, full stop. It would make no sense to. They are not continuous values to start with. I can't imagine anyone ever wanting to do such a thing! You want "heading bug increment" and "heading bug decrement". Much more sensible. Otherwise, for example, what happens when you get to the end of the lever's travel? And there is really no way ever of getting the output of the sorts of pots they use on a joystick to give you 360 different and consistent values, no matter how much smoothing or calibration you do. There are no parameters in the INI for controls which cannot be calibrated. No keywords for them, no entries, nothing. If you assign to "Heading Bug Set" you are responsible for making sure the value which is supplied is correct for the heading bug. i.e. 0-359. Those controls are mainly for use by programs which want to set the heading bug directly. The only way really to do it from an axis is to assign the axis to a Lua plug-in program which then converts the values coming in from the axis into 0-359, probably using a table of 360 ranges. Not that you'd ever be likely to find an axis which would reliably give you so many values. Pete

Okay. Something must have been corrupted, but I've no idea what could give those symptoms. I'm glad you are okay now. Pete

Logging L:Vars doesn't log controls, so i guess you aren't logging L:Vars. What did you do? Well that works fine, with the FS control 66373 and offset 2F68 changing accordingly, as logged here where I clicked the button twice: 114162 *** EVENT: Cntrl= 66373 (0x00010345), Param= 1 (0x00000001) ATTITUDE_CAGE_BUTTON 114193 Monitor IPC:2F68 (U32) = 1 114193 SimRead: 2F68="ATTITUDE CAGE" INT32: 1 (0x00000001) 119731 *** EVENT: Cntrl= 66373 (0x00010345), Param= 1 (0x00000001) ATTITUDE_CAGE_BUTTON 119762 Monitor IPC:2F68 (U32) = 0 119762 SimRead: 2F68="ATTITUDE CAGE" INT32: 0 (0x00000000) Regards Pete

You can use FSUIPC's logging to find out. Log Events to see if FS controls are being sent, and use the Monitor (right-hand side of the Logging tab) to log 07BC as type U32 to the normal log. Pete

So isn't my solution valid? If not why not? What is wrong with the flag method, exactly? Offset 07BC is the default FS master autopilot switch, for which 'Z' normally relates and toggles. 07BC is always toggled by the FS control AP MASTER. If this is being used by your aircraft, where does Ctrl+Shift+Z come in? Is that also toggling the FS master? Evidently clarification is needed on this. Why did you think 07BC might be useful? There's no need to be concerned there about bits and bytes. The offset is simply zero or non-zero. But it may not relate to your aircraft at all. That's the bigger question surely? I am pretty sure there aren't three conditions in FSX itself. FSUIPC is an interface into FSX, not into third party aircraft -- though some do have offset space reserved. The PMDG 777 isn't one of them. I don't know if PMDG provide status information for all of their subsystems. Pete

If Flight1 have implemented their own Attitude Cage mechanism and not provided a way for its state to be determined, then you are out of luck. Maybe it can be read as an L:Var (local panel variable)? Have you tried logging those? If you want me to actually check whether the built-in FSX facility is working with that offset, please tell me which default FS aircraft features one and how to enable / disable it. Pete

Okay, so it isn't the default A/P and that weird offset test attempt is a red herring? So you are using a non-existent button flag. Good. You could simply use two of those if you wanted to have to press the button twice, thus: 0=P3, 0, C1005, 3842 1=CP(F+15,2) (F-15,3)3,0,K90,8 2=CP(F-15,2) (F-15,3)3,0,K90,11 3=CP(F+15,2) (F+15,3)3,0,K90,11 4=CP(F+15,2) (F+15,3)3,0,C1005,3842 5=CP(F+15,2) (F+15,3)3,0,C1005,3843 6=CP(F-15,2) 3,0,C1005,3843 !st press, 15,2 = TRUE, 15,3 = FALSE, sends Z 2nd press, 15,2 = FALSE, 15,3 = FALSE, sends Ctrl+Shft+Z and sets 15,3 TRUE 3rd press, 15,2 = TRUE, 15,3 = TRUE, sends Ctrl+Shft+Z and sets both 15,2 and 15,3 FALSE If these commands are "toggles", then if you cannot determine the state of the autopilot then you cannot do any different. Everything must be synchronised properly all the time. If you can determine the autopilot state, then you can sort it. If they are not toggles, if 'Z' always turns the A/P 'on', then you are okay. If it is already on and you want it off, just press twice, plus a third time to silence the horn. Pete

Yes, and it identified the problem: The only times this has occurred before is with folks who have a non-standard DirectX module installed which FSX is picking up. It is evidently one which doesn't support the full range of Windows DirectX functions, hence the failure. Searching on the error number 80040154 I found these threads: http://forum.simflight.com/topic/76735-still-problems-to-assign-axis-in-fsx-for-fsuipc/?hl=%2Bdirectinput8create+%2Bfailed%2C+%2Breturn+%2B80040154#entry467162 http://forum.simflight.com/topic/76577-axis-assignment-not-responding/?hl=%2Bdirectinput8create+%2Bfailed%2C+%2Breturn+%2B80040154#entry466435 I'm confident one of these answers will answer your problem too. Pete

What version of FS, what aircraft? In FSX, offset 2F68 is simply the copy of the SimConnect value called "ATTITUDE CAGE". I've no idea what that is or what the value does. To change it there is only the Toggle attitude cage control. What is it you are wanting? Pete

Well, if you are sure this doesn't give you a simconnect log then something is really very very seriously wrong with your FS installation. this logging facility is not anything of mine, it is built into SimConnect (all versions). Sorry, but I'm all out of ideas. I can only suggest you reinstall everything and hope it then works. I'm absolutely amazed that you have the other add-ins loading -- it seems impossible given that even the basic Simconnect facilities aren't working. One last question -- you did prepare the file using something like Notepad, didn't you, not Word or a word processor of any kind? It must be a normal text file, NOT a word processed file. Pete

Did you omit the "file=" part by any chance? I think you'd better show me the SimConnect.INI file again, and also tell me where you put it! I've never ever have anyone fail to get a SimConnect log before. Pete

All that looks fine. Curiouser and curiouser. We need more logging to see what might be happening. Also please show me the JoyNames section of the FSUIPC4.INI file. For the extra logging, please edit the FSUIPC4.INI file, adding these lines to the [General] section: Debug=Please LogExtras=xA0000A LogButtonsKeys=Yes LogAxes=Yes Run FS, waggle some joystick axes, press some buttons, then close FS. Show me the FSUIPC4.LOG file. If too big send to petedowson@btconnect.com. Pete

Some questions first. If 'z' assigned in the add-on aircraft, or is it still assigned to the normal default FS aurtopilot master toggle? In otherwords, can you assign to the FS control instead of to the keystroke 'z'? And how is the "Shift+Control+Z" assigned? i.e. what control or function? I don't understand this bit. What button has to be held down? Flags on "unused" buttons are normally flags on "non-existent" buttons -- i.e. one of a joystick you don't have, so you can't press it down, you just set its flag or clear it by using the flag setting and clearing assignments. Can you explain what "D0&BC=0" means? Is the '&' a typo there? Are you trying to test an offset? Pete

Oh dear. The path to the FSX modules folder is NOT "path to ..." YOU must fill that part in with the actual path to the FSX folder on your specific PC!!!! There has to be a Drive, for instance, like C: A typical FS path is "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X", but it depends on your setup. On my system it is simply "E:\FSX"., so I would put: file=E:\FSX\Modules\SimConnect%01u.Log See? YOU have to fill in the path!!!! Pete

The filter option is in the Calibration part of FSUIPC. It doesn't matter WHERE or HOW you assign the controls, the calibration is separate. I have said this many times now and you still don't read what I say. Just assign in whatever way you like, then go and calibrate, and, yes, if you wish, set the Filter option. Why is this so difficult for you? Pete

The first lines are assignments, not calibration settings. The calibrations LeftBrake=-16380,16380 RightBrake=-16380,16380 are the default values, which means you've not actually followed the calibration steps at all. Please refer to the calibration section of the User guide and follw the numbered steps. There is really no point in using FSUIPC if you don't actually make it do anything! Do NOT mess about with numbers in the INI file! Just calibrate correctly according to the step by step instructions! Also note that almost all toe brakes need reversing ("REV" option) before calibration, otherwise they'll be on unless you press them! Pete

I don't know of any reason why FSUIPC should be able to fix Win8 problems. It is certainly nothing promised by FSUIPC at all. I have heard some folks say this, but there's really no reason why, as FSUIPC's methods are perfectly standard, like FSX. Perhaps you should have asked here before purchase? I would have said that I see no reason why it should be any different to fSX. FSUIPC uses exactly the same methods to read joysticks as FS, so I cannot imagine what can be wrong. Perhaps first of all you could find the FSUIPC4 log file and paste its contents in a reply here? I cannot really help with no information, and that would be a start. Pete

Not easily. What is the limit in any case, and what is the point of so many stations -- one per passenger? Seems daft to me. Pete