Introducing Pilot's Deck, a StreamDeck Plugin

[ark1320]

  On 11/4/2024 at 11:38 AM, Fragtality said:

Wow, that Version is seriously outdated - Time for an Upgrade ^^

Expand  

My mistake, I meant ver 7.12, not 7.9 above.  Ver 7.12 in conjunction with FSUIPC7 is working well for me so I'm reluctant to make any changes until I actually need some of the new features in ver 0.8.0.

Thanks for the info.

Al

[ark1320]

  On 11/3/2024 at 1:37 AM, Fragtality said:

Plugin updated to Version 0.8.0

Expand  

I am still using ver 0.7.12. Should that work with MSFS 2024? If not, does 0.8.0 work with MSFS 2024?

Thanks,

Al

 

[Fragtality]

  On 11/27/2024 at 3:44 PM, ark1320 said:

I am still using ver 0.7.12. Should that work with MSFS 2024? If not, does 0.8.0 work with MSFS 2024?

Thanks,

Al

 

Expand  

Obviously 'No' as it is outdated?

There was preliminary Release for 2024 already: 0.8.2

But there where already some Fixes - most prominently fixing the Connection to FSUIPC when used with 2024 (didn't catch that with my Profiles since they don't have any FSUIPC based Actions anymore). I'm hoping that John soonish releases 7.5 so that I can check for and update that Dependency properly.

These Fixes are available with the latest Dev-Build:  https://github.com/Fragtality/PilotsDeck/blob/master/Install-PilotsDeck-latest.exe

[John Dowson]

  On 11/27/2024 at 4:53 PM, Fragtality said:

I'm hoping that John soonish releases 7.5 so that I can check for and update that Dependency properly.

Expand  

The current 7.5.0-beta (available from Announcements sub-forum) is pretty much what I will be releasing as 7.5.0 (currently no outstanding issues). Working on the installer at the moment, finished but testing. I then need to update the documentation and will release the full installer + documentation as a beta when this is done, hopefully at the weekend. I will then leave in beta for a week or so, to fix any reported issues, then I will make this the next official release.

I recommend trying the v7.5.0-beta now and report any issues found. Or maybe wait for the installer release when it comes in a few days. The official release will be around the 7th December.

John

[Fragtality]

  On 11/27/2024 at 7:14 PM, John Dowson said:

The current 7.5.0-beta (available from Announcements sub-forum) is pretty much what I will be releasing as 7.5.0 (currently no outstanding issues). Working on the installer at the moment, finished but testing. I then need to update the documentation and will release the full installer + documentation as a beta when this is done, hopefully at the weekend. I will then leave in beta for a week or so, to fix any reported issues, then I will make this the next official release.

I recommend trying the v7.5.0-beta now and report any issues found. Or maybe wait for the installer release when it comes in a few days. The official release will be around the 7th December.

John

Expand  

Thanks for the Feedback!

I think I will then push my PilotsDeck Fixes to Release for the Moment, even when it can't check or update FSUIPC properly yet - but then Users going through these manual Steps can at least connect to it again (in 2024) 😅
Maybe I'll add a temporary Link to the Beta Thread 🤔

[John Dowson]

  On 11/27/2024 at 7:29 PM, Fragtality said:

I think I will then push my PilotsDeck Fixes to Release for the Moment, even when it can't check or update FSUIPC properly yet - but then Users going through these manual Steps can at least connect to it again (in 2024) 😅
Maybe I'll add a temporary Link to the Beta Thread 🤔

Expand  

Ok. If you are using Paul's .Net dll, he has already updated this for MSFS2024 and FSUIPC 7.5+ so update to that if not already. The only other thing to consider is if you are checking/reading offset 0x3308 for the FS version (new version number for MSFS2024, and now only populated when connected to the FS). Otherwise you should be ok.

Cheers,

John

[Fragtality]

Yep, just saw the new Client and included it 😉

Yeah that is fine, after 0.8.0 FSUIPC is only a secondary Connector now for (both) MSFS - i.e. it doesn't have any Influence if the Plugin considers the Sim to be connected, loading or ready.

 

With that being said:

*Version-Bump* 😅

Version 0.8.3:

• Plugin: fixed not connecting to FSUIPC7 in 2024
• Plugin: fixed not detecting Session as ready when (re)started when Session was already running
• Plugin: Updated FSUIPC C# Client
• Installer: Provides link to FSUIPC7 Beta

[ark1320]

  On 11/27/2024 at 8:49 PM, Fragtality said:

Yep, just saw the new Client and included it 😉

Yeah that is fine, after 0.8.0 FSUIPC is only a secondary Connector now for (both) MSFS - i.e. it doesn't have any Influence if the Plugin considers the Sim to be connected, loading or ready.

 

With that being said:

*Version-Bump* 😅

Version 0.8.3:

• Plugin: fixed not connecting to FSUIPC7 in 2024
• Plugin: fixed not detecting Session as ready when (re)started when Session was already running
• Plugin: Updated FSUIPC C# Client
• Installer: Provides link to FSUIPC7 Beta

Expand  

Ver 0.8.3 did not find MSFS 2024, only MSFS2020.  Both sims are MS store versions and are installed in their default locations, each with their own copy of FSUIPC7, own Community folder, etc. I don't know if that fact that each sim has it's own FSUIPC7.ini file is a problem. How does Pilots Deck locate the FSUIPC7.ini file for the currently active sim?

Any suggestions?

Thx,

Al

[ark1320]

  On 11/27/2024 at 8:49 PM, Fragtality said:

*Version-Bump* 😅

Version 0.8.3:

Expand  

BTW, using the Profile Manager I did get automatic profile switching working with ver 0.8.3 in MSFS2020, but like in previous versions of Pilots Deck,  I had to use the aircraft profile names for each aircraft as used in the FSUIPC7 profiles. I first though with ver 0.8.3 I could just use a unique subset of the name shown in the sim's aircraft.cfg file Title entry, e.g., LEARJET for the LEARJET 35A, but that didn't work.

 

Al 

[John Dowson]

  On 11/28/2024 at 12:42 AM, ark1320 said:

Both sims are MS store versions and are installed in their default locations, each with their own copy of FSUIPC7, own Community folder, etc. I don't know if that fact that each sim has it's own FSUIPC7.ini file is a problem. How does Pilots Deck locate the FSUIPC7.ini file for the currently active sim?

Expand  

Note that you probably need the latest FSUIPC7 beta version (7.5.0-beta) for full compatibility with MSFS2024. currently available from the Announcements sub-forum. 

[ark1320]

 

  On 11/28/2024 at 8:41 AM, John Dowson said:

Note that you probably need the latest FSUIPC7 beta version (7.5.0-beta) for full compatibility with MSFS2024. currently available from the Announcements sub-forum. 

Expand  

Yes, in the General section both FSUIPC7.ini files show
    UpdatedByVersion=7500b
 I should have mentioned that above. I also was using the latest Stream Deck version.

Al 

[Fragtality]

  On 11/28/2024 at 9:55 AM, ark1320 said:

 

Yes, in the General section both FSUIPC7.ini files show
    UpdatedByVersion=7500b
 I should have mentioned that above. I also was using the latest Stream Deck version.

Al 

Expand  

Doesn't make a Difference for these Issues and something I have already assumed - at latest the (PilotsDeck) Installer would have pointed you to the Beta.

 

  On 11/28/2024 at 12:42 AM, ark1320 said:

Ver 0.8.3 did not find MSFS 2024, only MSFS2020.  Both sims are MS store versions and are installed in their default locations, each with their own copy of FSUIPC7, own Community folder, etc. I don't know if that fact that each sim has it's own FSUIPC7.ini file is a problem. How does Pilots Deck locate the FSUIPC7.ini file for the currently active sim?

Any suggestions?

Thx,

Al

Expand  

Not every Sim does have a FSUIPC7.ini, one Sim does not even have any ini File at all 😉

Check if that File / Path exists:
%localappdata%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\UserConfig.Opt

If exists:
What is the Value of the Parameter "InstalledPackagesPath" in that File?

If not exits:
Check under %localappdata%\Packages\ if there is any Folder for 2024 - maybe AdoboSoft has renamed the Store-Path again ... heard they did that back then with 2020 also (it is so dumb *sigh*)

 

  On 11/28/2024 at 12:56 AM, ark1320 said:

BTW, using the Profile Manager I did get automatic profile switching working with ver 0.8.3 in MSFS2020, but like in previous versions of Pilots Deck,  I had to use the aircraft profile names for each aircraft as used in the FSUIPC7 profiles. I first though with ver 0.8.3 I could just use a unique subset of the name shown in the sim's aircraft.cfg file Title entry, e.g., LEARJET for the LEARJET 35A, but that didn't work.

 

Al 

Expand  

No. FSUIPC7 Profile Names are not evaluated anymore anywhere.

From the Readme:

[ark1320]

  On 11/28/2024 at 12:06 PM, Fragtality said:

If exists:
What is the Value of the Parameter "InstalledPackagesPath" in that File?

Expand  

The value is: "C:\Users\arkla\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages"

  On 11/28/2024 at 12:06 PM, Fragtality said:

No. FSUIPC7 Profile Names are not evaluated anymore anywhere.

Expand  

That's what I thought, but, for example, for the Learjet I could only get profile switching to work in MSFS2020 using the FSUIPC7 profile name LJ35A as shown below. If in place of LJ35A I used just LEARJET it did not work. In the aircraft.cfg file for the Learjet, the plane is identified as  Title="LEARJET 35A N145AJ PMSGTN750+RADAR"
Perhaps I am doing something wrong with the Profile Manager. Just had a thought -- does the entry in the Profile Manager have to uniquely identify the particular plane AND LIVERY, or just uniquely identify the plane. The addon Learjet has a number of liveries.

 

[Fragtality]

  On 11/28/2024 at 4:37 PM, ark1320 said:

The value is: "C:\Users\arkla\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages"

Expand  

Huh that is really strange! And in there is the "Community" Folder, right?
That is basically how both MSFS Versions are determined to be installed: UserCfg.opt found => Community folder found
So I would assume the Installer also didn't do any FSUIPC / Mobiflight Checks for 2024, right?
And MSFS2024 already had its first start completed when you ran the Installer?

I think I have to write a special Build to troubleshoot that, everything what is needed is there - still the Checks do not return successful 🤔 I'll get back to you.

 

  On 11/28/2024 at 4:37 PM, ark1320 said:

That's what I thought, but, for example, for the Learjet I could only get profile switching to work in MSFS2020 using the FSUIPC7 profile name LJ35A as shown below. If in place of LJ35A I used just LEARJET it did not work. In the aircraft.cfg file for the Learjet, the plane is identified as  Title="LEARJET 35A N145AJ PMSGTN750+RADAR"
Perhaps I am doing something wrong with the Profile Manager. Just had a thought -- does the entry in the Profile Manager have to uniquely identify the particular plane AND LIVERY, or just uniquely identify the plane. The addon Learjet has a number of liveries.

Expand  

We don't get anywhere like that. Please forget the Title, aircraft.cfg or FSUIPC Profiles. Nothing of that is queried. Trust me, I wrote the Code 😂

What is the Aircraft String that is reported? Does it contain LEARJET in *both* Cases (long/full and short/relative Path)?

[Fragtality]

@ark1320 Please get the latest Dev-Build here and start it with --debug
After that attach the Log (PilotsDeck-Installer.log) here - it is created in the same Folder the Installer is run.

[ark1320]

  On 11/28/2024 at 6:17 PM, Fragtality said:

What is the Aircraft String that is reported? Does it contain LEARJET in *both* Cases (long/full and short/relative Path)?

Expand  

Reported where? Sorry -- don't know where to look for this info.

Al

[Fragtality]

[ark1320]

  On 11/28/2024 at 7:37 PM, Fragtality said:

Expand  

This is the long path I assume.  Learjet does show up, but all lower case.





And this is the short path. I see now Learjet is all caps.

 

[ark1320]

  On 11/28/2024 at 7:32 PM, Fragtality said:

Please get the latest Dev-Build here and start it with --debug

Expand  

I got the latest PIlots Deck build, but how do I start Install-PilotsDeck-latest.exe with the --debug option? Usually I just click on the installer to run it.  

[Fragtality]

  On 11/28/2024 at 8:04 PM, ark1320 said:

This is the long path I assume.  Learjet does show up, but all lower case.





And this is the short path. I see now Learjet is all caps.

 

Expand  

Hmm, that could be a trace! I mean I think that I did all Comparisons against lowercase Strings, but I might need to check that.

Please attach also the Plugin-Log and give me the (rough) Timestamp where it should have switched but did not.

 

 

  On 11/28/2024 at 8:20 PM, ark1320 said:

I got the latest PIlots Deck build, but how do I start Install-PilotsDeck-latest.exe with the --debug option? Usually I just click on the installer to run it.  

Expand  

Command-Line (good ol' cmd.exe) or creating a Shortcut/Link with that Parameter

[Fragtality]

  On 11/28/2024 at 8:47 PM, Fragtality said:

Hmm, that could be a trace! I mean I think that I did all Comparisons against lowercase Strings, but I might need to check that.

Please attach also the Plugin-Log and give me the (rough) Timestamp where it should have switched but did not.

Expand  

Yeah, really need that Log. It should just not happen all, the Comparison is all done in lowercase.

And: what does happen when you use "learjet" for mapping?

[ark1320]

  On 11/28/2024 at 8:52 PM, Fragtality said:

And: what does happen when you use "learjet" for mapping?

Expand  

Using the lower case "learjet" for the mapping seems to work.

Here's how the install went:

 

And here's the log file:PilotsDeck-Installer.log  
Still didn't see that MSFS2024 was detected.

[ark1320]

I don't know what to do with the below. And what is a Switch-Back Profile. Where are details like this explained? Is there documentation somewhere for new Pilots Deck users that explains how to use the different features of the Profile Manager?

[Fragtality]

At the very same Location it has been for Years: On GitHub.

 

Tip: that Symbol on the right displays the TOC 

[Fragtality]

O M G - I'm so dumb !

Download the Dev-Build (-latest File) again, I had a Typo in the Path 🙄
The Installer Issue should now be fixed.

But I am still waiting for the Logs of the Plugin not switching. I don't understand any of that, because it doesn't make any Difference either Code-Wise or in my Tests which Case-Style the Search-Strings have. Even Camel-Case works.