Pete Dowson

Yes, FSUIPC3 for FS9 and before is a different version to FSUIPC4. Please NEVER publish your Key, or else it will have to be made invalid. Pete

Your choice. In FSX (but not before) the rudder and tiller are separate. FSUIPC's specific tiller control (assigned in the "direct FSUIPC" mode) is a control added by FSUIPC way back before FSX came out with an actual steering tiller control. You can use the FSX version if you wish, and you can assign it in FSUIPC's FS control lists. FSUIPC's one actually use the FS rudder control "under the hood" The special arrangement in FSUIPC's, when both its tiller and the rudder are assigned and calibrated, is that the tiller has 100% control at 0 knots whilst the rudder has 100% at a set ground speed ("MaxSteerSpeed") which defaults to 60 knots. Between 0 and that speed one becomes gradually less effective and the other more effective. The intention here is to simulate more closely the change in the real effectiveness of these two controls, where the pilot actually uses only tiller at slow ground speeds, but on the take-off roll gradually needs to be using rudder. This is all documented in the FSUIPC User Guide, page 40 -- the boxed section. Pete

Well if they are all 8 bit then you would be able to read 64 of them in one go. Mind you, do check for performance impact on FS. The requests to the Gauges system have to be made in the main thread. Or did you mean that they all need 8-byte (64 bit) floating point accuracy? Surely not. The two you showed earlier were for a switch position, no? Anyway, I'll put it in when I'm home -- Monday or Tuesday. It'll be in interim update 4.952. Pete

It was the way you asked, which was not nice at all, and pretty much guaranteed to get an adverse reaction. If you peruse the messages here I try my best to help every one who asks. I will help if you would like to ask specific questions about things you don't understand, but I cannot explain someone else's program anyway. Just tell me what specifically about it is giving you problems. Maybe I can fathom it out, maybe not. It's just that I didn't write that program, I did assume, because it had been used by many others without my help, that it was explained in its thread. Did you look through the thread itself? Maybe your questions were already answered? Pete

FSUIPC can only offer those controls which are implemented. They are FS controls. You could try writing to the relevant FSUIPC offsets instead, using the Offset controls FSUIPC provides.. Pete

Well, a single read before the Process. Ah, you can't. It will only work on the user-assigned offsets, 6C00-6CFF, so 64 bytes.BUT it would be dead easy for me to add a facility to read/write values or different sizes and types, doing the double float conversion internally. For instance, if you know a value is an integer then provide it or ask for it as such. I can use the high word of the offset value for this in 0D6C. So, use the offset 0x0nnnn as now for the full 8-byte double, or: 0x1nnnn for 32-bit float 0x2nnnn for 32-bit signed integer (SD) 0x3nnnn for 32-bit unsigned integer (UD) 0x4nnnn for 16-bit signed integer (SW) 0x5nnnn for 16-bit unsigned integer (UW) 0x6nnnn for 8-bit signed integer (SB) 0x7nnnn for 8-bit unsigned integer (UB) Then you could fit up to 64 values in, depending on their types. Pete

Sounds about right. Process switch, queuing on FS's message list, forwarding to a thread in FSUIPC, message to the gauges system in FS to get the variable ID and then another to get the value. No reason why you shouldn't do multiple write write read sequences before the process, just use separate offsets each time. Didn't you try that? Would save multiple process swiches. As documented, the read is processed before continuing, it's not asynchronous. Pete

Yes, the offset must be one of those assigned for general user usage. Without access to my system at home I can't check whether 6D88/8 is aleady assigned, but even if not it might be one day. I'm trying to ensure no conflicts except those the user can resolve himself. Pete

I'm not at home now till Monday--answering this on my iPhone. No access to my dev tools, nor documents, but it is as documented. Put the offset for the result to the place first. Pete

You don't need to. Best to use the appropriate event, where FSUIPC reads it and calls you when it changes. Oh, you mean from a program, not a Lua plug-in. Sorry. No, not at present. Obviously it's possible, because that's pretty much what the Lua event is doing. But there's nothing like that for external programs. There's really nothing like it to base it on, either, so it it was implemented it would be all new code.When you say "rather inefficient and problematic", what's the problem part of it? And how many Lvars are you talking about? All at 100 mSEc intervals? Are these critically changing values? Pete

If you want a separate log for a Lua plug-in you need to enable that option in the Logging tab in FSUIPC options. Otherwise the logging gets merged into the normal FSUIPC4 log. This is a more normal need for Lua logging as it shows Lua actions in relation to, say, events, buttons or keys when they are also logged The main use of the Lua log lvars plug-in is to be able to identify correct Lvars, and the values needed in them, by actually seeing the changes logged in real time on screen. If all you wanted was a list of them, then all you needed to do was assign to FSUIPC's built-in List local panel variables control, in the assignment drop down. BTW the current version of FSUIPC is 4.95, not 4.495. You may find the interim update, 4.951, useful, as it annotates your INI file with control and key press decodes. Interim updates are provided in the Download Links sub forum, above. Pete

Is FSUIPC running? I.e Does the Add-Ons menu list FSUIPC? When you post a question here it helps if you state basic stuff like the simulator you are using: FS98, FS2000, FS2002, CFS1, CFS2, FS2004, FSX, FSX-SE and PeD are supported by one version of FSUIPC or another -- and also of course the version of FSUIPC. Pete

Sorry, I've never heard of anything called "Tornado Tigermeet 2001" and we certainly don't host any cockpits here. This is a support site for utilities FSUIPC and WideFS. Same with the other request you posted. I think you must be in the wrong Forum. And why add to an existing thread entitled "FSUIPC keeps asking me to register"? That makes no sense whatsoever! Pete

Yes, we think it should -- It does in a real Boeing! But originally you said other things were happening too, like gear going down and spoilers arming. Pete

A question for the PMDG Support Forum, then? Pete

No, sorry. However, I believe L-M are hard at work improving this whole area of P3D. Pete

Yes. Just checked default assignments involving G: G Gear toggle Shft+G tail wheel lock toggle Ctrl+G gear extend manually Ctl+Shft+G TOGA I think, but I'm not sure, that the user can choose the keys to be used for some things in the PMDG aircraft. Really, if PMDG is catching them they shouldn't also be passed on for FS to handle. FSUIPC doesn't allow that. (But it can't stop FS detecting buttons and axes). Pete

Ah, thanks Thomas. Yes that's very likely to be true. It SHOULD be implemented like that in both PMDG 777X and 737NGX. What seems more odd in the OPs original post is this: When I fly with PMDG 737 or 777 the gear keeps going down, A/P disengages, spoilers arm without operating any keys during flight. Now looking again at the Key assignments above I wonder if that Ctrl+Shft+G assignment might sometimes be seen as a Gear toggle There isn't an obvious candidate for arming spoilers though. Whilst this part: I found any key programmed with Elevator trim Dn will disengage the autopilot only with NGX. should be true also for Elevator trim Up, and for the 777X. Really I would recommend that he re-assigns using controls where possible, not keypresses. Without going into FS and PMDG assignments to check we can't tell what keypresses are assigned to do outside of FSUIPC. Pete

No you haven't. Not easy to attach some filetypes here. With text files it is best to simply paste their contents into your message. However, now you have worked it out, it does not matter. I don't need to see any log. Pete

Okay. What you posted doesn't tally with what you said earlier. Let's review what you said earlier: Now, first, when you say "key" I now must assume you really meant BUTTON! Second, you said you hadn't programmed anything else, only this one key or button. However, the INI file shows no KEY PRESSES assigned, but 5 BUTTONS for your NGX profile. Should I assume that was the complete file? If it is I don't understand what the point of your Saitek yoke is because you have no flight controls. Do you only fly using the keyboard, discarding the yoke? If you are using the yoke, then since it isn't assigned in your FSUIPC settings, I must assume that you still have controllers enabled in FS, I suspect that's where your conflicts are arising. Disable controllers in FS and re-test. You can't use both FSUIPC and FS for assignments to buttons and axes, they will conflict or add undesired actions . Going back to your INI file, the ONLY assignments there for the NGX are these, all for yoke buttons: [buttons.PMDG 737] 1=P0,14,K71,11 2=P0,4,K84,11 6=R0,2,C65607,0 7=R0,3,C65615,0 8=P0,1,K65,11 (BTW if you download FSUIPC 4.951 (from the Download Links subforum above), these sort of assignments will be decoded for you. Makes life a bit easier when checking things) So they send keypresses Ctrl+Shft+G, Ctrl+Shift+T and Ctrl+Shift+A, and controls Elev trim dn, and Elev trim up. Both of those controls are set to repeat if the button is held. The log shows that when you pressed the button assigned to Elev trim dn, and held it down, you got this: 112719 Button changed: bRef=0, Joy=0, Btn=3, Pressed 112719 [Buttons] 1=R0,3,C65615,0 112719 Repeating flag set: bRef=0, Joy=0, Btn=3 (RepeatDelayCtr=1) 112719 FS Control Sent: Ctrl=65615, Param=0 112719 *** EVENT: Cntrl= 85639 (0x00014e87), Param= 1 (0x00000001) <85639> 112875 Button held, flags=X05, repeat set: bRef=0, Joy=0, Btn=3, (RepeatOk sets 2) 112875 [Buttons] 1=R0,3,C65615,0 112875 Repeating flag set: bRef=0, Joy=0, Btn=3 (RepeatDelayCtr=11) 112875 FS Control Sent: Ctrl=65615, Param=0 112875 *** EVENT: Cntrl= 85639 (0x00014e87), Param= 1 (0x00000001) <85639> Now what I find rather intriguing about this is that something is seeing the button, or maybe intercepting the control, and sending the event 85639, which most certainly is not one known to FS or P3D, so I assume it is something generated elsewhere. That number is out of the range understood by the NGX, which I think uses custom controls up to about 84232. There are also many occurrences shown in the log of this unknown control: 9797 *** EVENT: Cntrl= 196880 (0x00030110), Param= 0 (0x00000000) <unknown> which is way outside any any sensible range. So, conclusion: 1. The problem is not related to fSUIPC. 2. There are probably conflicts with P3D because I assume controllers are not disabled. 3. You have something else running, maybe Saitek software, or other add-ons, one or more of which is sending rather strange commands. Pete

By "will not install", what do you mean? What happens? What is the indication FSUIPC has not installed? By the time it asks you if you want to Register, it HAS installed! There's nothing else it does after that. And how does it "keep asking you to register"? It only offers the OPTION to register at the end of the installation. Just the once, each time you run the installer. Why would you keep running it? And it doesn't ask you to register, it asks if you want to register, or just check your existing registration, or just do nothing about the registration this time ("not now"). These are options being offered, that's all! WideFS consists of a server function inside FSUIPC4, and WideClient which YOU place and run on a Client PC. There's no installation for WideFS on the Server, only the registration so WideFS Server can be enabled. Pete

Oh dear. So, RCV4 hasn't been updated since 2006. The FSUIPC in that package is totally unusable now. If it does succeed in installing that old version, re-run the 4.95 installer to fix the mess it made. You should be using the RCV4 support forum on AVSIM for problems with the RCV4 Installer. You came here implying it was something to do with me! Pete

Okay, and it shows a perfectly good install into FSX-SE and even successful Registration Check. Your FSX-SE is situated in the normal place: C:\Program Files (x86)\Steam\steamapps\common\FSX and as it says, FSUIPC 4.95 is installed into C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules which is also where the usual copy of the correct Install log will be, alongside also your registration (FSUIPC4.KEY file), and a subfolder "FSUIPC Documents" with all of the documentation and other goodies. So, where are you getting that very old install log from, apart from the thread you referenced. and why do you think there's any problem? Haven't you even tried running FSX-SE yet and looking at the Add0Ons menu for the FSUIPC entry? Pete

I'm not sure how you really expected any controls to work with no assignments whatsoever. You already know yyou disabled controllers in FS. If you don't disable controllers in FS you risk many conflicts with what you are asking FSUIPC to do. You choose FS or FSUIPC. You said you only wanted one lot of settings for all aircraft except the F6F. So you just make assignments, as you wish, but without selecting Profile mode. Then only the F6F will load profiled settings, the rest will use generic settings, all automatically. This doesn't preclude you from making other profiles later. It's all on a need basis, as you find some aircraft need different things. I think you've only run into any confusion because instead of starting normally -- loading up FS with FSUIPC installed, and assigning your controls and buttons for all the normal stuff, ready to fly -- you immediately selected Profile mode and programmed only for the one aircraft. I expect quite a few button and joystick assignments might be common even to the F6F. Profiles for buttons and keys only override generic assignments where you've explicitly set them. Only axis and calibration settings are wholly either profile or generic. Pete

Pardon?