Pete Dowson

Certainly not FSUIPC. Pete

You'd need to use a little Lua plug-in, with just the one line: ext.run("<path of program>\\XYZ.EXE") where the path is, of course, points to where the program resides. Save it to the Modules folder, then, in FSUIPC options, assign you button to that Lua plugin. There are lots of facilities for external programs in the Lua ext library. The Lua documentation is in the FSUIPC Documents subfolder in Modules. Pete

No, after installing it just copy over your FSUIPC4.INI file and any .mcro and .lua files you might be using from your FSX Modules folder to the new FSX-SE folder. Or, if in doubt, after installing in FSX-SE, copy the whole contents of the FSX Modules folder over to the FSX-SE Modules folder, then re-run the FSUIPC Installer to get the module back up to date. If you are going to first uninstall FSX, be sure to save the complete contents of the Modules folder someplace safe. Pete

Please report this on the Active Sky support forum, as it must be something their end. There is no way FSUIPC is even touching the radar facility unless you opt for it, and in any case ASN should be able to cope with more than one program asking for it. Pete

All that information is to enable FSUIPC to support Weather Radar for users and for FSUIPC client applications, such as Prosim737. It has nothing whatsoever to do with what PMDG does. I suggest you remove any ASNWx lines from the INI file. They should not in any way affect PMDG (because the ASN facilities are independently available to all), but you are just wasting processor time if you are not using the resulting files. As stated (and you actually quoted above!!!) they are in the Lua examples package, as installed with FSUIPC and referenced in the Installation document in the original download ZIP for FSUIPC. How is it you found the WX radar document but not the file in the same folder it referenced explicitly? But you don't need them or want them unless you are implementing your own WX Radar display! Pete

Such behaviour is a result of the way the original Saitek drivers set the Registry incorrectly, defining some axes as "digital" (on or off) rather than analogue. This is the most frequently reported problem with Saitek throttles, and I'm sure a solution must be provided somewhere on the Saitek site or support forum, but i'm afraid I don't know what it is. Pete

No, none that I know of. SimConnect just adds them on an as-received basis. FSUIPC's should normally be in the same order, and, with luck, together. Pete

The freeware version is the same version. The documentation is already in your FSUIPC Documents folder, just as the Installation & Registration document explained (the one in the download ZIP). I understand Saitek have a support forum. You could check there for Saitek problems. I don't think there are any specific to FSUIPC. The only regular problem I ever see here which is specific to Saitek is that somehow their installer screws up some parameters in the Registry which can make one or two of the quadrant levers operate digitally (i.e. on/off, not smooth). I'm sure that one must have been fixed by now. And it wouldn't be specific to use in FSUIPC in any case. FSUIPC doesn't care or know about specific devices nor about specific aircraft add-ons (excepting only that it does have mapped values for the PMDG 737NGX). I think you need to peruse the documentation, I get the feeling that you might be confusing FSUIPC with a device driver. Yes, fine. I am only explaining that FSUIPC doesn't appear to be what you think it might be, that's all. If you read the document which came with the downloaded file, it tells you where to find the documentation which in turn tells you what FSUIPC does. Pete

You don't need to buy it. Just install it and the documentation will be installed. There are many more users who have not bought it than those who have, mainly because it is used by so many other applications -- that was always its main purpose, for which it is free to users. Things like joystick assignments and calibrations are additional user facilities which purchasers get, but it isn't its main purpose at all. Saitek are just joystick devices like any other. I don't like them, but that's just my personal opinion. But they are all alike as far as FSUIPC (and FS for thatmatter) are concerned. They are HID (Human Interface Devices) controlled and interfaced by Windows. FSUIPC reads them, if you wish, just like FS does, it just provides a wider variety of assignment and calibration options. Reverser methods depend more on the model of aircraft you are adding, and how it treats throttles. PMDG aircraft tend to be different from the rest, and, of course, good Airbus implementations act like real Airbuses which don't have true throttles in any case, just thrust modes. Without FSUIPC setting up reversers is a lot more difficult on most aircraft. FS doesn't have separate inputs for them. No. Use FS itself then. I'm not advising you to buy it. I'm actually not sure even why you think you might want FSUIPC if you've seen so much difficulty with it, so much criticism, and no one complaining about the same things with FS? Pete

Okay. Glad it is now sorted. Pete

That IS a file with filetype log!!!! It is called FSUIPC4.fsx.log to be exact. You ignored me when I asked you to changed the folder option so you didn't have Windows hiding things from you as if you are an idiot! Running inside Prepar3D v2 on Windows 7 ... Prepar3D has been renamed as "fsx" The problem you have is that you are running FSX but the Registry says it is Prepar3D. So FSUIPC is treating it as a renamed P3D. How on Earth did you get into such a mess? Please find the Install text file which is also a LOG, and show that to me. I might be able to help you unravel the mess your system is in. After you've changed the Windows Explorer option so you can see filenames properly, check whether there's a "Prepar3D.exe" file in your FSX folder -- there should not be. It may be that which is fooling FSUIPC that you are using P3D renamed as FSX (which folks apparently do to install programs which don't know about P3D). Delete Prepar3D.exe if it is there. Pete

Two logs, in the Modules folder, where FSUIPC is and the FSUIPC Documents folder where you would find the FSUIPC Documentation you must know about. There is nothing of FSUIPC ever outside the Modules folder. Pete

Ha ha. It's just that I don't much like P3D so don't use it. It is only installed on my development PC for testing and development. Whatever is causing the error could well be causing the problem,yes, but the logging itself won't. I've had full SimConnect logging on and 32000 lines is nothing once you've seen what that can produce -- and in a lot less that 1 hour 40! 32000 lines a minute, is closer (exaggeration for effect, sorry) -- but no stuttering is caused even then, just a large file which would be written at low priority by the clever Windows file system. But if you really think it might simply be the logging of the errors causing your problems, I can add an option to suppress it. Trouble is it will suppress logging of all reported SimConnect errors and some may be (more) important. Something is happening after a time, though, that's the point. What other add-ons are you running? The Battery Voltage is FSUIPC offset 2834. Other programs might be accessing it too. FSUIPC only uses it for the "magic battery" facility. The thing is, though the ID it uses is always the standard one meaning the User Aircraft. I've no idea how that can be corrupted -- it is used for many of FSUIPC's actions so if it was truly bad in FSUIPC you'd get thousands of other similar errors too. So it must be somethinig happening further down, in SimConnect. You could actually get a SimConnect log which would show more -- but with it not starting for 1h 40m you'd have millions of lines of entries before the bit we'd need. Especially with PMDG which uses SimConnect even more than FSUIPC does! Pete

The offsets are populated from SimConnect variables. I've never looked at them myself -- FSUIPC simply gets them sent to it by SimConnect when they change. Pete

If you get that far there is most certainly a log. There will be two in fact, one from the Installer and one from FGSUIPC run-time. You probably have Windows hiding the filenames from you and calling them things like 2text files" and "configuration files". Please just change the Folder options in Explorer! A previous version of what, and why? I cannot confirm what your problem is, but it is most likely acorrupt Weather file. The log should tell me. Pete

I haven't, sorry. I know nothing at all about the GPS. There are some GPS values mapped to offsets, but I don't know exactly what use they'd be. The stuff available includes: 132C GPS is driving NAV1 indications 6004 anumber of flags about GPS modes 60FC to 6170 a load of stuff, mostly about approaches Aren't any of those useful at all? Pete

Oh, so nearly 1 hour and 40 minutes into the session? Hmm. I've never run P3D for that long! What are all the "stops" before it? I only have default aircraft. But if it does it with any of those I suspect there's something wrong in your installation. Pete

I'm not sure if you are asking about some FSUIPC control assignment, or if this is really an EZDOK question, in which case you are in the wrong place. It makes it more confusing adding to an existing thread which appears to be about a different subject? Pete

I never did that for FSX because it wouldn't work in ints full screen mode, but it might with P3D because its full screen mode is, I think, just a borderless windowed mode (?). However, it can of course be done with WideClient. You need to set the ClassInstance parameter to a non-zero value, otherwise it won't run next to FS. Pete

Just count the number of times you create and destroy the Window. I'm sure it must be related to that -- but the problem it occurring deep in P3D code. I can't fix it myself. If it is a serious problem for users I would just remove the option for a plug-in's own separate Window for P3D. Right. Well, it seems that the L-M display facility I'm using (and bear in mind it was found in FSX by experimentation and hacking into the code, so I can't really complain to L-M) is not designed for use the way we could in FSX. Maybe it is a bug, maybe it is due to the way they are trying to reduce VAS usage. No, I think that's just the window appearing in its usual default position before the set position operates. It doesn't happen here, but my development PC is rather overloaded with other windows already. And it may be more obvious in full screen mode. It would be good if someone with an older version of P3D could check to see if it is a recent change in P3D. I might be able to find one in my archives. When I get time. Pete

Yes, I can reproduce it here too. But it is okay in FSX and FSX-SE. Do you know if it happened in earlier versions of P3D? I wonder whether the problem is because you are creating too many windows and overflowing the table allowed for them. Maybe when I close them in P3D their table entry isn't cleared down? I know it says you can use the setowndisplay more than once in a plug-in, but that was intended to allow the occasional need to re-size it or move it. But the real purpose was to allow separate plug-ins to have their own separate window, not recreated one every second. Doing that may be messing something up somewhere. (Why would you want to do it in any case?) If I rewrite your test example as: function DISPLAY()n = ipc.elapsedtime()ipc.display("The current FSUIPC Elapased Time = "..n)endn = ipc.elapsedtime()ipc.setowndisplay("FSUIPC has been running for "..n.." milliSeconds", 2, 40, 95, 10 )DISPLAY()event.timer(1000, "DISPLAY") then it seems okay, so I'm pretty sure it's the call to to close and create a new display all the time which is the problem.Of course you don't get the flashing or the title changing with the above method, if that's what you really wanted. Maybe on L-M (only) I shall have to prevent the use of setowndisplay more than once or twice. Pete P.S. It might be worth reporting to L-M if it is a new problem. They may just say I'm abusing the functions I'm calling, though.

Where is the other thread? Can't find it. The battery voltage is written to in order to operate the extended battery life option on FSUIPC's Miscellaneous options tab. The ID should be the ID of the user aircraft, and is standard. At what stage in that log did the first such error message get logged? Does it occur with all aircraft? Does it occur without that option enabled? I have enabled the battery life option here and do not get the same problem with the aircraft I have tried. It is possible for other addons to send these things to FS through FSUIPC, so check addons too. Pete

That's okay. The log for a working install isn't really of a lot of interest of course! ;-) Pete

I can't really help with a crash in SimConnect. It may happen only when FSUIPC is used because FSUIPC uses SimConnect 100% of the time. Does it crash at any old time, or during start up? Can you see if there's an FSUIPC4.LOG file produced. If so, please show it to me. Pete

What is "VAFS"? Does it use FSUIPC? Pete