markcellis
commented
1 month ago You have an interesting idea. I might suggest a slightly different approach:
X-KeyPad could scan your configurations to see if you used any of the X-Camera select view commands, if it sees them it could bundle a copy of the X-Camera configuration for that aircraft right into the JSON file.
When X-KeyPad loads that aircraft profile it could then see if the user also has X-Camera installed and if so could copy the X-Camera profile from the X-KeyPad configuration to the aircraft folder. It would check to see if one already exists and confirm that the user wants to replace it if they are different.
If X-Camera does not exist on the system X-KeyPad could offer a discount code for X-Camera.
There are probably other combinations of the above that could work.
Although X-keypad a X-camera are both excellent products on their own, there has been a visible trend especially with the impementation of STREAMDECK support in X-Keypad for developers to include x-camera views in the Streamdeck profiles. Potentially there is a problem with this as the end user can easily for example get a myriad of Airbus A320 camera view packs from the community files and thus create a new set of views that do not match those set up for the Streamdeck. This sets a potential that many will have issues to report that the view on the Streamdeck is different to what you was expecting or you get the voice saying that the view is not available. This would have a detrimental effect on the developers and Stick and Rudder as keeping a STREAMDECK profile to work every time is paramount to the success of the profile and X-Keypad. What I propose is an enhancement to X-keypad wherein a 'LITE' version of X-camera is built in and thus removes the potential errors that can occur having both X-keypad and x-camera in one Streamdeck profile. [1] no need for community stuff as the finished XKEYPAD/STREAMDECK profile etc would be put by the developer into the community. [2] obviously the SRS names would need to be independant of the SRS names in X-camera for it to work . [3] to offset the potential of reduced x-camera revenues perhaps increase X-keypad , but I see more benefit and potential sales if X-keypad had integrated camera views as well [4] just need a connection on the x-keypad menu to say 'X-KEYPAD Camera views' since the software layout is already there and they both look and feel and work in a similar way then that should look seemless to a user. [5] over a free or reduced upgrade to users and developers that have already got both products [6] renove also AIRPORT from the integrated part as to keep it 'LITE'
I am around alot to test and help get it from BETA to Production