Pete Dowson

You cannot use FSUIPC3 keys to register FSUIPC4. It is a different product, completely re-written. Please read the documentation and follow the links to SimMarket for key purchase. Pete

Why not use the search facility in Word or WordPad to find these things in the documentation? I have to do it for you? I searched on GPS and immediately found "NAV/GPS switch" at 132C. Do you think I remember all these? I have to search just like you could! :-( There is no C/O pushbutton control or state. The display shows IAS when IAS control is selected, MACH when MACH control is selected, via the standard A/P offsets. The FS gauges to actually change the display without the mode being selected, but that is a local function in the gauge, not in the FS A/P. Pete

Not really. The NAV button is the same as the LOC (sometimes VOR/LOC) button on a real MCP -- it captures the NAV1 radial set in the pilot's CRS window. Those more advanced cockpits which provide proper LNAV and VNAV fiunctions do so by sophisticated programming inside the cockpit coding (in the gauges usually), and both functions need a programmable FMS (with CDU and data entry keyboard) because it is the FMS which provides the data guiding the Lateral and Verical courses. If you use something like the PMDG 737NG you should be able to program all your MCP buttons to operate their buttons, but I think you have to do that using keystrokes unless you come to some arrangement with them for their SDK. You could use it with Project Magenta software (http://www.promagenta.com) because all of the PM MCP functions are accessible through FSUIPC offsets -- documentation on their website lists them in some detail. Regards Pete

Yes, I understood that. You think I'm the idiot? But when you turn it it has to go unclosed again before going closed on the next position, right? Else it is a useless switch. So it goes off-to-on, then on-to off, just like any other switch. That is all a switch can really do, you see? :-( Groan. You are evidently not reading anything I say. How many more ways do I have to say the same EXTREMELY simple thing? Each time you turn your switch and it makes contact, that is an "off" to "on" change. That is the same as a PRESS of a button. Therefore all you need to do is program the PRESS to do what you want!!! No it is not. It is NOTHING like holding a key down UNLESS you tell FSUIPC you want to do this! I have already explained this!!! Please go and re-read what I said. I really cannot explain such a simple concept any better. I do not understand why you cannot see that it is NOT the state ofv the switch you are programming, but the CHANGE, from off to on, or on to off, or both, as you like!! Think CHANGE not STATE!!! What can't you understand what "off to on" and "on to off" mean? These are simply short words. There is nothing complicated here. You seem to think it is. Why? I am off to bed now, it is late here. Please go and think about things for rather longer than you appear to have done so far and maybe the light will dawn. :-( A further thought. if you don't understand words, why not just go and try it? I'm sure you'll see what I mean. I have run out of ways to say it anyway. Pete

Offsets don't change from version to version, hopefully. Especially rather standard ones -- they would have been the same back in FS98 days! New ones are added but old ones don't dile easily ;-) The current version of FSUIPC4 is 4.05, by the way. N1 button ---- there isn't one exactly, but TO/GA is the closest you'll get: 080C. ALT HOLD Button ---- A/P altitude lock, 07D0 LNAV, VNAV button ---- no such thing in the default 737, they left those off. Where are you looking? FS doesn't provide these functions by default. Pete

With FSUIPC4 or FSUIPC3? If FSUIPC3, why are you needing to re-register? Since you have the original email send it to me at petedowson@btconnect.com and I'll check it. If FSUIPC4 then obviously your FSUIPC3 keys won't work because it is a new product and it didn't even exist in 2004. Regards Pete

Erassuming that somehow your switch is looking "closed" then "open" (i.e. pressed and released) as you are turning it, isn't that the same as programming only the "off to on", as for a button. Just don't program the on to off in that case. If your switch signals nothing on each turn then it cannot be used for anything anyway, can it? You seem to be thinking this is complicated when surely it is easy. Please think about it a moment longer and re-read what I said already. ALL any software can possibly see of a switch is its changing from off to on or on to off. You can program one or other or both, as you like. How much more flexibility can you get? If you are programming a keypress from a button press in FSUIPC's buttons option, you have the additional option of having the key held pressed or not. So the keypress can do "KEY DOWN" and "KEY UP" each time, or "KEY DOWN" but not "KEY UP" till you move the switch again. Surely all this is pretty obvious. If you are not understanding then obviously I'm missing something, but I'm pretty sure everything is covered by the options as documented and explained. Regards Pete

Where execly can a user set that? Thank you Pete! Registered users, in the 'miscellaneous' options; non-registered have to edit a parameter in the INI file. Please do check the FSUIPC user guide some time. It describes the user facilities including this one. Regards Pete

In FSUIPC you mean? You don't say. If you want it to do the same action when it goes from On to Off as it does when it goes from Off to On, just program the same action for "Release" as for "Press". This is surely easy to understand? After all: "Press" is off -> on. "Release" is on->off FSUIPC doesn't know what sort of switch it is. It only sees those transitions. Pete

Same as with all FS windows -- drag it, size it, dock it, undock it, do what you like with it. When you save a Flight it is saved as well. It is an FS window, it isn't mine. As I said before, and as documented, 3302 is set by user options, not by IPC writes -- the documentation explicitly says it is read-only. It is for user's to decide what they can read best. The white messages user option doesn't appear to work in FSX at present, by the way. Pete

No, that cannot be. For several reasons: 1) The title is written before the text, so if that activated it the window would be empty! 2) Only one title for the wole session is used, because once the window is created it stays created no matter what. FSUIPC doesn't support multiple such windows, only the one, so the first title sent wins. I'm pretty sure it says that too. You only write the title once, on initialisation, and hope you are the first such application. It most certainly says you need to write 32FA to activate it. 'Call FSUIPC_WriteS(&H3380, Len(writetxt), writetxt, dwResult) 'Call FSUIPC_Write(&H3302, 2, VarPtr(0), dwResult) Why is there a write to the read-only location 3302 there? I don't know what "VarPtr(1)" does. Is it a pointer to an integer 1? If so the display is only for 1 second maximum. Is that what you want? Not sure what you mean -- they are both pop up windows with text messages in them. Just a different place and, normally, a different shape. but both can be undocked and re-shaped and so on. Have you enabled the multiline message window on the first page of the FSUIPC options? Is there more than one line of text in your message? Even if you only want one line you need a New Line or Return character in there as the whole point is to filter single lines to the standard message window, allowing only multiline messages to the multiline message window. Regards Pete

Ahem. Did you check the documentation at all? Writing to 3380 just provides the text to be displayed. The activation is by what you write into 32FA. It does say this quite clearly if you look up 3380, and the options and values you can provide are detailed against offset 32FA, though some of those don't apply to the multiline window. Regards Pete

Sorry, didn't mean it to hurt! ;-) Regards Pete

Ah! Thank you. All is explained. ;-) Well, almost all. It is very odd that any attempt is made to connect to the internet to find your Server PC by its name! That is rather weird. It's as if the name server (on the router perhaps?) didn't know thename so went off to see if it could be matched. Regards Pete

In another thread? Why start another then? Have you a reference? I really cannot remember all the separate threads I respond to, you know! ;-) No, this is not specifically an FS2004 forum. It is a forum for support of my FS modules, which run on FS98, CFS1, CFS2, FS2000, FS2002, FS2004 and FSX. There are also some programs which are separate to FS altogether. I cannot guess what you are using, and most enquiries at present are about FSX. The latest FSUIPC3 is 3.71. What is your version of WideFS? You need to quote numbers because the "latest" just means the last ones folks bothered to download. Are you starting a different thread because you think the answer to the same questions might thereby be different? If you want detailed answers I need detailed information. I don't know the other thread offhand, but if your logs look like they did then the answer will be the same. You said nothing was changed but now you say: So in fact you've changed at least two things -- moving the computers and changing your internet. It sounds very much like one of those things has changed or even broken something that was working before. Regards Pete

WideServer7 is installed when you install FSUIPC4. There is no separate module, as has been made very clear. WideServer is mentioned on the first options tab in FSUIPC4. When it is registered you will see you can enable it there. The current version of FSUIPC4 is 4.05 by the way. It is available above, since yesterday, but it loos like Enrico's not updated his site yet. Odd that, he's usually pretty fast. There is NO WideServer.DLL for FSX. If you've put one in delete it please. It won't do any harm other than confuse you. Please please do read a little about these products. There has NEVER been a WideServer.DLL for FSX, it has always been part of FSUIPC4, and it says this clearly in several places. No it does NOT!!! It never has. It says this: :cry: :cry: :cry: Pete

FS does allow payloads to be changed via the same Aircraft menu entry as the one which sets the Fuel levels. You don't need to reload the aircraft. FSUIPC does allow you to change individual payload weights dynamically, but I think in FS2004 this didn't actually affect anything unless you then went into and out of that payload menu. I never found out how to "broadcast" the change to the aircraft dynamics sections. FSX now officially supports payload changes via SimConnect, so FSUIPC4 uses that method. It should deal with the changes properly, but I haven't tested that. I'm not really the best person to test it, not really knowing that much about aircraft dynamics. I suppose I could fly the Cessna with just a pilot payload, then use FSInterrogate to put a huge weight in the other seat and see if that causes lateral balance to go awry. I might do that when I get time. I didn't answer the original question because I don't know much about programming aircraft panels, and zero about XML. Regards Pete

ERhow? There's something screwy with your router then. It should be able to identify the correct PC from the correct name. And local "intranet" IP addresses are never in the same subclass as Internet ones. BTW why set the ServerName to the IP Address when there's a ServerIPaddr parameter you can set? Regards Pete

So, it was working one day, and not the next, and you've not changed anything whatsoever? Is that right? Assuming you aren't using a WideFS key with an expiry date (and very few such have been issued, only by Project Magenta I think), that really doesn't sound feasible. Something must surely have changed. I'm afraid that without any information so I couldn't even hazard a guess. Basic inforamtion like version numbers of everything is missing, and I'd need to see INI files and Logs. It would also be nice to know, please, whether you are talking about FSX or FS2004, or FS2002 or ... After you supply more information, we'll have a guess. Okay? But please do think long and hard about that "not changing anything" part. Thanks, Pete

No, I didn't know that! (Sorry, I never use FS ATC as I think it is dreadful. I am a firm Radar Contact user). Not specifically. Do the NUM pad keys also get taken? Have you tried changing the NUM lock state? What do the arrow keys do in the ATC menu anyway? Otherwise you could presumably simply assign key presses in FSUIPC4 to do the job. The keys are simply associated with the controls Ailerons left, Ailerons right, and Elev up, Elev down. You could do that via FSUIPC's Keys tab. In fact, try assigning them to the arrow keys -- there's a possibility that FSUIPC will trap them before the ATC window does. Regards Pete

I don't know "My Traffic Communicator" either. I installed My Traffic X for proper AI traffic, in correct liveries, in FSX. I really don't know any of this other stuff you are mentioning. Maybe it's part of a later version? Either way it isn't realted to my programs, FSUIPC or WideFS. Regards Pete

Sorry, this is not in any way related to anything FSUIPC offers or does. I have no idea how to solve such problems if merely saving the flight, once you have positioned the windows, doesn't work. It should work (but of course you must save the flight), so it certainly sounds like a bug -- please report it to Microsoft via tell_fs@microsoft.com. Regards Pete

No. Sorry. Pete

Sorry, no. I have never heard of "ANFS.EXE", and I have MyTraffic X. What is "My Traffic X Live"? Is that a separate product? I think you need to ask My Traffic support. Regards Pete

If it's a firewall, I can't help with firewalls -- all the information I can possibly get is there, in the point blank message from Windows: "connection refused". Maybe your two PCs are on different workgrpups or something? There's no other information I can get. If Windows refuses to allow WideClient to connect to your Server, there's not much I can do -- you need to find out why and fix it. It'll be something to do with your Netwrok settings somewhere. Sorry. Katy Pluta over in the FS2004 Forum is the person I always ask about network problems. Maybe try there? But first, check your Windows firewall settings on the Server. Disable it or explicitly allow WideClient / WideServer to talk to each other. Or maybe there's a firewall setting in the Router which needs changing? Some routers provide their own firewall protections, I think. Regards Pete