Fenix Autopilot again

[JPFLIGHT]

Hi,

My Fenix autopilot seems to have stopped working as intended, I know only get a slow turn of decrease/increase alt/speed/hdg settings, rather then the fast turn.

I don't think I changed anything and Fenix updates don't seem to have made a difference (i've done some regression testing with their assistance).

I've attached my ini and profile ini to see if there is something that i'm not seeing,

Any help much appreciated

James

Fenix A320.iniFSUIPC7.ini

[John Dowson]

Why 'again'? This is your 1st post...

What has changed?

Please show me/attach your FSUIPC7.log file.

[John Dowson]

I don't understand your ini...you are using profiles, but it looks like you were previously using profiles-in-separate-files, but no longer as you have:
     UseProfiles=Yes
rather than
     UseProfiles=Files

So most of your profiles are empty, except for your JF Hawk profile. Switch back to using Files to restore your profiles.

Also, update your profile aircraft names to use substrings. e.g. change

Quote

[Profile.Airbus A310]
1=A310-300 World Travel Airlines
2=A310-300 Orbit airlines
3=A310-300 White Livery
4=Airbus A310-300 Interflug DDR-ABA
5=Airbus A310-300 Hapag-Lloyd D-AIDD
6=Airbus A310-300 Hapag-Lloyd (D-AHLV)
7=Airbus A310-300 Iberworld (EC-HAL)
8=Airbus A310-300 HiFly 'Oman Air Hybrid' (CS-TEI)
9=Airbus A310-300 British Caledonian (G-BKWT)
10=Airbus A310-300 Airbus House 1980 (F-WZLI)
11=Airbus A310-300 WHITE
12=Airbus A310-300 Kibris Turk Hava Yollari (TC-TMT)
13=Airbus A310-300 German Air Force 10+22
14=Airbus A310-300 Blue Line (F-HBOY)
15=Airbus A310-300 Sabena (OO-SCA)
16=Airbus A310-300 Livery

to

Quote

[Profile.Airbus A310]
1=A310

and do similar for all your other aircraft profile names. When you add an aircraft to a profile, you should always edit the name for the shortest string that will catch all variants and no others,

John
 

[John Dowson]

You also have two [LuaFiles] sections....that can cause issues as you don't know which is being used, and one changed the LuaPath. And the files are assigned different numbers. Determine which is being used and remove the other.

You should NEVER touch that section - it is maintained by FSUIPC.

[John Dowson]

8 minutes ago, John Dowson said:

I don't understand your ini...you are using profiles, but it looks like you were previously using profiles-in-separate-files, but no longer as you have:
     UseProfiles=Yes
rather than
     UseProfiles=Files

By the way, when you change to Files it will move your profile assignments to separate files. If you change back, it does nothing, and so FSUIPC will NOT see your profile-specific assignments.

[JPFLIGHT]

Hi John,

thanks for those pointers, i've had a tidy up of my ini, and resolved the lua section issue. That in of itself doesn't seem to have ensured what my gut feeling was the Rotaries LUA not working

seemingly it won't let me upload even a zip'd copy of my log file, apparently the forum will only allow me to attach something 817 B in size?

[John Dowson]

13 hours ago, JPFLIGHT said:

That in of itself doesn't seem to have ensured what my gut feeling was the Rotaries LUA not working

That should be running as it is in your auto section. But if you think you have  an issue with a lua script you should set Lua debug logging, and as you seem to have quite a few lua sript running you shout also set to log lua plugins separately, and each running lua script will be debug-logged to a separate file.

13 hours ago, JPFLIGHT said:

seemingly it won't let me upload even a zip'd copy of my log file, apparently the forum will only allow me to attach something 817 B in size?

Your upload limit will increase the more you post. If its still too large after compression, you will have to use one of the free file transfer services, e.g. filetransfer.io or wetransfer.com.

Make sure you also include your latest FSUIPC7.ini file.

[JPFLIGHT]

HI John

thanks i've uploaded here: https://filetransfer.io/data-package/Te2Nenb4#link

using the rotaty i simply turned up quickly and slowly altitude, heading and IAS, then back down quickly and slowly

(edited for some double types)

Edited Thursday at 07:29 AM by JPFLIGHT
(edited for some double types)

[John Dowson]

I also need to see the Rotaries.lua script, and the Fenix A320.ini - the ini file used with the aircraft you are using, which is "Airbus A320-200 CFM Orbit Airlines D-AOAW".

6 hours ago, JPFLIGHT said:

using the rotaty i simply turned up quickly and slowly altitude, heading and IAS, then back down quickly and slowly

And the slow turns are working but the fast ones not? Was this previously working for the same aircraft?
Note that it may work in one aircraft but not another, depending on the controls you are using. Especially with (complex) add-on aircraft as many of the standard FS controls (or FSUIPC offsets) don't work, and you need to use other methods, such as custom controls, presets, input events, etc Presumably you are using the Rotaries.lua to set different virtual buttons for slow/fast in each direction, and have assigned the controls to these virtual flags, no?

And it is far easier for you to debug such issues, as you can see what is happening in real time when you turn the rotaries. Are the virtual button flags being set/triggered? Do you have assignments to these virtual buttons, and are they being sent?
But I can take a look to see if I can see anything. Please also activate FSUIPC logging for Buttons & Keys and Events, and send me the complete set of files.

[JPFLIGHT]

Hi John

should all be packaged here in one place: https://filetransfer.io/data-package/CCWEqbVi#link

This is common to all my fenix airbus' as they all naturally use the same profile regardless of being a319/a320/a321 as they all use the same presets

[John Dowson]

Looking at your log, only the virtual rotary buttons 0 and 2 are being triggered, so only one button in each direction. This needs to be checked first - but I need to see your Rotaries.lua script. Can you please attach that. The lua log is difficult to interpret (and nearly impossible without the source!) so I will add some extra logging statements to that to log what I need and you can turn off lua debug logging.

But it looks like 0 and 2 are the slow buttons, so no two consecutive button presses are being received within the time limit (100ms).
Looking at the rotaries log, it seems the poll function is only called every 150ms or more, and if it processes a button press then its over 1000ms! This is extremely slow, and is why there are no fast movements detected. Debug logging will slow things down quite a bit, but it has also been reported that lua is running quite a but slower in FSUIPC7. This is something I need to look into further,  when time permits. See 

One thing I commented there is that this only seems to occur when FSUIPC7 is auto-started by MSFS. So you could try waiting FSUIPC7 once it has been auto-started, and then start FSUIPC7 manually to see if that makes a difference. Please turn off lua plugin debug level logging when doing this, as that certainly slows things down, especially as you have so many scripts running.
You can also maybe try tuning/increasing the FastTimeLimit to see if that helps.

Also, your assignments are pretty much the same for each in/dec:
   - you have an inc/dec to the press and release of the slow button for each direction
   - you have an inc/dec to the press on the fast button in each direction
I am not sure how these assignments would give you a fast ind/dec anyway, even if the fast buttons were working, You are sending one in/dec control in fast, and two in slow, so slow is actually quicker!

Looking at the presets you have assigned to, e,g, FNX320_FCU_VS_KNOB_DEC :

(L:E_FCU_VS) -- (>L:E_FCU_VS)

this just substracts 1 from the lvar. For a fast action, you can define your own preset, e,g, FNX320_FCU_VS_KNOB_DEC_FAST as
    (L:E_FCU_VS) 5 - (>L:E_FCU_VS)
which would subtract 5. Or you could parameterize this:
   (L:E_FCU_VS) $Param - (>L:E_FCU_VS)
and specify the dec/inc value on the assignment.

But you need to get the fast buttons recognised before thinking about this.

John

[John Dowson]

You could also try setting the LuaAffinityMask ini parameter to move the lua threads off of core 1. This is not documented, but is basically a mask of the cores that can be used, where core 1 is 2, core 2 is 4, etc (core n is 2^n). So, for example, try using cores 3 & 4, by setting:

     LuaAffinityMask=x18

(core 3 is 2^3=8 (x8 in hex), core 4 is 2^4=16, or x10 in hex, so add then to get x16).

You can add or move to other cores. This may help as core 1 is usually saturated in MSFS (and most flight sims).

John