Pete Dowson

Sorry, I don't recall this. Can you give me a link to where this was discussed? There's no dock/undock facilities in the Lua library at present. I'm not sure how we would do it, assuming it is possible programmatically. It would be effectively duplicating the window content in a different class (different WndProc -- "FS98CHILD" <-> "FS98FLOAT"), so it really needs FS/P2D to do it for you -- i.e. you have to activate the right-click undock option. If I knew how to do it once, then, sorry, I've forgotten! (Old Age problem). Pete

Oh yes. Forgot you had to turn it on! 😞 Pete

I've now tried it both ways, ipc.macro and ipc.runlua, and i cannot make it fail with either. There's definitely something different on your system and the relation to being started from ipcReady is very mysterious. Perhaps a test with it starting from a different plug-in, but later, to eliminate anything to do with start up timing. For example, ipcLast.lua assigned to a keypress (temporarily of course). Pete

Developer access means having a menu at the top of your MSFS window with a Help option in which you can download the SDK installer. Pete

It shouldn't do anything related to a separate Lua it just happens to run. It was only me trying to envisage what might be going wrong. It might be a good idea to see if starting it with ipc.macro is any different. I'll try here later with both methods. If i can reproduce the problem I can get it fixed. Pete

The only thing preventing a proper Alpha/Beta test of FSUIPC7 at present is a missing SimConnect.DLL which is only available to developers. We'd like to include it but haven't got permission yet. 😞 Pete

What on Earth can change increments? There is an acceleration applied if INC controls are sent close together (that's a system which has been in FS since Bruce Artwick's days, before Microsoft), but I don't suppose you are doing something different after 1 hour. Nothing changing after an "exact hour"? Seems very spooky! Well, I can't see that being guaranteed since we don't know what is in your system which could be lying in wait for one exact hour then changing things. 😉 Pete

How do you invoke your plug-in with ipcReady? Perhaps you could show me ipcReady.lua, please? You see there are two ways: ipc.runlua (the best way) and ipc.macro("Lua ...). I'm thinking that your Lua terminates and in the process closes ports which were opened within its "realm" if it was just a macro. When I tested here I merely assigned a keypress to invoke the Lua script. I can re-test with your ipcready and see what the issue is. Pete

Not sure how it would make a difference. Maybe something else is going on which somehow closes it. You could try keeping it in the ipcReady.lua but preceding it with a delay (ipc.sleep). Okay. Let us know what you find please. Pete

Do you save a flight after positioning them, and make it the default? That should save the positions. You then build any other flights from that one. However, I have seen reports that it doesn't work properly on multiple screens. Perhaps if you use the nVidia Surround Mode facility to make them all look like one big screen it would work, but if they are of different sizes that may not be possible. Pete

You'd use the facility at offset 3110 to send any control. You need the Control number (from the list we provide) and whatever parameter you want for the axis value. Pete

The FSUIPC add-on DLLs like those for PFC are entirely dependent on the facilities FSUIPC provides, not interfacing directly to the sim in any case. So provided we manage to get everything needed from MS/ASOBO, and implemented in the new FSUIPC, then those should be fine. But as usual, no firm promises, just good intentions. 🙂 Pete

The prop calibration has ways of setting a "centre", which would probably correspond to your detent, as well as a minimum which will be max reverse/beta. This is a step in the Step-by-Step guide to calibration in the User Guide 6. For controls which have centres or intermediate ‘idle’ positions (aileron, elevator, rudder, spoiler, trim and the separate throttle and propeller pitch controls where centre (idle) is between forward and reverse), position the control in its centre, détente (e.g. “arm” for spoiler) or default position. Pressing the centre “Set” button will enter the value in one or other of the two boxes beneath. Each time you press Set the alternate value is recorded, and the boxes show the two most recent values in order (lower above higher). If the values are the same you will have no dead zone around the centre. Pete

Why ipc.macro? Why not simply ipc.runlua? Anyway, I'll go ahead and try that now. Thanks! Pete

There was a new facility added regarding detecting key presses in Lua -- the parameter LuaTrapKeyEvent to stop trappped keypresses also passing through to P3D. Maybe it's something about that change. Good clue. So i can test here with that script, getting a menu displayed, then pressing Shift X? If that's all i need i'll test now ... Pete

How is this script related to menus and ipc.keypressplus. are you saying that if this script runs whilst a GSX menu is displayed, then you get the key press problems? Pete

Oddly, today, with nothing in FSUIPC changed, I cannot reproduce any problems at all. I've been testing on my cockpit PC with the GSX menu, and both ipc.keypress and ipc.keypressplus work well to make selections there. i also tested using ipc.control to send the SimConnect_Menu controls, and they also work. These are: SIMCONNECT MENU 1 67136 SIMCONNECT MENU 2 67137 SIMCONNECT MENU 3 67138 SIMCONNECT MENU 4 67139 SIMCONNECT MENU 5 67140 SIMCONNECT MENU 6 67141 SIMCONNECT MENU 7 67142 SIMCONNECT MENU 8 67143 SIMCONNECT MENU 9 67144 SIMCONNECT MENU 0 67145 What caused the problem for me yesterday, and what is causing it for you, I really have no idea. i have looked carefully at all the changes between 6.0.8 and 6.0.9 and I can see nothing which affects any part of these actions. So, this is very worrying. What I would like to do is reproduce it using your code and settings, but it looks far too complex. Can you produce a slimline version, just the bare minimum which will still reproduce the problem for you? Please? Pete

Okay, after constructing a facility to create a menu that I can select from (I don't have anything installed on my Development Pc which creates SimConnect menus), I have finally seen the the problem, and can reproduce it every time. ipc.keypressplus appears to be changing the keyboard focus away from P3D (not sure where to yet), and it seems impossible to bring it back using mouse clicks on the P3D window. Weird. I'll investigate what changed here between 6.0.8 and 6.0.9. Pete

So it isn't anything to do with FSUIPC, but some problem with the P3D SimConnect menu system? BTW the two pictures appear identical to me. You must be seeing something very subtle which doesn't show up here. Have you tried programming the Lua to send the SimConnect Menu controls instead of using keypresses? I think they were supposed to be fixed in P3D5 HF2 (though I'm not sure about that). Pete

I don't know exactly what you need to do. As described in the Advanced user's guide for FSUIPC (about page 21), having two key actions programmed to a button like this gives you Press and Release key 1 then Press and Release key 2, rapidly. Is that what you do to make ChasePlane pan diagonally? Seems very odd. Do you do that when using the keyboard with it? So if you want to keep moving diagonally you rapidly press, for example, D then H then D then H etc? Why doesn't ChasePlane provide a single keypress for diagonal movement. Better, why doesn't it support Hat use itself? seems odd to me. Anyway, if you want two keys pressed together you can't program it the way you are doing it. You need to use controls to Press, Press, Release, Release. FSUIPC provides special assignable controls for separate press and release actions. Here are the details from later in the Advanced guide: 1071 Key Press/Hold (param is Keycode + 256*Shift code, or JsBk) 1072 Key Release (param is Keycode + 256*Shift code, or JsBk) So you need 4 assignments instead of two, like this 8=R3,33,C1071,580 -{Key Press/Hold: ctl+D}- 9=R3,33,C1071,584 -{Key Press/Hold: ctl+H}- 16=R3,33,C1072,580 -{Key Release: ctl+D}- 17=R3,33,C1072,584 -{Key Release: ctl+H}- because 580 = (2 x 256) + 68, 584 = (2 x 256) + 72. Pete

It is the ,INI file. The problem is that you have Windows Explorer hiding known filetypes from you (it thinks users are stupid). You should change that so you can see proper filenames! There are instructions to do this in the FSUIPC documentation. Pete

I can't imagine what could possibly have changed between 6.08 and 6.09 which could affect this action. Maybe John will take a look, as it is his program now and his changes, but I will try to understand. Thanks for the log and the plug-in, but it is far too complex for me to see what is going on. In fact I can't even see where in your code you are doing what. And although your Lua does a lot of logging of its own, you didn't activate the Lua trace logging option. So, I need it narrowing down for me please. First can you isolate the lines where the GSX menu is activated, and then the lines where the action is selected. Do this in both the log and in the Lua. Then, in order to analyse what is happening under debugging conditions, I might be able to construct something smaller and simpler to invoke the problem. I won't have time till tomorrow (Monday) at least, so there's no rush. Pete

No. All FSUIPC does is send the request on to SimConnect, within P3D. FSUIPC is in no way involved in the actual display itself, it is just a simple function call -- as documented for the SimConnect Text interface. These same display facilities are also used by the Lua plug-in "ipc.display" calls. Try, for example, the "VAS_Monitor.lua" plug-in provided in the Example LUA plug-ins ZIP in your FSUIPC6 documents folder. Or, perhaps easier, try a keypress assigned to the FSUIPC control "list LVars" which displays the current cockpit local variables. Another check is try with your "test" changed to "test\n2" so that two lines are requested, forcing the use of a different SimConnect function. ... [LATER] I've just tried your exact sequence with P3D5 HF2 and FSUIPC 6.0.9, and the green static line showing "test" appears and the frame rate doesn't change at all. I think you must have something else happening there. Maybe to do with your video driver or settings? Pete

I think there are some typos in Thomas's contribution, that is all. Just use the keycodes for the keys you want to press. Thomas was just illustrating how to make one button send two keypresses. The keycodes are listed on page 20 or thereabouts in the FSUIPC Advanced guide. You'll see these in the list: 96 NumPad 0 (NumLock ON) 97 NumPad 1 (NumLock ON) 98 NumPad 2 (NumLock ON) 99 NumPad 3 (NumLock ON) 100 NumPad 4 (NumLock ON) 101 NumPad 5 (NumLock ON) 102 NumPad 6 (NumLock ON) 103 NumPad 7 (NumLock ON) 104 NumPad 8 (NumLock ON) 105 NumPad 9 (NumLock ON) I'm sure you can figure out what you need to do from this. I seems very odd to me that something as sophisticated as Chaseplane does not provide a diagonal pan facility instead of having to use a combo job. Pete

I just done some testing with a simply Lua plug-in which uses ipc.keypressplus and cannot make it fail. I'm pretty sure there cannot be anything different with that function (there's been no change), so I think you must have something else going on. You need to enable key/button logging in FSUIPC's logging tab, and maybe Lua tracing too, so you can see what is happening. You can post the log here (paste into a message, use the <> facility in the editing menu to enclose it). You need to paste in your Lua plug-in too. Pete