Pete Dowson

Well that looks okay. 64 frames per second is a little high -- don't you set an upper frame rate in FS9? I don't think there's anything wrong with either the Server or the Client ends. The problem is your Registration for WideFS. You purchased this in 2010 but you are still using an old version of FSUIPC for which new Registrations simply are not valid. Look: Version 3.90 is now 18 months old and has not been supported for 16 of those! Please review the list of supported versions in the Announcements. The oldest valid version is 3.98. Regards Pete

Whilst you are using them? Or do you mean between FS sessions? Are they on an external hub? If so, is it powered? If not, use a powered hub. If it is, make sure the power is on all the time the PC is on -- if it switches on later it may be assigned differently. Either way, hubs or no hubs, check in your Windows Device manage that all USB connections (internal hubs etc) have power management turned OFF, where there is such a switch. Windows has a habit of defaulting power management on. In general, unless you disable all the controllers explicitly -- not just the individual assignments, but the controllers themselves -- FS will do its best to make default assignments. I think that may even happen without the power stuff going on, but certainly it makes it 100% more likely to happen if a device suddenly springs into life after FS has started. No, it cannot. If you assign in FSUIPC you should disable the relevant controllers in FS. Otherwise you could end up with dual assignments. If you don't want to make any assignments in FS or FSUIPC, then, no, no more than disabling the controllers in FS. However, on the other hand, if you actually still need to make assignments in FS but just don't want them all to be so assigned, then you can use FSUIPC to make specific assignments without it making any itself. And that would allow you to disable the controllers in FS. Regards Pete

Seems it was quite happily connected for 1056 seconds (nearly 18 minutes!), but then: What's going on there? Your server PC, "YAKOV" changed from IP Address 10.0.0.1 to 10.0.0.3?! There's something evidently wrong with your network setup. If your PCs randomly change IP addresses nothing can stay connected! That connection lasted for a while, allowing PLAN-G to connect: but, again, and after 460 seconds (nearly 8 minutes this time): the 10.0.0.3 reconnection failed and re-connected. So, something very odd is going on at the Server end. Unfortunately you have not shown the WideServer.LOG corresponding to this client log -- all connections have TWO (2) ends, you see? Either end could have a problem. Maybe it's a firewall? Have you disabled your firewalls, or at least allowed WideClient and FS through? Do your PCs see each other in Explorer? Also show me the FSUIPC Log file please. Close FS and WideClient down BEFORE grabbing any logs, else the files won't be complete. Also please always state version numbers -- you don't even say if it is FS9 or FSX or CFS1 or what. Regards Pete

Have you referred to the Announcement about this problem? That's what it is for. Much better than trawling through random other threads! Otherwise, please list that "everything I said ..". I really cannot spend so much time going through long old posts. Summarise what you did. There are only about 4 potential solutions I know of. Otherwise you'd need to Google more, same as I did. I am not an expert on Windows problems, I have to find answers in the same way an anyone else. Pete

I don't know how you have managed to get the error in the first place. But the only solutions i know are: 1. Removing SimFlight from the untrusted publishers list in Internet Explorer 2. Applying one or both of the Registry changes listed. 3. NOT disabling cryptographic services in an attempt to make FS run smoother or 4. Reinstalling windows. Regards Pete

No, not my program!! Are you sure that's not simply an option in whatever program you used? The WideFS and WideClient ZIPs are just zipped up files, with WideClient.EXE being one of them. There's absolutely nothing in WideFS that prompts you to do anything! Oh dear. Haven't you read any of it? It surely isn't difficult to see.The installation guide starts off, immediately after the Title details, with this followed by a list of all the extras installed for you. I can't understand how you'd think to read a User's Guide when you can't even refer to the Installation guide. It makes no sense to me how you can miss these things. :-( Pete

How strange. Where did you get the idea that WideFS was an Internet accessing facility? It's only ever been about connecting FS to other PCs in your local network. You do realise its only purpose is to allow FSUIPC-interfacing applications to be run on client PCs in your network, don't you? I hope you haven't bought it thinking it was going to let you browse the Internet or something! Pete

Erthis doesn't appear to be anything to do with this thread or its title. I use pmSystems all the time with FSX and FSUIPC4. There's absolutely hno problems with it. but if you want PM support you are in the wrong place. Regards Pete

Yes, in currently supported versions, and as documented. There's no difference. Regards Pete

The minimum supported version for FSX is version 4.60. Your purchase covers any version 4, not one specific release. Fine. This is where things you describe seem wrong. what exactly is prompting you to run what? With WideClient all you get is the ZIP containing the EXE. You put that where you like (there is no prompt) and run it when you like (no prompt). Okay. So by now you would have a WideClient log on the client PC and both an FSUIPC4 and WideServer log on the FSX PC. I need you to close down all the programs, then find those logs and show them to me. That's really hardly ever necessary. I always advised it for older PCs and Windows versions because otherwise every few seconds Windows sends messages out on the Network to ascertain other PC's addresses. That can cause small hesitations or stutters in FS. However, with modern multi-core PCs that's usually not at all noticeable. You'll need to solve your internet connection yourself. There is nothing in any of my software which has anything to do with that. You've most likely either set your IP addresses in a different subnet to your router, or have not correectly provided the router's IP address as the "gateway" in the windows settings. If you don't understand any of it I suggest you let it revert to automatic settings. Not if you mean the message from WideClient that it is waiting for a connection. It has nothing at all to do with the Internet. It doesn't use it. Well, yes, of course, exactly. Do you mean you've connected your PCs together and haven't even checked they can see each other yet? Please don't bother trying WideFS unless you know the network is working. Also bear in mind that Vista's firewall is enabled by default and may block WideFS connections even if Explorer can get through. Except for checking that the workgroup name is the same (Vista defaults this differently to XP), and your firewall isn't blocking the connection, no, there should be no difficulty whatsoever. I am using a mixed network with WinXP, Vista and Windows 7 on different PCs. No problems at all. But I've disabled the firewall on every one, preferring to rely on the protection my router provides. There is really nothing needed to be done with WideFS, and there is absolutely no difference in how it behaves between FS2004 and FSX. The difference I think you have is Vista, not FS. You've probably installed it with all the UAC (User Account control) and firewall settings left to default. Vista is far too over-protective. You need to sort that out. WideFS will take care of itself. It isn't complicated, it needs virtually no attention. Regards Pete

Was there no change at all? Did you check the install log? That needs clarifying. What exactly is "no joy" this way? Since you are not running the installer you can't get exactly the same message. That's all, really: install FSX, run it (with no add-ons). close it. Re-boot. Then SP1, same again, then SP2. Make sure you run FSX once each time. Don't start adding anything until you are happy FSX is running well. Regards Pete

See your previous identical question: viewtopic.php?f=54&t=81364 I gave you an answer yesterday. Please do look at your previous threads before posting an identical question, else it could go on forever! :roll: Regards Pete

You only purchase either FSUIPC3 + WideFS6 (for FS9 or earlier), or FSUIPC4 + WideFS7 (for FSX and ESP). There's no specific version numbers you purchase, but the earliest supported version numbers are 3.98 and 4.60 respectively. Rather than say "latest" please always quote version numbers. Also always check the Announcements here in the Forum, please. You will see much later versions, with details of what has changed, in the Updates announcement. If your versions really aren't the latest, please update and try again before coming back. You must have installed it otherwise you couldn't have run it, and if it isn't running it couldn't possibly say it was waiting to connect! This post? Why not refer to the documentation supplied? Have you been through that at all? That's what it is for! Er, what suggestion can possibly have anything to do with the Internet? You need to be a lot more specific. Nothing to do with anything I've ever "suggested", or documented, has anything whatsoever to do with the Internet! What do you mean by "network name"? Do you mean the workgroup? Installing WideClient is merely a matter on placing the WideClient.exe in a folder of your choice on the client PC(s). There is nothing else to installing it. That cannot possible go wrong! How they are all connected makes not one iota of difference to WideFS. The only thing you need to make sure of is that your computers can see each other on the Network. You've not mentioned at all whether your network is working at all. I cannot tell you how to make a working network -- Microsoft's help should be enough and plenty more than I can offer. First get your Network working. When all PCs can see each other and you can exchange files and so on between them all using Windows Explorer, then, and only then, try WideFS. I'm surprised you say you've researched so much about troubleshooting WideFS and never encountered any requests for viewing Log files. They are the paramount most important bits of information, as they say exactly what is going on. In the FS modules folder (you haven't even said whether it is FSX, FS9 or whatever) you will find the FSUIPC.LOG (or FSUIPC4.LOG) and the WideServer.LOG. Make sure FS is not running and show me both of those. In the same folder as the obviously already installed WideClient, on the Client PC(s) you will find a WideClient.LOG. Make sure WideClient isn't running and show me that too. These, along with version numbers, are ALWAYS needed! You also haven't mentioned firewalls at all. Or versions of Windows. Do you have the firewall enabled? Default or an add-on? What Windows versions are you using? All this information may be relevant. In your second message you say: Now this makes me think that you've misunderstood the purpose and use of WideFS altogether! First, as I said, installing wideclient is only a matter of putting the EXE program where you want it. There's nothing else to do unless you want to add optional parameters to its INI file. So what do YOU mean by "tried to install WideClient"? Second, if the laptop is not connected to any network, let alone one running FS + WideServer, how do you expect WideClient to connect to WideServer on your FS PC? By magic? Please explain what it is you think WideFS can do for you! It has nothing whatsoever to do with the Internet, so whether you have an internet connection is totally irrelevant. Regards Pete

Okay, both logs show everything is working well. However, the FSUIPC4.LOG file is incomplete. Did FSX "crash" after you stopped flight mode -- presumably going into the Menus, someplace as appears to be shown by the last line: ?If FSX didn't crash, I'd like to see the complete FSUIPC4.LOG file, after FSX is closed down. If FSX crashed, I need the description of exactly what you sawwhat you actually mean by "crashed". Is there a message, does it just disappear? Or what? If there's a message, what does it say? Information is important if we're to solve your problem. If you look back to my previous message I not only asked to see the Logs (thank you) but I asked these questions: I see already that you are running at least one add-on -- Digital Aviation PA31T1 Cheyenne I. So, that's the first thing to try: does it crash when using default aircraft, not this add-on? You'll also see, if you refer back again to my previous message, that I asked further questions: Should I really have to repeat myself all the time until we get somewhere? For instance, the most important question still remains unanswered: WHY DID YOU ORIGINALLY ASK ABOUT AN INTERNET CONNECTION? Is it, or is it not true that the crash only happens when you are NOT so connected? Since you made such a fuss over this point, surely that must be a clue. We should be looking for whatever add-on you have which is trying to access the Internet and causing the crash if it cannot! Regards Pete

Sorry, I have no idea. pmGetWeather is not my program and I don't even use it. Please direct questions to the appropriate place. pmGetWeather is by Project Magenta I think. Regards Pete

You mean the FSUIPC-added controls specially for PM? They aren't macros. They are listed in the FSUIPC Advanced User's guide, but the main reference for all things PM is their website. You will find the list of PM offsets there. Knob? On a 737 the WX and TERR buttons are on the EFIS control, to the left and right of the MCP, resectively, for Captain's and FO's NDs. I've no idea where they are on your aircraft as you don't specify one. For PM information please refer to the PM documentation from the PM site. I really cannot undertake to support PM as well as my own software. If you have specific questions on things in FSUIPC, by all means ask them, but i will not reproduce the documentation here. You need to be specific as to what you want clarification for. Regards Pete

Ah, Joshua Robertson's FSRealTime. Yes, I use that. Regards Pete

Yes. WideFS works with any mix of PCs, running any current Windows version (and even non-current ones like Windows 98). To make things easier to set up, make sure all PCs are in the same workgroup. WinXP and Win7 default workgroup names are different. Pete

Ask Saitek about that if you need to. I cannot support Saitek equipment. Most of the PMDG aircraft do not use standard FS controls. Check their documentation -- you might need to assign keystrokes instead, or use the mouse. In that case you may be one of those with a faulty Saitek yoke which apparently sends spurious button signals to the PC. You need Saitek support. I can't help I'm afraid. Unless the Saitek software is sending FS controls directly (or via FSUIPC offsets), it's obviously assigned somewhere, and you are getting erratic button signals. Check FS as well as FSUIPC. You can't mess up FSUIPC installation, so I assume you mean Saitek. Really your best advice is to go to their support site. To reset FSUIPC simply delete the FSUIPC INI file before running FS. Then it is no longer a factor. Please sort things out with the Saitek gear before even bothering to use FSUIPC on it. I really can't support their hardware. Sorry. Pete

I assume you must mean WideFS, as I've never heard of "fswide". Okay. Squawkbox 4 does not use either FSUIPC or WideFS, so I'm afraid you need to refer to their support, as I cannot support other folks programs. I've no idea what "realtime" and "pegasus from bav" are. You'll need to clarify that. Generally, for support for folks programs you need to go to their own websites. If WideClient is not connecting and Windows is converting your Server name into an invalid address, then this is always down to the way your router is set up. As stated in notes in the Updates announcement in this Forum: In the latest (possibly as yet unreleased?) WideFS Technical document I have added this section: If you cannot figure out how to resolve the settings there, you could always try specifying your server's IP address in the WideClient.INI file via the ServerIPAddr parameter. You'll need to provide the Protocol parameter too! Regards Pete

So, why do you think it is anything to do with the Internet? Please refer back to your earlier post where you stated: Was that not actually true, then? Unrecognisable? Why? So far you have provided no information whatsoever. I cannot help on that basis. If you have a problem to resolve i need information sufficient to resolve it. I need to see the Log files: there should be two, in the FSX Modules folder: an Install log and an FSUIPC4 log. I need more EXACT information about what you mean by "FSX crashes when I have FSUIPC installed". When does it do this? What exactly happens when it "crashes"? Are there messages, or what? What have you done before it does so? What other add-ons are you running? Please consider this: you posted your first complaint here a week ago, yet we are no further forward because you have all the time insisted that it is all to do with an Internet connection. Perhaps the problem is that one of your add-ons using FSUIPC is using the Internet too, and that is where the problem lies? List all of the add-ons you are using, maybe the culprit can be isolated. Try running with nothing else but FSUIPC installed, and introduce the add-ons one at a time ... Regards Pete

Okay. bug fixed in interim updates 4.624 and 3.989a, now available in the Updates announcement in this forum. As well as the fix, you can now receive an event on any of the 8 POV buttons by specifying button number 40. Also the undocumented value '0' for the "downup" parameter is confirmed as being the same as omitting it (i.e. acts like value 1). In fact any value other than 2 or 3 acts like 1. So, to log all POVs, pressed or released, my test program becomes: function showbutton(joy, btn, downup) ipc.log("NEW joy=" .. joy ..", btn=" .. btn .. ", downup=" .. downup) end event.button(1, 40, 3, "showbutton") Of course not all expected events will be detected -- pressing more than one button at a time (hard not to on some Hat designs, like the MS sidewinder, my test device) might result in two "press" events, but only the one "release", because that's all that is seen -- a Hat can only indicate one thing at a time, unlike true buttons which operate in parallel. Sorry about the inconvenience. Odd that the bug hadn't been found before. It was a pretty obvious one! Regards Pete

Okay, I'll check it here. Okay, I can reproduce it. Very strange. i'll investigate and fix. The Lua program I used was: function showbutton(joy, btn, downup) ipc.log("joy=" .. joy ..", btn=" .. btn .. ", downup=" .. downup) end event.button(1, 32, 0, "showbutton") event.button(1, 33, 0, "showbutton") event.button(1, 34, 0, "showbutton") event.button(1, 35, 0, "showbutton") event.button(1, 36, 0, "showbutton") event.button(1, 37, 0, "showbutton") event.button(1, 38, 0, "showbutton") event.button(1, 39, 0, "showbutton") As well as fixing this bug, I might add another "special button number" to represent "any POV button 32-39" so that this can be done more efficiently! Regards Pete

Okay, I'll check it here. You don't have a real POV? That's right. Does the Angle parameter stay the same on each repeat? Does it correspond to the buttons pressed? (For 8 way, angles 0, 4500, 9000, etc to 31500). Regards Pete

Interesting. Yes, I see I do say POVs are supported in this way. Sorry about that -- I clean forgot! However, according to the documentation, the "downup" parameter (the third above) should either be omitted, or set to 1, 2, or 3. I'm not sure what it would do with 0 there, though I'll check over the weekend. You mean move it in one or other direction? Well, the 2 seconds is explained by your programming, obviously -- the program is stuck in the "sleep" for two seconds on every occurrence of the event. Whether the phenomenon of getting events for all 8 possibilities one after the other is explained by your invalid 3rd parameter or not I can't say at present. Could you try omitting it instead, or using one of the valid values? Regards Pete