Talk:FlightGear Multiplayer Server: Difference between revisions
Jump to navigation
Jump to search
(→Where do the repository live?: Link at bottom is dead. Is the repository on SourceForge these days?) |
(Switch to the {{forum url}} and {{forum link}} templates for all "flightgear.org/forum" forum links.) |
||
Line 20: | Line 20: | ||
|The current MP system probably isn't able to deal with this amount of "traffic" at the client-side - thus, it might make more sense to develop this as a server-side module, that can be run as part of the fgms process.<br/> | |The current MP system probably isn't able to deal with this amount of "traffic" at the client-side - thus, it might make more sense to develop this as a server-side module, that can be run as part of the fgms process.<br/> | ||
<br/> | <br/> | ||
See this thread for some fgms-related pointers: | See this thread for some fgms-related pointers: {{forum link|p=136501}} | ||
|{{cite web |url= | |{{cite web |url={{forum url|p=168249}} | ||
|title=<nowiki>Re: Populate AI Traffic with real traffic</nowiki> | |title=<nowiki>Re: Populate AI Traffic with real traffic</nowiki> | ||
|author=<nowiki>Hooray</nowiki> | |author=<nowiki>Hooray</nowiki> | ||
Line 71: | Line 71: | ||
{{FGCquote | {{FGCquote | ||
|once we have network access in Nasal (i.e. socket support) and possibly a dedicated server-side property tree, it wouldn't be all that complex to come up with a dedicated Nasal interpreter that may run as a "weather server" in a standalone fashion, and push out property updates to all connected clients, similar to the concept employed by Torsten's FGPanel code: | |once we have network access in Nasal (i.e. socket support) and possibly a dedicated server-side property tree, it wouldn't be all that complex to come up with a dedicated Nasal interpreter that may run as a "weather server" in a standalone fashion, and push out property updates to all connected clients, similar to the concept employed by Torsten's FGPanel code: {{forum link|p=150341}}<br/> | ||
<br/> | <br/> | ||
On the other hand, all of this is touching a number of areas that will be directly affected by the ongoing HLA work. | On the other hand, all of this is touching a number of areas that will be directly affected by the ongoing HLA work. |
Latest revision as of 13:46, 6 June 2019
Where do the repository live?
Where is the repository located? I have found one at https://sourceforge.net/p/fgms/src/ci/master/tree/, which seem to be the main place these days as the link at the end of the article currently is dead.
—Johan G (Talk | contribs) 10:22, 7 May 2019 (EDT)
Working around fgms limitations until HLA has materialized a little more ...
Work in progress This article or section will be worked on in the upcoming hours or days. See history for the latest developments. |
I had something similar to your JSON/Nasal client working a while ago for ship AIS, but didn't have the time to develop something more substantial.
|
The current MP system probably isn't able to deal with this amount of "traffic" at the client-side - thus, it might make more sense to develop this as a server-side module, that can be run as part of the fgms process.
|
once we have network access in Nasal (i.e. socket support) and possibly a dedicated server-side property tree, it wouldn't be all that complex to come up with a dedicated Nasal interpreter that may run as a "weather server" in a standalone fashion, and push out property updates to all connected clients, similar to the concept employed by Torsten's FGPanel code: [2]
|
Adding socket bindings to the Nasal interface would be quite simple, and it is well documented: Howto:Extend_Nasal One would only need to use PLIB's socket wrappers and expose them via extension functions, or even objects - using Tom's new cppbind framework in simgear/nasal/cppbind. |