Pete Dowson

I'm sure you must be missing something. You most certainly do NOT need email or password to use those links correctly. I cannot help further without knowing your email address (or all of them if you have many). Then I'll ask further help for you. There has never been anyone else in all these years who cannot get messages through to SimMarket! Pete

The events listed in the FSUIPC dropdowns encompass all of those known to FS and detailed in its "Controls.DLL" module -- that's where it gets them from! I've really no idea what you mean by the events you mentioned -- where on Earth do you get them from and why do you think they are true FS events? Maybe the events you require are already there but you are not finding them? Do a search in the List of FSX controls" document installed in your FSUIPC Documents folder. Pete

I'm afraid I cannot advise about things like that for an add-on aircraft. I don't even know whether an "A400M" is a jet, prop, or what -- the starting procedure is different even for each default aircraft type, and can be even more different for an add-on aircraft. First, you need to know how to start the engines with the usual methods -- keyboard and/or mouse. Perhaps you do, and if so, describe it here? You could also use the FSUIPC logging facilities, especially "event" logging, to see what might be going on internally. But be aware that add-on aircraft may not use FS events and may not be susceptible to the documented FSUIPC offsets. Pete

It sounds like a USB problem between Saitek and Windows 8. Seems Saitek and Windows 8 are rather incompatible, at least judging by all the problems folks seem to have with unrecognised devices and ones which simply stop working mid-flight, all with Saitek. BTW I don't think there's any reverse zone as such on Saitek throttles, Most folks assign the button which is pressed when you pull the throttles back to "throttle decr" controls (like F2, but there are controls for each engine). Calibrating a reverse zone doesn't work in any case for some aircraft, which is why FSUIPC provides a "no reverse zone" option. Pete

Doesn't FSGRW have support? What do they say? I don't know what that message is nor what it is from, so I can't really help directly. But I assume you've actually checked that FSUIPC is installed and running? i.e. it's menu is there and works, showing the correct version -- 4.937? Remember, if you are running FS "as adninistrator" then every FSUIPC client program needs to be run at the same level too, otherwise they can't talk to each other. The converse is also true. Best to never run any of them "as administrator" (it should not be necessary). Pete

Why not either use the ServerName, then, so the IP address doesn't matter, or change your network to use fixed IP addresses? However, an automatically assigned IP address shouldn't keep changing unless something is set up really badly in your router. Assigned addresses are normally kept for days or weeks or until some other devices needs them when the previous owner is turned off. Another possibility, i think, is that your server PC is trying to maintain more than one IP address, offering more than one way to connect -- eg either through two Ethernet connections, or maybe Wifi and Ethernet? Certainly i can see such a setup making the link between the Client and Server very precarious. Neither choose which route to use. Your Server log shows, exactly as before, that no connection attempt is EVER seen by the Server. ********* WideServer.DLL Log [version 7.937] ********* Blocksize guide = 8192 (double allowed) Date (dmy): 30/10/14, Time 21:00:41.345: Server name is MOTHERSHIP 15850 Initialising TCP/IP server 15850 Initialising UDP/IP server 16162 Broadcasting service every 1000 mSecs 129185 Closing down now ... Memory managed: Offset records: 31 alloc, 30 free Read buffer usage: 0 alloc, 0 free, max in session: 0 Write buffer usage: 0 alloc, 0 free, max in session: 0 Throughput maximum achieved: 0 frames/sec, 0 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec ********* Log file closed ********* and this cycle in the Client log: 593 Connection made okay! 36723 Timed out response: connection assumed lost! 36723 Ready to try connection again 36785 Timed out response: connection assumed lost! 37783 Attempting to connect now 37783 Connection made okay! 37846 Connection closed by server! 37846 Attempting to connect now 37846 Connection made okay! 56192 Timed out response: connection assumed lost! 56192 Ready to try connection again 56254 Timed out response: connection assumed lost! 57252 Attempting to connect now 57252 Connection made okay! 57502 Connection closed by server! certainly shows that whatever it is answering on Port 8002, it isn't WideServer. You have something else there. Since you evidently can't find the culprit, why not simply change WideFS to use another port? It's a simple parameter change -- one in the FSUIPC4.INI file, in the [WideServer] section, and a matching one in the WideClinet.INI file. And whilst you are at it try changing from using ServerIPAddr to ServerName=MOTHERSHIP. Does AVG have a Firewall? Mine doesn't. You use that as well as the built-in Windows Firewall? Did you turn the latter off? Pete

WinZip isn't needed in any case unless your version of Windows is pre-XP, as Windows Explorer provides zip/unzip facilities built in. You only need to double click on the ZIP file in Explorer. If it says the ZIP is bad you either have a bad download, or your Virus Checker is detecting a false positive and refusing to let you access the contents. Pete

The worst that could have happened is that it overwrote your later version with an earlier one. Is this with FSX or FS9 or what? You don't give much information. That normally means you have another instance of FS still running but with no windows. That state of affairs can happen if the previous run did not fully terminate -- you'd need to check in Windows Task manager and delete it forcibly. The only other way possible to get unwanted modules loaded is to have copies in the main FS folder. You cannot actually have multiple copies of the same file in the Modules folder, it is impossible as the Windows file system only allows once instance of each filename in each folder. As I just said, there cannot possibly be more than one file called FSUIPC.DLL (or FSUIPC4.DLL, depending on your FS version) in the one folder, so what you describe makes no sense. If a bad installer for another add-on overwrites your copy of FSUIPC with an older version, the only sensible thing to so is re-run the current FSUIPC Installer to correct the matter. Registration numbers never change and do not suddenly stop working! You are making an error somewhere. Surely you backed up your KEY file as instructed in the documentation? Don't forget that all three parts -- name, email and key -- MUST be exactly right, exactly as when you first purchased it. Don't se any different email or different ways of spelling your name! Next time you post asking for help please do provide adequate information. You don't even say what version of FS you are using! Pete

How are you activating the Map view? you can get keypresses sent to FS even when it is in a dialogue (i.e. when the simulation isn't actually running) by using a Lua plug-in to send the keys. this wors because the plug-ins run autonomously, is separate threads. As examples, of this at work, please see the examples installed in your FSUIPC Documents folder -- the ones called Fuel737 and Payload737. Pete

Yes, provided only the Win XP version is at least at SP1 update level. You will probably find that the Workgroup names are different -- Microsoft changed the default names between XP and Win7. You either need to make them the same, or edit the client parameter file (wideclient.INI) to provide it with the FS PCss IP address or name, and the Protocol you want to use. Read the section in the WideFS doc about configuring your network. Pete

Okay. The install log is fine and shows that 4.937 was most certainly copied into the correct folder. Check it there: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL If the Properties on that file says it is NOT 4.937, but an earlier one, then something else you have installed has overwritten it. Please simply re-run the FSUIPC Installer. Pete

The "DynamnicFriction.lua" file must be present in the FS Modules folder. Don't edit the [LuaFiles] section at all! That's simply where FSUIPC registers the Lua files present in the Modules folder. The numbers assigned MUST stay as they are for assignments to Lua plug-ins to work. There is a space between "Lua" and the name of the plug-ib Lua is the command, the rest is the name. Everywhere this is published it contains that space so why question it now? If you are still using FSUIPC version 4.923, as [er thos thread#s title, then you must update as it hasn't been supported for a long time. current in 4.937. Pete

I think some Browser's have some default option set which stops pasting into Forums, but i don't recall where the option is or what it is called -- but you need to change it as the only way I will get to see your log and so help would be for you to paste it. Try using the <> button above the edit area to enclose the text. Otherwise, hopefully, someone reading this will be able to tell us what option you need to change. That sounds like something else you have installed has overwritten it with an older version. Unfortunately there are still some add-ons which do this sort of thing. try rerunning the current FSUIPC installer. Pete

Use the same email and name which is intimately associated with that key. The email does NOT have to be up to date, it was and is only used as further identification, to make them truly unique (which cannot be guaranteed with name alone). You'd have to purchase a new key if you really wanted to register with a different email address or name. Registrations don't expire no matter how many new versions I work on and release. but obviously, since they are made based on your original purchase details, they won't be valid when associated with different identification. Pete

It's also called "Catch 22" these days, after the same sort of trap detailed in Joseph Heller's book of that name (also a film). However, doesn't the link I gave you help? I asked the SimMarket boss and that's what he asked me to tell you. He also asked me to make it permanent, for reference, so I've added the same advice in the FAQ subforum. Please do let me know if it doesn't work the way he implied! Pete

I would need to see the actual NWI writes you are making to comment on that. When I test using the WeatherSet2 program, which is the demonstration and test bed for NWI, it works. To understand what might be wrong in your case I would need to see exactly what you are doing. Maybe via logging? I won't have time in any case to look at this till December now, earliest, and i would be loathe to change anything because it is very old and very complex code and I'm likely to do more harm than good. It is also well used code, at least in the past. Nowadays good weather programs like OpusFSX and ActiveSky use SimConnect directly of course. The above also applies to your precipitation base question. I am really amazed you can find such discrepancies after all these years though. Well it involves much less for FSUIPC to do -- it simply passes it on without checking. so any errors are yours. ;-) It's really my best answer because I don't think I'm in any position to ever adjust or change the NWI. If that's where it is documented -- sorry, i don't have access to my reference documentation at present. I think you might still need to set the ICAO (or 'GLOB') ID into the C8xx area -- doesn't it say that? I don't know. i wouldn't have thought so. Why would there be a "correct sequence"? I'd need to refer to the Simconnect documentation for such data in any case. All FSUIPC is doing for you in the mode is sending the request on. You read the weather as documented. That populates both the NWI data areas AND gives you a METAR in the appropriate offset -- probably B800 as far as I recall? Please be aware that the formats of READING and WRITING weather are rather different in a number of areas. The documentation is not good for either. Maybe the documentation in the P3D SDK is better. I don't know. Regards Pete

If you need to raise any sort of problem with SimMarket -- for instead you forget your password or can't access your account for any reason, you should go to SimMarket via this link and report the details there: http://secure.simmarket.com/customerservice.php Regards Pete

I think you need to raise a ticket here: http://secure.simmarket.com/customerservice.php. Pete

The problem is right there, showing a lack of understanding and ignoring what I advised. I don't think you are an idiot, I just think that you are so over-confident in your assumed knowledge of FS that you aren't actually reading what I have been writing. 1. There is NO calibration to "uncheck" in FSX. The only calibration available outside FSUIPC is in the Windows Game Controllers, and that is basic calibration of axis ranges, not specific calibration of aircraft control surface movements which is what FSUIPC offers. 2. You can ASSIGN controls in FSX. That's all you needed to do if you hadn't already. Mostly FSX makes automatic assignments in any case for controls it recognised. 3. If you actually disabled controllers altogether in FSX then that is a problem as nothing is then assigned. Go back and re-enable those controllers. 4. For now, do NOT try assigning in FSUIPC at all. That is a more advanced process and needs considerations differently for many of the more sophisticated add-on aircraft. Igf you have already assigned things then it would be best to delete the FSUIPC4.INI for from the FSX Modules folder before loading FSX. 5. Once controls are assigned, the calibration in FSUIPC is a doddle and to do it properly and efficiently you simply follow the numbered steps. That's it from me. I really do try to help everyone, but some folks just will not listen, out of pride or what, I do not know. You can see how much support I give and have given, over many many years (through the completely free times of FSUIPC as well as more recently) by just browsing this Forum. I don't thin you'll find many 9 year old products supported to this extent, if at all. Even FSUIPC3 is supported when the need arises, and that is now 11 years old. Good bye. Pete

What's that supposed to mean? I try to help you and you reject the help. Why? Pete

The latest list of offsets (which hardly ever changes in any case) is always installed in your FSUIPC Documents folder when you update FSUIPC. I don't understand the reference to "drives"? The Logging tab in FSUIPC options is not "complicated"! You can select tabs in a dialogue and click on buttons, can't you? Otherwise you wouldn't be able to use any Windows programs really. The log produced may contain some things you won't understand so easily, but the logging of FSX events, or controls, is straight-forward, giving both the number and name of the control invoked. The full list of built-in FSX controls is also provided in your FSUIPC Documents folder, by name and by number. Did you look at the User Contributions subforum threads about the JS41 and what others have done? Pete

The client log you supplied is incomplete. Please always close the program down before getting the log as valuable information is presented at the end. As far as it goes (only one second of operation) there were no errors at all. I don't think it can relate at all to the session you describe. The Server log you supplied shows no connection was made at all, so it evidently isn't the one relating to the Client log, even though judging by the time stamps in each they overlap -- the one second run of WideClient being within the 32 minutes of the Server log time -- but perhaps your PCs have different times set? Either that, or Wideclient was actually connecting (or trying to connect) to something different. Pete

There are no separate "free" and "registered" versions, there is only ONE version of FSUIPC4 (for FSX and P3D) and one of FSUIPC3 (for FS9). The only thing which makes a difference is you registering it! I don't know how you think you are managing to download "different versions". All the links, wherever, point to the same files, hosted here in the Download Links subforum -- and that includes the links on the http://www.schiratti.com/dowson page and on the SimMarket purchase pages. The ZIP format is the standard one supported by Windows and all other zipping and unzipping programs. Many thousands of users have successfully downloaded, unzipped and installed them. Have you never managed to unzip any downloaded files at all? WideFS is never necessary for any other programs, it is just a way of running FSUIPC-using applications on a Networked computer to reduce the load on the FS computer and make use of other PC's screens, keyboards etc. Many programs which need FSUIPC to run do include a version of FSUIPC in their packaging and may automatically install it too. It is up to them. There has never been any restriction on such actions if third parties wish to take advantage of that. The only thing to be wary of then is that such bundled copies may well be out of date -- only the current version is supported. The FSUIPC installer installs it where it needs to go, inside your FSX installation, and does this automatically when you run it. Pete

If it says it is 4.703, then it is 4.703. Check the Install log file which should be in the Modules folder. Paste the contents here if you don't understand it. The most likely thing I think could happen is that your registry says that FSX is installed in a different folder to the one you are loading it from,. Maybe you made a copy at some stage and are using that. FSUIPC's installer expects the Registry entries to point to your installed copies correctly. Pete

BTW, you do realise, don't you, that if any of the actions you wish to control are actually using the normal FS control system, you can find out what it is (so you can assign to it) by using FSUIPC logging. Just enable the Event logging. When you operate the control with the mouse, check the log to see what it reported, if anything. If you (temporarily) run FS in Windowed mode, you can also enable FSUIPC's console log and see the results on screen in real time. While I'm hereagain, let me try to clarify something. Please disillusion yourself of the apparent thought that there are FSUIPC "offsets" for everything any aircraft add-on can throw at your system. FSUIPC is an interface to FS and knows nothing at all about any add-on. If the system you are interested in is simulated internally by FS then there will probably be an offset relating to ts value (but not necessarily its control). Add-ons are pot luck, they do their own thing, and pretty much 0% of them have any interface to FSUIPC or use any of its offsets. Pete