Can some of you share your button images for others to use. I’m sure a few of us are graphicly challenged like me.
Thanks
2 Likes
Sure! Been forgetting todo this for a week now. Here are my Ver 2 ICON Files
They are mostly 500 x 500 px .PNG files. I let Stream Deck scale the icon images when it imports them. Most Toggle Buttons have on and off images.
The .PDN Files are the Templates I used to construct the PNG files they contain all the graphic objects in layers. You’ll need Paint.net from the Microsoft Store, Its light weight inexpensive and very easy to use. You open the PDN and just composite the parts by enabling the layers you want you want and save as PNG. The app will tell you it needs to flatten the image to save it. Let it do it and immediately after saving, simply click the flatten item in the command history to restore your layers again.
Hopefully they will help.
2 Likes
Is there a repository for all of the great profiles the community has been creating?
1 Like
Now that @NguyenQHy has implemented the “embed” image feature, you can share profiles with your images already in them!
Use the Discussions tab over on the github repo to share away! I posted a discussion thread, here
3 Likes
I’ve shared my basic G1000 PDF and MFD profile in there. Each is in its own folder. You can copy and paste those to your own profiles if you find them useful.
Note they need MobiFlight and a Stream Deck XL.
3 Likes
Thank you @XAxSys! Seems you fly to some mighty nice places 
Actually what I would like to know which of the “MOBIFLIGHT_” Toggle event can I use on XCub’s G3X console?
On G3000 consoles for example have got the TSC buttons and knob working fine, for example one of the softkey:
This is great. Thank you. I happened to install Paint.net and Skinman last week to do work with Air Manager.
Sorry to post this off topic question, how do I use Air Manager with the Mobiflight module?
Thank you for that tool. I have a question about using switches like “No Smoke” and “Seatbelts” in A320neo. I think I have to use:
CABIN_NO_SMOKING_ALERT_SWITCH_TOGGLE for “Toggle event” and
CABIN_NO_SMOKING_ALERT_SWITCH for “Feedack value”
CABIN_SEATBELTS_ALERT_SWITCH_TOGGLE for “Toggle event” and
CABIN_SEATBELTS_ALERT_SWITCH for “Feedack value”
But it those not works.
Do I something wrong or are those not supported? 
Thank you for feedback 
I’m pretty sure that G3X events aren’t currently available. If the unit itself isn’t implicitly listed in the events list, it’s not supported at this time. Not even sure MobiFlight supports the G3X natively.
1 Like
You are goin to have to roll your own code to do it or build out an Arduino setup. I kludged together so really bad code to make it sorta work before it crashed but I think for my needs I’m going to build an arduino setup.
The 2 decimal places in the comms select button panel are causing issues. Is there any plan to actually fix this?
There are multiple times now when I’ve been told to select a frequency, but I can’t because the comm panel rounds up to the .005. Case in point with the screen shot below. The expected frequency is 124.470. But there’s no way to enter that, as the plugin will always round that up to 124.475. In the real world perhaps that’s how it works, but the sim will NOT accept 124.475. It expects 124.470, and nothing else will work. At that point, the only way to select the correct frequency is using the ATC panel or using the cockpit controls, which defeats the purpose of being able to manually enter frequencies with the SD in the first place.
I’ve encountered this at many airports now. Culprits are frequencies ending in xxx.x20 and xxx.x70. It always rounds up to the .005 as xxx.x25 and xxx.x75, which is wrong as far as the sim is concerned. This really shouldn’t be that hard to fix. Every other comm button in the plugin supports 3 decimal points except that 1 key button. Not only does this inconsistency trigger my OCD, but it doesn’t actually work as intended.
1 Like
@Crunchmeister71, is that near a mod or payware airport you downloaded?
I wonder if that frequency is correct, it should .475
I’ll look into in the next couple days.
I only have 2 payware airports - KEYW and KSAN. Never had that happen there. This is standard airports. In this specific example, it was Toronto. But I’ve had it happen at other random airports as well. It assigns a frequency of 1xx.x2 or 1xxx.x7, but there’s no way to enter that from the SD with the current button as it rounds up.
I understand that in the real world, this wouldn’t be a thing. But in the sim, it is. In the real world it would be .x25 and .x75. But the sim seems to have different ideas.
On a side note, Nguyen said on the GitHub page bug report I made that it was modeled directly after the TBM’s input panel, but the TBM has 3 decimal places, not 2.
no worries, I’ll get it figured out. Sorry you’ve been having this for so long 
No problem my dude. I appreciate the efforts so far, and I always maintained this was a low priority issue. But I find that for whatever reason, I’m experiencing this more and more now. Only had it a couple of times prior to the last patch. Now it seems that I’m seeing this more regularly.
I suspect it may be a bug within MSFS itself where it’s assigning wrong frequencies, because when I look at the frequency charts for these airports, FIR, etc, the 1xx.x20 and 1xx.x70 DO NOT exist in the frequencies listed in Navigraph and Little NavMap. The actual frequencies are indeed .x25 and .x75 as they should be. But the sim seems to think otherwise and hands you off to .x20 and .x70 and will not accept the “correct” values that deviate from what they assign to you.
All frequencies in the US and Canada have 25 kHZ spacing as you noted. As such, controllers are trained to issue only the first two digits after the decimal place. So if you are told to tune to 124.47, you are expected to select 124.475. Radios with 760 channels may or may not show that third digit but will always tune the “.005” after a “.02” or “.07”. Some older radio sets required you to pull a knob to set the last digit. Unfortunately, in MSFS2020, radios do not work correctly and allow you to tune to unusable frequencies. Instead of going from .x00 to .x25 to .x50 and .x75 they also allow .x05, .x10, .x15 then jump to .x25. This continues all the way up, tuning every 5 kHZ except for the 5kHZ just before the proper frequency where it skips (leaving out .x20, .x45, .x70 and .x95).
This may clarify: https://www.pilotmall.com/blogs/news/common-aviation-frequencies-a-pilot-s-communication-guide
1 Like
There’s no dispute about that. That’s how it works in the real world. I understand the 25 kHz spacing of channels in NA and how it works.
The issue is that’s not how it works in the sim, and this button with only 2 decimal places is causing issues. Not everywhere, mind you, but in some locations as per my description and screen shot above. I’ve encountered this several times now much to my surprise, at it shouldn’t be like this.
But remember, this is Asobo. These are people who gained their aviation knowledge with on the job training while building the sim. What they built into the sim sometimes doesn’t reflect the way things work in the real world. As a result, third party add ons that expect things to work like the real world will have unexpected and unintended results in the sim.
1 Like
I’m working on taking some of the SIMConnect Events and Variables I have learned a little about with Flight Tracker to do some work in Air Manager 4. Right now I’m working to build out the COM and NAV Radio Swap functions that swap Active and Standby frequencies on the radios. I can see the Flight Tracker Events COM_RADIO_SWAP & COM2_RADIO_SWAP listed in Structs.cs and I’m trying to work out what SIMCONNECT Events they map to? They are not MOBIFLIGHT events and are not directly exposed in the COM and NAV Buttons as that functionality is embedded in the presets. Is there a mapping I can follow to work this out? I’ve looked in both the Prepar3d and MSFS SDK and have not found an event that would perform this action.
Probably COM_STBY_RADIO_SWAP
We used this list: Event IDs
2 Likes