Pete Dowson

Just got it in before August ;-). download FSUIPC 4.841 or 3.999t as appropriate. The Lua documentation is also updated -- see its own thread in Download Links. Regards Pete

Yes, that would do it! Ouch. Why not check the list of custom control numbers, released as part of the SDK? Here's what I see listed: // CDU #define EVT_CDU_L_L1 (THIRD_PARTY_EVENT_ID_MIN + 534) #define EVT_CDU_L_L2 (THIRD_PARTY_EVENT_ID_MIN + 535) #define EVT_CDU_L_L3 (THIRD_PARTY_EVENT_ID_MIN + 536) #define EVT_CDU_L_L4 (THIRD_PARTY_EVENT_ID_MIN + 537) #define EVT_CDU_L_L5 (THIRD_PARTY_EVENT_ID_MIN + 538) #define EVT_CDU_L_L6 (THIRD_PARTY_EVENT_ID_MIN + 539) #define EVT_CDU_L_R1 (THIRD_PARTY_EVENT_ID_MIN + 540) #define EVT_CDU_L_R2 (THIRD_PARTY_EVENT_ID_MIN + 541) #define EVT_CDU_L_R3 (THIRD_PARTY_EVENT_ID_MIN + 542) #define EVT_CDU_L_R4 (THIRD_PARTY_EVENT_ID_MIN + 543) #define EVT_CDU_L_R5 (THIRD_PARTY_EVENT_ID_MIN + 544) #define EVT_CDU_L_R6 (THIRD_PARTY_EVENT_ID_MIN + 545) #define EVT_CDU_L_INIT_REF (THIRD_PARTY_EVENT_ID_MIN + 546) #define EVT_CDU_L_RTE (THIRD_PARTY_EVENT_ID_MIN + 547) #define EVT_CDU_L_CLB (THIRD_PARTY_EVENT_ID_MIN + 548) #define EVT_CDU_L_CRZ (THIRD_PARTY_EVENT_ID_MIN + 549) #define EVT_CDU_L_DES (THIRD_PARTY_EVENT_ID_MIN + 550) #define EVT_CDU_L_MENU (THIRD_PARTY_EVENT_ID_MIN + 551) #define EVT_CDU_L_LEGS (THIRD_PARTY_EVENT_ID_MIN + 552) #define EVT_CDU_L_DEP_ARR (THIRD_PARTY_EVENT_ID_MIN + 553) #define EVT_CDU_L_HOLD (THIRD_PARTY_EVENT_ID_MIN + 554) #define EVT_CDU_L_PROG (THIRD_PARTY_EVENT_ID_MIN + 555) #define EVT_CDU_L_EXEC (THIRD_PARTY_EVENT_ID_MIN + 556) #define EVT_CDU_L_N1_LIMIT (THIRD_PARTY_EVENT_ID_MIN + 557) #define EVT_CDU_L_FIX (THIRD_PARTY_EVENT_ID_MIN + 558) #define EVT_CDU_L_PREV_PAGE (THIRD_PARTY_EVENT_ID_MIN + 559) #define EVT_CDU_L_NEXT_PAGE (THIRD_PARTY_EVENT_ID_MIN + 560) #define EVT_CDU_L_1 (THIRD_PARTY_EVENT_ID_MIN + 561) #define EVT_CDU_L_2 (THIRD_PARTY_EVENT_ID_MIN + 562) #define EVT_CDU_L_3 (THIRD_PARTY_EVENT_ID_MIN + 563) #define EVT_CDU_L_4 (THIRD_PARTY_EVENT_ID_MIN + 564) #define EVT_CDU_L_5 (THIRD_PARTY_EVENT_ID_MIN + 565) #define EVT_CDU_L_6 (THIRD_PARTY_EVENT_ID_MIN + 566) #define EVT_CDU_L_7 (THIRD_PARTY_EVENT_ID_MIN + 567) #define EVT_CDU_L_8 (THIRD_PARTY_EVENT_ID_MIN + 568) #define EVT_CDU_L_9 (THIRD_PARTY_EVENT_ID_MIN + 569) #define EVT_CDU_L_DOT (THIRD_PARTY_EVENT_ID_MIN + 570) #define EVT_CDU_L_0 (THIRD_PARTY_EVENT_ID_MIN + 571) #define EVT_CDU_L_PLUS_MINUS (THIRD_PARTY_EVENT_ID_MIN + 572) #define EVT_CDU_L_A (THIRD_PARTY_EVENT_ID_MIN + 573) #define EVT_CDU_L_B (THIRD_PARTY_EVENT_ID_MIN + 574) #define EVT_CDU_L_C (THIRD_PARTY_EVENT_ID_MIN + 575) #define EVT_CDU_L_D (THIRD_PARTY_EVENT_ID_MIN + 576) #define EVT_CDU_L_E (THIRD_PARTY_EVENT_ID_MIN + 577) #define EVT_CDU_L_F (THIRD_PARTY_EVENT_ID_MIN + 578) #define EVT_CDU_L_G (THIRD_PARTY_EVENT_ID_MIN + 579) #define EVT_CDU_L_H (THIRD_PARTY_EVENT_ID_MIN + 580) #define EVT_CDU_L_I (THIRD_PARTY_EVENT_ID_MIN + 581) #define EVT_CDU_L_J (THIRD_PARTY_EVENT_ID_MIN + 582) #define EVT_CDU_L_K (THIRD_PARTY_EVENT_ID_MIN + 583) #define EVT_CDU_L_L (THIRD_PARTY_EVENT_ID_MIN + 584) #define EVT_CDU_L_M (THIRD_PARTY_EVENT_ID_MIN + 585) #define EVT_CDU_L_N (THIRD_PARTY_EVENT_ID_MIN + 586) #define EVT_CDU_L_O (THIRD_PARTY_EVENT_ID_MIN + 587) #define EVT_CDU_L_P (THIRD_PARTY_EVENT_ID_MIN + 588) #define EVT_CDU_L_Q (THIRD_PARTY_EVENT_ID_MIN + 589) #define EVT_CDU_L_R (THIRD_PARTY_EVENT_ID_MIN + 590) #define EVT_CDU_L_S (THIRD_PARTY_EVENT_ID_MIN + 591) #define EVT_CDU_L_T (THIRD_PARTY_EVENT_ID_MIN + 592) #define EVT_CDU_L_U (THIRD_PARTY_EVENT_ID_MIN + 593) #define EVT_CDU_L_V (THIRD_PARTY_EVENT_ID_MIN + 594) #define EVT_CDU_L_W (THIRD_PARTY_EVENT_ID_MIN + 595) #define EVT_CDU_L_X (THIRD_PARTY_EVENT_ID_MIN + 596) #define EVT_CDU_L_Y (THIRD_PARTY_EVENT_ID_MIN + 597) #define EVT_CDU_L_Z (THIRD_PARTY_EVENT_ID_MIN + 598) #define EVT_CDU_L_SPACE (THIRD_PARTY_EVENT_ID_MIN + 599) #define EVT_CDU_L_DEL (THIRD_PARTY_EVENT_ID_MIN + 600) #define EVT_CDU_L_SLASH (THIRD_PARTY_EVENT_ID_MIN + 601) #define EVT_CDU_L_CLR (THIRD_PARTY_EVENT_ID_MIN + 602) #define EVT_CDU_L_BRITENESS (THIRD_PARTY_EVENT_ID_MIN + 605) #define EVT_CDU_R_L1 (THIRD_PARTY_EVENT_ID_MIN + 606) #define EVT_CDU_R_L2 (THIRD_PARTY_EVENT_ID_MIN + 607) #define EVT_CDU_R_L3 (THIRD_PARTY_EVENT_ID_MIN + 608) #define EVT_CDU_R_L4 (THIRD_PARTY_EVENT_ID_MIN + 609) #define EVT_CDU_R_L5 (THIRD_PARTY_EVENT_ID_MIN + 610) #define EVT_CDU_R_L6 (THIRD_PARTY_EVENT_ID_MIN + 611) #define EVT_CDU_R_R1 (THIRD_PARTY_EVENT_ID_MIN + 612) #define EVT_CDU_R_R2 (THIRD_PARTY_EVENT_ID_MIN + 613) #define EVT_CDU_R_R3 (THIRD_PARTY_EVENT_ID_MIN + 614) #define EVT_CDU_R_R4 (THIRD_PARTY_EVENT_ID_MIN + 615) #define EVT_CDU_R_R5 (THIRD_PARTY_EVENT_ID_MIN + 616) #define EVT_CDU_R_R6 (THIRD_PARTY_EVENT_ID_MIN + 617) #define EVT_CDU_R_INIT_REF (THIRD_PARTY_EVENT_ID_MIN + 618) #define EVT_CDU_R_RTE (THIRD_PARTY_EVENT_ID_MIN + 619) #define EVT_CDU_R_CLB (THIRD_PARTY_EVENT_ID_MIN + 620) #define EVT_CDU_R_CRZ (THIRD_PARTY_EVENT_ID_MIN + 621) #define EVT_CDU_R_DES (THIRD_PARTY_EVENT_ID_MIN + 622) #define EVT_CDU_R_MENU (THIRD_PARTY_EVENT_ID_MIN + 623) #define EVT_CDU_R_LEGS (THIRD_PARTY_EVENT_ID_MIN + 624) #define EVT_CDU_R_DEP_ARR (THIRD_PARTY_EVENT_ID_MIN + 625) #define EVT_CDU_R_HOLD (THIRD_PARTY_EVENT_ID_MIN + 626) #define EVT_CDU_R_PROG (THIRD_PARTY_EVENT_ID_MIN + 627) #define EVT_CDU_R_EXEC (THIRD_PARTY_EVENT_ID_MIN + 628) #define EVT_CDU_R_N1_LIMIT (THIRD_PARTY_EVENT_ID_MIN + 629) #define EVT_CDU_R_FIX (THIRD_PARTY_EVENT_ID_MIN + 630) #define EVT_CDU_R_PREV_PAGE (THIRD_PARTY_EVENT_ID_MIN + 631) #define EVT_CDU_R_NEXT_PAGE (THIRD_PARTY_EVENT_ID_MIN + 632) #define EVT_CDU_R_1 (THIRD_PARTY_EVENT_ID_MIN + 633) #define EVT_CDU_R_2 (THIRD_PARTY_EVENT_ID_MIN + 634) #define EVT_CDU_R_3 (THIRD_PARTY_EVENT_ID_MIN + 635) #define EVT_CDU_R_4 (THIRD_PARTY_EVENT_ID_MIN + 636) #define EVT_CDU_R_5 (THIRD_PARTY_EVENT_ID_MIN + 637) #define EVT_CDU_R_6 (THIRD_PARTY_EVENT_ID_MIN + 638) #define EVT_CDU_R_7 (THIRD_PARTY_EVENT_ID_MIN + 639) #define EVT_CDU_R_8 (THIRD_PARTY_EVENT_ID_MIN + 640) #define EVT_CDU_R_9 (THIRD_PARTY_EVENT_ID_MIN + 641) #define EVT_CDU_R_DOT (THIRD_PARTY_EVENT_ID_MIN + 642) #define EVT_CDU_R_0 (THIRD_PARTY_EVENT_ID_MIN + 643) #define EVT_CDU_R_PLUS_MINUS (THIRD_PARTY_EVENT_ID_MIN + 644) #define EVT_CDU_R_A (THIRD_PARTY_EVENT_ID_MIN + 645) #define EVT_CDU_R_B (THIRD_PARTY_EVENT_ID_MIN + 646) #define EVT_CDU_R_C (THIRD_PARTY_EVENT_ID_MIN + 647) #define EVT_CDU_R_D (THIRD_PARTY_EVENT_ID_MIN + 648) #define EVT_CDU_R_E (THIRD_PARTY_EVENT_ID_MIN + 649) #define EVT_CDU_R_F (THIRD_PARTY_EVENT_ID_MIN + 650) #define EVT_CDU_R_G (THIRD_PARTY_EVENT_ID_MIN + 651) #define EVT_CDU_R_H (THIRD_PARTY_EVENT_ID_MIN + 652) #define EVT_CDU_R_I (THIRD_PARTY_EVENT_ID_MIN + 653) #define EVT_CDU_R_J (THIRD_PARTY_EVENT_ID_MIN + 654) #define EVT_CDU_R_K (THIRD_PARTY_EVENT_ID_MIN + 655) #define EVT_CDU_R_L (THIRD_PARTY_EVENT_ID_MIN + 656) #define EVT_CDU_R_M (THIRD_PARTY_EVENT_ID_MIN + 657) #define EVT_CDU_R_N (THIRD_PARTY_EVENT_ID_MIN + 658) #define EVT_CDU_R_O (THIRD_PARTY_EVENT_ID_MIN + 659) #define EVT_CDU_R_P (THIRD_PARTY_EVENT_ID_MIN + 660) #define EVT_CDU_R_Q (THIRD_PARTY_EVENT_ID_MIN + 661) #define EVT_CDU_R_R (THIRD_PARTY_EVENT_ID_MIN + 662) #define EVT_CDU_R_S (THIRD_PARTY_EVENT_ID_MIN + 663) #define EVT_CDU_R_T (THIRD_PARTY_EVENT_ID_MIN + 664) #define EVT_CDU_R_U (THIRD_PARTY_EVENT_ID_MIN + 665) #define EVT_CDU_R_V (THIRD_PARTY_EVENT_ID_MIN + 666) #define EVT_CDU_R_W (THIRD_PARTY_EVENT_ID_MIN + 667) #define EVT_CDU_R_X (THIRD_PARTY_EVENT_ID_MIN + 668) #define EVT_CDU_R_Y (THIRD_PARTY_EVENT_ID_MIN + 669) #define EVT_CDU_R_Z (THIRD_PARTY_EVENT_ID_MIN + 670) #define EVT_CDU_R_SPACE (THIRD_PARTY_EVENT_ID_MIN + 671) #define EVT_CDU_R_DEL (THIRD_PARTY_EVENT_ID_MIN + 672) #define EVT_CDU_R_SLASH (THIRD_PARTY_EVENT_ID_MIN + 673) #define EVT_CDU_R_CLR (THIRD_PARTY_EVENT_ID_MIN + 674) #define EVT_CDU_R_BRITENESS (THIRD_PARTY_EVENT_ID_MIN + 677) [/CODE] Doesn't that cover most if not all, and for both left and right CDUs? Assigning custom control numbers directly rather than using Mouse controls would be much more reliable and change-proof. Regards Pete

To my knowledge no one has ever found a way to make FS9 (or earlier) recompute all the values when you change the payload -- other than visiting the menus, that is. In my younger days I would have taken this as a challenge and would have tried reverse-engineering the menu "OK" exit path to see what it called to do these things, but I'm afraid I am past that now. I did actually spend about a week on it years ago, but go nowhere and gave up. Sorry. Pete

Mouse macros? With the PMDG 737NGX? You do realise that they've now published the complete list of commands you can use for that aircraft? Maybe the list doesn't include some of the CDU buttons. Is that it? In FSUIPC's Logging tab, enable button logging and event logging, then use the button and see what it says in the log. Have you updated the 737NGX at all? If so it is almost certain that you have to regenerate all mouse macros for it, because they address actual positions in memory where code is to be executed. Regards Pete

But when you are hoping or expecting a new facility, or think you've found a new bug, isn't the best thing to do first to check for updates? ;-) There or the one here in the Download Links subforum. They both point to the same thing in any case. Regards Pete

Ah. that's probably why the problem hadn't been raised before, that I recall anyway! ;-) Pete

You'll only find Lua controls for assignment in the "normal" controls lists. The "direct to calibration" obviously isn't appropriate -- that's the last thing you want -- and the third is writing to offsets, again which you don't want. So it becomes obvious, doesn't it? ;-) BTW I confirm there's an oddity assigning LuaValue on the right-hand side. I'm investigating that now. It'll be fixed in the next update, hopefully within a week else Im on holidays. Pete

Don't you ever update your FSUIPC? The PMDG737NGX facilities were released back in early April. We're up to 4.84 now. You must be using a really out-of-date and unsupported version! Pete

Yes, very recent. I did it after I was clobbered by a change to tailwind after starting my takeoff roll. I am using Aivalsoft's EFB with its Data Provider set to synchronize the time in FSX to UTC. It seems that sometimes when the scenery refresh is forced by a time change, so is the weather mode. It is something you might not notice in the air with FSUIPC's wind smoothing enabled, and as I say, within minutes AS will have restored Global mode in any case. But I don't have wind smoothing enabled on the ground (so that weather program settings take effect more quickly). Sorry it came as a surprise. I didn't think anyone would notice! Regards Pete

It only does this with ActiveSky when ActiveSky is set to Direct Weather Control (DWC) mode, because, although ActiveSky WILL restore global mode when it next refreshes the weather, that can take minutes and meanwhile the weather goes all wrong because of the mode change -- with disastrous consequences sometimes. If you want to use the weather dialogues in FSX, or Prepar3D, don't also run AS in DWC mode, or turn it off beforehand. Just terminating AS isn't any good because FSUIPC doesn't really know whether it is still running or not. FSUIPC certainly doesn't do this for REX or FSRealLite because it isn't told when they are in DWC mode. Pete

No. FSUIPC is not aware of what macros exist until they are called. All it has is a numbered list of macro filenames, You can read that in the INI file. Then you'd have to read the macro file and scan the macro names, same as FSUIPC has to do in any case when you access one. Pete

Why are you using the range settings? Why not assign in the normal manner on the left hand side? Are you using different ranges for different things? I'll have to check but i think the axis value may only be passed as a parameter when assigning as an axis, not a control. Please first update to version 4.84 so you are up-to-date and supported. Then try to do it as originally suggested. I'll check into the matter of the Luavalue assignment not sticking in the range assignment separately, but I'd like to know what you are using the part for. Pete

What would be the application? WideFS is really just a way of extending the FSUIPC application interface over a Network. What FSUIPC applications are there running on an iPad? I shouldn't think there were any. Are you thinking of writing some? Regards Pete

There's a section in the user guide on calibrating flaps in FSUIPC. Pete

There are both mouse look and mouse move facilities in FSUIPC. See the checkboxes on the "Miscellaneous" tab. You can still use the space bar but it is more convenient to either assign to FSUIPC's mouse controls, or just to use the centre mouse button (wheel) to enable the 'look' mode. This is all covered in the documentation. just search on the word "mouse". Pete

It looks like it is designed to transfer the changes in the SB3 offset to FSInn via XML variables -- L:Vars I assume. It actually mentions that in some places, look: 859Mode: XML L:VAR, Transponder mode 0=Standby, 1=Normal 859ID: XML L:VAR, Transponder ident pressed, 0=Not pressed, 1=Pressed 859ATCInd: XML L:VAR, 0=No interrogation from ATC, 1= interrogation from ATC 859VFRMode: (optional), XML L:VAR, 0=IFR,1=VFR, I assume this XML stuff is in FSCopilot or some gauge added into aircraft for FSInn/FSCopilot? I don't know what these are though: BOOL32 named var as adopted by FSInn FSCOPILOT_TRANSPONDER_MODE, BOOL32 named var transponder is client, Transponder mode 0=Standby, 1=Normal, 2=Ident FSCOPILOT_INN_MODE, BOOL32 named var transponder is client, 1=FSInn running, 0=FSinn not running[/CODE] To be honest, most of that you quoted doesn't really make sense to me, except of course the first part which is the SB3 transponder interface in FS9. No, I think you are misinterpreting this. I'm pretty sure that neither FSInn nor FSCopilot use FSUIPC (and therefore not WideFS either). They use some other variables, maybe L:Vars, for this stuff. Have you tried logging the L:Vars? [CODE]For testing purposes I logged the 0x7B91 offset and I see, that's correctly set by the controls and that's transported via WideFS to the second PC running FSInn. It really looks like, that FSInn in the 64bit environment now doesn't react on this offset any more.[/CODE] I don't think it does in any case. it is converted by SB3gaugebridge into XML or other variables supported by the FSInn transponder gauge. I think 64-bits is confusing you, I really doubt that has anything at all to do with it. It is more likely you have not installed the requisite gauge or it is not compatible with FSX. Pete

Ah, the Squawkbox ones. SB4 for sure, isn't using FSUIPC. With SB4 they provided SimConnect supported "client data" values for this, so all i did was map the offsets to the SB4 client data. I don't know what FSInn did, if anything, for FSX. Isn't there anything in their website or their documentation about it? No idea what that does. I assume it's reading offsets and writing to FSInn's tranponder control gauge? Do you mean to say the FSX FSInn is identical to the FS9 one? That hardly seems possible. I don't think 64- vs 32- bit will have anything to do with it. All this is 32-bit software no matter what the Operating System. Seems more likely that the SB3gaugebridge, whatever it does, doesn't work in the FSX environment, or with the FSX version of FSInn. You need info from FSInn about how it works. And where did SB3GaugeBridge come from and why is it related to FSInn? Regards Pete

I don't use this software (neither FSInn nor Squawkbox), but i'm curious to know what mechanism you used on FS9 for the transponder mode. I know Squawkbox 3 used offsets and I carried them on into fSX and automatically operated the transponder mode using the Simconnect facility SB4 implemented for this. But I don't know how FSInn does it -- is FSInn the same in this on both FS9 and FSX? Pete

Sorry, I've no idea. What is SFP2? And surely, in any case, it depends how you want to use your MCP. -- how much you need or want to reprogram it. The software supplied by VRi drives it correctly for many aircraft, I'm sure. And certainly you don't need VSPE if you are NOT uing any VRi software, but programming it all in FSUIPC via Lua or other programs. You might be better asking in the VRInsight support forum. I don't actually use VRi stuff myself. Regards Pete

Have you checked you have the right number? It seems most unlikely that PMDG are re-using many in the initial range from 65536- upwards. Nearly all of the first few hundred are already allocated. Here, I've checked for you. You have it all wrong. These are the definitions: So the battery switch is 69632 + 1 = 69637. The starting value they are using is well above the FS values, at 65536 + 4096!!! Please do read these things more carefully. I shouldn't need to do this for you! Pete

You seem to have missed some steps out. What do you do between 3 and 4? Having sleected a key you have to ASSIGN to "<custom contro>" and give the number you compute -- i.e. 65537. Okay out. Is that what you did? If not why not, and why not tell me what you did? Additionally, I supect that this control is not a "toggle control", but a proper switch needing a parameter, like 1 for "ON" and 0 for "OFF". Did you provide a parameter? These are getting to be questions for PMDG support not mine. I cannot support PMDG product -- s I don't know what all their controls do. I don't even use any PMDG products! Pete

They are published by PMDG, not me. I mention this in my list of PMDG 737NG offsets. Did you miss that as well? Here: It is a bit of a waste of time me writing all this stuff when folks don't bother to read it :sad:. evt files are merely text lists of named custom events, and are described in the FSUIPC Advanced User's guide (in the section "Add-on Custom Events" and easily found by searching on evt). But i don't know of any such events provided by PMDG in their 737NGX. In that thread I did say "If they are named custom events". Have you got information on some? As far as I'm aware they expect everyone to use the control numbers, not named events. Please do refer to documentation supplied. Pete

As in the User Guide. Did you not find this paragraph in the section on assigning controls? What do you need an example of? A number? e.g. 65667. That's a nuber in the correct range. I don't understand your problem. Pete

Sorry, there are no inputs provided specifically by FSUIPC. You must use the special control numbers added by PMDG -- see their file for the list. You can assign in FSUIPC to custom controls by number, as documented. What do you mean by "eventlogs"? Where are you reading? Regards Pete

It is published! Where have you been? The facility and documentation was built into version 4.82 soon after that thread you refer to. You really need to check the subforums here, especially the Updated Modules one in Download Links. The full list was included several months ago and has been included in every release since. The documentation is now installed in your FSUIPC Documents folder by the version 4.84 installer. Note that the earliest supported version for FSX is actually 4.84 so you should have installed it already. Pete