Pete Dowson

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

There is no "data it can make" which causes this, only the possibility that you have not calibrated it at all. I can't tell without more information -- check your FSUIPC4.INI file. You can paste its contents in a message here if you want. Pete

Unless you've disabled it, the default FSUIPC access capability to frictions is listed n the start of the log like this: --- SIM1 Frictions access gained and basic values patched along with several other successful hooks So check that. If you want logging of Lua plug-ins loading and ending then you have to enable Button/Key logging, or for much more info, Lua debug/trace. You don't mention how you are loading the Lua plug-in, so I can't really suggest much else. Pete

After you install it you will finf the there is documentation explaining everything in the FSUIPC Documents subfolder, in the Modules folder. The "User Guide" contains everything, including step-by-step (with pictures and numbers to help) calibration. Unless you want to do ambitious things, it is simple. It is like a box of tools --.you just use the ones you understand and need. Pete

I can't see anything which would do as you say in the Lua. I don't understand the rest as I don't know HIDMacros or the taxi program, I assume you want to write 1 to the 16 bit word at 66C1 (why a full word, not a byte?), and cancel with -1. Why not 0? Will the HidMacros action try to keep writing 1 or does it wait for the -1? And are you sure nothing else you use is also using 66C1? Try, say, 66FF as a "SB" type. Pete

There is no mapping for the 777 yet. I do not ant to buy and install the 777 as I have no use for it, so I am waiting to see the SDK if and when it is available. Pete

No wonder your Throttle aren't working! First off, you have two different AIRBUS profiles, but in both you have an FSUIPC assignment for Throttle 2, but none for throttle 1! [Profile.AIRBUS] 1=Airbus A320 United Airlines N465UA [Axes.AIRBUS] 0=2R,256,D,23,0,0,0 flaps 1=2U,256,D,22,0,0,0 spoilers 2=2V,256,D,10,0,0,0 throttle 2 But at least this profile has some sort of calibration: Throttle1=-6875,-512,512,5216/32 Throttle2=-5365,-512,512,6496/40 The other profile, also only with Throttle 2 assigned: [Profile.AIRBUS X] 1=Airbus A320 US Airways [Axes.AIRBUS X] 0=0R,256,D,23,0,0,0 1=0U,256,D,22,0,0,0 2=0V,256,D,10,0,0,0 has no proper calibration at all, just a fixed position! [JoystickCalibration.AIRBUS X] Throttle1=-7132,-7132,-7132,-7132 Throttle2=-5333,-5333,-5333,-5333 Well, if you use Joystick Letters, so that FSUIPC would recognise your devices by name, then you could use the same INI file in both. Even as it is you cuold copy over the calibrations sections. HOWEVER, looking at that, it was a mess too. For instance: [Profile.Twin Engine Airbus and Boeing] 1=Boeing 737-924 United Airlines (Merger) Winglets [JoystickCalibration.Twin Engine Airbus and Boeing] Throttle1=-16380,-512,512,16380 Throttle2=0,0,0,0/16 Throttle3=0,0,0,0/16 Generic calibration: Throttle1=0,0,0,0/32 Throttle2=-16380,-512,512,16380/32 and this profile: [Profile.AIRBUS] 1=Airbus A320 United Airlines N465UA had exactly the same issues as in your new INI. Quite honestly, I think you'd be best off deleting the INI and starting again, following the User Guide steps exactly for the calibrations. Pete

Custom controls are just numbers used by some add-ons to allow greater access to facilities. The only add-ons I know that definitely use this method are the PMDG 737NGX, and probably their 777, and their list will be in the documents -- probably in their SDK folder. Pete

Sorry, this is the wrong place for your question. This site is for FSUIPC, WideFS, in FS9, FSX and P3D only. I know nothing about Phidgets, OpenCockpits, SIOC, XPlane or XUIPC. Pete

By "not starting", what exactly do you mean? Please describe what you see. The migration tool is more likely to prevent FSUIPC even installing, or running at all when installed. Perhaps you should show me the Install LOG (and the FSUIPC4.LOG, if there is one) both from the Modules subfolder. You can paste their text here -- use the <> button above the Edit area to enclose them. Pete

Just run the Installer! There is a document in the downloaded ZIP which also tells you this, and more. After running the Installer, just copy the files in your FS Modules folder over. Dead simple. But best to update the installation on your old PC first (run the Installer), or re-run it again on your new PC, to be sure it is up to date. Pete

With FSUIPC axis assignment "direct to FSUIPC calibration", you get automatic arbitration between two or more inputs to the same flight controls -- the one with the greatest deviation from 'normal' (i.e. zero or centre) wins. However, I've a feeling that PMDG aircraft don't like their controls fed from FSUIPC's calibration facilities. This might only apply to the throttles, so it may be okay, but best to check for yourself or ask other PMDG users -- I have no PMDG aircraft myself. If you can't assign them that way then you need to make sure there is no jitter at all of the axes -- i.e. no unwanted inputs. Possibly using the dead zone in FSX would help there. Surely that simply depends on how many throttle quadrant levers do you need -- i.e whether you want separate levers for speed brake and flaps. With a 747 that's 6 levers. Aren't there only three on the Saitek quadrant? Pete

The email address is only part of the mechanism used to identify you uniquely -- names are normally not enough. So just leave it as it is, you'll be fine. Pete

No one else has such problems, and the files are good. Sounds like your connection is bad. Are you sure it isn't a false positive from your virus checker? Note that there are two sources for the Installer, the Schiratti.com/dowson page as referenced in the SimMarker purchase pages, and in the Download Links subforum here. Pete

The free use of FSUIPC only supports the interface for add-on applications (its primary purpose since FS98 days), and the Logging facilities to test/debug them (the other Tab you can't recall). All the User facilities are for registered users. There is documentation installed in your Modules \ FSUIPC Documents folder (as pointed out by the Installation and Registration document). I suggest you peruse that. It tells you these things. Pete

Actually, I just noticed. Sorry, I didn't read your message carefully enough. You were wrong: look 313c - 78 - N 313d - 55 - 7 313e - 54 - 6 313f - 48 - 0 =============<<<<<<<<<< 3140? 3141 - 76 - P 3142 - 48 - 0 where is 3140? I've checked here and I get the whole tail number. Please do your checks using FSInterrogate. Pete

Yes, despite FSUIPC allowing for more characters (12), and SimConnect SDK documentation stating it is up to 10 characters, I think SimConnect limits it to 6 including zero terminator. Sorry, I don't know why, but FSUIPC4 is presenting you with all it receives. Here's the SDK definition of the variables FSUIPC is reading: Offset 3160 ATC TYPE Type used by ATC String (30) Offset 3500 ATC MODEL Model used by ATC String (10) Offset 313C ATC ID ID used by ATC String (10) Offset 3148 ATC AIRLINE Airline used by ATC String (50) Offset 3130 ATC FLIGHT NUMBER Flight Number used by ATC String (6) Because FSUIPC is using the original offsets from FS9 and before, its lengths are different -- 24, 24, 12, 24, 12 respectively, so in the cases of ATC TYPE and ATC AIRLINE it may be truncating, but in the other cases it will be zero filled where SimConnect stops. Pete

Yes, I had my suspicions, but I needed the crash data for the current version to confirm them. I can't match the module offset for old versions. Do you have a file called "as_btstrp.dll" installed in your FS folder? If so it shouldn't be there and needs deleting. It is the operating link for the ASN weather program. If you actually have ASN installed, and that module is only in the ASN folder, then that is okay and should work, but please check that your version of ASN is up to date. It seems that some other add-ons install a stolen copy of as_btstrp.dll in order to make some sort of weather radar work, one which will only work accurately with ASN. I am preparing an update for FSUIPC4, hopefully for release before the weekend, in which FSUIPC attempts to protect itself against rogue copies of as_btstrp.dll. Please let me know what you find. Pete

Please update to the current version of FSUIPC4. I cannot support old versions! Next time you have a problem I also need to see the FSUIPC4.LOG file from the FS Modules folder. Pete

Well, I don't know anything about SPAD. But I can help with FSUIPC. Not sure why, as a beginner, you'd want to get into Lua scripts. In FSUIPC, multiple assignments to the same control axes can easily be made. If those assignments are done in the mode "direct to FSUIPC calibration" then FSUIPC will arbitrate between them, just selecting the input with the largest deviation from zero, or centre. This allows both sets to remain connected at all times, with the one not-in-use simply not being moved. The calibration, however, works on the FS control, NOT on the axis. So it works best if all the parallel assignments are from the same type of device. With modern control devices there shouldn't be too much problem in finding a good calibration for differing makes and types, but you would always need to make sure they are well calibrated in Windows first. There's no way at present to actively select the joystick for the one aircraft, except by using one instead of the other. If both are being moved then the one which has moved the furthest "wins" until the other one exceeds it. The Profiles system in FSUIPC allows different assignments for different aircraft, but that is obviously a different matter. These things are described and discussed in the FSUIPC User Guide. Sorry, I don't know and cannot help with SPAD. Pete