Pete Dowson

I moved this to the Support Forum because it likely won't get noticed in User Contributions, which is the subforum for folks providing advice and goodies, not asdking for help! ;-) Yes for NAV radios, which is your question, no for COM radios which is your example. NAV1 signal detection is indicated by bit 3 in offset 0C4D being zero, and by the signal strength in offset 0C52. There are similar offsets for NAV2. Check the FSUIPC offsets lists in the SDK. Regards Pete

No. You created a Profile called "Lufthansa". All the aircraft you add to that profile will be listed under that Profile because you are adding them to it using its name! You should really have thought of a more appropriate name for your Profile, like "TwinJet" or "737" or "PMDG737", whichever more appropriately defines the sort of assignments and calibrations you made for that Profile. Having a "Lufthansa" profile sounds like there are a set of special assignments which suit all Lufthansa aircraft no matter what type they are! If you want to change that now you'll need to edit the INI file, changing "Lufthansa" to something more appropriate in all the Section headings ending in .Lufthansa] You merely need to set ShortAircraftNameOk=substring in the INI file, before running FSX, and also edit the aircraft name(s) in the [Profile. ...] lists to some part of the whole name which is common to all liveries. FSUIPC really isn't clever enough to know what part of the name refers to the aircraft type or make and what only refers to how it is painted (how could it?). If the name is "737" it'll match all names containing "737". If it is "PMDG" it'll match all PMDG aircraft. If it is "PMDG737" ... well, you should get the idea by now. Pete

I'm sorry but I cannot possibly support such an old version of FSUIPC. If you want support please update. The earliest supported FSUIPC4 is 4.70, and there's an interim update 4.722 available in the Download Links subforum. Pete

Without some change in a file somewhere, or a hardware fault, things don't suddenly stop working on their own. Something has changed or got messed up. It is usually the DLL.XML file which tells SimConnect what to load. See if FSUIPC4 is actually loading -- if it is there will be a new Log file created when you run FSX. If there isn't one then your DLL.XML file is corrupted. If FSUIPC4 is actually loading but the menu isn't created then you have a more serious problem, possibly a windows side-by-side error with SimConnect. In this case show me the FSUIPC4.LOG file. Regards Pete

Unless you have a hardware fault, perhaps memory chips or hard disk, there is nothing which will change whether Simconnect works and shows the menu except you installing or uninstalling things or changing files. You really should update your FSX in any case. The original version had lots of bugs. Regards Pete

The best way to use FSUIPC like this is to switch to Profiles. Go into the INI file and change "UseProfiles=No" to Yes. Also change "ShortAircraftNameOk=No" to Substring. The latter enables you to abbreviate names to get automatic assignment for aircraft with the sames names bar liveries. Also update the the latest FSUIPC version from the Download Links subforum. There's an additional facility now which enables you to build a new Profile from an old one, without messing about in the INI file. I'll probably change the defaults for FSUIPC in the next major release, to assume Profiles and short aircraft names initially if the user hasn't yet embarked upon aircraft-specific settings. Regards Pete

The INI file appears to be incomplete. These parts are wrong: [Axes.] 0=AX,1,D,0,1,0,0 1=AY,1,D,0,2,0,0 2=AZ,256,D,4,0,0,0 3=AV,130,F,65706,0,0,0 4=AS,256,D,22,0,0,0 5=BX,256,D,7,0,0,0 6=BY,256,F,0,66388,0,0 7=BR,256,D,3,0,0,0 [Profile.] 1= Delete those lines, because you cannot have sections like this without names after the '.' character. It maybe these lines which are messing things up. This may have been the result of somehow entering a profile name with only [ ] characters, a bug fixed recently as listed in the update notes as follows: 15. The use of [ and ] characters in Profile names has always been disallowed (they are replaced by ( and ) respectively), but if the 'new profile' entry contained only [ and ] characters an invalid null profile section would have been produced. This is now fixed. Download and install the current interim version (4.722 or later) from the Download Links subforum just in case this happens again. Regards Pete

Yes. For a simple flag just use, say, a byte at offset 66C0. In Lua set it by ipc.wruteUB(0x66C0, 0) or ipc.wruteUB(0x66C0, 1) and test is as an offset condition in the [buttons] section be preceding the usual button assignment by B66C0=0 or B66C0=1 B is for Byte. U is for Unsigned. Pete

Not at present, but it wouldn't be a bad idea to add such a facility! Great idea. I'll do it next week! No. I really can't see that being practical. Each Lua thread has its own set of flags. Linking to one of them would be quite complex and I'm not sure how you'd record that within the 32 bits available for button encoding. Well, I don't know what route you are following -- really any type of compound or conditional button programming can be done by straight Lua scripting without complex button definitions. But the main thing which can relate Lua capabilities to button conditions is their access to FSUIPC offsets. Your Lua can write to offsets which are then defined as conditions on button assignments. You can use the user offsets 0x66C0 to 0x66FF. Correct. The IAS/Mach display is local to the MCP gauge code. Whether the autothottle is following the IAS or the Mach value is, however, dependent on A/T settings -- IAS hold or Mach hold. Those two are certainly separate and will therefore tell you which to display. The problem really only arises when the A/T is NOT engaged and you want to adjust or display a mach or IAS value which isn't actually dictating speed. Really that can all be done locally to the MCP without the FS simulation being involved. If you think that way it makes it easier. Regards Pete

Ah, that was more luck than skill! ;-0 Pete

Can you clarify what you mean by that? Do you mean that if you go into the World -- Time & Season menu and set a time, when you okay out of the menu, FS will adjust it by 4 hours? If so are you sure it isn't to do with time zones? GMT and your Local Time, in Houston, will differ by several hours. There's nothing I know which will change the time to anything but the current time -- and the only programs I know that do that are EFB (as an option) and FS Real Time (again, only if you've selected the option). But there might be others. For instance, I don't know anything about on-line flying, and I see you list FSINN. Are you sure it isn't a function of FSINN or its partner FSCoPilot? Obviously, to eliminate something doing it through FSUIPC (like FSRealTime), just try renaming FSUIPC4.DLL and loading FSX so it doesn't run. As Andy says, there's nothing in FSUIPC itself touching the time unless you use its time sync facility, and that normally only adjusts seconds -- minutes optionally, at most. Regards Pete

If you think you could use the [buttons] assignments matching those ButtonScreens, you could try asking the user who did them. Not sure if he would still have the same layout. Here's the forum thread about it: Button Screen I note it's dated 2009, so maybe it's a little late, but you could try sending him a message. Regards Pete

Yes, I'm afraid there's no solution to that except to re-make all the macros. The recompiled code only has to have the entry points moved one byte and they obviously can't call the same code. You probably need to note the DLL or GAU version or date with them. They shouldn't do any harm used with the wrong version -- that's what the check bytes are for in the macro encoding. FSUIPC checks that the bytes at the place it calls are the same, and if not it won't call the code. Regards Pete

I thought they might do. I just haven't got my development PC with the reference documents on it powered up at present so I wasn't 100% sure. I also don't know which files I read for what off-hand. Most of that code dates back many years. I'd have to look up the code. I don't know what the application for having the country provided would be, but i don't make changes to MakeRunways without good reason. Bolting on more and more bits is making it a bit of a nightmare, gradually. The newest part, that making the XML file, would probably be easy enough to change, though -- it already contains airport name and city name. I'll wait to see what the OP wants it for. Regards Pete

Have you assigned all the buttons in FSUIPC? The definition of the client button screen just determines what it looks like on screen. All those functions need assigning in FSUIPC, in the Buttons and Switches tab. Don't forget, the example in the WideFS documentation was just that, an example. The parameters were provided to show how that part is done, but it is only half the job. I use ButtonScreens as well, with touchscreens (better than a mouse), but mine look nothing like that one. Each user does his own thing. I thought you realised that. This is why it is so flexible. Pete

Not at present, unless you want to decode that from the ICAO identifier. I'm not sure if it is retrievable from the particular scenery files I'm processing. Regards Pete

Whether it's a GAU or a DLL which is called isn't your choice, but depends only on where the mouse click leads to in the code. If the same DLL is used for both MCPs then they will probably be calling different entry points, so you should be able to create macros for both in the same Macro file -- just give them different names. Regards Pete

Sorry, that isn't a message from my program. You really need to ask the support for the program reporting that. One thing, though. If you let FS install into the "program files" folder then it is quite likely that the FSUIPC application you are trying to use cannot access FS -- Win7 protects all Program Files folders. BTW you need to run both FS and the application at the same privilege level -- either both normally or both "as administrator" so they can talk to each other. You cannot run one "as administrator" and not the other -- different privilege levels cannot communicate. Regards Pete

Ah, sorry. I missed that. It shouldn't be a problem -- I'll have a look. [LATER] Okay, I'll increase it to 32 max (1-32). Only in FSUIPC4 though, not FSUIPC3. Look out for version 4.722 later today. [LATER AGAIN] 4.722 is uploaded. 4.721 is dead. ;-) Regards Pete

I've edited it for you. If you mean number of macros per file, it was until recently limited more by the actual file size -- until recent updates a large enough MCRO file (over 16k, approaching 32k) caused a memory problem in FSUIPC which stopped everything else working. That was fixed in one of the recent interim updates. The inbuilt limits are 255 files, each with up to 1023 macro lines. That's to do with internal reference encoding. The whole system was bolted into the general joystick button assignment and messaging system which only gives room for 32-bits for the encoded assignment. This is defined by the Windows messaging system for "WM_COMMAND" which has a 32-bit "wParam" and a 32-bit "lParam". The wParam holds the command encoding and the lParam the parameter value. In this I have to allow for Lua calls, Macro calls, FSUIPC added controls, Offset controls, and of course all of the possible FS and add-on controls. I'd hoped it would be enough forever! ;-) Regards Pete

Perhaps you could post this with a suitable title in the User Contributions subforum, please, so it doesn't get lost? Thanks! Pete

Excellent! Do you think you could re-post this with a suitable thread title in the User Contributions subforum? That way it will remain a reference. If it's only here it will eventually scroll away into the distance! Thanks, Pete

The format is described in the Advanced User's guide -- those are all to key presses -- but it is easier to simply do the assignments in the FSUIPC options dialogue. Regards Pete

do you mean this? [ButtonScreen] Size=13,5 Colour4=221,250,182 Colour5=235,250,160 Colour6=238,183,172 Colour8=180,44,2 Colour7=26,122,144 Colour9=231,155,17 Title1="SYSTEMS MENU" Title2="AUTOPILOT MENU" Title3="NAVCOM MENU" Title4="G1000 PRIMARY FLIGHT DISPLAY" Title5="G1000 MULTI-FUNCTION DISPLAY" Title6="GPS" Title7="MISC" ===========PAGE 1 SYSTEMS========== 0=7G0r"SYSTEMS" 1=Tl"Battery\rMaster" 2=T"Alternator\rMaster" 3=T"Avionics\rMaster" 4=T"Pitot\rHeat" 5=T"Fuel\rPump" 6=Bl"Engine 1\rAuto start" 7=B"Engine 2\rAuto start" 8=B"Engine 3\rAuto start" 9=B"Engine 4\rAuto start" 10=B"Engine\rAuto\rShutdown" 11=Trl"Parking\rBrake" 12=4G325l"GPS" 13=4G65r"AUTO\rPILOT" 14=6Blt"Magneto\rOFF" 15=6Bt"Magneto\rLeft" 16=6Bt"Magneto\rRight" 17=6Bt"Magneto\rBoth" 18=6Bt"GA Engine\rStarter" 19=5Btl"APU\rOFF" 20=5Bt"APU\rON" 21=5Btr"APU Fire\rExtinguisher" 22=Bt" " 23=Btl"Cowl Flaps\rOpen" 24=Btlr"Gear\rUp" 25=4G390l"Misc" 26=4G130r"NAV\rCOM" 27=Ttbl"Panel\rLights" 28=Ttb"Beacon" 29=Ttb"Landing\rLight" 30=Ttb"Nav\rLights" 31=Ttb"Strobe\rLight" 32=Btl"Anti-ice\rOFF" 33=Btr"Anti-ice\rON" " 34=Ttr"No\rSmoking" 35=B" " 36=Blb"Cowl Flaps\rClose" 37=Blbr"Gear\rDown" 38=U 39=4G195r"G1000\rPFD" 40=7Bl"Standard\r Barometer\rSetting" 41=6B"Barometer\r+" 42=6Br"Barometer\r-" 43=T"Prop\rSync" 44=T"Water\rRudder" 45=Bbl"Prop\rDe-ice" 46=Brb" " 47=Trb"Seat\rBelts" 48=B" " 49=B"Release\rTow\rLine" 50=B"Request\rTow\rPlane" 51=U 52=4G260r"G1000\rMFD"" 53=6Blt"Aileron trim\rLeft" 54=6Bt"Aileron trim\rRight" 55=6Bt"Rudder trim\rLeft" 56=6Btr"Rudder trim\rRight" 57=B" " 58=Tl"Door" 59=T"Jetway" 60=T"Pushback" 61=2B"P/B\rLeft" 62=2B"P/B\rRight" 63=B"Call\rFuel\rTruck" 64=U ==========PAGE 2 AUTOPILOT========= 65=4G0r"SYSTEMS"" 66=Tl"A/P\rMaster" 67=T"Heading\rHold" 68=T"Nav\rHold" 69=T"Apr" 70=T"Back\rCourse" 71=T"Alt\rHold" 72=T"A/T" 73=T"Speed\rHold" 74=T"Yaw\rDamper" 75=T"Flight\rDirector" 76=Tr"Loc\rHold" 77=4G325l"GPS" 78=7G65r"AUTO\rPILOT" 79=Bl"Nav/GPS" 80=5B"Heading\rBug +" 81=5B"Obs1\r +" 82=5B"Obs2\r +" 83=5B"ADF\r+" 84=5B"Alt\r+" 85=5B"TOGA " 86=5B"Speed\r+ " 87=5B"Vert Speed\r+" 88=5B"Spoilers\rArm " 89=5Br"Autobrake\rIncrease " 90=4G390l"Misc" 91=4G130r"NAV\rCOM" 92=Tbl" " 93=5Bb"Heading\rBug -" 94=5Bb"Obs1\r- 95=5Bb"Obs2\r-" 96=5Bb"ADF\r-" 97=5Bb"Alt\r-" 98=5Bb" " 99=5Bb"Speed\r-" 100=5Bb"Vert Speed\r-" 101=5Bb"Spoilers\rOFF" 102=5Bb"Autobrake\rDecrease" 103=U 104=4G195r"G1000\rPFD" 105=Bl" " 106=B" " 107=B" " 108=B" " 109=B" " 110=B" " 111=B" " 112=B" " 113=B" " 114=B" " 115=B" " 116=U 117=4G260r"G1000\rMFD" 118=Bl" " 119=B" " 120=B" " 121=B" " 122=B" " 123=B" " 124=B" " 125=B" " 126=B" " 127=B" " 128=B" " 129=U ===========PAGE 3 NAVCOM=========== 130=4G0r"SYSTEMS" 131=5Bl"Com 1\r Int\r+" 132=5Br"Com 1\rDec\r+" 133=5B"Com 2\r Int\r+" 134=5Br"Com 2\rDec\r+" 135=7Br"Com 1\rSwap" 136=6Bl"ADF\r100s\r+" 137=6B"ADF\r10s\r+" 138=6B"ADF\r1s\r+" 139=6B"ADF\r0.1s\r+" 140=7Bl"DME 1" 141=7Br"DME 2" 142=4G325l"GPS" 143=4G65r"AUTO\rPILOT" 144=5Bbl"Com 1\rInt\r-" 145=5Brb"Com 1\rDec\r-" 146=5Bb"Com 2\rInt\r- 147=5Bbr"Com 2\rDec\r-" 148=7Bbr"Com 2\rSwap" 149=6Bl"ADF\r100s\r-" 150=6B"ADF\r10s\r-" 151=6B"ADF\r1s\r-" 152=6B"ADF\r0.1s\r-" 153=Bl" " 154=Br" " 155=4G390l"Misc" 156=7G130r"NAV\rCOM" 157=1Bl"Nav 1\r Int\r+" 158=1Br"Nav 1\rDec\r+" 159=1B"Nav 2\r Int\r+" 160=1Br"Nav 2\rDec\r+" 161=7Br"Nav 1\rSwap" 162=6Bl"XPDR\r1000s\r+" 163=6B"XPDR\r100s\r+" 164=6B"XPDR\r10s\r+" 165=6B"XPDR\r1s\r+" 166=Bl" " 167=B" " 168=U 169=4G195r"G1000\rPFD" 170=1Bbl"Nav 1\r Int\r-" 171=1Brb"Nav 1\rDec\r-" 172=1Bb"Nav 2\r Int\r-" 173=1Brb"Nav 2\rDec\r-" 174=7Bbr"Nav 2\rSwap" 175=6Bbl"XPDR\r1000s\r-" 176=6Bb"XPDR\r100s\r-" 177=6Bb"XPDR\r10s\r-" 178=6Bb"XPDR\r1s\r-" 179=Bl" " 180=B" " 181=U 182=4G260r"G1000\rMFD" 183=2Bl"Com 1" 184=2B"Com 2" 185=T"Both" 186=T"Nav 1\rIdent" 187=T"Nav 2\rIdent" 188=T"MKR" 189=T"DME" 190=T"ADF" 191=2B"NAV/GPS" 192=Bl" " 193=B" " 194=U ========PAGE 4 G1000 PFD======== 195=4G0r"SYSTEMS" 196=Bl"Group Knob\rIncrease " 197=B"Group Knob\rDecrease" 198=U 199=U 200=U 201=U 202=U 203=U 204=U 205=B"Range\rZoom Out" 206=Br"Range\rZoom In" 207=4G325l"GPS" 208=4G65r"AUTO\rPILOT" 209=Bl"Page Knob\rIncrease" 210=B"Page Knob\rDecrease" 211=U 212=U 213=U 214=U 215=U 216=U 217=U 218=B"Direct" 219=Br"Menu" 220=4G390l"Misc" 221=4G130r"NAV\rCOM" 222=Bl"Cursor" 223=B" " 224=U 225=U 226=U 227=U 228=U 229=U 230=U 231=B"FPL" 232=B"PROC" 233=U 234=7G195r"G1000\rPFD" 235=6Btrl"Soft Key\r1" 236=Bb" " 237=U 238=U 239=U 240=U 241=U 242=U 243=U 244=Bb"CLR" 245=Bb"Enter" 246=U 247=4G260r"G1000\rMFD" 248=6Bl"Soft Key\r2" 249=6B"Soft Key\r3" 250=6B"Soft Key\r4" 251=6B"Soft Key\r5" 252=6B"Soft Key\r6" 253=6B"Soft Key\r7" 254=6B"Soft Key\r8" 255=6B"Soft Key\r9" 256=6B"Soft Key\r10" 257=6B"Soft Key\r11" 258=6B"Soft Key\r12" 259=U =========PAGE 5 G1000 MFD========== 260=4G0"SYSTEMS" 261=Bl"Group Knob\rIncrease " 262=B"Group Knob\rDecrease" 263=U 264=U 265=U 266=U 267=U 268=U 269=U 270=B"Range\rZoom Out" 271=Br"Range\rZoom In" 272=4G328l"GPS" 273=4G65"AUTO\rPILOT" 274=Bl"Page Knob\rIncrease" 275=B"Page Knob\rDecrease" 276=U 277=U 278=U 279=U 280=U 281=U 282=U 283=B"Direct" 284=Br"Menu" 285=4G394l"Misc" 286=4G130"NAV\rCOM" 287=Bl"Cursor" 288=B" " 289=U 290=U 291=U 292=U 293=U 294=U 295=U 296=B"FPL" 297=B"PROC" 298=U 299=4G195"G1000\rPFD" 300=1Btl"Soft Key\r1" 301=U 302=U 303=U 304=U 305=U 306=U 307=U 308=U 309=Bb"CLR" 310=Bb"Enter" 311=U 312=7G260"G1000\rMFD" 313=1Bl"Soft Key\r2" 314=1B"Soft Key\r3" 315=1B"Soft Key\r4" 316=1B"Soft Key\r5" 317=1B"Soft Key\r6" 318=1B"Soft Key\r7" 319=1B"Soft Key\r8" 320=1B"Soft Key\r9" 321=1B"Soft Key\r10" 322=1B"Soft Key\r11" 323=1B"Soft Key\r12" 324=U =============PAGE 6 GPS ============= 325=4G0r"SYSTEMS" 326=Bl"Group\rKnob\r-" 327=B"Group\rKnob\r+" 328=U 329=U 330=U 331=U 332=U 333=U 334=U 335=B"Zoom\rIn" 336=Br"Zoom\rOut" 337=7G325l"GPS" 338=4G65r"AUTO\rPILOT" 339=Bl"Page\rKnob\r- " 340=B"Page\rKnob\r+" 341=U 342=U 343=U 344=U 345=U 346=U 347=U 348=B" " 349=Br"Direct\rTo " 350=4G390l"Misc" 351=4G130r"NAV\rCOM" 352=Bl" " 353=B" " 354=U 355=U 356=U 357=U 358=U 359=U 360=U 361=B" " 362=Br"Menu" 363=U 364=4G195r"G1000\rPFD" 365=Bl" " 366=B" " 367=U 368=U 369=U 370=U 371=U 372=U 373=U 374=B"Cursor" 375=Br"Clear" 376=U 377=4G260r"G1000\rMFD" 378=Bl"PWR" 379=B" " 380=B" " 381=B" " 382=B"NRST" 383=B"OBS" 384=B"MSG" 385=B"FPL" 386=B"TERR" 387=B"PROC" 388=Br"Enter" 389=U =========PAGE 7 MISC ========= 390=4G0r"SYSTEMS" 391=Bl"" 392=B"" 393=B"" 394=B"" 395=B"" 396=B"" 397=B"" 398=B"" 399=B"" 400=B"" 401=Br"" 402=4G325l"GPS" 403=4G65r"AUTO\rPILOT" 404=Bl"" 405=B"" 406=B"" 407=B"" 408=B"" 409=B"" 410=B"" 411=B"" 412=B"" 413=B"" 414=Br"" 415=7G390l"Misc" 416=4G130r"NAV\rCOM" 417=Bl4G260"G1000\rMFD""" 418=B"" 419=B"" 420=B"" 421=B"" 422=B"" 423=B"" 424=B"" 425=B"" 426=B"" 427=Br"" 428=U 429=4G195b"G1000\rPFD" 430=4G260trb"G1000\rMFD" 431=B"" 432=B""

It is explained in the user guide. Rotaries alternately set the button input "on" then "off". To have each click do something you have to assign to both "press" and "release", not just one or the other. Pete