bug report for Saab 340A v1.5, XP11

[CMOS]

Commands in LES/* and JGX/SAAB/* are not properly displayed.
This is not a new bug, but does not seem to have been fixed with v1.5.
Thank you in advance for quickly fixing this bug and releasing another version soon!

 

 

[Ben Russell]

45 minutes ago, CMOS said:

Commands in LES/* and JGX/SAAB/* are not properly displayed.
This is not a new bug, but does not seem to have been fixed with v1.5.
Thank you in advance for quickly fixing this bug and releasing another version soon!

 

 

What version of xp? I added code to use the full cmd name if the description is blank.... I wonder if a new version of XP with tool tips is being too smart by half and blanking it out of the description is the same as the full cmd name.. 

[CMOS]

Thank you for your response.
I am using X-Plane v11.11.
I cannot reproduce the error anymore.
I remember exactly what I did:

1. Update the existing Saab 340A to v1.5.
2. Run XP.
3. From the main menu, click "Settings". Flight has not been started yet at this moment.
4. You see the error.

So, the error is only visible upon the very first run since the update, and it disappears if you exit and run it again.

[Ben Russell]

1 hour ago, CMOS said:

Thank you for your response.
I am using X-Plane v11.11.
I cannot reproduce the error anymore.
I remember exactly what I did:

1. Update the existing Saab 340A to v1.5.
2. Run XP.
3. From the main menu, click "Settings". Flight has not been started yet at this moment.
4. You see the error.

So, the error is only visible upon the very first run since the update, and it disappears if you exit and run it again.

Hmmm. Odd but a good lead. Thanks

[Lorenzo.D]

It's normal also for other aircraft. You need ti load the aircraft before assign command.

Inviato dal mio ASUS_X008D utilizzando Tapatalk