John Dowson
-
Posts
13,780 -
Joined
-
Last visited
-
Days Won
288
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by John Dowson
-
-
1 hour ago, John Dowson said:
Using "Run" does not work either. Programs were only started after Ready to Fly was pressed.
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...
-
15 hours ago, Fragtality said:
Using "Run" does not work either. Programs were only started after Ready to Fly was pressed.
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
-
7 minutes ago, Fragtality said:
Hmm, the ini reports "UpdatedByVersion=7400b" and the changes.txt reflects the new Parameter.
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
-
2 hours ago, Alpin-Flier said:
Mouse macros were a very nice FSUIPC feature for otherwise unreachable functions in the past, but not available any more for MSFS. However, with the new interface capabilities of MSFS, is there a chance to get this functionality back in a near future?
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.
2 hours ago, Alpin-Flier said:his would be really a highlight in the desert of missing MSFS functions ...
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.
-
41 minutes ago, Warmbrak said:
Any access to those would be extremely useful.
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 -> Throttle2There 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
-
11 hours ago, GandALF said:
any chance to try it out with a trial license before buy?
License sent.
John
-
6 hours ago, Warmbrak said:
What would be useful if there was an option to apply modifiers or tweaks to any axis that has been assign through FSUIPC without having to head to the .ini file.
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.
6 hours ago, Warmbrak said:What would be the correct way then to calibrate these axes assigned through FSUIPIC that are not included in the Joystick Calibration pages?
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
? -
11 hours ago, Fragtality said:
I see no Difference with the new CONNECTED compared to READY - the Programs are only loaded after Read to Fly was pressed
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
-
6 minutes ago, Oriel46 said:
Here is the log file
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.
-
15 minutes ago, DaveSCUSA said:
Again, all I need is: 1. Event.button or event.key executing a function in a module. 2. Run that module via the [Auto] section. 3. Have a LuaPath in the [LuaFiles] section if the Lua is located in that folder. That's it? No other actions needed?
Yes
15 minutes ago, DaveSCUSA said:As an ex-pilot and retired programmer, I have options I want to use to make the use in the home built cockpit more realistic. I have the pilot manuals for several aircraft. I can more easily tie functions together that aren't correct in the MSFS aircraft. E.g. Upon start. Ensure the ignition is on. Fuel valve is open. Starter stops after reaching its minimum rpm.
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.19 minutes ago, Oriel46 said:EventFiles, HvarFiles, SDK, Utils, Documents, events.txt, events-license.txt, fscuipc.exe, installfscuipc.log, uninstallfscuipc.exe
This is obviously incorrect, due to typos, if nothing else...
-
1 hour ago, John Dowson said:
The next beta release, 7.4.0b, which will be released tomorrow
Now released...a bit early....!
-
Just released...
-
2 minutes ago, Oriel46 said:
That's the only log file in the install folder,
Impossible - there MUST be an FSUIPC7.log file. If that wasn't created, there is something seriously wrong...
3 minutes ago, Oriel46 said:even after I unchecked the hidden items.
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
-
11 minutes ago, DaveSCUSA said:
What would the input event entry look like using DontLogTheseIE parameter? Its number or name as appears in the log list of input events found?
Name, e.g.
Quote[Profile.DA62X]
DontLogTheseIE=PRESET_FADEC
1=DA62John
-
Just now, DaveSCUSA said:
You keep saying "assignment on your Alpha is starting the Alpha_Buttons.lua script" and "lua on a button press, as i have said many times now". where is the Lua started by a button/key press?
And I have showed you this twice now. For the third time, and to be clear - from your FSUIPC7.ini:
1 hour ago, John Dowson said:1=PC,143,CL1:R,1 -{Lua Alpha_Buttons}-
This will start the lua script when you press button 143 on joystick C, your Alpha yoke.
1 hour ago, John Dowson said:2=PC,144,CL1:R,0 -{Lua Alpha_Buttons}-
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:
QuoteLua <name> to run the named program So, each of your button assignments is starting the lua script, and as it is already running, it will be killed first.
5 minutes ago, DaveSCUSA said:Between the lines interpretation, does every button/key assignment in the [Button] and [Key] sections start the Lua module?
Only if you assign it as such, which you seem to have done for all your alpha buttons (and similarly for your Bravo).
6 minutes ago, DaveSCUSA said:1. List the Luas in the [Auto] section or use the ipcready.lua module.
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.
8 minutes ago, DaveSCUSA said:2. The event.button and event.key statements in the module will be executed whenever a button/key press is completed.
Yes, if the lua is running.
9 minutes ago, DaveSCUSA said:3. Don't need the entries in the [LuaFiles] section in FSUIPC7.ini except the LuaPath entry.
No!. Don't EDIT this section, apart from LuaPath. All numbered entries are managed by FSUIPC7. Do not add or delete from this section.
10 minutes ago, DaveSCUSA said:4. No [Buttons] or [Key] sections in the FSUIPC7.ini are needed except if one wants to start a module with a press.
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.
12 minutes ago, DaveSCUSA said:If the above is not correct or I still don't understand, please point me to documentation that provides the steps needed and what entries are needed where to execute a function on a button or key press.
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
-
On 11/25/2023 at 6:06 PM, Fragtality said:
Even though my Tools don't have a Problem with that (they're designed to be even started before the Sim): Would it be possible to have an additional RunIf Option in the Future - maybe let's call it "PROC" or so. It would start the given Program when SimConnect is ready to process.
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
-
1
-
-
On 11/25/2023 at 10:22 AM, John Dowson said:
I will add something similar for Input Events at some point. but not sure when I will have time for this - it mat be after the initial release.
This will be available in the next beta release, 7.4.0b, available tomorrow. The new parameter is DontLogTheseIE.
John
-
6 minutes ago, Oriel46 said:
It definitely starts by itself
It does NOT start by itself. Something must be starting it. I cannot help you with this - it is your PC. There are two other applications started fromyour EXE.xml:
C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe
C:\Program Files (x86)\FSRealistic\FSRealistic.exeMaybe one of them is starting FSUIPC? Try disabling each in turn to find out - just temporarily rename each exe and see if the 2nd instance is started or not. If not, then you have found the culprit.
9 minutes ago, Oriel46 said:I've attached the log file below, thanks for your help, John.
Not sure why you attached that. I said I could take a look at your FSUIPC7.log file, to see if there was anything in that that related to your pause/freeze issue, but I doubt it. You probably get some data-stalled issues logged, but this is expected if the sim is freezing.
John
-
10 minutes ago, Jesper Franzen said:
It was the fenix 320 by the way but I guess it doesn't matter.
Well, it does matter - in fact it is vitally important! Different aircraft use different controls. What works in one A320 version will not necessarily work in another.
I don't have the Fenix - and you said:
On 12/4/2023 at 12:04 AM, Jesper Franzen said:It was the default a320.
So I assumed Asobo. If using the Fenix, it is up to you to determine what works. Strange that I see the same as you using LIGHT_POTENTIOMETER_15_SET but in a different aircraft.
14 minutes ago, Jesper Franzen said:So then I can use a rotary encoder too to set the lights then?
You should be able to, but you have to work out what to use. Have you checked the presets available for the Fenix A320 on HubHop? If available, they should give you a clue, or you can use them directly.
16 minutes ago, Jesper Franzen said:Will I be able to use encoder or pot to adjust the light in cockpits?
You should be able to, as I said, But I cannot help you much as I do not have this aircraft. Use the tools available - presets and logging. Also check if any Input Events available.
17 minutes ago, Jesper Franzen said:And for this do I need the paid version or not? It seems though that you really need the paid version, because unregistered I didn't see much. Don't get me wrong I am willing to pay for what I need, just don't what to pay for what I don't need
Assignments are only available in the paid version. You can do this in the free/unregistered version, but you would have to write a program and do this via the FSUIPC offsets. The free/unregistered version is mainly used to support FSUIPC third-party apps.
FSUIPC7 Trial license - available here
in FSUIPC7 MSFS
Posted
Sent.