Pete Dowson

No. Did Elite? It seems to be their problem, don't you think? Pretty much all of those symptoms really cannot be anything whatsoever to do with FSUIPC. It seems that the Elite DLL is misbehaving rather badly. What do their support say? I really know nothing about what Elite have done. They have never contacted me for any assistance nor ever been interested in any way in obtaining a license for their use of FSUIPC. They are determined on "going it alone" and must therefore support their own devices themselves. I am sorry, but there is nothing I can do. Regards, Pete

Okay then. Sorry, I'm all out of ideas as far as my software is concerned. it is only reacting to what it is told by Windows. Something is not right, but it looks like it is between the Network driver/card/cable at each end. Possibly uninstalling the network hardware in both PCs and reinstalling (so it reinstalls drivers and restores itself) should be the first step. If it is hardware playing up it doesn't look like it, and unless you have alternative Network cards/connections it isn't so easy to check. Regards Pete

The "buffer problem" is not the problem, as I said -- that is merely the result of all those failing attempts to connect. The Windows sockets available are getting all used up. On my systems that would take 128 tries, on yours only 16. But it is a symptom not a cause. Your WideClient log is odd: The timing out of the response is occurring only 50 mSecs after the attempt to connect. Have you been changing parameters in the WideClient.INI file by any chance? Show me, or, probably best, delete the INI file and start again. Regards, Pete

No, only the 4 separate engine cowl flaps in floating point -- 37F0, 3730, 3670, 35B0, as documented (just do a search on "cowl"). The old 0-16384 axis offsets were for compatibility with FS98 practice, and that didn't provide cowl flap axes. Otherwise you'll need to use offset 3110 to send COWLFLAPn_SET controls with appropriate fixed-point parameters. Regards, Pete

Sorry, that makes no sense. There's no "type" called FS98CHILD. That's just a Class Name. HWNDs are always of type HWND. You only use the Class Name to register a new window or to find one of that class. For all other Window activities you use the handle (HWND is a Window Handle). Pete

That is a sure sign of a bad key. Where did you purchase your keys? I have no record of your current email address -- is the one you are using here different? The only explanation which fits everything you are seeing is that you have somehow acquired a bad (possibly illegally generated) Key, either for FSUIPC or for WideFS, or for both. If you would like to ZIP up your KEY file along with the receipts from SimMarket or wherever, or at least the name and email with which you registered, then I can try to resolve your problem. Make sure you ZIP things and send to petedowson@btconnect.com. Regards, Pete

What do the WideFS logs say? (There will be a WideClient.Log and a WideServer.Log). You say "will not work with my 3.5 reg", but there are no version-specific registrations. It actually sounds very much like you are using an invalid user Key for either or both of FSUIPC and WideFS. Delete your FSUIPC.KEY file and try again. If that makes everything work, you will need to send me all your details (not here -- I'll give you the email address then) so we can find out why your registration is wrong. Regards, Pete

SB3 needs TWO completely separate connections to FS. One is to FSUIPC (optionally via WideFS). The other is through FS's own Multiplayer interface. Check the latter. I know nothing about Multiplayer and it isn't anything to do with FSUIPC or WideFS. Regards, Pete

The reason may be on the Client side, or at least it may be logged there. There is no error logged by the Server. Look: I've never actually seen the "no buffer" message, but it will have occurred only because there are already the maximum number of connections (Sockets) allowed in your network settings. If you count them there are 16 before the 17th one fails. Probably 16 sockets is the maximum allowed by default on your Server. Although you can probably increase that, it isn't the problem. The problem appears to be that the Client is not actually seeing any notification that its connection has been accepted. So it tries again. It is doing two attempts every 60 seconds, if you notice. What was in the WideClient log? That may be more helpful. According to this log you never actually got properly connected at all, though you say This log shows no successful connection at all -- there was no transmission to be stopped! Regards, Pete

That's a bit odd. PM normally deals with the V/S in 100's. BTW rather than use /1 (divide by 1) just have no multiplication or division. i.e. remove your /1, it will only make it a little slower. Dividing by 1 doesn't actually accomplish anything. Anyway, checking back, according to the PM documentation offset X4E6 is used as follows: but this is a bit ambiguous. If correct it means that a V/S of, say, 6000 would be 60000 here. I read it the other way, that 6000 is here as 60. After all, a value of -6000 would otherwise give -60000, which is actually impossible in the two bytes alloted. I must admit I am very confused by this, as well as how you were (before) seeing the CORRECT value when you were adjusting it. Hmm. It shouldn't do either normally -- BC is a Back Course on the ILS, but this is something airliners (like those supported by PM) do not have! I canot recall what Button number the BC button sends to FSUIPC now, so I cannot check how it is programmed. Sorry. But it is rather unlikely that I assigned it to "V/S", as Level Change is more useful in most A/P modes. Doesn't the MCP have a V/S button in any case? [LATER] Reading a bit of my own documentation (for GFdisplay), I found this: So, unless there's a mistake in the FSUIPC.INI stuff the BC button should do neither of the actions you suggest. ;-) Regards, Pete

Ernow I'm confused. How did you program GFdisplay then? It is supplied as a basic kit with documentation and a few examples. The user (i.e. you in this case) is supposed to do what he likes with it. That's the whole point. Are you just using some examples I included and nothing else? no changes, no editing, nothing? I'm sorry, but I am having difficulty imagining that. It sounds like somehow you have FS's own VS indication (which is NOT divided by 100) mixed up with PM's VS system which does, I think, use the value divided by 100. If you can explain exactly what you have done I can try to investigate. I'm afraid I sold all my GoFlight gear this Summer past -- except for a couple of RP48 and P8 units -- and so have no display units left to test things on. (It isn't something I planned on developing any further -- there's been almost zero feedback in any case). Regards, Pete

Sounds like you have an error in the GFDisplay parameters. You can divide the value by 100 before display if needed. Did you look? Show me the relevant code if you are not sure. Regards, Pete

Okay. That is called a crash! In particular that would be "FS crashing to the desktop" or a CTD. This is an FS problem. If you are not using the 9.1 update, then get that and install it. It fixes at least 75% of all known crashes to desktop (CTDs). If you still get the CTDs, then it is likely you have a bad scenery file or scenery texture. These are the two most likely causes at any rate. There are others. None of this has anything to do with either FSUIPC, WideFS, or even Project Magenta. You need to do a process of elimination to find the cause. First examine everything you have added, especially scenery, textures, and similar. Regards, Pete

Looks like your joystick is faulty then. You'll need to get it fixed or replaced. Regards, Pete

Seems best to do away with the second PC then, and run SB3 on the same PC as FS? Otherwise you need a mixer to mix the two outputs, or wire one to the left and the other to the right earpiece? On the other hand, there's also a volume control for the sound card with the speakers, of course! ;-) Regards, Pete

Sorry, I still don't understand, what do you mean by "FS2002 is going out"? What do you actually SEE happen? These lines are not errors, the just log the aircraft name (from the Aircraft.CFG file) when you load an aircraft. What are "lost data area in FSUIPC .."? If by FS2002 "going out" you mean FS2002 is crashing, then naturally WideClient loses its connection with WideServer. wideServer runs in FS, so if FS crashes, it takes WideServer with it. I will try to help if I can, but I need you to explain what you actually see. "Going out" is what girls and boys do of an evening. I don't know what that means applied to FS2002. Sorry. Regards, Pete

No -- possibly the firmware is too early to support that connection, but that seems unlikely. I'm afraid the software can only deal with what it sees. Your course of action lies with PFC I'm afraid, not me. The switch you are talking about sends a 0 to 1 change or a 1 to 0 change. It is only a single switch, akin to a single button. What were you expecting? To program any switch in FSUIPC you simply need to IDENTIFY it by toggling in in whichever way FSUIPC will see it. In the programming page FSUIPC is only looking for an "off to on" transition -- otherwise it would get triggered on wrong events. You can still program it for both "press" and "release" transitions. Regards, Pete

Sounds like the throttle axis is set up incorrectly. Before doing anything in FS or FSUIPC you need to go to Windows "Game Controllers" (in the Control Panel) and calibrate all the axes correctly. Then, in FS, go to Options-Controls-Sensitivities and make sure the sliders for "sensitivity" are all far right (max) and the ones for null zone are far left (zero). If an axis seems to have the reverse effect (i.e. max throttle when pulled back, min when pushed right forward, then see about checking the Reverse option in FS's Options-Controls-Assignments. Also, in the Assignments makes sure you don't have any other devices which FS has assigned -- maybe joysticks you also have connected, or used to have. Check the dropdown list of devises and deallocate anything assigned to any device you don't use. Don't bother to even try calibrating anything in FSUIPC until you have it working basically in FS. 16380 is actually roughly the normal (default) value for max thrust. Most joysticks should give a negative number when the throttle is pulled right back. It sounds like you definitely need the reverse option checked -- there's one in FS as well as in FSUIPC. Only use one, but since you want to get it all working WITHOUT FSUIPC first, best to do that in FS. Regards, Pete

But why on Earth would you want all the sound mixed on one set of speakers or, worse, a headset? Surely one of the true benefits of having the ATC on a separate sound card is that you get the sound separated -- for a separate set of speakers, or more realistically a headset. Why would you want to mix them back into the general aircraft engine and other noises? If you really wanted to take such an odd step you could use a mixer, of course. But it seems to me to be losing the biggest advantage you have with SB3 on a separate PC! Radar Contact version 4 is recently announced, for release in December --- see the "Sticky" thread above on the subject from the author JD. Visit http://www.jdtllc.com. Regards, Pete

Eryou connect your headset to whichever PC is running whichever program it is providing the sound you want to hear on your headset. Of course! If SB3 has its own voice built in (and I think it does -- previously you would have had to use Roger Wilco or AVC I think), then of course it is where SB3 is that will have the SB3 sound. Surely that is the IDEAL situation? You want the ATC on the headset, but the aircraft and other sounds on the main speakers. Much more realistic -- you surely don't want all the sounds mixed on the same headset or speakers? BTW none of this is anything to do with either FSUIPC or WideFS, which don't deal with sounds. I don't actually use SB3, but I do use Radar Contact and I run that on a separate PC under WideFS specifically so I can get the ATC on a headset, or separate speakers. Regards Pete

I'm not sure whether there is anyone here who can help, but I wish you luck. It isn't an area I know anything about I'm afraid. Just in case, you may want ot try posting your questions on other Forums too. I'm not sure which would be the most suitable, though, I'm afraid. Regards, Pete

But, as I said, your name and email must also be exactly as they were when you purchased the registration. All three fields are needed. They are inter-dependent. Don't display anything here. And a Key on its own is useless to me, I would need the name and email too (the ones you bought it with) in order to check it. Have you no idea what name and email you used? Do you change them regularly? If you think you have all the details and still can't get it to accept them, include them in an email to me at petedowson@btconnect.com and I'll check them here. But if you have forgotten any part of the essential three pieces of data then really there is no way possible to retrieve the situation. Without those details or your receipt from SimMarket (or wherever) there's no way to retrieve your purchase. Regards, Pete

Sorry, I don't know what this means. When you say "FS2002 switched off" do you mean you FS PC reset itself or had a power failure? If not what do you mean by "switched off"? Neither of those versions are supported at all in any case. The mnimum supported FSUIPC version at present it 3.50. Version 3.51 will be released within 2 weeks I hope. Why should FSUIPC show any errors? Are you running all of Project Magenta on the same PC as FS or do you use a Network? Does PM indicate any errors. What is it you are actually seeing -- does your FS PC power down, for instance? This is what I would mean by "switching off". You really do need to explain a little more, please. I have no idea what you mean by "switched off" or "lost data are with non exist engines", nor do I know what you configuration is at all. Please, if you use WideFS, do make sure it is a supported version too -- 6.50 or later. Regards, Pete

The only thing which affects how it starts is the parameter in the WideClient.INI file. Did you check? Take a look please, or just delete your INI file and start again. BTW I always need to know version numbers in any query or problem report, please! [LATER] The business of "restore" making the Window disappear (for that's what it is doing -- there will always be a Task bar entry in any case) will be due to corrupted Window coordinates in the WideClient.INI file too -- delete the line containing the 4 numbers. It is likely that the position is off-screen because you changed screen resolutions or monitor connections or similar. As an alternative, of ccurse, you could "restore" then "move" and use the cursor keys in assorted directions until you see the window frame coming into view. Pete

I think that depends entirely upon the video drivers & card you are using, and the mode they are set into. You are best asking in the FS2004 forum -- this is the sort of thing some folks certainly do manage. However, I do think there's a problem with FS2004 remembering the positions on multiple screens next time to load FS, even if you save a Flight with them all set. I have read that folks need to undock and move the Windows each time. Also, you may need to do that with FS in Windowed mode, then put it into full screen mode afterwards. But i'm not sure --- I think, again, it depends on the drivers and video modes set. Ah .. doing it by program? Hmmm. It may well be possible, if you know Windows programming very well. The main problem will be locating the correct Window handles. All FS's child windows seem to of the same class ("FS98CHILD"). You'd need to investigate with MS's Spy++ I think. Regards, Pete