John Dowson

@lonesbeats@gmail.com First, you posted in a topic that has been closed for over 5 years and is not really related. You would be better off creating a new topic with an appropriate title. What you would like to do is quite straightforward using the event.button function and a global variable to hold the current state (or number of button presses). You can use and adapt the following lua script. Makle sure to add it top the [Auto] section of your FSUIPC ini file so that it auto-starts. John

There is currently a time-limit key file valid until the end of the year available for download in this topic: John

There doesn't seem to be any control, either internal or external, to control this at the moment. You may want to raise a new feature request with Asobo for this. John

Toggle your switch and assign the PARKING BRAKES control to both your button press ad release. Then located those assignment lines in your FSUIPC7.ini. I have just assigned to a spare switch, and these are my lines (where '109' is my device id, and button id is 15): To add an offset condition on 0x0BC8 (BRAKE PARKING POSITION), I would change those entries to Then the control would only be sent on the switch on position if the parking brakes were off (0x0BC8 contains 0), and sent the toggle control on release only if the parking brakes are on (W0BC8 is equivalent to W0BC8!0). John

Why are you posting the same question multiple times? See John

FSUIPC7 does not have a native web-service interface. However, there is a websocket server provided (and included in the FSUIPC7 installer) by Paul Henty. See http://fsuipcwebsockets.paulhenty.com/ John

v7.0.3 is now the latest official release - you can download it from the usual places (e.g. www.fsuipc.com or in the Download Links section of this forum). And I can only re-iterate what I have already said... If MSFS crashes, it is an issue with MSFS that should be reported to Asobo. You should report any CTD with any crash log reports from the Windows Event viewer. If its an issue in the SDK, SimConnect logging may also help. John

Hi Al, looks like Asobo have changed the key codes used for those keys. I have update in the attached version v7.0.4a if you would like to try it: FSUIPC7.exe John

Strange. I'm not sure what happened, but as its now working there is no point in looking into this now. Thanks for reporting back. John

@crash924 There are several other posts about with users who have the same problem and have found solutions. See Or John

It is there, it is just not a annotated correctly: 39=PC,30,C1024,0 -{}- This is because there is an issue with the annotation/comments for FSUIPC added controls. This has been corrected in the latest version, v7.0.3. You are till using v7.0.0 - can you please update (as only the latest version of each product is supported). Also, if you have a two-phased type rotary, you can only have one speed in each direction. It maybe better to assign to use offset 0x0BC0 and the increment/decrement controls, as explained in this post: You also need to determine which two buttons control the phase of the rotary - i.e. what are buttons B1 and B2 as explained on P23 of the Advanced user guide. John

You have commented-out the relevant lines with the ';' character - try: John

I'm not sure it is. What are you using to set the position? There is an indexed simvar GEAR STEER ANGLE that I could add, with indices for centre, left, right and aux (and also individual variables for each), but I'm not sure if this is what you are after or if this would be populated when using ProSim. Do you want me to add these to see if they can be of use? John

Hi Al, No, the ipc.ask() lua function isn't currently working due to problems with the SimConnect_Text function. Unfortunately I don't think there is an alternative to this at the moment, sorry. Thanks - and a very Happy festive period for you as well! John

Have you tried following the steps outlined in the User Guide, under the section 'CALIBRATING MULTIPLE THROTTLE, PROP & MIXTURE AXES TO "LINE UP"'?

It may be worth activating SimConnect logging anyway as this may show some errors when it stops responding. You can also determine the number of SimConnect connections used when this occurs, which would confirm or otherwise if this was the issue. It may be that with P3Dv4 there are less re-connects done by any SimConnect clients. ...and have a Happy Christmas! John

You are probably using the freeware version - do you have a license for FSUIPC4, and if so did you register it during the installation process? If not, or if it was installed for use by another program, then there are only limited user facilities available (mainly logging). Please see the FSUIPC4 user manuals, which should be installed with FSUIPC, or available under the Downloads sub-forum.

Following on from what Pete has said, you do not even specify what product or FS version you are using. Please provide enough information for us to understand and investigate your problem. Before posting again, please read this: Also note that support for our products is now closed for the festive period. I will still be monitoring support and maybe assist for urgent or simple problems, but if you are complaining and providing no supporting evidence you will be ignored. John P.S. And what does your topic title of 'FSUIPC' mean, when posted in the FSUIPC support forum? Please give any new posts an appropriate title.

Thanks for the update. Maybe worth checking the Asobo forums for issues with the latest release before you report - I still haven't had time to do this (or review the documentation updates for the latest release). Regards - and have a healthy and enjoyable festive period, John

@pilotjohn Ok, thanks. Let us know how it goes or if you need any assistance, although support will be occasional for the next 2.5 weeks or so. Regards, and have a Healthy and Happy festive period, John

You need to make at least one assignment to the rotary first. Your video showed device C with buttons 24 & 25 firing, and you have no assignments to those buttons. Try making one assignment in one direction, then look at the ini to find that assignment. Then, as Pete has said, follow the instructions half-way down P23, where 'Joystick 1' would be your Joystick C, B1 would be 24 and B2 is 25 (for the rotary you showed in your video). Otherwise, post your ini again after making an assignment to the rotary, and let us know the device and button number you assigned to. John

Hi Jan, I will look into this but I'm afraid that it will now have to wait until after the christmas holidays. I will get back to you once I have had time to look into this. John

Hi Hermann - Ok, and thanks for reporting back. Regards - and best wishes for a Happy and Healthy Christmas, John

There is a known issue in the SimConnect SDK since FSX that affects P3D (all versions) and also MSFS. It occurs when the number of SimConnect clients is exceeded, and tends to happen after long flights when using several simconnect clients (as they often close the connection and re-connect when the connection stalls). I haven't got time to dig out the references now, but there are various posts in this forum where I have explained the issue, given references and also how to improve (by increasing the max number of allowed SimConnect clients in a SimConnect config file). John

@daern I'm surprised about those events as your log shows FSUIPC7 exiting normally and that it was MSFS that crashed. I guess they are non-fatal errors due to the MSFS error. Your problem is almost certainly due to MSFS and you should raise a zendesk bug report. Btw, can you please ALWAYS attach your full log rather than pasting extracts, as there is further information I need to see, such as devices being used and the build version of FSUIPC (and any dlls) that you are using. @rvroman As you have not attached any relevant information (i.e. your logs) I can't really comment, but if it is similar to your previous log (or that of daern's) then it will also be the same issue. Maybe worth checking the MSFS forums for any similar reports - I haven't had much time to check out any issues with the latest release yet.... John