John Dowson

Please see

Maybe also try testing with this disabled, as well as any other add-on or plugin you may have running or recently added.

Ok. Could you also try with a default plane. I've just tried here with FSUIPCv6.0.10 and P3Dv5 HF2 and its working as expected. It looks as though FSUIPC is receiving (or continually receiving) a mouse click for that rectangle id. The escape key may be exiting the window, but it gets displayed again due to receiving another mouse click event - do you notice any slight flickering when you git the escape key? Have you managed to create a mouse macro for that aircraft previously? I'll check for some additional logging flags that may help in tracking down the issue.

I was going to suggest that you update! From your log file: This suggests that your key file couldn't be created for some reason. Can you check if you have the file FSUIPC6.key in your installation directory (C:\Users\44781\Documents\Prepar3D v5 Add-ons\FSUIPC6). If its not there, you can create this file manually with the following contents: I don't know why the key file couldn't be created, I've not seen this issue before. John

What option is this? If you are using the lua event.textmenu function (and maybe the TextFileForDisplay option), then these were only added to FSUIPC in versions 5.15/5.16, and are only available in FSUIPC5 & 6 (as well as WideClient). John

Your installation log shows that you have installed a single version for both P3Dv4 and P3Dv5. Could you post your FSUIPC6.log file please. Also, let me know your order number and purchase date (do not post your key!) and I will check your registration details. John

That seems to be an issue with Acars, have you tried their support? You could post your FSUIPC log files, in case there is an error there. John

I have moved your post to the main support forum. Please download and try the latest version, v6.0.10, released yesterday. John

Try: MakeRwys 4.91

Asobo are aware of the issue and we have been informed that the team will be contacting us "soon". That was 10 days ago.

This is why we have requested permissions to include the SimConnect.dll in the FSUIPC7.zip, and we are still awaiting a response after 4 weeks.... John

Maybe you could also try updating to v6.0.9, or better still, the v6.0.10b release posted in this thread: It helps if we are testing on the same version... John

Not quite...you need 'developer privileges' to be able to see the "DEVELOPERS' options in Options->General menu screen, where you can then turn on "DEVELOPER MODE" to gain access to the developer menu bar. John

@vegasjon777 Do you have access the the 'Developer' options? You currently need this to access the SimConnect.dll. If so, I can PM you the post (including link) so that you can start using/testing. If not, maybe try and request this access to Asobo and explain why you need this - we've been waiting for around 4 weeks now for permission to include the SimConnect.dll, but still no response. John

Hi Dane, ok, thanks for reporting back. There are still some issues related to this issue that we have cleaned-up and are now testing. I'll probably release v6.0.10 in the next week or so, so please upgrade to that once released. John

Too many different posts with people asking the same questions....see

Could you post that lua so I can take a look? We have recently identified a problem with lua scripts using key events that came to light in v6.0.9 due to an addition we made to trap lua key events (although the problem also exists in FSUIPC5). There is a temporary workaround in that post I referenced in the (striked-through) PS I added, but we'll release a full fix in v6.0.10 in the coming days, so you may want to try that script again after this release. In the mean-time you can also try the dll in that post to see if it works until the final v6.0.10 is released. I may roll the fix for this back into FSUIPC5, but this won't be for a while due to other pressing issues. Thanks, but not needed if your problem is solved. Is your axes "jittering" still present in FSUIPC6? Cheers, John

This is not possible via those offsets. You could try looking at the additional slew axes provided by FSUIPC: SlewAhead, SlewAlt, SlewHeading & SlewSide. However, I do not know how you would use these via the .net client dll. Or maybe even the provided key events/controls for slewing, starting with KEY_AXIS_SLEW_.... John

Didn't you just try it as it was first? I left all your settings, just removed the duplicates. There is only one setting in the ini not assigned to a controller, which was this one: 1=P0,8,C66506,14401 -{PANEL_ID_TOGGLE}- What do you mean 'nothing works'? From the log file you posted, I can see your buttons being pressed and the controls sent (although this was with your original ini), e.g: 152781 [Buttons] 47=R2,3,C65615,0 152781 Repeating flag set: bRef=0, Joy=2, Btn=3 (RepeatDelayCtr=1) 152781 FS Control Sent: Ctrl=65615, Param=0 ELEV_TRIM_UP 152781 *** EVENT: Cntrl= 65615 (0x0001004f), Param= 0 (0x00000000) ELEV_TRIM_UP No, this is not possible. I am sure many people use FSUIPC gear toggle over the years (including me!) and this would surly have been reported before if it was an issue. Your problem lies elsewhere. I also confused by this, as you previously said 'nothing works', whereas this implies things were working until you applied the gear toggle. Which is it? There is no difference between FSUIPC5 and FSUIPC6 in this area.Check that you have controllers disabled (in both sims). I also see that you are auto-starting a lua file relating to your gears: 141672 LUA.0: beginning "C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\Get_Gear_Height.lua" Try removing this for the time being.. So, I suggest you try the following: - remove the auto-start of the lua - remove all FSUIPC logging except 'Events (non-axis controls)' and 'buttons and switches' - check various button assignments using a default aircraft - let me know of any issues and re-post your .log and .ini John P.S. If your issue is related to the auto-started lua, it could be related to the problem reported in this thread. You could download and try the dll posted there - forget this for now. The fix there is for lua key events, not buttons.

Think we've found the issue. Can you try the following dll please (v6.0.10b): FSUIPC6.dll

Did you run P3D at least once before trying to install FSUIPC6? Do you have an install log - if so, please post that. If it can't find P3D, it means that the registry entries are not there. Try uninstalling and re-installing the P3D client. Then run P3D once, and close it down before trying to install FSUIPC6. John

@duyvh0309 We have now added facilities for this. Could you try the following dll please (v6.0.10a): FSUIPC6.dll There are facilities to create menus either via lua facilities or offsets: LUA FACILITIES ipc.SetMenu or ipc.setmenu(title, prompt, table_of_items) Prompt can be omitted for black in that space Title and prompt can be omitted for blank in both spaces The table of items is a Lua table with up to 10 entries. event.MenuSelect or event.menuselect(result, "function_name") or event.menuselect("function_name") With the former you can have a different function for each result. In both cases the result is supplied to the function which is declared as function function_name(result) The result is 1 - 9 for items 1-9 selected 0 for item 0 (10) selected -1 for Menu Removed -2 for Menu replaced (eg by another Lua -- all use the same ID) -3 for menu timed out (not likely -- no timeout facility offered. -4 for something else (not just "queued" or "displayed" -- not reported. OFFSETS: 5100 - 51FF: write menu tests here, up to 256 bytes including final terminator. Each string terminated by zero byte. First string = Title Second string = Prompt Then up to 10 more strings. The text (no item numbers) of item 1-9 and 0. Limited to 256 bytes altogether. Write 0 to byte 5100 to close it unanswered. Results: 0 is written by FSUIPC to Byte 5100 when selection is made or other things happen. The selection is written to Byte 5101. Here are a couple of scripts we have used to test this: menuViaOffsets.luamenu.lua

Sorry, but I don't understand this... What values are you actually writing to offsets 05EB and 05ED? As the documentation states, the speed is controlled by the values that you write there, from -127 (fast forward/left) to +127 (fast backward/right) for offsets 05EB and 05ED (vertical & forward/backward) and 0-32767 for 05E8 (vertical rate). John P.S. Try logging offsets 05EB, 05ED and 05E8 from the FSUIPC logging tab to see what they contain.

You can assign to the Situation Save control. This is the same as using the default P3D key ; (semi-colon). There is also an Auto-save Toggle control, which you can use to toggle auto-save on/off once it has been enabled from the AutoSave panel. John

Hi Dane, looks like your devices GUIDs have changed for some reason - have you had a windows update or re-install? Anyway, can you try the attached ini: FSUIPC6.ini I have tried to keep most of your settings, but you should review them. Cheers, John