Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Engine Power and ECAM Buttons not correct. #57

Closed
Pyrolator opened this issue Aug 1, 2023 · 10 comments
Closed

Engine Power and ECAM Buttons not correct. #57

Pyrolator opened this issue Aug 1, 2023 · 10 comments
Labels
bug Something isn't working

Comments

@Pyrolator
Copy link

Pyrolator commented Aug 1, 2023

PedestalEngineError

Hello Creators.
As you see in the attached Picture - the Value for the Engines are not shown.
Also the ECAM-Buttons dont work, except the "ALL" Button.

Please investigate how to correct this Error's

All neccesary Files and Modules are latest Versions.
FBW A320 Stable V0.10.1

For fixing this Issues an Sponsoring follows :)

BTW thanks for this great TouchPortal Modul

@mpaperno
Copy link
Owner

mpaperno commented Aug 1, 2023

Hello,

This is some problem with the page created by GoodSeb over at flightsim.to (this one, I presume). This is not, apparently, an issue with this plugin itself (unless that can be demonstrated somehow directly).

Sorry I can't help further at this point, that's not a page or model I personally use. Please ask GoodSeb for help (and if he can trace the issue to something to do with this plugin, I'm happy to take a look).

Best,
-Max

@mpaperno mpaperno closed this as completed Aug 1, 2023
@Pyrolator
Copy link
Author

Thx for the fast answer, i try to contact GoodSeb.

@mrussell1958
Copy link

The answer is to use this https://github.com/mpaperno/MSFSTouchPortalPlugin/releases/download/1.3.2.0/MSFS-TouchPortal-Plugin-1.3.2.0.tpp The newer plugin isnt seeing all the FBW variables. I loaded this into touch portal and all works fine.

@Pyrolator
Copy link
Author

Yeah, thx a lot, that fixes the missing Engine Values !
So its not a failure from the Pages. I hope Max read this lines and had the time to correct his TPP in a future Version.

ECAM Buttons maybe a error in the Page from GoodSeb, but its OK for now.

Thank you mrussell :)

greets from Germany
Roger

@mpaperno
Copy link
Owner

mpaperno commented Aug 4, 2023

Could someone provide the list of variables affected?

I would like to see the actual .INI config file entries for them, please.

The big difference in plugin v1.4 is that Local vars are being requested via SimConnect now, not WASM. As far as I know so far, all other Local vars work fine. So we would need to know which vars/requests are affected specifically.

As always, plugin log files showing the issue (in v1.4) would also be appreciated.

Thanks,
-Max

@mpaperno mpaperno reopened this Aug 4, 2023
@mpaperno
Copy link
Owner

mpaperno commented Aug 4, 2023

It could also be related to this change in v1.4:

Added some basic validation of variable request parameters when loading from .INI configuration files. Invalid requests are rejected. Validation errors and warnings are reported in the plugin's log.

So again, need to see the actual variables please, and ideally the corresponding log entries.

To be clear, I'm talking about the plugin's log, not TP's. As explained here: https://github.com/mpaperno/MSFSTouchPortalPlugin#troubleshooting

Thanks,
-Max

@Pyrolator
Copy link
Author

OK, i send my 2 logfiles, V1.3.2 and V1.4.1
i hope they are the correct ones.

1.3.2MSFSTouchPortalPlugin20230804.log
1.4.MSFSTouchPortalPlugin20230804.log

Greets from Germany

@mpaperno
Copy link
Owner

mpaperno commented Aug 4, 2023

Hi Roger, perfect, thank you. And thanks for the buck! :)

The issues are what appear to be L vars with : in the names, like A32NX_ENGINE_N1:1. I guess this is what @mrussell1958 was trying to tell me in the related discussion, but this proves it.

I didn't think this was allowed in L var names, but I could be wrong. The question then is, are those the actual variable names the "FBW A320 Stable" uses? I will try to check their SDK docs, but if someone with the model installed could check the L vars list that would be a big help (Dev mode -> Behaviors Inspector -> Local Variables).

Thanks again!
-Max

@mpaperno
Copy link
Owner

mpaperno commented Aug 4, 2023

Answering myself... indeed the FBW API docs lists L vars with :index numbers in the names. So I guess these are legal names, and I will indeed need to fix the validation on the plugin side. Don't know why they chose this unusual syntax (it may backfire on them one day), but c'est la vie.

Thanks for the reports!
-Max

@mpaperno mpaperno added the bug Something isn't working label Aug 5, 2023
@mpaperno
Copy link
Owner

mpaperno commented Aug 5, 2023

Should be fixed in v1.4.2!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants