Pete Dowson

The offset 04F4 is dealt with by the drop-down FSUIPC control called "PM GC controls (by param)", or very similar. It is one of the additions listed in the Advanced Users guide. Why are you looking in the SDK? That is for programmers. You say you are not a programmer, so why look there? It is the parameter, so it goes in the box where is clearly says "parameter". I don't understand why this isn't obvious? If you go out of your way to make it more complicated, by choosing to use Hexadecimal offsets like x04F4, instead of the additional PM control names especially provided and documented for you, then you would expect the parameters to also be presented in hexadecimal. The values x0086 and x0087 are 134 and 135 in decimal. According to the PM documentation those operate the First Officer's side, not the Captain's side (it says "Add 100 for First Officer") -- so they are obviously 34 and 35 but with the 100 added. Regards Pete

No, but it would be easy to do with a Lua plug-in --just three lines, by the sound of it. You could call it "programming", but it is a lot easier than messing with some of the Button 'programming' tricks. Something like ipc.writeUB(, ) ipc.sleep(5000) ipc.writeUB(, ) Save that as, say, "MyLight.lua", and assign the switch to "lua mylight" in the drop-down. Regards Pete

There's no difference between "free" and "paid for" (really "unregistered" and "registered", respectively), except accessibility to options. Yes, that's what I assumed. If this "mode switch" on the Saitek does change the button numbers it submits, then that is done already -- unless that makes button numbers in execess of 31 (or 32 if you count from 1). FSUIPC uses the interface in Windows which only supports 32 buttons per device. DirectInput can accept up to 64. If the mode switch is merely another button, or selection of buttons, then you can still do the same thing but then it involves "conditionals" in FSUIPC -- programmed only in the INI file, by editing. This is described in the Advanced Users guide. Erthe mouse macro facilities do extend what can be done with FSUIPC, but you seem to have made a big jump somewhere here. The assorted FS autopilot values, the ones you mention, can be changed by standard controls, assignable directly in FSUIPC. The "mouse macros" tend only to be needed for add-on aircraft which ignore the FS values and do their own thing. I don't have a "route". At least nothing you'd recognise. i use Project Magenta, no add-on panels, no default panels, just 8 networked PCs. Regards Pete

None of those are simulated in FS 2004 as far as I know. Do you know different? Because FSUIPC can only present information actually present in FS. Of course. It does say that, and the title is "FSUIPC4 ...". The overhead in the default 737 for FS2004? The so-called "overhead" only contains 6 toggle switches, a simplified fuel switch (for crossfeed only), and two incorrect starter switches. Where are you looking? Add-on aircraft, like those from PMDG, may implement the other systems more adequately, but their values are not necessarily accessible, and certainly not identifiable, to FSUIPC. Regards Pete

I couldn't esily find what you are trying to say in the above mishmash. I've extracted this bit, though: If the buttons work, they work. If you Airbus doesn't work, there's something set in FS which is preventing it, or, more likely perhaps, considering the airbus is a fly-by-Wire aircraft, you have it in a mode where direct trimming by hand is not allowed. Since the PFC controls are only doing the same sort of thing as you would do by using the keyboard -- i.e. incrementing or decrementing the trim value (the elevator trim is 1 and 7 on the number Pad) -- why not check that method too? Regards Pete

Hmm. I'll have a look -- but i don't think the changes i made can have influenced that. The randomisation of variance and turbulence would still be, er, randomised. Maybe it's related to the accuracy (or rather inaccuracy) of the FS timer value I'm using now (probably only updated once per Frame), compared to the Windows tick time. I doubt it but I'll look anyway. Yes. I don't take facilities out. Well, not often! . I just haven't documented it yet because I was waiting for your feedback. I'll add the documentation for it to the next update. Regards Pete

You can use all three with or without FSUIPC. Like FSUIPC, FS supports whatever game controls are connected and recognised in Windows. FSUIPC is not a joystick or game device controller, it merely uses Windows the same as FS does. Regards Pete

Which version of FS? Before FSX none of these were simulated as far as I can tell. In FSX the others are hardly simulated. There's no readout of the APU EGT nor fuel temperature supplied. I can't see any mention of "duct pressure" -- is there another name for that? But in FSUIPC4, as documented in the SDK, all the pressurisation values are included -- didn't you do a search? Offsets 0318-0328. Pete

Probably not, depending upon whether the buttons looks like different buttons in different "shift states". FSUIPC reads buttons from Windows, so it gets them via the drivers you have installed. If Windows "Game Controllers" can recognise them all separately, then so can FSUIPC -- up to 32 buttons per joystick. Two answers to that part: 1. As above, if they look like different buttons, and fall into to first 32, yes, because they look distinct. OR 2. FSUIPC does allow any amount of complex button functionality, by either the use of "conditional" actions -- actions dependent upon other buttons, or flags set/cleared by other buttons, or even upon values read from FS (representing states like "on ground" or "over 50 knots" etc). On top of this you can have buttons instigating execution of little Plug-In sequences programmed in "Lua" (a popular game parameter programming language). But all of the things you can do in (2) are relatively complex, and done by editing files with parameters or program lines, not from simple assignment as in (1). I don't know the Saitek programming software, so i couldn't say whether ambitious use of FSUIPC would be more or less of a nightmare. But you can do all sorts of clever things with Lua plug-ins if that is what you want to do. However, that said, I'm not aware of any normal controls which will automatically set specific autopilot and autothrottle values -- normally you would either use a rotary dial (inc one way, dec the other), or a button or lever to increment and decrement, same as on the keyboard. Why not download and install FSUIPC in any case and peruse the documentation. I'm sorry, you can't actually try the things you mention before purchase, but you can most certainly read all about them and make up your own mind whether it looks scarey or not. Maybe you can then ask more constructive questions afterwards? Regards Pete

Buttons are only "captured" in FSUIPC in any case, the same, presumably, as FS2Crew would be doing. Why would it think they don't exist? Sorry, that doesn't make any sense. There's no "hex code" passed, and where would it come from and go to? There are two ways of getting button presses in Windows -- direct using the Windows "joy" API, which is what FSUIPC uses, and DirectInput (part of DX) which FS and most newer programs use. There are no facilities in FSUIPC for it to emulate real joystick buttons through Windows I'm afraid -- you need a real USB or GamePOrt device for that. If your buttons are on a standard joystick recognised by FS and Windows, then the question you need to ask (of FS2Crew) is why their program can't see them. How is it looking for them? Regards Pete

Oh dear. :-( When you click the Add-Ons then FSUIPC, the main tab, the one that tells you about FSUIPC, with the version number on, the one actually labelled "About", is also the one with the Window options! If you look carefully in the FSX Modules folder you will find a User guide PDF. It has been provided especially to help you in the unusual circumstances that you cannot see the options in front of you. Please look at that. It has documentation for this stuff, even with pictures showing the different Tab pages and describing options such as the one you seem to be blind to. There's even a Contents page, listing "Message Window Options" amongst its subjects, along with a page number to go to! Regards Pete

Aha! So, you've sorted it -- 4 lines = 1000, just what you wanted, no? Regards Pete

Registration is not actually necessary for the option you want -- it is on the first FSUIPC option tab you see when you go to the FSUIPC options via the Add-Ons menu. Regards Pete

Versdion 4.50 is the oldest currently supported version. Hmmm. No idea what that is, then. What changed two months ago? You need to track that down. this is enabling turbulence in FSX, or in FSUIPC? Have you tried disabling turbulence in FSUIPC? There are two turbulence sources -- cloud and wind. You might want to disable both. Normal turbulence effects should not screw up any of those things except when they are fairly extreme -- even real aircraft don't react kindly to extreme turbulence. You'd need to fly above or below such regions. Regards Pete

Two points there: 1. Advdisplay doesn't run on a client -- it's a DLL which used to be supported, but only on the FS PC, in the Modules folder. maybe you are thinking of "ShowText", the little display program provided inside the Advdisplay ZIP file? 2. AdvDisplay itself is not supported any more. For displays on the FS window you use the built-in window facilities provided via FSUIPC. "Latest version" is almost meaningless. Please ALWAYS quote version numbers. I've had folks say "latest" and they were using a year-old version -- the "latest one they'd seen"! You surely don't have Advdisplay.DLL installed in any case? It doesn't work on FSX. If you mean the FSUIPC window, it's one of the options on the FSUIPC first option screen, the one also showing the VERSION NUMBER! ;-) The window control facilities are explained near the front of the FSUIPC User Guide. Please peruse that some time, it does explain all of FSUIPC's options. Regards Pete

Instead of, what, 500 were you expecting? Okay. sounds like they've implemented control acceleration, same as FS does if you hold a switch with a mouse instead of just clicking it. I assume you've mis-typed that. you mean 300 feet each time? 5 x 300? Why not simply reduce the number of entries proportionally? If you are getting 1500 and want 1000, reduce to 2/3rds. Of course 1000 isn't a multiple of 300 so you'd have to use 3 to get close then use your 100 dial. This is on FSX, isn't it? You might want to investigate the new facilities in FSUIPC for manipulating gauges using "L:vars" (Local gauge named variables). You never know, PMDG might be using those to deal with the altitude on their MCP? Pete

No, that can only appear if you go to the Add-Ons menu and select FSUIPC. It IS running! Else you'd not be able to get the Menu!!!! you are posting in an Announcement. Please, if you have any more questions, post in the main forum. I'm locking this one now. I obviously forgot to do it before. Pete

sorry, I don't understand what you are trying to say. If the SimConnect variables which FSUIPC reads are changed, then SimConnect will notify those and the values will be readable. You would apply to me in writing, by email, but such codes are not needed any more, so don't bother. Pete

You'd need to ask PMDG. They do have a support forum I think? I expect the PMDG programs talk to each other. If they do this using "L:variables" (FS Local Gauge named variables) then you may be able to identify them and influence them using the new Lvar facilities offered in the latest version (4.50) of FSUIPC4. Regards Pete

Always 2 knots and 2 degrees? I've not heard of anything like that, though FS's turbulence is not terrible well implemented. Are you using FSUIPC at all? A lot of work was done within the FSUIPC wind smoothing facilities to get realistic turbulence emulated, and the algorithm used was well tested with PMDG aircraft, which appear rather sensitive to such things. Sounds like you are talking about default FSX weather settings. There are well known errors in the wind implementation in FSX -- carried forward from FS9, in fact, but probably more noticeable because FSUIPC's smoothing did work 100% in FS9, whereas it can't quite achieve that in FSX. I can only suggest investing in FSUIPC4 and using the wind smoothing facilities. They seem to have been well received. Regards Pete

There's no difference between FS9 and FSX in that area. And do the buttons actually work -- i.e. are they detected, shown in the "Test" tab when operated? And if the are shown okay, check that they are not shown as being assigned in FSUIPC. All buttons and switches can optionally be programmed in FSUIPC instead, and this takes precedence. No. That is for calibrating trim wheels and steering tillers -- axes, not buttons. You could check that tab, make sure they are all disabled. But do also check the trim sensitivity setting, on the Console page. Maybe you have set that very low, or too high? It defaults to 256, which is about right. Version 4.40 of FSUIPC is no longer supported. The minimum current version is 4.50. Regards Pete

Well, the T8 shouldn't have changed -- T8's and RP48's are assigned different groups of joystick numbers in FSUIPC. No, it hasn't come up before. And, of course, It would not always result in everything changing -- that's just bad luck. If the existing units were all in the USB chain/sequence before the last one you added, then I think none of the existing ones would have changed. Seems your setup was the reverse -- if you are using a hub for them all, maybe they are all plugged in starting at the "wrong" end in this respect. Regards Pete

I'm not sure anyone here will be able to help. I think you'll be better off in one of the SimConnect forums? Try http://www.fsdeveloper.com/forum/forumdisplay.php?f=60 http://forums1.avsim.net/index.php?showforum=255 Regards Pete

Are these all the same type of module? If not, you have a real big puzzle there as I'm sure they are all ennumerated separately, by type. If they all changed it is probable that the new connection happened to be the first in the USB scanning system, however that works. You'd probably needed really to move all the others "up" one and put the new one at the end . The problem is, of course, you don't know which socket is which in terms of how Windows counts them. This sort of query would be best addressed to GoFlight really, as they must presumably know about USB and their driver. FSUIPC can only deal with the identities it is provided, and if the new number 1 is number 1, then it is number 1. And so on. How can it know that the new number 1 is supposed to be number 4 or whatever? There's absolutely no way to differentiate like modules apart from their identity as supplied by their driver. Pete

Wasn't the example and so on clear in the document? The format 1=decrease=RX3880*X5300 is the SINGLE line format. The fact that it is complete in that line stops FSUIPC looking for any more! You need 1=decrease 1.1=RX3880*X5300 1.2=RX3880*X5300 1.3=RX3880*X5300 1.4=RX3880*X5300 1.5=RX3880*X5300 Pete