Difference between revisions of "Project Hamac"
(Hamac summary) |
(Removed category.) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
}} | }} | ||
| − | + | Having experience with first and second generation [[Multi-player|multi-player]] projects in [[IRCMFD]] and [[MultiOrb]], the [[CCCP Fleet|CCCP Team]] were looking for multi-player strategies for their in-development simulator [http://openkosmos.sourceforge.net/ Kosmos]. Two methods were suggested. The first was developed wholly internally by Russell Smith based on plans for [[MultiOrb]] before it was shelved. The second, a 'thin client' system, had no previous developments to build on, so a plug-in for Orbiter was made to obtain test results. | |
| − | Having experience with first and second generation [[ | ||
==Method== | ==Method== | ||
| − | Using bare TCP and UDP connections between server and clients, Project Hamac would rightly be a third-generation | + | Using bare TCP and UDP connections between server and clients, '''Project Hamac''' would rightly be a third-generation multi-player system, in the same bracket as [[OMP]]. |
The concept of the ''thin client'', however, means Orbiter is only used as the rendering engine and supplier of basic ship-local physics (rotation, thrust, docking etc.). A central physics server determines the dynamics, specifically the orbit, and controls the flow of data to the clients providing a jitter-free inter-user experience at the expense of slight lag when executing translations. | The concept of the ''thin client'', however, means Orbiter is only used as the rendering engine and supplier of basic ship-local physics (rotation, thrust, docking etc.). A central physics server determines the dynamics, specifically the orbit, and controls the flow of data to the clients providing a jitter-free inter-user experience at the expense of slight lag when executing translations. | ||
==Current status== | ==Current status== | ||
| − | Whilst some modifications were made to the code to make the system user-facing, | + | Whilst some modifications were made to the code to make the system user-facing, multiple problems were encountered when trying to extend the system to Orbiter (for example, when a ship is docked, it will not update its position at the same time as a neighbor making three-way docking impossible with this system), consequently development was stopped as the technique was proven as successful and the [http://openkosmos.sourceforge.net/ target system] will not have these problems that need to be worked around. |
| − | The project, comprising the physics server (''orbits'') and the | + | The project, comprising the physics server (''orbits'') and the plug-in (''hamac.dll''), is publically available for users to experiment with or to deploy a public service. |
==See also== | ==See also== | ||
| − | [[ | + | * [[Multi-player]] -- an overview of multi-player add-ons for Orbiter |
| + | * [[IRCMFD]] | ||
| + | * [[Multiorb]] | ||
| + | * [[OMP]] | ||
| − | [[ | + | [[Category:Articles]] |
| − | + | [[Category:Add-ons]] | |
| − | [[ | + | [[Category:Utilities add-ons]] |
| − | + | [[Category:Multi-player add-ons]] | |
| − | + | [[Category:Add-ons by David Henderson]] | |
| − | |||
| − | [[Category: | ||
| − | [[Category: | ||
| − | [[Category: | ||
Latest revision as of 13:05, 8 November 2022
|
Project home: Project Hamac |
Having experience with first and second generation multi-player projects in IRCMFD and MultiOrb, the CCCP Team were looking for multi-player strategies for their in-development simulator Kosmos. Two methods were suggested. The first was developed wholly internally by Russell Smith based on plans for MultiOrb before it was shelved. The second, a 'thin client' system, had no previous developments to build on, so a plug-in for Orbiter was made to obtain test results.
Method[edit]
Using bare TCP and UDP connections between server and clients, Project Hamac would rightly be a third-generation multi-player system, in the same bracket as OMP.
The concept of the thin client, however, means Orbiter is only used as the rendering engine and supplier of basic ship-local physics (rotation, thrust, docking etc.). A central physics server determines the dynamics, specifically the orbit, and controls the flow of data to the clients providing a jitter-free inter-user experience at the expense of slight lag when executing translations.
Current status[edit]
Whilst some modifications were made to the code to make the system user-facing, multiple problems were encountered when trying to extend the system to Orbiter (for example, when a ship is docked, it will not update its position at the same time as a neighbor making three-way docking impossible with this system), consequently development was stopped as the technique was proven as successful and the target system will not have these problems that need to be worked around.
The project, comprising the physics server (orbits) and the plug-in (hamac.dll), is publically available for users to experiment with or to deploy a public service.
See also[edit]
- Multi-player -- an overview of multi-player add-ons for Orbiter
- IRCMFD
- Multiorb
- OMP