Aileron assignment in DA62

[John Dowson]

13 minutes ago, Sunny9850 said:

But now when I do the "2. The calculator code/assignment is not correct. To check this, activate logging for Axes Controls, and WAPI -> Debug logging. Open the logging  console (Log -> Open console) and move your assigned axis, and see if you can see the correct preset/calculator code being sent."  the console does not show anything for aileron or rudder....but they work in the aircraft. 

No, sorry - the calc code executed by a preset is not currently logged in the FSUIPC7.log, only in the WASM log file. I will correct this at some point.

Glad its all now working.

Cheers,

John

[Sunny9850]

37 minutes ago, John Dowson said:

No, sorry - the calc code executed by a preset is not currently logged in the FSUIPC7.log, only in the WASM log file. I will correct this at some point.

Nothing to be sorry about....I was a little puzzled because yesterday I did see some action in the console doing this but no action in the aircraft. 
Now today after the uninstall, reinstall the ailerons worked but not the console. 

Again thank you very much for your help with this. 

Cheers
Sunny

[Hazzer111]

Hello, I was looking tomyevents.txt use lvars to resolve this issue with my sim and the DA62. Unfortunately the axis does not show up, nor can I see it when I request the LVARs to be listed. 

Logs attached below. Hopefully you can advise what im doing wrong.

FSUIPC7.rar

[John Dowson]

11 hours ago, Hazzer111 said:

Unfortunately the axis does not show up, nor can I see it when I request the LVARs to be listed. 

What axis?   You are defining a preset, not an axis or an lvar.  You can see presets in the axis assignment panel once you have selected 'Send Preset to FS'. You should then see the presets you have defined in the axis assignment drop-down. When you list the lvars, you can see the lvars that the presets you have defined are using: INPUT_AILERON & INPUT_RUDDER_S.

Note I have just released a new version which, amongst other things, reduces the presets in the axis assignment dialog drop-down menu  to contain only those presets which accept a parameter, which drastically reduces the number of presets available and makes them far easier to find and assign. So please update at your earliest opportunity.

John                            

[Hazzer111]

On 9/15/2023 at 8:36 AM, John Dowson said:

What axis?   You are defining a preset, not an axis or an lvar.  You can see presets in the axis assignment panel once you have selected 'Send Preset to FS'. You should then see the presets you have defined in the axis assignment drop-down. When you list the lvars, you can see the lvars that the presets you have defined are using: INPUT_AILERON & INPUT_RUDDER_S.

Note I have just released a new version which, amongst other things, reduces the presets in the axis assignment dialog drop-down menu  to contain only those presets which accept a parameter, which drastically reduces the number of presets available and makes them far easier to find and assign. So please update at your earliest opportunity.

John                            

Hi John,  

 

Apologies for the poor wording. As you have said I should see Input Aileron or DA62X Aileron. Neither of these are showing so I assume I have done something wrong.

[John Dowson]

12 hours ago, Hazzer111 said:

As you have said I should see Input Aileron or DA62X Aileron. Neither of these are showing so I assume I have done something wrong.

Neither of these are showing where? Did you check 'Send Preset to FS'?
Your log file shows 11085 presets have been loaded, so you should see at least that that many entries in the drop-down when you select  'Send Preset to FS'.

Can you first update to v 7.3.23, which was released a few days ago. In this version, there will be far fewer entries in the axis assignment drop-downs when 'Send Preset to FS' is selected as only those accepting a parameter will be displayed. How many presets do you see loaded (check your FSUIPC7.log file, near the top)?  You should see 11090 +the number in your myevents.txt file.