John Dowson
-
Posts
13,765 -
Joined
-
Last visited
-
Days Won
288
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by John Dowson
-
-
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.
-
You assign a button/key to start the lua if that is what you want to do. You would normally do this for a lua script that ran to do something and then exited, or for testing purposes. Lua scripts that wait for events are started and left running. Such scripts are usually automatically started, but you can start such a script on a button press, but every time you press the button the lua will be started, and if already running that will be killed first.
Your lua script is used for assignments, so it should be auto-ran. You do not need to start auto-ran scripts on a button.
4 minutes ago, DaveSCUSA said:Can I understand from your statement quoted above that an Lua entry in the [Auto] section and an event in an Lua module are mutually excleusive?
No, but used with care. You can assign to a button if you have a need to re-start a running (auto) lua script.
5 minutes ago, DaveSCUSA said:You state "assigned EVERY button to start the lua script". Not sure what that means. Does every entry in the [Buttons] and [Keys] sections in the .ini start a Lua script?
You have the lua script started on (almost) every button press, as I showed you in my last post:
3 hours ago, John Dowson said:Quote1=PC,143,CL1:R,1 -{Lua Alpha_Buttons}-
2=PC,144,CL1:R,0 -{Lua Alpha_Buttons}-
3=PC,145,CL1:R,1 -{Lua Alpha_Buttons}-
4=PC,146,CL1:R,0 -{Lua Alpha_Buttons}-
5=PA,13,CL1:R,0 -{Lua Alpha_Buttons}-
6=PA,14,CL1:R,0 -{Lua Alpha_Buttons}-
7=PA,15,CL1:R,0 -{Lua Alpha_Buttons}-
8=PA,16,CL1:R,0 -{Lua Alpha_Buttons}-
9=PA,17,CL1:R,0 -{Lua Alpha_Buttons}-
10=PA,18,CL1:R,0 -{Lua Alpha_Buttons}-
11=PA,19,CL1:R,0 -{Lua Alpha_Buttons}-
12=PA,20,CL1:R,0 -{Lua Alpha_Buttons}-
13=PA,21,CL1:R,0 -{Lua Alpha_Buttons}-
14=PA,22,CL1:R,0 -{Lua Alpha_Buttons}-
15=PA,23,CL1:R,0 -{Lua Alpha_Buttons}-
16=PA,24,CL1:R,0 -{Lua Alpha_Buttons}-
17=PA,25,CL1:R,0 -{Lua Alpha_Buttons}-
18=PA,26,CL1:R,0 -{Lua Alpha_Buttons}-
19=PA,27,CL1:R,0 -{Lua Alpha_Buttons}-
20=PA,28,CL1:R,0 -{Lua Alpha_Buttons}-
21=PA,29,CL1:R,0 -{Lua Alpha_Buttons}-
22=PA,30,CL1:R,0 -{Lua Alpha_Buttons}-
23=PC,133,CL3:R,0 -{Lua Bravo_Buttons}-
24=PC,134,CL3:R,0 -{Lua Bravo_Buttons}-
25=PC,135,CL3:R,0 -{Lua Bravo_Buttons}-
26=PC,136,CL3:R,0 -{Lua Bravo_Buttons}-
27=PC,137,CL3:R,0 -{Lua Bravo_Buttons}-
28=PC,138,CL3:R,0 -{Lua Bravo_Buttons}-
29=PC,139,CL3:R,0 -{Lua Bravo_Buttons}-
30=PC,140,CL3:R,0 -{Lua Bravo_Buttons}-
31=PC,141,CL3:R,1 -{Lua Bravo_Buttons}-
32=PC,142,CL3:R,0 -{Lua Bravo_Buttons}-
33=PC,143,CL3:R,0 -{Lua Bravo_Buttons}-
34=PC,144,CL3:R,0 -{Lua Bravo_Buttons}-
35=PC,145,CL3:R,0 -{Lua Bravo_Buttons}-
36=PC,146,CL3:R,0 -{Lua Bravo_Buttons}-See that every button assignment on your Alpha is starting the Alpha_Buttons.lua script. That is just crazy!
7 minutes ago, DaveSCUSA said:What are my steps to correct the situation if it is other than removing the Lua entries from the [Auto] section?
No! You want the lua auto-started. You should remove/delete all those button assignments that start the lua script, as you dont need these as the lua is already running nd waiting for button press events from your Alpha.
10 minutes ago, DaveSCUSA said:What am I not understanding from the sequence of actions above that is causing errors.
Step 3:
10 minutes ago, DaveSCUSA said:3. The .ini entries tie the button press/key press to the Lua module.
You do not need this. You only need to do this if you want to start a lua on a button press, as i have said many times now. Your lua is already running, via the [Auto] section.
Also, step 5:
12 minutes ago, DaveSCUSA said:5. Add the Lua module to the [LuaFiles] section ("1=Alpha_Buttons" and "4=Sayo-12Keys") also include "LuaPath=C:\FSUIPC7\LuaFiles" to use a folder to contain the .lua files.
You should NEVER manually modify the [LuaFiles] section (unless you REALLY understand what you are doing!). This section is maintained by FSUIPC7 by scanning your folders.
But why are you doing all this in lua anyway? Why not just assign directly in FSUIPC?
-
20 minutes ago, Oriel46 said:
After some searching I found my exe.xml file in the the LocalCache. Here is the info from the xml file.
That looks fine, with just the one entry that is starting FSUIPC7. If two copies are being started, then something else is starting it. Are you sure that you hadn't manually started FSUIPC before starting MSFS, or that it wasn't already running for some reason?
21 minutes ago, Oriel46 said:Where do I find the log file?
The FSUIPC7.log file is in your FSUIPC7 installation folder (C:\FSUIPC7\), together with your FSUIPC7.ini file (your settings). If you cannot see it, you have windows Explorer set to hide extensions of known file types. Change this in the Explorer View Options.
-
1 hour ago, John Dowson said:
I have just tried the LIGHT_POTENTIOMETER_15_SET control here in the Asobo A320 and it doesn't have any effect whatsoever - it isn't even logged, which means it is not doing anything in the sim. I don't understand why you see what you do...
I don't know what happened before, but I tried this again and see similar results to you... I get a full white screen using this control. I don't know why you are using this, it just doesn't work!
51 minutes ago, John Dowson said:You can only assign to an event that takes multiple parameters by using a preset. If you want to try this, I can define such a preset for you.
I tried this and this doesn't work either. For some reason, the parameters are not being used correctly.
You need to use the provided Input Events to control the lights. I have tested a few of these (pedestal, called LIGHTING_PEDESTRAL_1 for some reason, panel 1-4 and glareshield 1-3) and they seem to work as expected. They all need a parameter between 0 (off) and 100 (full on).
John
P.S. Why are you using the Asobo A320 and not the FBW version? The FBW version is a lot more complete...I would forget the Asobo one and just use the FBW. There are many presets for lights also available for the FBW version.
-
Checking further, the panel brightness in the Asobo A320 uses the Lights Potentiometer Set control with 2 parameters, the first being 15 and the second being a value between 0 and 100 for the actual brightness:
Quote4312359 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 5 (0x00000005) LIGHT_POTENTIOMETER_SET
4312734 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 10 (0x0000000a) LIGHT_POTENTIOMETER_SET
4313203 *** AXIS: Cntrl= 67042 (0x000105e2), Param= 100 (0x00000064) LIGHT_POTENTIOMETER_24_SET
4313656 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 15 (0x0000000f) LIGHT_POTENTIOMETER_SET
4313719 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 20 (0x00000014) LIGHT_POTENTIOMETER_SET
4313765 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 25 (0x00000019) LIGHT_POTENTIOMETER_SET
4314219 *** AXIS: Cntrl= 67042 (0x000105e2), Param= 100 (0x00000064) LIGHT_POTENTIOMETER_24_SET
4314359 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 30 (0x0000001e) LIGHT_POTENTIOMETER_SET
4314437 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 35 (0x00000023) LIGHT_POTENTIOMETER_SET
4314469 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 40 (0x00000028) LIGHT_POTENTIOMETER_SET
4314969 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 45 (0x0000002d) LIGHT_POTENTIOMETER_SET
4315031 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 50 (0x00000032) LIGHT_POTENTIOMETER_SET
4315234 *** AXIS: Cntrl= 67042 (0x000105e2), Param= 100 (0x00000064) LIGHT_POTENTIOMETER_24_SET
4315469 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 55 (0x00000037) LIGHT_POTENTIOMETER_SET
4315547 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 60 (0x0000003c) LIGHT_POTENTIOMETER_SET
4316015 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 65 (0x00000041) LIGHT_POTENTIOMETER_SET
4316094 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 70 (0x00000046) LIGHT_POTENTIOMETER_SET
4316125 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 75 (0x0000004b) LIGHT_POTENTIOMETER_SET
4316250 *** AXIS: Cntrl= 67042 (0x000105e2), Param= 100 (0x00000064) LIGHT_POTENTIOMETER_24_SET
4316609 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 80 (0x00000050) LIGHT_POTENTIOMETER_SET
4316687 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 85 (0x00000055) LIGHT_POTENTIOMETER_SET
4317062 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 90 (0x0000005a) LIGHT_POTENTIOMETER_SET
4317125 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 95 (0x0000005f) LIGHT_POTENTIOMETER_SET
4317172 *** AXIS: Cntrl= 67227 (0x0001069b), Param1= 15 (0x0000000f), Param2= 100 (0x00000064) LIGHT_POTENTIOMETER_SET
N,B. Logging of multiple parameters is only available in the latest beta.
You can only assign to an event that takes multiple parameters by using a preset. If you want to try this, I can define such a preset for you.
-
I have just tried the LIGHT_POTENTIOMETER_15_SET control here in the Asobo A320 and it doesn't have any effect whatsoever - it isn't even logged, which means it is not doing anything in the sim. I don't understand why you see what you do...
Looking at the lights in the Asobo A320, the following Input Events are available:
QuoteLIGHTING_PEDESTRAL_1<;FLOAT64>
LIGHTING_PANEL_1<;FLOAT64>
LIGHTING_GLARESHIELD_1<;FLOAT64>
LIGHTING_GLARESHIELD_2<;FLOAT64>
LIGHTING_GLARESHIELD_3<;FLOAT64>
LIGHTING_PANEL_2<;FLOAT64>
LIGHTING_POTENTIOMETER_17<;FLOAT64>
LIGHTING_POTENTIOMETER_18<;FLOAT64>
LIGHTING_POTENTIOMETER_19<;FLOAT64>
LIGHTING_EFIS_CS_ND_WX_BRT<>
LIGHTING_EFIS_FO_ND_WX_BRT<>
LIGHTING_POTENTIOMETER_20<;FLOAT64>
LIGHTING_POTENTIOMETER_21<;FLOAT64>
LIGHTING_POTENTIOMETER_22<;FLOAT64>
LIGHTING_POTENTIOMETER_23<;FLOAT64>
LIGHTING_STROBE_0<;FLOAT64>
LIGHTING_BEACON_0<;FLOAT64>
LIGHTING_TAXI_2<;FLOAT64>
LIGHTING_LANDING_2<;FLOAT64>
LIGHTING_LANDING_3<;FLOAT64>
LIGHTING_WING_0<;FLOAT64>
LIGHTING_NAV_0<;FLOAT64>
LIGHTING_TAXI_1<;FLOAT64>
LIGHTING_PANEL_4<;FLOAT64>
LIGHTING_CABIN_1<;FLOAT64>Input Events are relatively new and are available for assignment in the latest FSUIPC7 beta, available from
Maybe try assigning to the input event for the lights you want to control?
You need to determine the range the input event expects. You can do this by logging Input Events, and adjust the lighting you want to assign from min to max in the virtual cockpit. This will then log the input event with the parameter, and you can determine the range needed.
You cannot assign an axis to an input event directly. You have two choices:
1. Assign to the input event on axis ranges, using the right-hand side of the axis assignment dialog. This can give you up to 10 discrete positions, which you can assign to set discrete values.
2. If you want the full axis range, assign your pot axis to write its value to a (free) FSUIPC offset. You would then need a lua script that monitors for changes to this offset using event.offset. The handling function would calibrate the value received to the Input Event range, then send to the Input Event using ipc.execInputEvent. I can help with such a script, which should be auto-ran, if you want to do this.
John
-
2 minutes ago, Jesper Franzen said:
So my values are 16375-16384.
What values - in or out? That is a very small range, and also doesn't match the values shown in your previous log. But if those are the values FSUIPC is showing, tttthose are the values that FSUIPC is receiving from windows. Did you try calibrating your pot in windows game controllers, as advised?
7 minutes ago, Jesper Franzen said:I am sooo curious about the light potentiometer 24 set, where is that coming from? Is that like just the normal overall light set by the sim? I thought I would have nothing in the log except my card.
FSUIPC logs all events seen, not just those sent from FSUIPC. In fact, controls sent are never logged, only those that are applied. It is possible to send an event that isn't appplied/used in the loaded aircraft, and this will not be logged. And many aircraft in MSFS contiually emit certain events, and these events vary from aircraft to aircraft. You can ignore such events using the DontLogThese ini parameter.
10 minutes ago, Jesper Franzen said:Maybe this is a stupid question but I thought your program would like work together with the sim and not changing the sim.
Not sure what this means... It does work together with the sim, and it only changes it if you instruct it to do so.
11 minutes ago, Jesper Franzen said:But this light issue must mean that it's changing the parameters/code or what you call it, not a programmer
No it doesn't. As I said, that is just an event that is occurring and that FSUIPC is logging. It does not originate in FSUIPC. FSUIPC will log every event it sees, not just those that are sent.
13 minutes ago, Jesper Franzen said:To go beyond the original program. If this is the case, and this was a bad thing obviosly, do you have examples of this being helpful or even benefit to us?
No idea what this means... Of course it is helpful to log all events, this is thee whole point of event logging.
The log you attached shows the LIGHT_POTENTIOMETER_15_SET event/control with values going from 16119 to -16184 and back again:
Quote416953 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 16119 (0x00003ef7) LIGHT_POTENTIOMETER_15_SET
417047 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 15855 (0x00003def) LIGHT_POTENTIOMETER_15_SET
417187 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 15599 (0x00003cef) LIGHT_POTENTIOMETER_15_SET
417828 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 15343 (0x00003bef) LIGHT_POTENTIOMETER_15_SET
417937 *** AXIS: Cntrl= 67042 (0x000105e2), Param= 100 (0x00000064) LIGHT_POTENTIOMETER_24_SET
418141 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 15079 (0x00003ae7) LIGHT_POTENTIOMETER_15_SET
418562 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 14815 (0x000039df) LIGHT_POTENTIOMETER_15_SET
...426234 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 5656 (0x00001618) LIGHT_POTENTIOMETER_15_SET
426297 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 5328 (0x000014d0) LIGHT_POTENTIOMETER_15_SET
426359 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 5048 (0x000013b8) LIGHT_POTENTIOMETER_15_SET
426391 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 4760 (0x00001298) LIGHT_POTENTIOMETER_15_SET
426453 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 4464 (0x00001170) LIGHT_POTENTIOMETER_15_SET
426531 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 4136 (0x00001028) LIGHT_POTENTIOMETER_15_SET
426609 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 3824 (0x00000ef0) LIGHT_POTENTIOMETER_15_SET
426687 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 3552 (0x00000de0) LIGHT_POTENTIOMETER_15_SET
426734 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 3256 (0x00000cb8) LIGHT_POTENTIOMETER_15_SET
426797 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 2968 (0x00000b98) LIGHT_POTENTIOMETER_15_SET
426875 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 2680 (0x00000a78) LIGHT_POTENTIOMETER_15_SET
426953 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 2352 (0x00000930) LIGHT_POTENTIOMETER_15_SET
427031 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 2032 (0x000007f0) LIGHT_POTENTIOMETER_15_SET
427094 *** AXIS: Cntrl= 67042 (0x000105e2), Param= 100 (0x00000064) LIGHT_POTENTIOMETER_24_SET
427141 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 1768 (0x000006e8) LIGHT_POTENTIOMETER_15_SET
427203 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 1456 (0x000005b0) LIGHT_POTENTIOMETER_15_SET
427297 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 1200 (0x000004b0) LIGHT_POTENTIOMETER_15_SET
427344 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 944 (0x000003b0) LIGHT_POTENTIOMETER_15_SET
427391 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 624 (0x00000270) LIGHT_POTENTIOMETER_15_SET
427453 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 368 (0x00000170) LIGHT_POTENTIOMETER_15_SET
427500 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 80 (0x00000050) LIGHT_POTENTIOMETER_15_SET
427547 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -200 (0xffffff38) LIGHT_POTENTIOMETER_15_SET
427594 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -489 (0xfffffe17) LIGHT_POTENTIOMETER_15_SET
...432187 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -14670 (0xffffc6b2) LIGHT_POTENTIOMETER_15_SET
432266 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -14982 (0xffffc57a) LIGHT_POTENTIOMETER_15_SET
432344 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -15287 (0xffffc449) LIGHT_POTENTIOMETER_15_SET
432406 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -15599 (0xffffc311) LIGHT_POTENTIOMETER_15_SET
432484 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -15895 (0xffffc1e9) LIGHT_POTENTIOMETER_15_SET
432562 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -16184 (0xffffc0c8) LIGHT_POTENTIOMETER_15_SET
433141 *** AXIS: Cntrl= 67042 (0x000105e2), Param= 100 (0x00000064) LIGHT_POTENTIOMETER_24_SET
434172 *** AXIS: Cntrl= 67042 (0x000105e2), Param= 100 (0x00000064) LIGHT_POTENTIOMETER_24_SET
435187 *** AXIS: Cntrl= 67042 (0x000105e2), Param= 100 (0x00000064) LIGHT_POTENTIOMETER_24_SET
435250 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -15887 (0xffffc1f1) LIGHT_POTENTIOMETER_15_SET
435312 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -15583 (0xffffc321) LIGHT_POTENTIOMETER_15_SET
435359 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -15247 (0xffffc471) LIGHT_POTENTIOMETER_15_SET
435422 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -14942 (0xffffc5a2) LIGHT_POTENTIOMETER_15_SET
435500 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -14614 (0xffffc6ea) LIGHT_POTENTIOMETER_15_SET
...438859 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -1177 (0xfffffb67) LIGHT_POTENTIOMETER_15_SET
438906 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -825 (0xfffffcc7) LIGHT_POTENTIOMETER_15_SET
438984 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -521 (0xfffffdf7) LIGHT_POTENTIOMETER_15_SET
439047 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -144 (0xffffff70) LIGHT_POTENTIOMETER_15_SET
439125 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 112 (0x00000070) LIGHT_POTENTIOMETER_15_SET
439203 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 392 (0x00000188) LIGHT_POTENTIOMETER_15_SET
439203 *** AXIS: Cntrl= 67042 (0x000105e2), Param= 100 (0x00000064) LIGHT_POTENTIOMETER_24_SET
439250 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 664 (0x00000298) LIGHT_POTENTIOMETER_15_SET
439312 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 920 (0x00000398) LIGHT_POTENTIOMETER_15_SET
439391 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 1216 (0x000004c0) LIGHT_POTENTIOMETER_15_SET
439469 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 1600 (0x00000640) LIGHT_POTENTIOMETER_15_SET
439547 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 1936 (0x00000790) LIGHT_POTENTIOMETER_15_SET
...442031 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 13415 (0x00003467) LIGHT_POTENTIOMETER_15_SET
442109 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 13687 (0x00003577) LIGHT_POTENTIOMETER_15_SET
442156 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 13943 (0x00003677) LIGHT_POTENTIOMETER_15_SET
442234 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 14231 (0x00003797) LIGHT_POTENTIOMETER_15_SET
442266 *** AXIS: Cntrl= 67042 (0x000105e2), Param= 100 (0x00000064) LIGHT_POTENTIOMETER_24_SET
442281 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 14543 (0x000038cf) LIGHT_POTENTIOMETER_15_SET
442328 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 14799 (0x000039cf) LIGHT_POTENTIOMETER_15_SET
442391 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 15079 (0x00003ae7) LIGHT_POTENTIOMETER_15_SET
442437 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 15351 (0x00003bf7) LIGHT_POTENTIOMETER_15_SET
442484 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 15655 (0x00003d27) LIGHT_POTENTIOMETER_15_SET
442562 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 15927 (0x00003e37) LIGHT_POTENTIOMETER_15_SET
442719 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 16183 (0x00003f37) LIGHT_POTENTIOMETER_15_SET
So that shows your pot axis is working as expected....so I am confused about your issue.
I will take a look at that control in the Asobo A320 here, when time permits, to see what effect it has.
John
-
14 hours ago, DaveSCUSA said:
1. Kept getting Lua compile errors with the ipc.readSTR statement with the Alpha_Buttons.lua module - attached:
-- Find A/C Title
local acloaded = "None"
acloaded = ipc.readSTR(0x0618,4) - Read ICAO Designator from acraft.cfg
ipc.log("A/C - "..acloaded)So I commented the statements out (See the Lua module).
What error? I see no error in the log you attached. Note that the comment characters are '--' and not '-'. i.e. a double-dash. Is that your issue? The error message should indicate what the issue is....
14 hours ago, DaveSCUSA said:2. Now I have a clean compile but receive the errors:
140078 LUA: "C:\FSUIPC7\LuaFiles\Alpha_Buttons.lua": killed
144062 LUA: "C:\FSUIPC7\LuaFiles\Alpha_Buttons.lua": killed
145125 LUA: "C:\FSUIPC7\LuaFiles\Alpha_Buttons.lua": killed
189672 LUA: "C:\FSUIPC7\LuaFiles\Alpha_Buttons.lua": killed
191984 LUA: "C:\FSUIPC7\LuaFiles\Alpha_Buttons.lua": killed
195187 LUA: "C:\FSUIPC7\LuaFiles\Alpha_Buttons.lua": killed
197031 LUA: "C:\FSUIPC7\LuaFiles\Alpha_Buttons.lua": killedEach line item above appeared every time I exercized a switch on my Honeycomb Alpha.
Your lua script is auto-started, However, it looks like yo have also assigned EVERY button yo start the lua script:
Quote1=PC,143,CL1:R,1 -{Lua Alpha_Buttons}-
2=PC,144,CL1:R,0 -{Lua Alpha_Buttons}-
3=PC,145,CL1:R,1 -{Lua Alpha_Buttons}-
4=PC,146,CL1:R,0 -{Lua Alpha_Buttons}-
5=PA,13,CL1:R,0 -{Lua Alpha_Buttons}-
6=PA,14,CL1:R,0 -{Lua Alpha_Buttons}-
7=PA,15,CL1:R,0 -{Lua Alpha_Buttons}-
8=PA,16,CL1:R,0 -{Lua Alpha_Buttons}-
9=PA,17,CL1:R,0 -{Lua Alpha_Buttons}-
10=PA,18,CL1:R,0 -{Lua Alpha_Buttons}-
11=PA,19,CL1:R,0 -{Lua Alpha_Buttons}-
12=PA,20,CL1:R,0 -{Lua Alpha_Buttons}-
13=PA,21,CL1:R,0 -{Lua Alpha_Buttons}-
14=PA,22,CL1:R,0 -{Lua Alpha_Buttons}-
15=PA,23,CL1:R,0 -{Lua Alpha_Buttons}-
16=PA,24,CL1:R,0 -{Lua Alpha_Buttons}-
17=PA,25,CL1:R,0 -{Lua Alpha_Buttons}-
18=PA,26,CL1:R,0 -{Lua Alpha_Buttons}-
19=PA,27,CL1:R,0 -{Lua Alpha_Buttons}-
20=PA,28,CL1:R,0 -{Lua Alpha_Buttons}-
21=PA,29,CL1:R,0 -{Lua Alpha_Buttons}-
22=PA,30,CL1:R,0 -{Lua Alpha_Buttons}-
23=PC,133,CL3:R,0 -{Lua Bravo_Buttons}-
24=PC,134,CL3:R,0 -{Lua Bravo_Buttons}-
25=PC,135,CL3:R,0 -{Lua Bravo_Buttons}-
26=PC,136,CL3:R,0 -{Lua Bravo_Buttons}-
27=PC,137,CL3:R,0 -{Lua Bravo_Buttons}-
28=PC,138,CL3:R,0 -{Lua Bravo_Buttons}-
29=PC,139,CL3:R,0 -{Lua Bravo_Buttons}-
30=PC,140,CL3:R,0 -{Lua Bravo_Buttons}-
31=PC,141,CL3:R,1 -{Lua Bravo_Buttons}-
32=PC,142,CL3:R,0 -{Lua Bravo_Buttons}-
33=PC,143,CL3:R,0 -{Lua Bravo_Buttons}-
34=PC,144,CL3:R,0 -{Lua Bravo_Buttons}-
35=PC,145,CL3:R,0 -{Lua Bravo_Buttons}-
36=PC,146,CL3:R,0 -{Lua Bravo_Buttons}-As the lua script is running, when you press a button that is assigned to start the lua script, the currently running script is killed and then restarted, hence the error messages.
As your lua script is auto-started and waiting for your alpha button events, you don't need any assignments in FSUIPC7. just remove all of those. As it says in the lua plugins document:QuoteFSUIPC allows up to 256 simultaneously running Lua programs, each independently running in their own FS thread. When you start a Lua program running which is already running, the previous incarnation is first ruthlessly and unceremoniously terminated. ...
John
-
14 hours ago, Oriel46 said:
I deleted fscuipc7 and downloaded the latest version
You should not delete FSUIPC7. If you want to remove it, run the uninstaller or uninstall via the windows app management panel. And if you are updating FSUIPC, just download and run the installer, no need to uninstall.
If two copies of FSYUPC7 are running, check your EXE.xml file - you can get the location from your InstallFSYUPC7.log file. If there are two entries for FSUIPC7, remove one, However, this shouldn't be possible as the installer for FSUIPC7 should only add an entry if non exists, so if there are two then something has gone wrong. Please show me/attach your EXE.xml before you edit it.
As for your pauses, I doubt very much that these have anything to do with FSUIPC7. If you are using auto-save with a complex add-on (e.g. PMDG 737) then this can cause substantial pauses, but there are also remedies for this (see the FAQ entry Problems with Autosave on Windows 10/11 : The Answers!). You can also attach your FSUIPC7.log file and I can see if there are any issues reported there.
John
-
There are also the following presets available:
They use the custom controls via the ROTOR_BRAKE method - see
-
Not easy to read your comment...please don't use a black background. If you are pasting, paste as plain text...
For the horn cut-out, use the following custom control:
Quote#define EVT_OH_CAB_ALT_HORN_CUTOUT_BUTTON (THIRD_PARTY_EVENT_ID_MIN + 183)
and for the speed intervention, maybe this one:
Quote#define EVT_MCP_SPD_INTV_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 387)
To use custom controls, please see the following FAQ entry:
John
-
28 minutes ago, Jesper Franzen said:
But I haven't manage to calibrate it yet in FSUIPC. I see throttles and other things but I don't know how to calibrate this potentiometer.
You cannot calibrate a LIGHT_POTENTIOMETER_* axis, and this shouldn't be necessary. You only need to calibrate the main flight control axis.
Have you calibrated this axis in windows game controllers? That is where it may need to be calibrated.31 minutes ago, Jesper Franzen said:What I find strange is that the light never went back to normal. That must mean that the value of the pot is way off in the lowest setting, right?
Probably. But you can check via logging - keep the logging console open (Log->Open Console) and you can see the values sent in real time.
What In/Out values do you see in FSUIPC's axis assignment panel when you move the axis? What do you see as the minimum and maximum values for both in/out?
33 minutes ago, Jesper Franzen said:Should I delete what I already uploaded since now I can only upload 4.37kb?
You can do. Your limit is low as you are a new user - it will increase as you post more.
38 minutes ago, Jesper Franzen said:Both in the program and in msfs I see that the axis is pretty smooth with no jumps.
What program? Do you mean FSUIPC? The log you attached shows very erratic values...
-
18 minutes ago, gr8guitar said:
I am using logging,
Not in the log file you attached, which also ended after 97 seconds and was attached while FSUIPC was still running. I cannot tell anything from that!
Anyway, glad its now sorted.
-
Please do not use the New Log function when sending logs to support - i need to see the full log file. If its too large, it can be zipped/compressed. This menu item will be disabled (by default) in the next release for this reason...
If you look at the log file you attached, you can see that the parameters to the LIGHT_POTENTIOMETER_15_SET control, which will be the values your pot is sending, after calibration, jump all over the place:
Quote570078 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -16384 (0xffffc000) LIGHT_POTENTIOMETER_15_SET
570094 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 14335 (0x000037ff) LIGHT_POTENTIOMETER_15_SET
570094 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 10463 (0x000028df) LIGHT_POTENTIOMETER_15_SET
570110 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 16383 (0x00003fff) LIGHT_POTENTIOMETER_15_SET
570157 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 10687 (0x000029bf) LIGHT_POTENTIOMETER_15_SET
570172 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -16384 (0xffffc000) LIGHT_POTENTIOMETER_15_SET
570188 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 16383 (0x00003fff) LIGHT_POTENTIOMETER_15_SET
570219 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -16384 (0xffffc000) LIGHT_POTENTIOMETER_15_SET
570235 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 1448 (0x000005a8) LIGHT_POTENTIOMETER_15_SET
570250 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 16383 (0x00003fff) LIGHT_POTENTIOMETER_15_SET
570266 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 16071 (0x00003ec7) LIGHT_POTENTIOMETER_15_SET
570282 *** AXIS: Cntrl= 67033 (0x000105d9), Param= -12284 (0xffffd004) LIGHT_POTENTIOMETER_15_SET
570297 *** AXIS: Cntrl= 67033 (0x000105d9), Param= 16383 (0x00003fff) LIGHT_POTENTIOMETER_15_SETNot sure why this is, but it certainly doesn't look correct... what values do you see when you move the pot slowly through its full range and back again? You should see the values increase and then decrease (or vica versa). If its not sending such values, there is an issue somewhere.
What are you trying to control with this?
-
6 minutes ago, snizbatch said:
I apologize for my ignorance to the the names of controls vs offsets. I'm completely new to all of this.
It is just confusing for me when you keep talking about offsets as opposed to events. Offsets are FSUIPC-specific and are just memory addresses that you can read and write to. Controls/events are the commands that you send to the FS, which are defined either by the FS (standard controls), the aircraft (custom controls) or FSUIPC (FSSUIPC added controls).
9 minutes ago, snizbatch said:I know I could have turned on logging for events to capture 3110. It was so noisy that I simply elected to cut and paste the value for you as I did.
Yes, logging events can show many events that you are not interested in, and many add-on aircraft can continually emit some events which are just noise. You can ignore these by using the DontLogThese ini parameter.
11 minutes ago, snizbatch said:It appears that everything is being sent as intended and that I simply need help from PMDG.
Yes, that is what I thought.
Please update this thread if/when you get a response or understand why the controls are not having the desired effect.
Cheers,
John
-
Try logging offset 0x66C0 - this is an offset designated as 'free for general use', so you must have something else writing to that offset. Also activate logging for buttons & keys, and this will show you what is happening when you trigger those key assignments.
Also the limits set in those assignments don't look correct. What values is that offset holding? A lower limit of 1 when decrementing looks ok, but not when incrementing you need to set the upper limit. And you are incrementing and decrementing by 9, which also seems strange...
John
"Error setting Client Data Calculator Code" when using execCalcCode
in FSUIPC7 MSFS
Posted
Now released...a bit early....!