Pete Dowson

If that is all of the Runways.txt file then you have a corrupted Scenery.cfg file. Check that. If there is more of the file I need to see the end part. But you have not placed the LorbySceneryExport program into the P3D folder alongside MakeRwys, so ay add-on scenery will not be scanned in any case. Please READ THE INSTRUCTIONS, especially the NOTE for Prepar3D versions 3 and 4 right there on Page 1! Pete

Ah, sorry. Much more complicated than I thought. It looks neater to me than using keypress interception, though. The questions arising are: does itnow work? and is it more or less laggy than the keypress interception? There is another possible solution which may be more efficiet as it will bypass FS's involvement right up to the point you use the SimConnect facility. Instead of assigning to FS controls, assign to FSUIPC Offset controls. Offsets 66C0-66FF are free for users to do with as they please. You can then use event.offset to catch changes. Pete

Do you realise that you are posting in a thread which is 15 months old, and referring to a very old version of MakeRunways? You are lucky i spotted it! If you are using a recent version of the program, can you give a little more information please? * What version of MakeRunways? (The actual version number). * What version of flight simulator? (FS9, FSX, P3D1-3, P3D4) * What exactly is means by "it won't work"? Is there an error message, the wrong reslut, or what? The file named "Runways.txt", in the main sim folder, next to Makerwys.exe, will also contain useful informaation. Perhaps you could show me that, please? ete

Thanks John! Pete

Well, the KEYUPs are being sent now with a large enough interval between, and still very few of them seen by FSUIPC for its log. very strange. Looking at the FSUIPC log above, can you identify where the interval would be in which you were still sending the keypresses but getting no response from FS? To me ther gaps in time are 9 seconds or so 6 minutes into the sim session, here: 361000 *** EVENT: Cntrl= 65608 (0x00010048), Param= 0 (0x00000000) ELEV_DOWN 370625 KEYDOWN: VK=37, Waiting=0, Repeat=N, Shifts=0 and 6 seconds about 20 seconds later, here: 392890 *** EVENT: Cntrl= 65607 (0x00010047), Param= 0 (0x00000000) ELEV_TRIM_DN 398640 KEYDOWN: VK=37, Waiting=0, Repeat=N, Shifts=0 Does that seem correct? Please, don't forget, also, to try assigning the keypresses in FSUIPC instead of relying on the default assignments. Pete

I think I may have nailed it. Can you try this test version, please, and let me know: PFChid64_511_TEST.zip Pete

Please try WideClient 7.15: download WideClient715.zip I'd like to see Client and FSUIPC logs for the PostKeys method, I have lengthened the delay between KEYDOWN abd KEYUP substantially. Please also test without PostKeys set. It won't work -- I cannot work out why SetWindowsHookEx doesn't work. but thids version logs the error number, so I'd like to see the wideClient log, please. I'm going to try to reproduce this here as well. Pete

I don't understand what changes. Certainly Wideclient doesn't change after two or three. it is doing exactly what it should be doing. I can't see any way to improve that. The FSUIPC log shows that FSX is receiving the KEYDOWNs but it isn't logging the KEYUPs. Could you enable event logging in its FSUIPC Logging tab so we can see what FS is making of them? It might also be worth assigning the keys to the normal controls they invoke, but in FSUIPC instead of relying on the FS assignments. This is more efficient and might avoid losing the KEYUPs. The only other thing I can think of is the KEYDOWN to KEYUP timing, which looks to be about 15 mSecs mostly. Maybe I'll try adjusting that, upwards. I don't see your manual keypresses in the log above. does it not include them? I will also try to gather more information about the failure of the SetWindowsHokkEx call, as really that is the original puzzle. I shoud be able to do that here easily ejnough. I'll try to get back with a revised WideClient.exe later today. Pete

Looks good. The message is not an error. It is preventing you messing up your edit because compound button assignments cannot be changed in the dialogue. Why do you want to change it again? So the whole use of a computer to simulate an aircraft is programming. That is what you do when installing and, especially, configuring, the simulator and any add-ons you are using. And you are certainly telling software what to do all the time you are using a computer flight simulator! In this case you are trying to force a momentary button press to act like a toggle for an aircraft control which is a toggle switch (i.e one which toggles on and off, like a normal light switch). To make things do something they are not designed to do takes a little more effort. Surely you can understand such a concept? Additionally, you are using an add-on aircraft which, in the wisdom of its programmers, does not follow any of the controls, switches and so on actually built into the Flight Simulator, and for which FSUIPC was purpose-built. you are twisting the use of FSUIPC to suit that add-ons quirks. Next time perhaps I will refer you to the PMDG support forum, where it is their job to support their add-on. If setting parameters in a programs controlling parameter file is programming, then all of the INI and CFG files in your system, doing likewise for other programs, are programs. Programs can be a lot easier to understand than parameter files, because they can and often do use English words. You could "program" your switch that way using plug-in to FSUIPC written in Lua programming language. Perhaps you should try that, then you'd see the difference. Pete

Please, just read my answers properly, then you wouldn't have a problem I have been doing this now since 1998, and 95% of folks who come here are satisfied with the help I give. I gave the answer explicitly as well as giving a reference. But come back next year. I will be 76 and retired. Then someone else will have to deal with it all, and probably at a more normal rate, not within minutes or hours as I strive to.

You should have read this pinned post at the top of this Forum before posting: READ BEFORE POSTING FSUIPC PROBLEM REPORT It is NOT programming, and certainly easier to understand than many hard core aircraft simulations! I helped you by showing you EXACTLY what to do. But still you aren't satidfied? ... Pete

I tried to reproduce this problem here by faking things on one of my only PFCHid devices (a couple of panels on their 737NG MIP), but effectively exactly the same setup (though a different switch, naturally) worked fine. I'm afraid I'm out of ideas. I really don't understand the problem, as it only occurs on one of the positions on your multiway switch. The code is the same for each case! I'll have a look at the log when I can allocated some time, but meanwhile why not use the Lua plug-in i suggested and do away with the macro intervention? i.e this idea from August 22nd: Pete

The more complex / ambitious settings like compound or conditional button actions or multiple results of a key or button press need you to edit the INI file. There are simply too many possibilities to make for an easy to use User Interface, and I'd rather not limit the facilities. That's the trouble with providing a generalised toolbox that folks can use for almost whatever they want. Pete

Did you look on Page 23? In any case I reproduced the important part for you, and told you EXACTLY ghow to do it! What more do you expect me to od? i don't understand. 😞 You button is A,7, so simply put A,7 instead of 3,5 in what I gave you. As explained in the manual (perhaps you need a translator?), + means if SET, - is if CLEAR, and F means Flag. 3,5 is just the button identification (like your A,7). BUT I actually gave you an example!! You write as if you didn't even bother to read what I wrote! 😞😞 Well, the current version is 5.14. I don't support old versions. You must always update before asking for support! The correct manual for the version you install is ALWAYS installed for you in your FSUIPC Documents folder. Pete

So it changes airports. Do you want MakeRunways data to take those changes into account or not??? MakeRunways changes NOTHING!!! Why on Earth are you using it? It merely extracts data from your scenery for other programs to use. That is all. If you have nothing needing that data DO NOT USE IT!!! Folks only download and use the program because they are using a program where the instructions say to do so! Pete

There is something odd here: You want to install 4.8.5.3. Why? That is an old one, and aimed at FSX and P3D1-3. But your install log shows: Installer for FSUIPC5.DLL version 5.14 and the Installer log shows a perfect install for FSUIPC5 in your P3D4 installation. So what is this really about? Pete

Assuming the elevation corrections change something to do with airports (if not, what do they do?), then obviously MakeRunways last. Else you'd get the wrong elevations in the data, wouldn't you!? Please do think a little about these things before posting such questions. Pete

Well, that's strange, because the log shows it working throughout: the Press and Release of the keys is the same all the way through, and all to the same window. So, where are the keypresses going? What is changing after a few uses? Do the keypresses still work on the keyboard itself? That still uses SetWindowsHookEx, so it is effectively the same problem as the original one. I don't know what to suggest. The PostKeys method is simple -- that's just what it does, posts the keypress and then release (about 15 mSecs later) to the specified programs named window (by class "FS98MAIN"). The fact that it does that every time, and that it did work for a few times, indicate that it working. so what is changing on the target (the sim) to stop that? Do you have FSUIPC installed on that PC? If not, install it, if so, enable Key/Button logging in its Logging menu and we'll see if the keypresses are actually registered in the Sim. If they are then somehow it is FSX which is suddenly ignoring them. Pete

Okay. I cannot find why Win10 objects to the use of SetWindowsHookEx. It is used for the default method of implementing KeySend, whether you give a classname or Window name, or not. However it is not used if you select either of the following options: PostKeys=Yes or UseSendInput=Yes So please try each of these, separately, and let me know which if any works okay for you. Pete

Depends why you are using it. Obviously if an airport is added, removed or changed then the previous generated data for that airport will be wrong. If nothing cares about that then there's no need to generate new files. But then if that is the case why did you generate them in the first place? Why would you want to replace an existing up to date program with the same up to date program? I don't understand why you ask this question. Pete

Two things, please: 1. Seems like you have Windows Defender set to stop some functions. I think Win10 has much fiercer "protections" to stop you doing (silly) things with your PC. Try running WideClient "as administrator" (though I found other reports on the Web about SetWindowsHookEx not working even then on Win10). 2. More logging would be useful. Try "Log=KeySend" in the [User] section. Is that the complete WideClient.INI file? Currently I don't really understand why it is setting hooks for simpe KeySend operations to send key presses. The code is rather ancient now (WideClient actually dates back to FS98 and the original widevieW, on which it once "piggy-backed". That's why I need the extra logging to see why it is going where it is. Pete

I do not conduct support in the reference subforums. It is not appropriate there. If the problem has a solution which is different to the details posted in User Contributions then by all means append it there. Meanwhile I have moved your post here. Pete

FSUIPC autoclave merely calls upon The SIM to save a flight, exactly as you can manually using the Menus or the ; keypress. It doesn't have any of its own files. And "playing" or loading flights is not an FSUIPC function either. All FSUIPC is doing is making things easier for you. The optional Load Flight and Load Plan menu entries were added to allow access to flights saved elsewhere, not in the regular folders, perhaps if you archive some or split them off into categories. It still calls upon the SIM to load them. Pete

Either use two buttons or a tggle switch, or use an FSUIPC button flag to record which to send, so they alternate on alternate presses. See this part of the FSUIPC Advanced Users manual (page 23 in the FSUIPC5 edition): the important part is that every button has a flag which is toggled every time it is pressed. So, say your button is joystick 3, biutton 5 (substitute joystick letter if you are wisely using letters), then CP(F-3,5)3,5,C69994,1 sends the 1 if the button flag is not set, AND sets the button flag CP(F+3,5)3,5,C69994,0 sends the 0 if the button flag is set, AND clears the button flag Pete

Very sorry, but the examples in the SDK are very dated, and depend on very old versions of the C/C++ Microsoft tools. It's never been updated because there is a much better solution -- Paul Henty's .Net Client DLL. Almost all current developers interfacing to FSUIPC use that. it is a much tidier, slicker systen and works with all versions and all (or at least most) .Net visual Studio languages. There's a Sub-forum of this forum above dedicated to this and worth perusing, but check http://fsuipc.paulhenty.com/#home Pete