You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all thank you for making this, it's awesome, great freeware alternative to other paid tools.
Some background, I'm the author of freeware VR panel for MSFS that integrates with LNM. To implement current functionality I'm forced to parse HTML which is quite prone to errors and changes on your side. I'm also getting some feature requests which are currently impossible to implement. It would be really appreciated if current web API functionality could be enhanced to make the experience better.
I would suggest to start with:
/api/airport/info - missing runway information, add interpreted METAR (could live without that one)
/api/sim/info - would suggest separating sim info and progress, enhancing progress with information that is already available
/api/map/features - features that are vor/ndb are missing frequency
adding an endpoint for current flight plan information (read only would be ok)
adding an endpoint to get a list of available maps and setting a map
I'm attaching a file with the interfaces I use currently, for reference - interfaces.txt
I understand if interoperability wouldn't be a top priority for LNM, my thing caters to quite niche market of VR users, although I think it's beneficial for everyone involved and who knows what it might bring in the future.
Anyway, have a great new year.
Best,
b.
The text was updated successfully, but these errors were encountered:
Makes sense. But I'm a bit too busy fixing 3.0 stuff and updating the user manual. I can either put this into a 3.2 (not soon) or one of the smaller 3.0.X releases. Have to see.
But I'd like to enhance the interface for sure.
Hi.
First of all thank you for making this, it's awesome, great freeware alternative to other paid tools.
Some background, I'm the author of freeware VR panel for MSFS that integrates with LNM. To implement current functionality I'm forced to parse HTML which is quite prone to errors and changes on your side. I'm also getting some feature requests which are currently impossible to implement. It would be really appreciated if current web API functionality could be enhanced to make the experience better.
I would suggest to start with:
/api/airport/info
- missing runway information, add interpreted METAR (could live without that one)/api/sim/info
- would suggest separating sim info and progress, enhancing progress with information that is already available/api/map/features
- features that are vor/ndb are missing frequencyI'm attaching a file with the interfaces I use currently, for reference - interfaces.txt
I understand if interoperability wouldn't be a top priority for LNM, my thing caters to quite niche market of VR users, although I think it's beneficial for everyone involved and who knows what it might bring in the future.
Anyway, have a great new year.
Best,
b.
The text was updated successfully, but these errors were encountered: