Pete Dowson

Okay, I found the problem with the 4.938 installer -- just a silly error. I forgot to increase an install count by 1: FSX, FSX-SE, P3Dv1, P3Dv2. That's 4. The count stopped at 3! Stupid! :-( You can re-download 4938 now. I've not changed the version number -- the FSUIPC is still the same. Pete

I'll look at the problem when I can. Trouble is I am running on a crippled system till at least Tuesday, when a replacement PC should be ready. Meanwhile, if this is your first time with FSUIPC, use the 4.937 installer: link Install FSUIPC4937. Pete

I did not say I would not try to do wind smoothing in FSUIPC, I just cannot locate the right places to hook. the code is just too different. I will try further in the New Year, but I cannot promise anything. This part of your post is confusing me. Are you talking about FSX or FSX-SE? Have you got any information whatsoever about G3D crashes in FSX-SE? I cannot apply the same patch in SE as I do in FSX because the code I patch just isn't there, or is there but is unrecognisable. And don't forget there are many other G3D crashes which FSUIPC never patched. Pete

Sorry, but there is absolutely no relationship between FSUIPC and the PMDG 777. I don't think the PMDG aircraft are even ready for SE yet. You need to go to the PMDG support forum. Pete

Not sure why that would be. I'll check it again. Thanks. Pete

I'm pleased to report that after a day of struggling (Friday) I got my development PC working well enough to do some work. I just dare not switch it off or I think it won't come on again!. It is crippled -- it won't run P3D because I had to substitute an older non-DX11 video card. but it was okay for testing with FSX and FSX-SE, FSUIPC Version 4.938 is now available, and works as best as I can make it with FSX-SE. The installer copes with both ways FSX-SE installs (free-standing or alongside FSX Boxed), and all the hooks appear to work except for the full wind-smoothing fiddle (rarely used these days with such good weather programs), and the "G3D crash" patch. In the latter case the code in that area has changed and i'm not sure whether the fix would still be needed in any case. Feedback on any of the FSUIPC facilities would be useful, but I may not deal with it now for a week or two! ;-) Oh, the latest version of MakeRunways, also available, also copes with FSX-SE's possibly different SCENERY.CFG location too. Happy Christmas! Pete PS If you downloaded it before 12 midnight UK time, and have P3Dv2 also installed, you may want to download it again so the installer can install into P3Dv2 as well. A silly oversight on my part. Sorry!

I'm pleased to report that after a day of struggling (Friday) I got my development PC working well enough to do some work. I just dare not switch it off or I think it won't come on again!. It is crippled -- it won't run P3D because I had to substitute an older non-DX11 video card. but it was okay for testing with FSX and FSX-SE, FSUIPC Version 4.938 is now available, and works as best as I can make it with FSX-SE. The installer copes with both ways FSX-SE installs (free-standing or alongside FSX Boxed), and all the hooks appear to work except for the full wind-smoothing fiddle (rarely used these days with such good weather programs), and the "G3D crash" patch. In the latter case the code in that area has changed and i'm not sure whether the fix would still be needed in any case. Feedback on any of the FSUIPC facilities would be useful, but I may not deal with it now for a week or two! ;-) Oh, the latest version of MakeRunways, also available, also copes with FSX-SE's possibly different SCENERY.CFG location too. Happy Christmas! Pete

I've managed to recover my Development PC enough to do some initial investigation. Originally I thought FSX SE compatibility was just going to be an installer revision, to find the right Registry entries and paths, but I now see that FSX has been recompiled with a later version of MS development tools, so it's going to be a bigger job than I thought. In other words, it is unlikely to be just a weekend job as I thought at first. I'm afraid that even if things go well on this invalided PC, Christmas, New Year and family take precedence over the next two weeks. So the estimate of 9th Jan I gave above is still really the more realistic one. Sorry. Pete

I don't know. Is it a standard joystick device, as seen by FSX? If FSX can see it in its assignments, then so can FSUIPC. But note that FSUIPC's button recognition is limited to the first 32 buttons (numbered 1-32 in FSX, but 0-31 in FSUIPC). Pete

The lack of GUID entries is worrying, but FSUIPC doesn't really care about them unless there are two devices with the same name. Then it needs the GUIDs to differentiate between them. As far as I knew, ALL properly registered devices have GUIDs, so I don't know what's going on in your system. The problem where with both connected neither are seen seems most likely to be a USB problem. Try different USB sockets, and not two of a pair (on the PC each pair of USB sockets has the same controller). It might just be power -- if you are using a USB Hub make sure it is powered, but in any case also try directly connecting to the PC, not via the hub. You didn't actually say whether FS can see the devices, or Windows for that matter? Pete

Unfortunately my development PC finally died this afternoon. There's been an intermittent mobo fault on it for a while and Ihave a replacement PC on the way, but it isn't due till next Tuesday, and by then I will be tied up with family for Christmas. Then I'm away till 4th Jan. I'll get on to FSXSE as soon as I can after that, but it'll take me a day or two to get the new PC into shape -- and re-download FSXSE. So, sorry , it could be around 9th Jan by the time I have something. Sent from my iPhone! Pete

I purchased the Steam edition yesterday at the introductory price specifically so I could check and adjust the Installer. However, I was out all evening so I was unable to go further. I will be downloading it today and should be able to have a revised install package ready over the weekend if not before. Pete [ouch computer died -- see later message]

Just remove the aircraft name from the [Profile.<profile name>] section of the FSUIPC4.INI file, in your FS Modules folder. Please always post support questions to the Support Forum. The FAQ subforum is a repository of standard answers, not a place for new questions. Thank you, Pete

As I am sure you will find the User Guide clearly explains, the Delta value is simple the smallest CHANGE in the value from the joystick which will have any effect. For example, with the maximum range a joystick can provide, 32768 (ie -16384 to +16383), the default Delta of 256 gives 128 different positions. That's about normal for most consumer level devices. The whole point of the Delta is to prevent minor unreliable changes (jitter), usually caused by small electrical, temperature, humidity or just plain dirt changes affecting the otherwise smooth flow.For software controlled inputs the Delta is usually changed to 1 so that the software has precise control. But it sounds like you increased it, so giving fewer different axis positions and thus apparent jumps. Null zones are produced by correct calibration, following the numbered steps given for this in the User Guide. Pete

Doesn't the B1900d use standard FS controls for most things? It is usually only the very complex add-ons like PMDG 737NGX which replace all of the FS sub-systems with their own and therefore need special attention. Enable FSUIPC's event logging, in the Logging tab, and also the console log. Run FS (temporarily) in Windowed mode, so you can see entries into the log in real time. Then operate each of the switches you want to program, in turn. see what is logged. Otherwise, check to see if the B1900d accepts keystrokes to operate the switches. If so you can assign those. Finally, many modern add-on aircraft do use local panel variables (L:Vars). There's an FSUIPC control you can assign which will list them and their current state, or you can log them as they change using a Lua plug-in provided in the Examples ZIP in your FSUIPC Documents folder. Pete

These days there are fewer and fewer cockpit gauges which are compatible with the Mouse Macro facility. Such gauges need to have been written strictly in accordance with Microsoft's C/C++ gauge SDK. Even the default FS gauges are hardly covered. And more and more cockpits now are written using XML for the gauges. These are usually more amenable to the Local panel variables method (L:Vars) instead, however. If you refer to the Chapter on Mouse Macros in the FSUIPC4 User Guide, on page 36, the very second paragraph explains this restriction, in bold italics! Pete

Nothing in the FSUIPC Installer can possible "mess up his system". It simply replaces the modules itself and updates the documentation and Lua package as well. There's a maximum of 127 Lua modules recognised and listed in the [LuaFiles] section of the INI file. Unwanted ones should be deleted in there and in the Modules folder. Also Lua filenames should be limited to 16 characters before the .Lua part. I cannot support old versions of FSUIPC. The current Lua function set is far greater than the original so most of the useful functions will not be in such an old version inany case. Pete

Well, the second paragraph in the Lua document "FSUIPC Lua Plug-Ins", in your FSUIPC Documents folder, tells you it first implemented in FSUIPC versions 4.211 and 3.841. You can find the approximate date of those in the relevant FSUIPC History document -- 4.20 was October 2007 and 4.25 was February 2008, so that places it either very late 2007 or January 2008. I have to work it out as above. I don't keep historical records that far back! ;-) Pete

Flight Sim Universal Inter-Process Communicator. Not my choice of name, really. It derives from Adam Szofran's names "FS5IPC" and "FS6IPC". The original purpose of these was to provide access into FS's inner variables, for display or control, by add-on external programs. This is also FSUIPC's main function, and the part which has always been free -- the pay part is the added User Facilities. Adam did not maintain his FSxIPC module after FS98, and when I did the first replacement I decided to retain the same interface for all subsequent versions of FS, so allowing continual compatibility for add-ons. (Adam's modules required revising add-ons for each version). Hence "Universal" instead of "FS5, FS6 ...". Pete

Well, that last line is not executed. The !1= in front of it makes it a comment -- i.e. this user has commented out the running of "fraps". So, you also just happen to have TrackIR and FSXWX also installed, and in the same folders as this other user? Coincidence? The extra run looks okay, if that's where your "Plan-G3" program is. So the crash is nothing whatsoever to do with these lnes, because they all have the "ready" keyword, which means those programs will not be started until FS is ready to fly. In fact the lines will not be processed during FS initialisation. There is nothing in FSUIPC's INI you can corrupt which will cause a crash. And in any case, all re-installing does is replace the FSUIPC4.DLL module with the same FSUIPC4.DLL module. It changes no settings, nothing else. It wil replace your FSUIPC Documents, but they don't play any part in running FS. Ah, so that is more likely a problem with one of the programs you are now trying to load -- or did you still leave the [Programs] section out of FSUIPC's INI file? Well, from an FSUIPC point of view, the first thing to do is look at the FSUIPC4.LOG file, to see how far it got. Maybe the clue is right there. Since FSUIPC is not loading Ezdok, I assume you have programs and modules being loaded by SimConnect via the EXE.XML and DLL.XML files. You might also need to look at those, to see if all of those loaded and if not which one it failed on. Pete

If both sides are assigned AND calibrated in FSUIPC, then FSUIPC will arbitrate between them. It will take only one of the competing values -- the one with the greatest divergence from "normal" (i.e. centred for yoke and steering, idle for throttle). If one is interfering with the other it must be because of some serious jitter, I suspect that the more likely thing is that you have multiple assignments from the same devices, possibly in FSX, You need to disable controllers altogether in FS. Have you tried usng the FSUIPC logging facilities to see what is going on? If you enable the console log and temporarily run FS in Windowed mode, you can see the axis events as they occur. Pete

I moved this from the specialist programming subforum about .NET client DLL into the general support forum. Please remember always to post support questions into the support forum. On this particular question, as well as what Vic says, please see the FAQ subforum thread "FSX fails to run after FSUIPC4 first installed", which essentially discusses the same SimConnect problem. If that doesn't offer a suitable solution, please take a look in the FSX Modules folder, see if there is an FSUIPC4.LOG file produced. If so, it may not be the usual SimConnect problem, but another initialisation error -- for instance, corrupted start-up weather files can have this effect too. If it is making a new file each time, then I need to see it. Paste its contents here, using the <> button above this edit area to enclose the text. Pete

Okay, good. There are two ways of logging L:Vars -- the built-in FSUIPC added assignable control, which gives a static one-off list each time it is invoked, and an example Lua plug-in, which logs the values live, as they change. Pete

I just noticed that the User Contributions subforum does have a thread about the A2A P47, giving some uses of L:Vars (not ones you want). And I think it is also listed in another thread there as not amenable to mouse macros. Pete