Pete Dowson

It's this new Forum software. I edited the text but there's a hidden link behind. Damn. fixed now. I'll need to remember that. Thanks, Pete

Okay. I fixed it by making the sound playing routine run in the main FS thread. It seems that, on WinXP, the termination of the thread playing the sound kills the sound too. This doesn't happen in Win7 which is why I never spotted it. Please download 3.989e or 4.628 from the Updates topic in the Downloads sub-forum above. Regards Pete

As you said: i.e. SimMarket order receipts, names, email addresses, and which registration you want changing to match the other. Regards Pete

Well, that's a new one on me. Sorry. It certainly has never done that here. I cannot understand why it should do such a thing. I think you must ask Robert about this, about why it is messing with MakeRunways -- which really should NOT be run whilst FS is running as it is accessing all of the BGLs which might clash with an FS access. It really does sound like a bad bug in IYP. I can't help, I'm sorry. I cannot imagine why Robert referred you to me. And for sure I cannot see why RC4 and MakeRunways has anything whatsoever to do with finding ROUTE.BIN. Please do feel free to quote my replies when talking to Robert. Regards Pete

So, do you have a question? Pete

For WideFS problems with Windows seemingly translating the FS server PC's names into IP addresses on the Internet, please see section 10 on page 4 in the WideFS Technical guide.

FSUIPC7 documentation only (without Installer) FSUIPC7_Documentation --- When FSUIPC7 is Installed, these documents are optionally installed in a folder called FSUIPC7 under your Documents folder FSUIPC6 documentation only (without Installer) FSUIPC6_Documentation --- When FSUIPC6 is Installed, these documents are optionally installed in a folder called FSUIPC6 under your Documents folder FSUIPC 4.975 documentation only (without Installer) FSUIPC 4.975 Documentation --- When 4.975 is Installed, these documents are placed automatically in the FS Modules \ FSUIPC Documents folder Revised list of FSX controls FSX and P3D Controls Note that not all of these necessarily work -- though I know for sure most do! FSUIPC 5 and FSUIPC6 produce are more up to date list as a text file automatically -- check your FSUIPC Documents folder. FSUIPC 3.999z8 documentation only (without Installer) FSUIPC 3.999z8 Documentation --- When 3.999z8 is Installed, many of these documents are placed automatically in the FS Modules \ FSUIPC Documents folder SIMSAMURAI's FSUIPC Tutorial Sim Samurai Tutorial --- Updated on 18th January 2010. FSUIPC 4.60 documentation in FrenchFSUIPC460Francais --- Translation kindly donated by Mr. Philippe Hantzberg, 19th March 2011 WideFS documentation in Frenchhttp://philcl.durand...Utilisateur.htm --- Translation kindly donated by Mr. Philippe Durand, 4th July 2011 WideFS documentation in German: WideFSundFSUIPC.pdf --- Translation kindly donated by Mr. Sibylle Berdermann-Welz, June 2022

Full FSUIPC SDK (all versions) FSUIPC SDK Updated 27th August 2020 with: - New version of Java SDK (32 & 64 bit), courtesy of Radek Henys (@Mouseviator). Updated 22nd December 2018 with: -- New version of the Python section of the kit, courtesy of István Váradi vJoyOffsets - a utility program for linking FSUIPC offset values to virtual Joystick inputs: vJoyOffsets -- requires the freeware package vJoy, provided by Shaul Eizikovitch 64-bit Module User kit on its own ModuleUser64 64-bit External User kit for C/C++ on its own UIPC64 SDK C maxx's free SPAD: Saitek Panels Advanced Driver Go to http://fstools.weebly.com GPSout version 2.61 for use with FSUIPC3 only (FS2004 or before) GPSout 2.61 -- Adds option for Sim Mode field added to the RMC sentence (for Apple devices) -- Signature removed ShowText by Rob van der Wiele ShowText TrafficLook accessory program TrafficLook Version 1.551 includes an Airport filtering option Version 1.56 displays nearest traffic information in the title bar (needs FSUIPC 4.966 or later). Version 1.57 works on Windows XP through to Windows 10. Version 2.01 is just a re-build using up to date tools. WeatherSet accessory program WeatherSet WeatherSet2 only, Version 1.60 WeatherSet2 Version 1.60 of WeatherSet2 handles FSX Global Mode multiple visibility layers, and "GapAbove" surface wind. HidScanner: A little program for scanning connected (or even just Registered) Joysticks and other HID (Human Interface) Devices and providing full details. It can stay running and monitor changes too, if needed: HidScanner GFdev64.dll for GoFlight users (P3D4 & P3D5 only) GFDev64.dll This is version 2.2.2.1 (January 2013). GFdev.dll for GoFlight users (FS2004, FSX, P3D1-3) GFDev.dll This is version 2.2.2.1 (January 2013). GFdisplay version 1.30 for Goflight users (FS2004 or FSX) GFdisplay 1.30 (Now including GF-MCP Pro support) Flight plan converter, FxmlToFLT, FxmlToFlt.zip This utility, written and copyrighted by John Nunez in 2014, converts the new format "FXML" flight files into the older format "FLT" for use by unmaintained programs such as RCV4 (Radar Contact version 4). RCV4 provides restart options from saved flights but can only read the old FLT format. Make Runways utility version 5.131 MakeRwys.zip For use with FSX, FSX-SE, P3D1-6, and MSFS. See the READ ME included in the ZIP. Note that MakeRunways is now closed for further development, as Peter Dowson, the original author of this product, has now retired. However, you can download the source and update for your own needs. The source code for this utility is available on GitHub at the following location: https://github.com/jldowson/MakeRunways/. If you would like to take over development and support of this product, please PM me (John Dowson). Please note that this version of MakeRunways is not suitable for use on Win7 based systems or earlier. It is also not intended for use with FS2004 (FS9) or earlier It is aimed primarily at P3D and MSFS, though will also work with FSX and FSX-SE, on a Win10 system. For older system setups please use MakeRunways version 4.70, listed below. Note that for P3D3, P3D4 and P3D5 , this version uses a Lorbi-SI's AddonOrganizer derivative called "LorbySceneryExport", (included with MakeRunways) to create a scenery.cfg fil it can use even when the scenery add-ons are distributed according to various XML file. Please see the document included in the MakeRunways ZIP! Also note that MakeRwys is not able to decode, or even find, the BGL files installed from the Microsoft Store which are encrypted and likely hidden. For airports added in this way the data you'll get will be from the default airports. -- Version 5.131 added support for P3Dv6 -- Version 5.13 fixes a very old (22 year) bug affecting some fields in the r5.bin file (binary runway data).. -- Version 5.129 fixes the /Jetways option -- previously it didn't flag the correct gates in many cases -- Version 5.128 includes changes in the MSFS data scanning to avoid problems with overlong file pathnames -- Version 5.127 has an encoding declared which allows accented characters in strings -- Version 5.126 just adds extra logging (in the Runways.txt file) for diagnosing MSFS scenery path problems. -- Version 5.124 processes any visible unencrypted add-on scenery installed in the Official\OneStore folder after all the default (fs-base), Asobo and Microsoft scenery. -- Version 5.12 fixes incorrectly attributed threshold offsets when process older style sceneries. -- Version 5.11 fixes the /+Q ("quiet") option so the program now properly terminates. -- Version 5.10 is a 64-bit version, to allow for the much increased amount of data assembled when used with MSFS. -- Version 5.02 copes with 8.33kHz spaced COM frequencies in its f4 and f5 csv files. The current f4 and f5 files will only contain 25kHz compatible frequencies, with the 8.33 ones converted to the nearest. Applications which can handle the 8.33kHz spacing frequencies should use the new files f4x.csv and f5x.csv. -- Version 5.01 correctly decodes the MSFS runway surface GUIDs for the Runways.xml file -- Version 5.00 is the first which also handles MSFS airport data. -- Version 4.91 Fixes an omission in version 4.90 for the new P3D5 format airport files: version 4.90 omitted runway threshold offset, approach lights and VASI information. -- Version 4.90 can handle the new airport data types for runways, taxiways and gates being used in Prepar3D v5 in order to support sloped runways. -- Version 4.880 corrected the incorrect classification of "no draw hold points" as gates. Such hold points have been used more recently in addon scenery in order to get the default ATC to recognize AI ready and waiting when the actual visible hold point, previously used by AI, is too far for the rather dumb default ATC. Make Runways utility version 4.70 MakeRunways_470.zip For use on Win7 systems (or earlier) with FS9 or earlier, and FSX, FSX-SE, P3D1-3. See the READ ME included in the ZIP. If you are using Win10 then you should use version 5 of MakeRunways, listed above. FliteStar plans exporter, FStarRC, version 2.31 FStarRC.zip This update works with versions of FliteStar/FliteMap up to and including 9.5.2.1, and with the latest FStarRC.rws and F5.csv files produced by MakeRunways 4.52 or later. -- Signature removed EPICINFO5 Beta version 4.941 for FSX/ESP EPICINFO5 Beta 4.941 For use only by experienced EPICINFO users. This is the DLL only, which was etrieved from archives after an unintended absence of 6 years, but without any documentation at all. It cannot be supported at this time. MixW freeware virtual port simulator (not for Vista/Win7 or 64-bit) MixW Freeware HHD freeware virtual port simulator at http://www.hhdsoftwa...al-serial-ports (works with bioth 32-bit and 64-bit Windows 7) (Alternatively, for Vista and Win7 try the Eterlogic one, 32-bit version is free, 64-bit reasonable at $25 (U.S.): VSPE Website

If merely registering FSUIPC causes it not to work, then either you are using an illegal pirated registration, or the date set in your computer is before the Registration date, making it look invalid. Rather than post a whopping great picture just the FSUIPC log would have been more appropriate. Additionally I ALWAYS need to know the version number of the FSUIPC you have installed (though that too would have shown in the Log). Pete

What is this "weather engine"? Why is it using FSUIPC, if it is, on FSX? SimConnect provides the weather interface for FSX. I don't know of any way FSUIPC can be sensitive to geographical location, so possibly it is a scenery problem, causing corruption inside FS. Hmmm. The part of FSUIPC which responds to that is running in the main FS thread, so it cannot be FSUIPC which is "hung" else FS itself would be hung. The Windows menmu system uses messages via the main message window, however, so possibly that is being overwhelmed. Do any of the other menus in FS fail to respond? If not I can only thing there's some localised corruption, again implying a scenery problem. Does the FSUIPC4.LOG file show anything odd? Regards Pete

There is no way that I would ever change FSUIPC to allow both different names and different email addresses. That makes no sense and loses any proper "one person" registration protection. Don't forget that unlike many products I am not using machine identities because i want to allow you to use my programs on any machines you use. The only way is to send everything to petedowson@btconnect.com and let me make you another key. SimMarket would also do that for you -- you simply raise a problem ticket and explain. When I'm away (as I was) that's far faster of course. Yours is the first ever case, in 7 years, of a different NAME being used. I had thought that by allowing different email addresses there would no longer be any problem! Pete

Sorry, don't see it. But are you saying that IYP instructs you to run "MakeRunways" everytime you are running FSX and IYP?That makes no sense at all, I'm afraid. makeRunways processes all of your scenery and compiles data for RC. What does IYP want you to do this for? I use RC4 mode too. It shouldn't be. IYP only reads it in order to know the destination, so it can tell you things. It shouldn't fail or hang if there isn't one. Yes, but the ROUTE.BIN file is created by doing that too -- it is read by the PM PFD/ND program in order to display the magenta line and other details, and by the MCP in order to control LNAV and VNAV. In my case I find that IYP happily reads the ROUTE.BIN file after that point in the checklists where I've ready=programmed the CDU. You must select RC4 mode, as I do. Regards Pete

If Windows recognises all of the buttons and axes, and there are no displays to update, then you don't need anything else but FS. You can use FSUIPC too, if you wish. I don't know what the Saitek software does. Just look in Windows Game Controllers, make sure everything you need is seen by Windows. Regards Pete

Ah ... I (think I) see! Pete

No idea. I can't explain the default choices made by FS. They are defined in files in the FS folder someplace. You can reassign easily enough though. Check FS help if you don't understand FS. What is there to understand that you need? If you are wanting to simply calibrate in FSUIPC, just follow the numbered steps. You don't need to read anything else. Keys? What does this have to do with rudder pedals and such? Keypresses are a totally separate subject. what do you want to do with those? Well, you seem to have assigned some buttons and calibrated some axes. And I see you are ASSIGNING axes in FSUIPC too. Any good reason for that? Certainly, if you assign buttons and axes in FSUIPC you should not also assign them in FS or you will get two, possibly conflicting, actions for each. If you don't want anything assigned in FS just disable the controllers there. Regards Pete

Yes. Miguel has referred me to Burkhard's forum and asked me if I wanted subforums. I've said yes, with subforums: FAQ Announcements Download links User contributions This should allow me to put the old "stickies" in the User part, my download stuff, in categories, in the Downloads part, and split the old Announcements into real Announcements and answers to FAQ. Oh, you think it might be better split by subject instead of (or as well as?) function? I'm not sure I like that as I like to work through things in sequence. Regards Pete

Try calibrating in FSUIPC and setting the slope you desire for the areas you want more "sensitive". Not that the notion of "sensitivity" is ambiguous. It could be used to refer to the amount of movement you get in the real surface for movement of the stick (more being more "twitchy", less "controllable") or the reverse, fine adjustability for more positions on the stick -- a lot of stick movement for bigger changes, but more fine control or surface "sensitivity". One is represented by slopes with a flattish centre and the other by slopes with a steeply sloping centre. Pete

What performance and setup problems? Pete

No. Is this for FS9 or FSX or neither? Wind smoothing is not 100% effective in FSX in any case. The wind smoothing smooths changes to wind speed and direction when these are explicitly changed. Things like gusts and variance are not affected and in fact can be added or enhanced by FSUIPC -- though your best weather control will come not from FSUIPC but weather add-ons such as ActiveSky. You don't need a registered install of FSUIPC for those. The best way of finding out what facilities FSUIPC offsets is to install it and read the User Guide sections which interest you. youdon't need to purchase a registration for this. Regards Pete

I'm afraid I can't tell from the posted copy whether it is okay or not. This new forum software seems to remove all of the control lines. Could you try putting files into "code" brackets? (after pasting, select the data and click the "<>" btton above the message entry area). Is there an FSUIPC4.LOG file in the Modules folder? If so, it won't be a DLL.XML problem -- show me the Log file please. Regards Pete

Why are you messing in the FSUIPC INI file? Buttons and Switches, whether for a WideFS client or local on the FS PC, can be assigned in the FSUIPC options -- see the Buttons & Switches tab! Keypresses on a Client PC are NOT sent to the FS PC unless you set the option for this in the WideClient.INI file ("SendKeyPresses"). And for WideClient to see the keypresses it needs the keyboard focus. Generally this is not useful. Better to use the "ButtonKeys" facilioty in WideClient.INI and get your keypresses operating virtual buttons in FSUIPC, where you can then assign them. Regards Pete

Did you re-enter your registration in the Installer when installing on your newly-reinstalled Windows PC? Any former registration is wiped out by Windows re-installation, you need to re-enter everything. Run the Installer again. Regards Pete

No, there isn't. FSUIPC can't interfere with how specific aircraft interpret FS controls -- and certainly not mouse operations, if you are using the mouse. You could enable the Event logging in FSUIPC's Logging tab, then check the log to see what is being send when you are changing the heading. Maybe something could be fiddled, but otherwise it's a case of a bug report to the aircraft makers. Regards Pete

When I've caught up with things and can find my way around a bit better, I'll try. Do you know how to do it? At present, altough I'm supposed to be the Moderator I can't even delete posts except my own, same as anyone! :-( Pete

This all happened whilst I was away. I think it's horrid now, but it isn't in my control. Is that even possible? I'll have to check. I'm having a job finding my way around in this mess. :-( Pete