search

spitice / msfs-input-viewer

In-game panel mod to show various axis inputs in MSFS2020
MIT License
16 stars 4 forks source link

Seems broken in WU6 #1

Closed sonicviz closed 3 years ago

sonicviz commented 3 years ago

No response to control inputs anymore

spitice commented 3 years ago

Thanks for your report!

That's strange because, on my side, the addon works without any issues even after WU6 as well as today's hotfix.

If the root cause is the addon itself, I reckon the config data for the addon might be somehow corrupted, but I'm not sure, tbh.

I'm not 100% sure about this topic either but there are many reports posted by the community that MSFS downloader sometimes does poor jobs, and game files ended up being broken. So there's a chance some of the files that the addon depending on are not working properly after the update. In those cases, the safest thing to do is to remove packages in a bad form and letting the sim download those files and hope it fixes, but it takes considerable time.

If you have MSFS SDK installed on your machine, then you can easily check the logs in the UI debugger app. Posting those log data would be appreciated.

sonicviz commented 3 years ago

Thanks, I'll retest it. Sent from my Galaxy smartphone. -------- Original message --------From: spitice @.> Date: 19/9/21 12:18 am (GMT+09:00) To: spitice/msfs-input-viewer @.> Cc: Paul Cohen @.>, Author @.> Subject: Re: [spitice/msfs-input-viewer] Seems broken in WU6 (#1) Thanks for your report! That's strange because, on my side, the addon works without any issues even after WU6 as well as today's hotfix. If the root cause is the addon itself, I reckon the config data for the addon might be somehow corrupted, but I'm not sure, tbh. I'm not 100% sure about this topic either but there are many reports posted by the community that MSFS downloader sometimes does poor jobs, and game files ended up being broken. So there's a chance some of the files that the addon depending on are not working properly after the update. In those cases, the safest thing to do is to remove packages in a bad form and letting the sim download those files and hope it fixes, but it takes considerable time. If you have MSFS SDK installed on your machine, then you can easily check the logs in the UI debugger app. Posting those log data would be appreciated.

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

sonicviz commented 3 years ago

ah, that would be because I'm still on 1.2.0

Doh!

sonicviz commented 2 years ago

Hi. I wanted to have a play with the js features of the SDK, and I like what you're doing with the ts. Could you explain what the build process for this is? I see the scripts in package.json, but interested in what you typically do?

I guess installation is npm install as per usual to grab the dependancies? Edit: yes, confirmed.

Where to set $MSFS_SDK? I'm using VSCode on Win 11, but it's not picking it up as a system environment variable, which works in regular batch scripts.

Maybe add that to the readme?

Thanks!

spitice commented 2 years ago

Hi. I hopefully get free time tomorrow so I will try to make a more detailed guide for this topic. But, it is basically done by the following steps:

For ${MSFS_SDK}, IIRC only yarn can recognize it as env variable, and npm cannot. So, maybe you need to specify the path to SDK directly or replace it with a batch file. However, I never use build and build-msfs anymore since it consumes a very long time to load up the msfs packaging tool somehow. Instead, I typically use build-without-msfs, then build the package on MSFS to generate files for releasing it.

sonicviz commented 2 years ago

Thanks