Pete Dowson

That is certainly starting to sound like a hardware problem. Maybe in the networking hardware or possibly in computer memory. One thing to check, first, though, is whether there's a memory leak from something running on either PC. If the memory becomes rather full one of the first things to suffer are the TCP/IP network exchanges as they get no buffer space. You can run the memory resources part of the task manager to compare free memory at the start with the state when the networking stalls. It means you haven't installed the IPX protocol into Windows, that's all. You only need that if you want to use it. It used to be a standard part of Windows until WinXP -- it's the original very efficient local networking protocol (not for Internet) invented by Novell. WideFS has always supported it because it is so efficient -- but it is more difficult to set up. I suspect this is mainly because Microsoft don't seem to like it. WideServer prepares listening sockets for all three supported protocols -- TCP, UDP and IPX. Those are of increasing efficiency in that order. But the only protocol you use will be the one you select. You could try "Protocol=UDP" in the WideClient INI to see if your connection lasts longer. It will certainly use less buffers (or rather the same number of buffers, but for less time, as there 's much less checking and confirmation in UDP). Incidentally, Windows Explorer uses UDP when exchanging files over the local Network. Regards Pete

Can you please re-read the thread and answer the questions already asked which you have not yet done so. Most importantly show me the FSUIPC Log file which you've not bothered to do yet. I'm afraid it is useless to continue until there is some measure of understanding about what the problem actually is. I'm afraid you've only been confusing the issue so far, and supplying the wrong information. In order to progress we need to be clear AND have the correct information to hand. Regards Pete

The "condition" levers are the Mixture axes. Just calibrate your mixture lever(s) correctly. Sorry, but I don't understand that part. What don't you see exactly? The axis assignments are in the "Axes" tab. Their Calibration is performed in the Joysticks tab, and Buttons are assigned in the "Buttons & Switches" tab. Please refer to the User Guide. There are also pictures in there showing where things are. Regards Pete

I ddidn't know that route. I shall investigate it in Win7. Thanks! Pete

Er .. you just unzip the FSUIPC4546.zip file into the FSX Modules folder. Let it replace the one that's there. It isn't "patching", merely a rpelacement DLL. Pete

If it says "Peter L. Dowson" then that's for my signature from GlobalSign which expired in August. None of the main issuing authorities will now issue signatures to private individuals, only registered companies. I think it was an edict from Microsoft, to tighten up security. So SimFlight kindly stepped in and did the business, which is why the signature is now in SimFlight's name. It's been that way since versions 3.90 and 4.50, earlier this year, as I wanted plenty of overlap. When the signature has expired the security checking in FSUIPC, against tampering in the code, will prevent it working correctly. so it was important to allow time for everyone to update.. If the individual gauges aren't actually signed then they'll not be affected by anything in the publishers lists. Are you sure they are signed? The publisher might have been installed during installation only. I've never been asked to confirm trust more than the once for any FSUIPC updates on any of my PCs -- SimFlight are now listed as trusted on them all. ;-) Regards Pete

Sorry, what patches? You mean SP1 and SP2 for FSX? If you put FSUIPC 4.546 into the FSX Modules folder and it loaded correctly, it will say 4.546 in the About tab in the menu, and in the Log file, and it will show that version in its Properties-Version details. Whether it is registered or not makes no difference. Registration doesn't change the version number. The Sync Pos facilities have been available on the 4 throttles, 4 prop pitches and 4 mixtures pages for several versions now, including 4.546. Regards Pete

In my Internet Explorer 7 on XP it's in the Tools-Internet Options-Contents-Publishers tab. In Win 7 it's the same, so I must assume it's pretty similar in Vista. Right click on the DLL, select Properties-Digital Signatures. You can select the signature, then Details-View-Install. It's the same in XP. Not a site. A publisher. But I don't think you just add the details yourself -- you have to use the signature, which contains athe certificate. The "security" stuff was something I didn't know about -- someone else reported this: but i think that must have been a mistake now that I've tried. I think he used the Digital Signature route I mentioned above. Sorry for the misdirection. Regards Pete

If the publisher details are added to the Trusted list in Windows (not in FSX.CFG) then you never again get that prompt. The publishers are listed in one of Internet Explorer's menus -- there's a "trusted" list and an "untrusted" list there. In XP and, I think, earlier versions of Vista, there was a drop down choice in the prompt you get from FSX where you could get the trusted status recorded. It seems to have disappeared lately. Someone said you could do it by right-clicking on the DLL, and selecting the security options. I've not tried that yet. Regards Pete

Well, if there are no buttons or joysticks set to operate the spoiler I don't think FSUIPC can be involved. However, it can help you track down the cause. In the Logging Tab in FSUIPC options enable the Button logging and also the Event logging (not Axis events though). When the problem occurs the log should then show how it happened. Just add the line "EliminateTransients=Yes" to the main [buttons] section in your FSUIPC INI file. The INI file is the configuration settings for FSUIPC in the FS Modules folder. Sorry, I can't help with that. Get things working without FSUIPC first. It sounds like you need to calibrate your throttles in Windows for starters. And what is "the last"? That's meaningless I'm afraid. I always need to know the version NUMBER!!! It is easy enough to find, it is displayed on the About TAB in FSUIPC options. So far you've not even saif if you are using FS98, CFS1, FS2000, CFS2, FS2002, FS2004, FSX or ESP. All of those versions of FS can run FSUIPC! Aha! If the problems are all with the one aircraft, you have a problem aircraft, not a problem with FSUIPC! You are in the wrong Forum! You need to find the Support place for that aircraft! Regards Pete

I have also now implemented a "brake release threshold" into FSUIPC. There's a new parameter: BrakeReleaseThreshold=75 added to the [General] section of the FSUIPC INI file. This sets the amount of braking needed to release the parking brakes and autobrakes. The number is a percentage of total braking -- so the default here is 75%. If you set 0% it turns the facility off. Action on both brakes to more than the set level is required, and the release action is not "re-armed" until both brakes have returned to "off". The toe brakes must both be calibrated in FSUIPC. This facility works in FSUIPC3 and FSUIPC4, and works with the "Direct to FSUIPC" assignment option. In FSX it works the same way with all assignment methods, but in FS9 it only works with Direct assignments because FS9 automatically disables the braking on any brake action, so the threshold, although applied, is meaningless with FS control assignments.. I think this will better meet the needs of the serious cockpit builders among us! These facilities will be in the next incremental updates, 3.943 and 4.547, in the Updates & Goodies Announcement, either later today, or maybe tomorrow. Regards Pete

Sure you can. I added the author credits. Thanks! Pete

Great? But surely wrong. However, that is what does appear to happen with the FS controls, so if you want that to occur, that is the way you should be assigning -- NOT to "direct". So, just do as I keep telling you. Assign to FS controls, not "direct", then set the null zone in the calibration section as you've been doing! Yes. Hurrah! (I've only said it about eight times! ;-) :roll: ) Regards Pete

Serious problem? More information is needed I'm afraid. What version number for FSUIPC? Do the spoilers arm all on their own, without you touching anything? What have you assigned to the spoiler arm control, as evidently you are triggering it. Did you try using FSUIPC logging to find out what? The early Saitek devices had firmware problems which caused them to send spurious button presses. There's an INI file option in FSUIPC to "EliminateTransients". Have you tried that? What else have you tried -- you say "everything". What does that mean? Regards Pete

Yes, of course. It was a helluva lot of work -- a complete re-write for FSX and ESP, not just an update like for the previous versions of FS. Regards Pete

WideServer is in the FS PC, all of the Networked PCs connected to FS are clients. The terms "Client" and "Server" are nothing to do with the PCs themselves, or their function come to that, but to do with how the communication protocol is programmed. The Server "listens" for clients, the Clients find the Server, in one way or another, and then ask it for a connection. Think of the Internet. When you go to a website, you are acting as one of the many clients connecting to that website which is acting as a server top all of its clients. Yes. In XP? First make sure you are set for simple folder sharing. In Explorer use the Tools menu, Folder Options, Views. I think it's the last item in the list. Then all I do is right-click on the folder in Explorer , click "Sharing and security", the "Share this folder on the Network" and "Allow network users to change my files", and give it a useful name. For that folder I call it "FSPLANS", because programs like Project Magenta expect that name. But that's your choice. Choose a decent short name "FSFiles" would do, for example. In Vista it's more complicated. I'm not sure I'm the best person to explain it, since I get in a mess with it too! :-( (Oh, and I only use Vista Ultimate -- actually now Win7 Ultimate. So it's probably different). Regards Pete

I'm very interested in getting you to run some tests for me so I can dig into the problem and see if I can find a proper solution. The same sort of problem occurs regularly -- infrequently, thank goodness -- but on WinXP, Vista, as well as Win7. In fact I know it goes at least back to Win98 and WinMe. But I've never been able to reproduce it. If i can work out a way of detecting when it happens, automatically, and reconfiguring something internally to circumvent it, I'd like to. Write to me at petedowson@btconnect.com if you are interested in pursuing a solution. Thanks, Pete

Have you managed to fix this at all? If so, can you tell us how, please? If not, I'm interested in getting you to run some tests for me so I can dig into the problem and see if I can find a proper solution. The same sort of problem occurs regularly -- infrequently, thank goodness -- but on WinXP, Vista, as well as Win7. In fact I know it goes at least back to Win98 and WinMe. But I've never been able to reproduce it. If i can work out a way of detecting when it happens, automatically, and reconfiguring something internally to circumvent it, I'd like to. Write to me at petedowson@btconnect.com if you are interested in pursuing a solution. Thanks, Pete

Thanks! That's neat. Can I add this to the Lua examples package? You'd get the credit -- if you can put your name in some comments at the beginning, perhpas? Regards Pete

Erit does? I thought you said when assigning "direct" it doesn't do those two things. In fact I know it doesn't, because I tried it here. However, assigning to the FS controls, Axis left brake set and Axis right brake set, does. You want to do this but still have the toe brakes operating BEFORE the point where the parking brake and autobrake cut out? I'm afraid that cannot be done at present, with or without FSUIPC. I will be considering adding such a facility, though (see my P.S.) Now this is where it gets completely daft. What on Earth do you mean by that? If you do not press SET and calibrate the brakes, there is no point whatsoever in using FSUIPC at all. And if you have your brakes assigned "direct" to FSUIPC calibration, then unless you calibrate they simply will not work! If you don't press "SET" and calibrate the brakes you are not using FSUIPC. You might as well forget about FSUIPC for axes if you don't calibrate, as it cannot do anything for you. I really don't understand how you have become so totally confused, and I really don't know how to explain any further. I've repeatedly explained that what you want to do can very easily be done by simply doing what you did already, but assign to the FS controls -- i.e. NOT assigning Direct. By assigning direct, in FSUIPC3, you are bypassing the FS controls, and it is those very FS controls which disengage the parking brake. You can still set your null zone. That can be set no matter how you assign your controls. As I keep repeating. The calibration part can apply to any way of assignment. I'm sorry, I do not have any more ways to say the same thing. You seem simply not to be reading me at all. :-( Pete P.S. I probably will add a new option to FSUIPC, to set a threshold for brake release operations, independently of calibration. This would be needed on FSX where none of the methods of assigning will do it at present. At least using FS9 you have a method -- simply assign to the FS controls in the drop down.

FS9 uses FSUIPC3. FSX uses FSUIPC4. Different products, different keys. Regards Pete

The autobrake going off function is to do with the aircraft you are flying, is it? But you just implied you wanted it to! As I tried to explain, obviously unsuccessfully, setting a smaller range for any axis is performed in the Joystick Calibration part of FSUIPC, and that part is the same no matter how you assign your axes! And setting greater of lesser "dead zones" (which is what you have done) is not what stops the parking brake or anything else coming off -- it is the fact that, in FS9, the brake axes when assigned normally do that but FSUIPC3 is not using them when you assign direct. (In FSX neither does what you want). Really, by reducing the effective range on your brakes, you are actually making them more "sensitive", but with a wasted unused part at either end of the movement. If you really want less sensitivity you'd use the slopes facility to have a flatter slope near the "brakes off" position. Yes, still with a small dead zone to make sure they can always come off. You can do all of that whilst assigning the toe brakes in any way you like. Using the "direct to FSUIPC calibration" is no different for that at all. The Joystick Calibration section operates for the left and right brakes just the same -- and it does so even if you don't even use FSUIPC's axis assignments at all! So, you are entirely missing the point. I'll repeat it again, shall I? You can assign toe brakes in FS9 or in FSUIPC. In FSUIPC you can assign them "direct to FSUIPC calibration" or you can assign them to the usual FS controls. So, that's three ways of assigning them. With me so far? Right. Now, the crunch point. It doesn't matter which of the three ways you assign the brakes. You can still open the FSUIPC calibration tab, go to where the toe brakes part is, and calibrate them there. Yes, by pressing "Set" (if it isn't already pressed and showing "Reset"). That facility, the one for calibration, has been in FSUIPC for nearly 10 years. The facilities for assigning axes in FSUIPC is only half that age. The ways of assigning do not change the way you calibrate. Sorry, I thought it was you that needed help! ?? You didn't read that part of my message either? Do NOT assign to an offset control! The facility I was talking about is on the RIGHT-HAND SIDE of the Axis Assignments tab -- you are still looking at the LEFT! The right-hand side facilities allow you to associate any controls with movement of the axis through any one of up to 10 zones in either or both directions. Assignment there does not affect assignment on the left. Anyway, the offset control I suggested would only release the parking brake, it would not affect the autobraking action. If merely blipping the normal brakes control ('.') does that, it will do both things, so it is probably better to use that -- it's the control called just "brakes". However, I don't think you need to do any of that -- if you assigned to the FS controls for toe brakes and calibrated in FSUIPC as you wish, there wouldn't be a problem. You are only getting into a problem because you insist on using the "direct" assignment, but as I keep pointing out that is not necessary. No, of course not. I haven't made any changes to FSUIPC yet. I said I would think about it, remember. It would mean a new version of FSUIPC, not just an INI change! Regards Pete

That's what I was hoping, yes. Regards Pete

Problems starting Windows 7? I don't know of anything about that. Dragged what, precisely? Version 4.53 comes as an Installer, which you have to run. "no dragging". Nothing in any of my software can have any possible affect on whether Windows 7 will start correctly or not. Windows has to be properly running long before you even run FS, let alone anything of mine! There's never ever been just a "Version 4". that's the generic name, to distinguish it from "Version 3". All versions 3.000 to 3.999 are "version 3", and all versions 4.000 to 4.999 are "version 4". It's like saying "windows 7", which could be any one of a number of builds of Windows 7! I don't know where you are reading "version 4", but the real version number will be shown in the main "about" tab in the options. You can also find it in the Log file, and in the DLL properties-details. Do you mean the new facility added recently? That isn't in 4.53. For that you must download the latest update from the Updates announcement above. There's 4.546 there now. Pete

Oh dear. Please update. Version 3.93 is the earliest supported version. There's also a 3.942 version available in the Updates announcement. There's no separate "direct" calibration window. There's one place for calibration and it works identically no matter how you assign the axes. You can change over to non-direct assignment and the exact same values will still be there and work as before. Ah, autobrake is a totally different matter. By default FS9 does not switch off autobraking after landing, no matter what you do with the toe brakes. I use other software to provide that. Sorry, you've lost me there. I don't think parking brake release is relaed to autobrake at all. Can you explain? Yes, but you could always set the MIN and MAX in the FSUIPC calibrations, no matter how you arrange the assignments. There's nothing different for any of the methods. That would be great! I'm now not sure why you'd think that. Turning off the parking brake won't change anything to do with autobrakes. If that was your only concern, what's the point? And if you get what you want by assigning to the FS controls, Why not do that? Just calibrate your MIN and MAX as you want to. That's no different. From FS there's only the Parking Brake control, which is a toggle. But you can easily use Offset Word Set control. Set the Offset to x0BC8 (the Parking Brake offset) and the parameter to 0. But please explain (a) why you think you cannot calibrate in FSUIPC except by assigning Direct. That is worrying for me. The "direct" facility was added much much later than all the calibration facilities that folks have used for 10 years or so. (b) why you think anything operating on Parking Brake will reset the Autobraking. Thanks, Pete