Pete Dowson

Sorry, you mean the limiter value, in the Miscellaneous tab? I use 250 as my limit and get lots of (mainly BA or course, with the odd Iberia) at EGLL Terminal 5 -- and without this new parameter. Maybe with an airport with as many gates as EGLL you sre simply being too restrictive at some number below 100? (You didn't say what you changed FROM to 100). Pete

As I think I said, for departure the nearest airport is chosen. There won't be an arrival airport, so the function won't work for the arrival. Pete

Does the E175 implement default FS lights or do its own? Those controls you are using are standard FS controls. Maybe your E175 doesn't use them? Have you tried using the normal FS shortcuts for the lights? One way of working out what controls the aircraft uses, assuming it does (some cockpits are mouse only), is to enable Event logging in FSUIPC's logging tab and operate the lights on the panel. See what gets logged for those, if anything. In the log you attached you have Axis event logging and Button logging enabled, but not the non-Axis events, which of course is what you actually needed! Pete

Sorry, you are trying to use Windows Messages to interface to P3D, not FSUIPC? Rather than use FSUIPC assignments to "see" if a key is arriving, why not simply use the Key/Button logging in FSUIPC's logging tab, and enable the Console log? Then if you run P3D in windowed mode you can see what Keyboard events FSUIPC detects. Did you not see this, BTW? Pete

RAW mode gives the actual value arriving from the device, with no interference from any calibration made elsewhere -- e.g.. in windows "game controllers". That's the only difference. Pete

But "display vals.lua" is not about creating a file with values. You should use the "record to csv.lua" example as a base. It has most of the values you might be interested in already. Just change the filename it uses if you wish. Pete

If you count the cores 0, 1, 2, 3 then core 2 is bit 2 or 2^2 = 2x2 = 4, so decimal 4 or hex x4. Likewise core 3 is bit 3 or 2^3 = 2 x 2 x 2 = 8, so decimal 8 or hex x8. If you count the cores 1, 2, 3, 4 then core 2 is bit 1 or 2^1 = 2, so decimal 2 or hex x2. Likewise core 3 is bit 2 or 2^2 = 2 x 2 = 4, so decimal 4 or hex x4. There's a FAQ thread about numbers, bytes and bits. Pete

Wow! Really? That's very kind of you. Paypal to petedowson@btconnect.com Pete

Please ALWAYS post support questions to the Support Forum, not to places like the FAQ subforum, which is a reference place for others to find things. I've moved this one for you. Sorry, there is almost no useful information here. You are programming a Key press to do something in FSUIPC's Key assignment tab? To do what, exactly? What is this "input field" you speak of, where you expect a "K" to appear? Why would a "K" appear anywhere in any case if you have assigned it to do something? You really do need to be much more explicit. i.e -- What is "K" assigned to do? An FS or FSUIPC control? Which? Or something else? -- How is your program actually sending it? Via a Windows facility, via some FSUIPC controls? What? -- What is supposed to happen when the "K" is used? I also need ALWAYS to know things like version of FSUIPC (the number, exactly), and the version of P3D. Have you tried using FSUIPC's logging facilities to examine your problem? Pete

I've looked at the code, and I think I might have messed up the offset for the second 777X data area when I added the 747 data, which is also wrong. I'm just fixing both now. If you write to me at petedowson@btconnect.com I'll send you a revised version (tomorrow) which I'd like you to check for me and let me know. Pete

So others, in the same data block, are okay? FSUIPC just receives the entire data set in one block from SimConnect. It doesn't interfere with any of it. Because the data was too large for the space, it just splits it into two parts: 6420 - 65EB and 6C00 - 6CEC If something was going wrong, the whole of one or the other would be wrong. I've no idea what all those crossed out lines in your last message are about, but there's nothing there about any other 777X offsets, so which other 777X offsets have you checked? As I said, I can't check here. I've never had the 777X. I need to know if all the data is wrong, or just the second part, or only isolated values. If it is just isolated values that must be some other interference, because the data is moved en bloc from the memory supplied by Simconnect. Pete

Sorry, I don't know what is changed. I recently added the PMDG 747 data, mapped to the same locations, but that would not conflict as you can only have one aircraft loaded at a time. I have not knowingly changed the 737NG or 777X offset mapping in the process of adding the 747 ones. I don't have any PMDG aircraft, so you'll need to tell me. Are all of the PMDG 777X offsets unpopulated? Can you check as many as you can please? Pete

Is anyone still interested in checking the PMDG 747 mapped offsets? I didn't seem to get the emails I expected. If interested, email me please petedowson@btconnect.com. Pete

For anyone interested in trying a new option and letting me know how they get on, download the interim update FSUIPC4962c_TEST.zip This allows you to set a separate preference for deleting excess traffic at your planned airports of Departure and Arrival. (Sorry, not alternate as well at present, but I might consider adding this if folks do actually use it enough and the facility appears to be useful). The new parameter, in the [Traffic Limiter] section of the FSUIPC4.INI file is PlannedAirportsPreference=50 As with the others, the default is 50, but it will be set the same as a previously set GroundPreference value initially. For this to operate fully you need to have a plan loaded in FSX/P3D. Since it doesn't know your planned departure until the plan is loaded, it will initially assume that the nearest airport IS your departure airport. This will be confirmed or changed when the plan is loaded. The "GroundPreference" value determines the probability of excess aircraft being deleted from any airports within FS's "reality bubble" EXCEPT your departure and arrival airports. In that case it is this parameter which decides the probabilities. So you could, for example, set the GroundPreference to 75 to get rid of more ground traffic at other airports, but put this one down to 25 to ensure more traffic at your planned airports. When you first run FSUIPC with this new feature, it will set the added PlannedAirportsPreference value to the same as the GroundPreference, so that nothing will change unless you change this or the other parameter. It is tested here but I'm not sure yet how effective it is for real flights,, which I've not got time for at present. Keep your current FSUIPC4.DLL to return to in case of problems, and let me know how here you get on, please. Pete

I think you need to report this to L-M. Have you already checked through the crash reports already there. L-M will probably ask you to test with no add-ons at all first, then add things back bit by bit. I think you should do that in any case, before reporting on that Forum probably. The first Windows crash above is in something called "MicrosoftEdge". I don't think that's anything to do with P3D, is it? Maybe it's another indication of something else wrong in your system. Pete

Did you fully uninstall the previous device? Otherwise registry entries will still say that the old one is still there, and trying to read non-existent devices is likely to give problems. Go t the Control Panel - System and uninstall from there as well as uninstalling any programs associated with it. I see that one of your devices is constantly re-connecting. This: 209094 ***** HID USB device reconnected: re-initialising FSUIPC connections occurs many times, each time immediatley after the other, during start up. That's not good. FSUIPC isn't polling for new devices, it simply asks Windows to notify it if any are freshly connected. However, this in itself should not make P3D crash, though it may hang it. Unfortunately, though you say you found the Windows crash details you show none at all, so there's nothing to point out which P3D or System component actually crashed. Pete

Oh dear. That's nothing to do with ipcBin files. That just forces a Pause when an aircraft crash (not a Sim crash) is detected, to stop it auto-reloading the flight!!! The option controlling the ipcBin file use is "Reload FSUIPC data" which defaults to "Never". Please don't just enable options without knowing what they do. Leave them to default. I suggest you do have a look at the FSUIPC User Guide some time. All this is described on pages 17-20. Pete

Aha! The ipcbin files are optionally produced and reloaded. They store the complete state of all FSUIPC offsets, which includes the 3380 / 32FA ones. Folks normally only use those when they are using complex cockpit accessories, like Project Magenta, and want to be able to continue a flight from where it crashed or was aborted without having to set the whole cockpit up again. Unless this is what you need I suggest you turn off the options for this on the Miscellaneous tab in FSUIPC options. I haven't heard of anyone using those options for many many years. I used to, but it doesn't really help with ProSim (I changed from Project Magenta a couple of years back). Pete

FSUIPC 4.961 is not supported. It was replaced by 4.962 six days ago. Please ALWAYS check for new versions before reporting a problem. it only wastes both our times. Pete

Oops. Sorry. My error. I clciked on your link which downloaded it to a folder on my PC, then I picked up the wrong file!! :-( I was rather distracted, with guests here today and trying to do several things at once. Please, unless files are really very long, just paste their contents into the message. Use the <> button to enclose them for tidiness. I've just done that with your last message, above, so you can see what it looks like. If the text is very long, it puts scroll bars on the right rather than showing it all at once. I agree, there's no Lua plug-in being run by FSUIPC, and no display sent either. I have no idea where your FSX installation is getting that from, sorry. Pete

You've got something wrong then. It's a built in function in FS and P3D. What, renaming the DLL.XML? No, that is wrong. P3D ALWAYS loads DLLs and EXEs from both files. Pete

As shown in the Log, you are still runningyour Ask application which is most certainly still in the Modules folder: 370830 KEYDOWN: VK=65, Waiting=0, Repeat=N, Shifts=0 370845 .. This key is programmed in FSUIPC4 'Keys' options 370908 KEYUP: VK=65, Waiting=0 370908 LUA.0: beginning "E:\Steam\steamapps\common\FSX\Modules\Ask.lua" 370955 LUA Asks: " Enter Distance to Move A/C in NMs (0-500), or just the ENTER key for 0 NM * to Exit " 374683 LUA Reply: "a" 374683 KEYUP: VK=13, Waiting=0 Pete

Where's the logging I suggested? It's no use saying these things without presenting information. There's absolutely no storage or memory of Lua actions or display scripts. There's no where for them to be stored. You've got something else going on there and it's only unexplained because you won't do the diagnostic actions I suggest. Pete

No, not at present. It complicates what is currently a very simple facility. There's already an utility program which can do that. The amount of programming additions just to do that would actually exceed the amount needed to implement the facility in the first place. If I thought it would be wanted to go that far I wouldn't have started implementing it. It was to be efficient and simple. And such an addition would also tend to defeat the object, which was to limit the effect on performance of a lot of traffic. Deleting traffic far away or out of sight really doesn't actually help that much. It is precisely the reduction of nearby traffic, at the airports you are at, which helps. Just reduce the Ground parameter. When it is zero is doesn't even consider deleting ground traffic. I'm sure you can finf somethnig to suit you. Pete

If the display is from a Lua plug-in then you most certainly have a Lua plug-in being executed. There's no way any such thing will be produced by a flight file and anything else like that. The displays are howver produced by lots of other programs, of course, as well as through normal things like Shift+Z to display coordinates, frame rates and so on. It is the same display mechanism. No, no way. Enable Button/Key logging and Lua Debu/Trace options in the Logging tab in FSUIPC.It will show you what Lua plug-in is being run, if any. Maybe through an "Auto" section you've forgettoen about. Pete