Featurrequest: Connectability to flightgear

merspieler commented 6 years ago

It would be great if it would work with flightgear as well. If you intend to do not so, feel free to close the issue.

slawekmikula commented 3 years ago

@albar965 Not a problem at all. Some work is planned on my side (as you see the time is rather slow with my development ;) Thanks for info. I think it should be enough to look at this and get it working. Thanks !

merspieler commented 3 years ago

What's standing in the way of getting this directly into LNM?

sfrsfrsfr commented 3 years ago

another FG user here. i too would like to see this integrated into LNM. thx for all your efforts that went into LNM.

AgentSmith0 commented 1 year ago

Enroute Flight Navigation (https://github.com/Akaflieg-Freiburg/enroute) is able to get flight data from Flightgear, maybe this could help implementing this feature.

albar965 commented 1 year ago

Enroute Flight Navigation (https://github.com/Akaflieg-Freiburg/enroute) is able to get flight data from Flightgear, maybe this could help implementing this feature.

Thank you. I'll check this out.

japrudhomme commented 6 months ago

I would love to see LMN support FlightGear. I have been a FlightGear user for over decade on Windows and Linux. I recently found out about LMN after I purchased X-Plane 12 and enjoy it for XP12.

I would be happy to assist in development of this through testing. I can test Windows 10 and Linux Mint with FlightGear.

merspieler commented 6 months ago

See this comment on how to use it https://github.com/albar965/littlenavmap/issues/138#issuecomment-753488343

Note that you need to build against an older atools since with the latest it has issues https://github.com/slawekmikula/littlefgconnect/issues/3

Not sure if that means you also need an older LNM version.

Been using it before the update and apart from needing to dis- and re-enable the plugin in flightgear it worked fine.

albar965 commented 6 months ago

I have the FG connection constantly in the back of my mind. I'll see if I can create a fork and update it for new atools.

slawekmikula commented 4 months ago

@albar965 Alexander. Questions: What are the rules for using branches in atools/littlenavmap repos. Sometimes master was aligned with release/x.x branches. Sometimes (mostly) branches are moved forward and master branch is left for a very long time in the back. If I want to provide this tool aligned with LittleNavMap releases how should I proceed. Should I provide littlefgconnect for 3.0 branch in littlenavmap and 4.0 in atools AND 2.8 branch in littlenavmap and 3.8 in atools AND for master branches in both repositories ?

I was using master branches in order to be at the very head of development and in this case provide binaries for all future releases in LNM but the branches commit history does not allow this :)

albar965 commented 4 months ago

@slawekmikula Master is only for unstable development branches. I divert from the official recommendations on branching.

Currently active are atools release/4.0 and littlenavmap/release/3.0 . This remains until I'm done with the 3.0 versions and continue new development in master.

atools release/3.8 and littlenavmap release/2.8 are EOL and more or less equal to master. I'll archive these soon. Don't waste time working on these.

Alex

albar965 commented 2 months ago

@slawekmikula Anything I can help with? I see the last commit in littlefgconnect is a long time ago.

slawekmikula commented 2 months ago

Real life issues, but when original Author cared to look at this ticket, I think I'll go back to the repository and find what can be done :)I do not fly currently at all, too much topics in my self-owned company so I won't be able to test anything thoroughly, but I'll try. As far as I remember, everything was ready for a basic usage. On my disk I've got code (not completed) to feed multiplayer/ai planes to LNM from FG, but not everything was working. In this thread there are some issues with Qt socket and multithreading. This is the only project, in which i'm using Qt/Gui and my C++ is also quite rusted ;)

Main issues (for me, and as I remember them) were:

software stacks - we need fg addon, littlefgconnect running in the background. Quite complicated to run (FG, addon, fgconnect, LNM), so I was looking for better solution, but haven't got anything easy to replace
if this is kept, maybe there is a possibility to include some "tool run configuration" in LNM, in order to run littlefgconnect from LNM menu. The xplane/msfs are "included". For inexperienced user configure all and outside LNM was complicated.
distribution and building littlefgconnect for windows/linux/mac? (and code compatibility). I'm only Linux user and don't have access (nor time) to look at it. Does (if the code will be good and above LNM quality gate for the code) should be a part of the LNM distribution or it should be distributed somewhere else. On FG forums there were questions how to run it on Windows/Mac from non-devs users and there (at that time) was no other answer than to get the code and compile itself

albar965 commented 2 months ago

software stacks - we need fg addon, littlefgconnect running in the background. Quite complicated to run (FG, addon, fgconnect, LNM), so I was looking for better solution, but haven't got anything easy to replace

Frankly, I have no idea how it is used now. I'll have a close look. Maybe I can integrate some of it into LNM.

f this is kept, maybe there is a possibility to include some "tool run configuration" in LNM, in order to run littlefgconnect from LNM menu. The xplane/msfs are "included". For inexperienced user configure all and outside LNM was complicated.

I'll have a look at it. Normally it should be as easy as using X-Plane IMO.

distribution and building littlefgconnect for windows/linux/mac? (and code compatibility). I'm only Linux user and don't have access (nor time) to look at it. Does (if the code will be good and above LNM quality gate for the code) should be a part of the LNM distribution or it should be distributed somewhere else. On FG forums there were questions how to run it on Windows/Mac from non-devs users and there (at that time) was no other answer than to get the code and compile itself

I'd fork littlefgconnect, adapt LNM (connect FG tab in connect dialog, etc.) and then use the same build chain as I already have for Navconnect. Then deploy FGConnect in the same way as Navconnect and Xpconnect. This means: Include it in the archive.

slawekmikula commented 2 months ago

@albar965 ok, but please wait 1 week or something. I'll try to do as much as I can with the code right now on my repo and not pushed to github.

Integrating with LNM - don't think so with the "core" FG interconnect right now. Shared memory is a good idea and allow to change anything on the FG side (thinking online data etc.) and fiddle with it without interfering with the LNM. If all be feature complete ;) (real FG users will surely find something to add to payload data etc) maybe there would be something to integrate.
building - OK, thanks. I've started to modify LNM GUI to allow FG connection in my LNM form (as far as I remember :D). Just for that i've taken navconnect code and modify it to keep the gui/toolchain the same and only insert FG specific handlers.

albar965 commented 2 months ago

No problem. Will wait.

albar965 / littlenavmap

Featurrequest: Connectability to flightgear #138