Pete Dowson

You must check the REV option in calibration BEFORE you calibrate, otherwise the calibration will be wrong. The speed brake is not being placed fully down when it should be, when on the ground with wheel speed below 60 knots. When you choose reverse all it does is reverse the values, Once calibrated the behaviour is identical but with the lever going the other way. Any other problems you have with your PMDG product need to be referred to PMDG. I really cannot support add-on aircraft. FSUIPC is just an interface to FS, a tool for you to use as you wish. Pete

4.853 is about two years old and well out of date. You need to download the currently supported version, 4.937. I cannot support old versions. Pete

I'd need to see the Installer log -- which would be in your FSX\Modules folder. Also see if there is an FSUIPC4 log file. Both files are plain text, and you can paste them into a reply here. Use the <> button above the edit area. Pete

FSUIPC is a toolkit You use it for what you want to use it for. Did you not do any research before purchasing it? Really? Why? I've not heard that! If you want more precise calibration, of course. If not, then no. It's your choice. It's just one of the facilities in FSUIPC. If you assign "direct to FSUIPC calibration", then, yes, you need to calibrate. That's the point. If you assign in FS or direct to FS controls in FSUIPC, then, again, it is your choice. That sounds correct. Have you referred to the 737 operating manual? You should not deply spoilers after engaging reverse. Why on Earth would you do that? There is no "reverse" for spoilers! Please read uip a little on the aircraft you are using! Pete

The implementation for CFS2 was a subset of the facilities in FS2000 (whilst CFS1 was a subset of FS98). The AI traffic system which FSUIPC recognises was not incorporated into FS until FS2002 -- a year after CFS2. (I don't include CFS3 because that was not based on FS code at all). Pete

Two points there: First FSUIPC has not used or needed an access code from applicatins for many year. Second, I do not deal with X-plane at all. XPUIPC is not mine. I think you need to look for XPUIPC support elsewhere, possibly via X-plane forums? Pete

There's no way FSUIPC does anything with any keypresses or controls unless it is asked to. You need to look elsewhere. You can use FSUIPC's logging facilities t see what is going on. Maybe you have something using FSUIPC. BTW the currently supported version is 4.937, not 4.93. Pete Pete

As the log shows, there is only 200 milliseconds or so between the "clicks". What do you think is slow about that? Pete

The specific offset is in the list. 3110 I think. I don't have it nearby at present. Pete

Is there an assignable control for firing a gun? There's no specific offset for sure, but you can send controls via an offset. Pete

The "XXXX_SET" axes are the original ones from FS98 and FS2000 days. The "AXIS_XXXX_SET" ones are the newer ones introduced in either FS2002 or FS2004. Don't remember. The main control axes as assigned in FS9 and FSX will be the AXIS .... versions, and some add-on aircraft only process those. There's little to no difference in operation of these, assuming the add-on accepts both, EXCEPT in the case of Throttles and PropPitch. In those cases the AXIS values range from -16384 to +16383 to give only positive inputs in FSX (the range is mapped to 0-16383. The older versions actually use the negative part of the input range to set negative values for those controls -- giving reverse thrust, for instance, or reverse prop pitch. This application of those controls is essential for mapping parts of a levers range to reverse. Pete

Is this with specific aircraft or all? Normally the acceleration, to 10's for instance, is part of FS's inbuilt control acceleration facility, to get to very different values quickly. It is instigated by seing two of the same controls successively -- like double taps on the keyboard instead of definitely separate taps. Your Elite driver, or whatever you have operating those controls, is doing the value increments/decrements internally and writing the resulting values. That is a much more reliable and smooth way of dealing with such instrumentation, and most of my controls are like that -- using my own drivers. Okay. So look: 88093 Button changed: bRef=0, Joy=5, Btn=1, Pressed 88093 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,0 88093 FS Control Sent: Ctrl=65880, Param=0 88156 Button changed: bRef=0, Joy=5, Btn=1, Released 200 mSec gap before next "click" 88359 Button changed: bRef=0, Joy=5, Btn=1, Pressed 88359 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,0 88359 FS Control Sent: Ctrl=65880, Param=0 88390 Button changed: bRef=0, Joy=5, Btn=1, Released Over 1 second gap before next "click" 89731 Button changed: bRef=0, Joy=5, Btn=1, Pressed 89731 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,0 89731 FS Control Sent: Ctrl=65880, Param=0 89794 Button changed: bRef=0, Joy=5, Btn=1, Released About 240 mSec gap before next "click". etc etc You appear to be turning it too fast. One click = one increment or decrement. You might also want to make sure you have "Fix control acceleration" enabled in FSUIPC (on the Miscellaneous Tab). This fixes a bug in FS where it does sometimes accelerate changes when it shouldn't I don't want to watch videos, sorry. Pete

Does the error apply to all FlyTampa airports, though? I'd better check my Copenhagen ... No, seems okay. Phew. Yes, so? ADE is still showing it incorrectly because the FS convention has always been, and still is, -ve = West, +ve = East. So a variation of 9E is +9 whilst 9W is -9. Have you reported this to ADE support? Regards Pete

That's truly weird. I still think, for consistency, the display ADE shows in Airport Properties should show it in its normal form, -ve West. The fact that it's reversed in the binary is really just an encoding matter (probably down to an original error by a Microsoft programmer). By showing it as ADE does, with not even a warning that it is opposite, you are bound to come across implementations, like FlyTampa's, which get it wrong! I wonder if it is wrong in all FlyTampa sceneries? And how many other add-on scenery makers using ADE? So, next step, tell FlyTampa they have it wrong? Pete

That is truly weird. I'll see what ADE makes of the default ... ... YES! ADE shows +15.00 for the stock FSX CYUL airport too -- both ADE 1.65 and the earlier 9x version. So, it looks as if it is a bug in ADE -- and presumably the FlyTampa airport was built with, or at least modified, with ADE. Best report this to both sources, please. Pete

I've looked at your BGL with both ADE 1.65 (same as your pic), and also with AFX 1.10. Interestingly, AFX shows the airport Mag Var as +15.00 whilst ADE shows it as -15.00. Evidently there must be two places where this is recorded. AFX evidently gets it from the same place as MakeRunways -- a 32-bit floating point value at offset 36 in the airport structure. Both programs do give -15.00 Mag Var in each of the ILS navaid entries. Maybe FlyTampa can explain this discrepancy Pete

Makerunways won't make a special case for CYUL. It ca only deal with the data it gets. It certainly gets -15 for CYUL with default FSX scenery as you can see from the log: Airport CYUL :N45:28:04.9911 W073:44:29.0003 118ft City Name="Montreal" Airport Name="Montreal-Pierre-Elliott-Trudeau" in file: Scenery\0301\scenery\APX28150.bgl Runway 6L/24R centre: N45:28:19.9897 W073:45:01.5005 118ft Start 6L: N45:27:41.3109 W073:45:52.2715 118ft Hdg: 42.7 true Computed start 6L: Lat 45.461105 Long -73.765027 Start 24R: N45:28:58.6685 W073:44:10.7280 118ft Hdg: 222.7 true Computed start 24R: Lat 45.483330 Long -73.735812 Hdg: 42.670 true (MagVar -15.000), Asphalt, 11020 x 200 ft Primary ILS ID = IUL Primary ILS: IUL 109.30 Hdg: 43.0 , Flags: GS DME BC "CAT II ILS/DME 06L" Secondary ILS ID = IZZ Secondary ILS: IZZ 111.90 Hdg: 222.7 , Flags: GS BC "ILS 24R" *** Runway *** CYUL0061 Lat 45.461105 Long -73.765030 Alt 118 Hdg 58 Len 11020 Wid 200 ILS 109.30, Flags: GS DME BC *** Runway *** CYUL0242 Lat 45.483330 Long -73.735809 Alt 118 Hdg 238 Len 11020 Wid 200 ILS 111.90, Flags: GS BC Runway 6R/24L centre: N45:28:02.4968 W073:43:43.4997 118ft Start 6R: N45:27:29.1306 W073:44:27.5004 118ft Hdg: 42.8 true Computed start 6R: Lat 45.457775 Long -73.741412 Start 24L: N45:28:35.8629 W073:42:59.4993 118ft Hdg: 222.8 true Computed start 24L: Lat 45.476948 Long -73.716092 Hdg: 42.810 true (MagVar -15.000), Asphalt, 9526 x 200 ft Primary ILS ID = IOA Primary ILS: IOA 110.50 Hdg: 43.0 , Flags: GS DME BC "ILS/DME 06R" Secondary ILS ID = IMQ Secondary ILS: IMQ 110.50 Hdg: 222.8 , Flags: GS BC "ILS 24L" *** Runway *** CYUL0062 Lat 45.457775 Long -73.741409 Alt 118 Hdg 58 Len 9526 Wid 200 ILS 110.50, Flags: GS DME BC *** Runway *** CYUL0241 Lat 45.476948 Long -73.716095 Alt 118 Hdg 238 Len 9526 Wid 200 ILS 110.50, Flags: GS BC Runway 10 /28 centre: N45:27:47.4982 W073:45:07.9989 118ft Start 10 : N45:27:46.0404 W073:45:55.3873 118ft Hdg: 87.5 true Computed start 10 : Lat 45.462780 Long -73.765854 Start 28 : N45:27:48.9235 W073:44:20.6123 118ft Hdg: 267.5 true Computed start 28 : Lat 45.463612 Long -73.738586 Hdg: 87.510 true (MagVar -15.000), Asphalt, 6979 x 200 ft Primary ILS ID = IDO Primary ILS: IDO 110.10 Hdg: 88.0 , Flags: GS BC "ILS 10" and the consequent R5: CYUL,0061,45.461105,-73.765030,118,57.670,11020,109.30BDG,200,-15.000,45.472218,-73.750420,0,, CYUL,0062,45.457775,-73.741409,118,57.810,9526,110.50BDG,200,-15.000,45.467361,-73.728752,0,, CYUL,0100,45.462780,-73.765854,118,102.510,6979,110.10BG,200,-15.000,45.463196,-73.752220,0,, CYUL,0241,45.476948,-73.716095,118,237.810,9526,110.50BG,200,-15.000,45.467361,-73.728752,0,, CYUL,0242,45.483330,-73.735809,118,237.670,11020,111.90BG,200,-15.000,45.472218,-73.750420,0,, CYUL,0280,45.463612,-73.738586,118,282.510,6979,0,200,-15.000,45.463196,-73.752220,0,, So I think you need to check your addon scenery for CYUL. Have a looks at the runway magvars. Pete

Well, in the assignments list in FSX it will tell you which joystick device and which button numbers they are. If it doesn't then they are not being assigned in FSX, but being sent directly by another piece of software -- perhaps some driver you don't realise you have running. From what you are saying that sounds the most likely. Either that, or they are actually producing keystrokes -- try FSUIPC's button and keypress logging. Yes, all that means is that FSUIPC is detecting the controls arriving in FSX. It isn't logging button detection, just the controls. As you say, it isn't seeing the buttons.. Pete

I think the ID toggle uses the panel ID number which you'll find somewhere in the panel.cfg file in the Panel subfolder. For the right CDU it looks like ident=420 That is, at least, what it says for "CDU (Right)" in my old outdated NGX install. The other panel toggle uses the menu sequence number as in the Views menu. Pete

Okay -- without "repeat whilst held" and nbo assignment to button release? In that case it will send one such control on each "on" pulse from the encoder. If you turn it slowly it should decrease one step per click. I have encoders set up like this and they work fine. If you turn them fast then of course you will get multiple clicks and FS will respond to the fast arriving controls appropriately. FSUIPC and FSX both use the same set of functions in Windows to read joystick type devices. If Windows doesn't see them then neither will FS nor FSUIPC. So how did you get them assigned in FSX, and what identification does FSX give them in its assignments? And for that matter, how are they logged by FSUIPC? What joystick number and button number? Or are you only talking about FSUIPC's logging of the event being caused, not the buttons themselves? Pete

FSUIPC is not a device driver. It can only read axis values which Windows itself also recognises. Check Windows first. That said, many folks have problems with Windows 8 and USB joystick devices, problems which were never present in Windows 7 or before. Pete

Apart from a few special facilities for GoFlight devices there are NO provisions in FSUIPC for supporting specific devices. It will recognise anything which looks to Windows like a joystick, but nothing else. FSUIPC is NOT a device driver. Pete

There's no difference. A lever is a lever is a lever. Just assign them to whatever you want, and follow the numbered steps for good calibration. The FSUIPC documentation is all provided in the FSUIPC Documents folder as stated in the installation guide. Pete

You will need to be more specific. Exactly how are you assigning it? Pete

The addon aircraft is taking its time assembling the data for the FMS file. FSUIPC does nothing more than call the FS routines which save flight data. It does nothing itself. It is exactly the same as if you pressed the ; key and entered a filename for the saved files. If this is not acceptable to you I can only suggest turning off Autosave or switching to a different aircraft. Pete