Pete Dowson

That should be okay. Can you try it with an FS throttle quadrant showing on screen, so you can see whether the spoiler engages or not? It may simply be the PM indication which isn't correct. ... Or of course you can use an outside view on touchdown to see if the spoilers are raised -- assuming you are using an FS model with animated spoilers. [Later] I've posted a message to Enrico to ask about his spoiler indications in PM as well. I may have a modification to FSUIPC which will help. But note that the % deployment shown by PM isn't actually correct in any case. The minimum deployment is 7%, represented by the value 5620. the range the % should be measured over is actually 4800-16384 but PM currently measures it over 0-16384. This is my fault, as I've documented it like that since FS2000 days. Recent investigations, whilst adding the spoiler axis calibration facilities, have revealed the true behaviour of these FS controls. Anyway, let me know what you see actually happening on the aircraft, as opposed to what PM indicates. If the spoilers, when armed, do deploy on touchdown but then almost immediately revert to "armed", then I can fix that I think. However, I need to know what you are actually seeing. The problems arise, of course, because on a real aircraft the spoiler lever would be driven to the flight detente on loading, whereas your lever will remain in the "armed" position even though it has deployed. It may be that this is causing the unwanted extra movement, assuming it isn't just a PM indication. Regards, Pete

Try FSUIPC 3.556, now available above. I think that is fixed now. No, that isn't an FSUIPC function at all. The idea is to split the multiline type messages, like Radar Contact uses for menus, from the single line displays at the top of the screen. Normally those programs which create those have an option in them to disable them. Regards, Pete

You can "choose" multiline? If Advdisplay isn't installed when you FIRST run this version of FSUIPC, then the option should already be checked, automatically. Are you sure you haven't run 3.553 before, with AdvDisplay installed? If so then, yes, it will initially appear unchecked. I have just managed to reproduce a case when it doesn't seem to remember the check mark first time. I'm investigating now. But then: Ersorry, I don't understand what that last sentence means. How can there be a "new window" but "everything is like before"? What are you expecting to happen, please? The FSUIPC window only appears if there is something for it to display. You want to "disable multiline", yet you set "SuppressMultilineFS=No". Shouldn't you have set that to "Yes"? Or do you mean you want to suppress the new FSUIPC window, in which case you should have "ShowMultilineWindow=No". I'm confused about what you actually want to do. Regards, Pete

I don't like the sound of "the newest one in my module folder" -- there must only be ONE FSUIPC in your modules folder! If you have others, albeit renamed, delete them. Additionally, the oldest currently supported version of FSUIPC is 3.53 which was released on January 1st this year. Please replace your 3.52. I don't know how you managed to get copies of the DLL all over the place, but just copy updates directly into the FS Modules folder, only. Do all those products which you say come up with errors actually have checks on the age of FSUIPC, and even messages reporting this? That really surprises me! I think you may be misreading something. Can you tell me more about these 'messages' please? There's nothing wrong shown there except: 34406 Module [M1] identified = "FSUI.DLL" which indicates something wrong with one of your installed modules or gauges. The "FSUI.DLL" module is an original part of FS by Microsoft and most certainly does not use FSUIPC. It's the FS "User Interface" in fact. Anyway, next time before showing me a log, please close FS first. Only a complete log for a session is of any real use. Regards Pete

It isn't "unnamed", it is part of the defined "idle" or "centre" zone -- there are always two values for any zone, one at each end. You cannot define a zone with one vlaue, that is just a point!! Please re-check the documentation. You are evidently not following the calibration steps outlined clearly. In particular step 6 which includes these words: Pressing the centre “Set” button will enter the value in one or other of the two boxes beneath. Each time you press Set the alternate value is recorded, and the boxes show the two most recent values in order (lower above higher). If the values are the same you will have no dead zone around the centre. Please start at Step 1, proceed through the subsequent steps, and read each one. Dont' skip any, then you cannot go wrong! Pete

No, unless you have less than 10 mbps bandwith I don't think that can possibly be true. Even with less than 10mbps it is unlikely just with one client. The traffic WideFS generates is pretty miniscule by comparison. At times I have 10 or more computers on my network, all linked by WideFS, and with up to three of them operating on the Internet with a broadband connection via a router on the same network. All of it runs at pretty much top speed as far as I can tell, even though some of it is wireless (at about 25 mbps) and some over a mains cable adapter system 9running at around 50 mbps I would guess. I am not the best person to answer Network problems -- my system when there's a problem is one of trial and error for a few days, then ask someone else. The most knowledgeable person I know on Networks lives over in the FS2004 Forum, so ask there too. But I think you will need to spell out your actual settings and errors reported (not for WideFs, for the Networks). Regards, Pete

Oh dear. Run FS. Do ALT M F to see FSUIPC options. Selct Buttons. Make your microswitch operate. When FSUIPC sees it, select assign to FS control. For button press find and assign "Throttle Dec" and check Repeat. For Release find "Throttle Cut". Press OK. Surely all that is just basically what I said before, combined with a little common sense looking at what is in front of you? I don't understand what you don't understand! If you don't say, and can't be more specific in your questions, how on Earth can I help more, or even ever improve the documentation -- which incidentally has stood the test of many users over the last five years or more! I'm sure all the previously successful users weren't really more intelligent than you despite what you imply. Pete

Sorry, you've lost me. Tell me want you want to do and how you are trying to do it. If you are trying, you cannot mix control and keypress assignments. Just stick to one or the other! For FS operations there is no advantage using keypresses -- they go through FS's key assignments and operate controls in any case, so it is obviously more efficient (and reliable) to use FS controls. The keypress facilities are useful for add-ons which don't have "FS controls", but almost everything in FS does! It should be obvious and intuitive, as thousands have used the facilities in the past. I cannot explain any better than I have, else I would have. What is it you don't understand? I don't see any point in reproducing the documentation here. What is so complicated? Surely if you are intelligent enough to fly you can do something so simply as assign an FS control from a dropdown list? :-( Pete

Yes. No, only in the FS to which you wish to connect clients. WideServer has nothing to do if there are no clients connecting to it. If you do have more than one WideServer offering service then you will need to change the Port number in one of them (it defaults to 8002) and likewise in the clients which contact them. Not necessarily. If both PCs are using WinXP they should find each other automatically (with current WideFS releases). Otherwise the ServerName is usually a safer option than the IP address. Erare you now saying you have buttons connected to BOTH PCs which you want seen by both? i.e. a symmetrical arrangment? You didn't say that before -- you said the buttons involved were on an EPIC on one PC. If you want symmetry, yes, you need WideServer on both, and WideClient on both, each of the latter with a classname change and one pair of Server-clients using a different Port. Regards, Pete

If it only happens with that aircraft, it cannot be FSUIPC, as FSUIPC makes no distinction between aircraft. In any case, it does not interfere between gauges and FS -- unless the writers of that aircraft use FSUIPC as their source for such information instead of FS as others would. What does it do if FSUIPC isn't even present? Pete

Sporry, I don't know CH manager. If the CH documentation doesn't help, maybe you can check out Bob "Sticky" Church's documentation on the subject? Try http://www.stickworks.com Sorry, where and when did I ever say that? Once you have registered successfully for any Version 3.xxx you don't need to re-register unless you re-install FS or Windows or move to another PC. I've always said that. Regards, Pete I re loade down 3.53 but it tells me i am already registered a bit confused :roll:

Erwhere are you reading this "slope value" please? The only "slope" facility offered in FSUIPC is one based on curves selectable graphically. They do have a reference number, but only a small one (-15 to +15, with 0 = straight). Please see the pictures in the documentation, where both extremes are illustrated. For throttles you'd normally want a linear response unless your throttle lever is very off-kilter in its resolution. The "slopes" are mainly useful on the main flight controls. You make them less sensitive near the centre whilst more sensitive at the extremes -- the "S" shaped curves with a flattened centre is the most useful (+ve "slope" values). There is nowhere which offers anything called a "slope" with values like -7000. I really cannot imagine what you are doing there I'm afraid. Regards, Pete

I think this is where the confusion lies. the "reset flight" resets to the last loaded OR saved flight, not only to the last loaded flight. When you have no AutoSave running, the reset flight only goes back to your original loaded flight because you haven't saved one since. Try it for yourself. Remove autosave, run FS and fly, at some point save a flight (; key). Then see what the Reset Flight facility does. I think maybe you are assuming the "reset flight" does something different to what it really does? As far as I recall it has always reloaded the "current" flight, and the "current flight" would naturally be the last one saved or loaded, would it not? Pete

I did answer this substantially in my earlier reply last October!!?). Didn't you understand it? If the buttons are programmed in EPIC ot look like standard joystick buttons, then WideClient ought to be able to see them just as well as FSUIPC. The joystick interface used is not "exclusive" -- i.e. it isn't one in which the joystick is grabbed as a resource by the program, so any program can see them. So you just need to get WideClient running on the same PC as FS and your EPIC. To do that you have to tell WideClient to use a different Class Name, as I pointed out in my earlier reply. If the other (non-EPIC) PC running FS is running WideServer and you get this WideClient connected to it, then the FSUIPC installed there should see the buttons as well. No idea, sorry. But why are you ignoring the help I gave? Why ask if you don't use the answers? Regards, Pete

Yes, this shows it is working correctly, as designed. The flight is the regular Autosaved flight. You have it operating every 60 seconds, so it will, on average, have saved 30 seconds ago if you crash at random times. If you don't want AutoSave to do this, then why have you installed it? If you want to reload from an earlier flight, to give you more time, you just need to use the Flights menu and select one rather earlier. I actually use 180 seconds (3 minutes) as the Autosave interval, which with 10 iterations saved allows me up to half an hour of flight to choose to go back. Also, with 180 seconds the average is 90 seconds ago. With your average of only 30 seconds ago it is quite likely that this seems more recent due to the time FS seems to spend deciding what to do on a crash. Please, either don't use AutoSave if you don't want a recent flight restart, or change the parameters to suit what you do want. That's what they are for. Regards, Pete

Then the flight that is reloading is the one which was last saved, which could be anything from 0 to 60 seconds ago if you are autosaving every 60 seconds. Regards, Pete

The main panel design system is provided by Microsoft in their panels SDK. Regards, Pete

Is the flight being saved actually called "My Restart" as you implied? If not, what? Can you check the comment in it (the stuff showing up on the Flight selection screen in FS)? That might give a clue. If you cannot attach a file, just show it all in your reply here -- it would be easier in any case. it is only a very short text file. It might be worth your whilst searching generally for any other "Autosave.CFG" files too, though I really don't think it can pick them up from anywhere else. Does the timestamp on the one you are looking at seem correct for the last time it was updated (by AutoSave on a normal timed save)? The list of files in it may help. As I said, there's nothing inside the program itself which can name a restart flight, it has to get it from that parameter. Pete

It cannot do that as it doesn't then know the name "My Restart" -- that is a name you have chosen (it is the example in the TXT documentation). It isn't actually part of the program, only the "AlsoSave" word itself is. Are you perhaps looking in the wrong place for the AutoSave.CFG file? It is in the main FS folder, not in the Modules folder. I put INI files with the Modules, but keep CFG files with FS's own, in its main folder. Well, it wasn't. But it doesn't matter. Check you have it in the correct folder please. Regards, Pete

A router? You never mentioned one of those. Sounds like it was creating a block. Nor am I. I only know what Windows help says, and then some of it is confusing. That's why I'm puzzled. No doubt an expert would know once you'd laid out all the facts. I don't even know what INI parameter you changed now -- all that got very confusing along the way, me advising one thing you doing something different, if you look back! ;-) Never mind. It'll have to remain a mystery. Regards, Pete

Well, I'm glad you got it working, but there are many puzzles left unanswered. You don't set the IP address in the INI by either line, it is the "ServerIPaddr" parameter, as I tolkd you earlier, viz: If "192.168.1.100" works why did you set "192.168.1.1" before? Have you simply changed the IP address? And here: The log shows you are using "ServerName=MAIN", not the IP address in any case. So, what has all this been about? Just getting the name or address wrong each time? Surely not? And why cannot your Server broadcast to your Client, so the whole thing works "out of the box" as it does on all other all-WinXP networks? Something is very strange somewhere. Regards, Pete

Historical? Accidental? Sorry, I don't know. Pete

This is one reason it is usually better to put the reversing zone on the main throttle lever, possibly with a notch or interlocking bar, ideally operated by your reversing levers. You should be able to do it with your button though, but you will certainly have to find out what the button actually does so you can program it correctly. seems like it has been a guessing game so far. FSUIPC does supply enough tools for you to work it out, as I've described. Regards, Pete

Well, that's a bit better. That error is normally due to a firewall blocking access. Pete

Does it? Sorry, I didn't remember that. If there's a choice, choose any you like. Providing you have two linked COM ports it doesn't matter what they are. Either one of the two. It matters little which .. . what is the difference? How does it recognise a GPS? Is FS and WideClient running, with one of the COM ports assigned at the time? If it isn't running how can you expect it to find one? If you can select the port instead, just select the other one -- ie. the one you didn't give to WideClient. Think of the two ports as if they are on each end of a null modem cable, linking Wideclient to your map program. I think you seem to be thinking this is complicated, when in fact it is too simple. Pete