Pete Dowson

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

The wireless network has absolutely nothing to do with the MixW virtual serial port solution I provided. Just get WideFS working okay on your Network first. It is totally irrelevant whether it is wireless, wired, parallel, serial, Ethernet or firewire. The network is a network. That's all, WideFS doesn't know how the signals travel and doesn't need to know. MixW is only used to create and link two "virtual" COM ports on the client. Just install it, find out what ports it is assigning (in the System hardware manager list) and tell WideClient one of them and your map program the other. I don't recall there being any way to "control" what MixW actually does, but maybe you can. I simply installed it and used the virtual ports it created. There's nothing else to it. Look in the Control Panel (Settings) -- System -- Hardware -- Device Manager -- Ports (COM & LPT). Regards, Pete

In FSUIPC's Logging options you will find checkboxes to log Button actions, and Events (two separate checkboxes). Enable both of those then look in the FSUIPC.LOG file to see what is going on. If they only go "on2 once, and aren't held on for repeated "Throttle dec" controls to FS, then I don't know how you are getting full reverse thrust -- there's no FS Control to sent full reverse in one operation. Pleay with the F1-F4 keys on your keyboard. notice how they make the throttle change when you press them, but do nothing when you don't. It is the same with buttons. Nothing happens if you don't make it happen. Of course. Haven't you even looked? I call it "press" and "release" though, not "closing" and "opening". New builds and "things" of what? Nothing of this is different in FSUIPC -- there are lots of new facilities, but you aren't using any of them. Why not wire up proper reverer levers then? Mixing buttons and levers doesn't seem to be good when they all address the one axis control in FS. Regards, Pete

Okay. So these "reverse levers" are not really reverser levers. They simply press a button? You have no control of the amount of reverse? It isn't that GoFlight quadrant is it? I had one for a while, but removed the non-lever reverser levers and programmed a reverse range on the throttles instead. By "lowering" the reverse levers, you presumably mean pushing them forward, away from the microswitch? Surely, all that is happening is that, whilst the reverser lever is against the switch, it is pushing it on and presumably generating a repeating F2 to decrement the throttle. When you push the levers away from the switch, that stops happening, that's all. Then, your throttles, in FS, are left where that sequence of F2 pushes left them. Without any other input, FS won't know that you want the throttles to go to idle! You need something else to tell it -- another button, or an axis change. Axis changes send messages to FS, but if you don't move an axis it isn't sending anything. So you either need to move the throttles a tad, as you say, or program another button event to set the throttles back to idle. Possibly you can program the microswitch to send a "Throttle Cut" control when it is released? In FSUIPC Buttons this would mean programming it to do "Throttle Decr" (with repeat enabled) on "press" and "Throttle Cut" on release. Isn't it as simple as that? Where does GoFlight come into this, by the way? If it is a GoFlight device you should contact them for support. If it isn't, why are you using their drivers? Regards, Pete

The indicator should be used as an indicator, the control to actually control it. Naturally the one reflects the other. Regards, Pete

No need to be sorryI was just puzzled as to why you'd think of FSUIPC in this context. ;-) Pete

Why would you think FSUIPC had anything whatsoever to do with it? FSUIPC has nothing to do with normal FS gauges at all -- Gauges are supported by FS directly, they do not need FSUIPC. After all, you do realise that FS is sold with gauges for all of its aircraft already! Sounds like you have an aircraft with a bad panel. Write to the supplier or maker. Regards, Pete

So, are you calibrating the reverse thrust though FSUIPC's reversers? If you don't need to use FSUIPC's reverse zone facilities, you can simply press "reset" on the FSUIPC calibrations, so FSUIPC doesn't touch them, and simply use FS's throttle assignments -- there is no reverse section on the default throttles at all! The whole advantage of the FSUIPC system was to provide a reverse zone on throttle levers. If you have enough levers to assign separate reversers then why the bother in the first place? Something is making no sense at all here! :-( I must admit to be totally confused with what you say about buttons operating your reverse -- perhaps you'd like to clarify that? There you go again. What is this "button function"? Why not forget the button? How are you calibrating the reverser levers? Surely all you want is for your throttle levers to behave like normal FS throttle levers, which only have idle to forward thrust on in any case! Pete

Well, Windows in the client cannot translate the server name into an IP address. This is all the error on "gethostbyname" means -- in this case the computer named "Main" is not known to your Client. I guess that means that the service which provides this in one or other of your systems is not running. This in turn would mean paths like \\Main\c .... would not work either, and I'm reasonably sure this means "Main" would not be seen in Windows Explorer. I really don't know what you are seeing in Windows Explorer as if it can see the name "Main" then so should any other program running on the same PC. You could try setting the "ServerIPaddr" in the Client INI instead. This assumes you have a fixed assigned IP address for your Server. Regards, Pete

Please, after starting a thread on a subject, could you please keep subsequent exchanges relevant to that thread in the same one, not keep starting new threads? It makes intelligent conversation quite difficult and rather nullifies the whole point of this neat Forum structure! That sounds fine. Isn't that what you want to happen? About what? Regards, Pete

Yes. You should really have pointed this out to SimMarket when you ordered it. However, if you send all the details of both registrations to me at petedowson@btconnect.com I can change the older one for you. Regards, Pete

Okay. Thanks for letting me know. No doubt they will have it fixed in due course. Pete

The part relevant here is in the sections headed Joysticks. You'll find a series of numbered steps towards proper calibration. The step you obviously missed is #6. Here it is. I have highlighted the parts you needed to notice: That "dead zone" around the centre is the extent of the "Arm" zone on the spoiler, it is the "idle" zone" on throttles with reverse, and it is the "hands-off" zone on flight controls. It is quite important, and 'central' to the whole method FSUIPC provides for accurate calibration! Regards, Pete

No! The middle set has two values. You are not following the steps. The centre sets in all cases have two values, to delineate the zone. Please read the instructions, it should be clear. it should even be reasonably clear from the screen where you can surely see boxes for two values in the centre? The same applies equally to aileron, elevator and rudder settings, and of course also to the individual throttle calibrations where the centre declares the idle range. Please please please read the documentation. That part at least is in simple numbered steps :-( Regards, Pete

You don't need to buy WideFS to download it!! I'm surprised you did it that way around -- you should download it and read the documentation first, to make sure you really want it! Many folks get mixed up with WidevieW. ALL my software for FS is downloadable from http://www.schiratti.com/dowson, as it always has been. All the links lead there! How could you miss it? Don't forget to pick up the current FSUIPC too while you are there. Pete