John Dowson

I suspect that you were still using the previous release - maybe your browser had cached the download. Anyway, I have released a new version, recompiled to the new SDK released yesterday with SU14. Please download and try this, and check it is installing 7.4.0d.

Are you sure that you are using the correct version?

Sent.

No programs are started now here, with Run or RunIf. It looks like the latest update has broken quite a few things. I have a lot of work to do tomorrow...

I don't understand this at the moment... it was all working as expected when I tested this. I will test further and let you know when an update is available. Quite a few issues with the latest SDK. Pain in the ass... xmas lunch today with quite a bit of wine. I will look into this tomorrow 😉 John

Your log also shows lots of other errors which are rather worrying.... There is an SDK update with the latest release to SU14 last night/today. I am currently in the process of updating to the latest SDK and will make a new release when done and tested, hopefully tomorrow. John

Good, I was only checking... I see you are using RunIf. I haven't tested with this - I will check this and update if needed.... John

No, no chance. There are no facilities provided by Asobo/MSFS to implement this feature, and theere is no planto do so. Things have moved on..... There are several other options available that replace the need for these: hvars, input events, and presets/calculator code. But there are also so many new ways to control/assign. Have you looked at the presets available? See https://hubhop.mobiflight.com/presets/ - these are all available from FSUIPC by selecting assignment to presets. Hvars (html variables0 are also available, but these are difficult to discover and best best used via presets. Input Events are the latest innovation. Currently these are only available in the latest beta release of FSUIPC7, which I will release before the end of the year. You can try these in the latest beta, available from John

All license details for products purchased from SimMarket can be found in your SimMarket account. Look at your Purchase History and click the relevant Order No.

Ok, I will look into this next week. Is that mapping I proposed ok? I will also map the following helicopter throttle controls: AXIS_HELICOPTER_THROTTLE_SET -> Throttle HELICOPTER_THROTTLE_SET -> Throttle AXIS_HELICOPTER_THROTTLE1_SET -> Throttle1 HELICOPTER_THROTTLE1_SET -> Throttle1 AXIS_HELICOPTER_THROTTLE2_SET -> Throttle2 HELICOPTER_THROTTLE2_SET -> Throttle2 There is also AXIS_TAIL_ROTOR_SET, but I am not sure about this one.... If you could update to the latest beta at some point (currently 7.4.0b), I will post an updated beta here for you to try this when done. The latest beta is available from John

License sent. John

I understand your issue, but there is no way I could possibly allow calibration for any axis. Calibration is only useful for the main flight control axis, and I fully understand that this is currently not possible for the new axes for helicopter flight control. The only possibilities at the moment are to use the axis scaling functionality, as you are doing, or to write the axis value to an FSUIPC offset and have a lua script pick-up the value and apply any calibration needed before sending to the FS. I am not prepared to add further calibration pages for helicopter axes at the moment - I just don't have the time for such a large undertaking. What I could do is to map the helicopter-specific axis to the existing calibration sections (i.e. aileron, elevator, rudder, throttle, mixture, prop pitch). As I am not familiar with helicopter flight controls, does this seem reasonable, and if so what would the mapping look like? e.g. AXIS_CYCLIC_LATERAL_S -> calibrate as aileron AXIS_CYCLIC_LONGITUDINAL_SET -> calibrate as elevator AXIS_COLLECTIVE_SET -> calibrate as prop-pitch ?

Are you sure that you are using the latest beta release, 7.4.0b? Please check this as your browser may have cached the download file. If that is not the issue, please show me your .log and .ini files... John

So it was there...why couldn't you find it earlier? That log file ends after less than a second (94 milliseconds) and shows nothing. FSUIPC7 was also still running. Unless something is stopping it. Check your anti-virus. But I don't think it is going to reveal anything anyway. You are using an unregistered version. There is no way your pauses/freezes have anything to do with FSUIPC7. I have now finished for the day. John

I am not interested in seeing images... Run FSUIPC7 and open the logging console (Log->Open Console). Do you see messages logged? Then use File->Open Installation Folder. That will open a windows Explorer window on the folder being used. Is the log file there? If there is no FSUIPC7.log and FSUIPC7.ini files in the folder, then something is wrong. Check any anti-virus software that may be blocking this.

Yes You can do this via lua, but if its on-start, why have a continually running lua? For on-start, you can also use the InitialButton ini parameter (see Advanced User guide), This can trigger one-off actions already assigned to buttons. Alternatively, consider individual lua functions - one to insure the ignition is on, one to open the fuel valve, etc. Or combine as needed, These don't need to be continually running - they can exit once their function is complete. From the lua you attached, you seem to want to handle all your assignments via lua and event.button. You can do this (this is what LINDA does), but it can get really complicated and is not necessary. Assign your buttons/switches as normal, via the button assignments, and just use lua for more complex things.

If you have ran FSUIPC7 at least one after installation/re-installation, there must be a .log and .ini file there, unless you have very stringent anti-virus protection. Open a command prompt, change to your FSUIPC7 installation folder: cd C:\FSUIPC7 List the files: dir and show me/paste (i.e. cut and copy, not just write whatever you see) the output. This is obviously incorrect, due to typos, if nothing else...

Now released...a bit early....!

Just released...

Impossible - there MUST be an FSUIPC7.log file. If that wasn't created, there is something seriously wrong... Its not hidden. As I said, uncheck 'hide extensions for known file types'. John

As I said, check the available presets for the aircraft you are using: https://hubhop.mobiflight.com/presets/ That should give you an indication of what to use to control things. Also try Input Events, using the latest beta. Also see the following to determine what to use for an assignment: https://www.badcasserole.com/uncovering-input-events-using-the-msfs2020-model-behavior-dialog/ And the MobiFlight discord server, MSFS 2020 channel, is the place to discuss and ask questions about how to define a preset for a function/aircraft that is not yet available on the HubHob server, I just provide the mechanism for these to be used. John

Name, e.g. John

And I have showed you this twice now. For the third time, and to be clear - from your FSUIPC7.ini: This will start the lua script when you press button 143 on joystick C, your Alpha yoke. This will start the lua script when pressing button 144. etc etc. You have such assignments for EVERY button. Can you not see this? What do you think those assignments actually do, if not starting the lua script? From the Lua plugins document: So, each of your button assignments is starting the lua script, and as it is already running, it will be killed first. Only if you assign it as such, which you seem to have done for all your alpha buttons (and similarly for your Bravo). You do this if you want the lua ro be auto-started. Many luas run on a button press. It is up to YOU to decide how to start the lua. However, almost all luas that use the event library, and just run waiting for an event to happen, should be started in the [Auto] section. Or, better, in the profile-specific [Auto.xxx] section, if they are specific to certain aircraft only. Yes, if the lua is running. No!. Don't EDIT this section, apart from LuaPath. All numbered entries are managed by FSUIPC7. Do not add or delete from this section. No! If you have an assignment to a button or key press, then it will be added to this section. You just DO NOT need to assign your buttons/keys to start a lua that is already running. Read the user guide on button and key assignments. If you are a beginner, a I do not understand why you are starting with lua, and not just assigning your buttons/keys to the standard controls/events or presets (also Input Events will be available for assignment in the next release, currently available as a beta - see Announcements sub-forum). It is a lot easier then using lua, and you can do most things via the UI. John

The next beta release, 7.4.0b, which will be released tomorrow, will allow for an additional parameter for [Programs] section entries: CONNECTED. This will delay the start of programs until FSUIPC is connected to MSFS (via SimConnect) and has received the initial data to populate the offsets. John

This will be available in the next beta release, 7.4.0b, available tomorrow. The new parameter is DontLogTheseIE. John