Editing Multi-player
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 17: | Line 17: | ||
Hurdles split into roughly two camps: logical and technical. Logical hurdles need cunning to overcome but are wholly soluble in the addon (eg. lag compensation). Technical problems relate to limitations placed on the addon by Orbiter itself (eg. being unable to jump simtime, inability to control landed craft etc.). | Hurdles split into roughly two camps: logical and technical. Logical hurdles need cunning to overcome but are wholly soluble in the addon (eg. lag compensation). Technical problems relate to limitations placed on the addon by Orbiter itself (eg. being unable to jump simtime, inability to control landed craft etc.). | ||
| − | The first logical problem with multiplayer in Orbiter is | + | The first logical problem with multiplayer in Orbiter is range of speeds. The craft need to be visible to other players whilst sat on the ground at Havana, and equally when [[LEO|orbiting]] 200 miles above the Earth prograde, and equally retrograde. That's a difference in speeds of 15 kilometres per second. |
So what? | So what? | ||
| Line 23: | Line 23: | ||
Well, in your driving game, if you have a tenth-of-a-second lag at 180mph, your car will appear to jitter 8 metres. Irritating, but still on the road. | Well, in your driving game, if you have a tenth-of-a-second lag at 180mph, your car will appear to jitter 8 metres. Irritating, but still on the road. | ||
| − | If your point of reference is the surface of the Earth, so you have no jitter on the ground, a tenth of a second in [[LEO]] will cause jitter of 750 metres -- half a mile. It's not going to be easy to dock when you're not sure which | + | If your point of reference is the surface of the Earth, so you have no jitter on the ground, a tenth of a second in [[LEO]] will cause jitter of 750 metres -- half a mile. It's not going to be easy to dock when you're not sure which cublic kilometre your craft will be in next second! |
| − | An example of a technical hurdle is how to deal with time acceleration, and different system times. Orbiter works out the rotation angle of the planet depending on the SimTime. Different start times, time accelerations, pauses etc. cause these to become desynchronised. Suddenly a vessel | + | An example of a technical hurdle is how to deal with time acceleration, and different system times. Orbiter works out the rotation angle of the planet depending on the SimTime. Different start times, time accelerations, pauses etc. cause these to become desynchronised. Suddenly a vessel sat on the pad at Canaveral appears half way into the Atlantic to one user and somewhere around India. |
| − | Another technical hurdle would be supporting animations on | + | Another technical hurdle would be supporting animations on ship (eg. opening the DG's docking doors), or telling the Shuttle to start in Orbiter configuration on everybody's system. |
As one delves deeper into this it becomes aparent the technical hurdles are the key to the viability of a multiplayer plugin. It's been postulated core support is required before a general interface can become effective. | As one delves deeper into this it becomes aparent the technical hurdles are the key to the viability of a multiplayer plugin. It's been postulated core support is required before a general interface can become effective. | ||
| Line 48: | Line 48: | ||
*Toni Ylisirniö developed the first recorded interactive multiplayer plugin with his seminal [[IRCMFD]]. Added mostly as a toy for regulars on Orbiter's [[IRC]], it needed manual updates and really only addressed the speed-difference hurdle by switching to relative-to-closest-vessel position reporting when vessels passed within 15km of each other. Development has ceased. | *Toni Ylisirniö developed the first recorded interactive multiplayer plugin with his seminal [[IRCMFD]]. Added mostly as a toy for regulars on Orbiter's [[IRC]], it needed manual updates and really only addressed the speed-difference hurdle by switching to relative-to-closest-vessel position reporting when vessels passed within 15km of each other. Development has ceased. | ||
*[[MultiOrb]] took the IRCMFD model and provided automation (to deal with the logical hurdle of advising other craft of orientation and accelerative changes), as well as expanding the supported craft range and addressing some of the relative position reporting issues. Again it didn't seek to address time differences. Development has ceased. | *[[MultiOrb]] took the IRCMFD model and provided automation (to deal with the logical hurdle of advising other craft of orientation and accelerative changes), as well as expanding the supported craft range and addressing some of the relative position reporting issues. Again it didn't seek to address time differences. Development has ceased. | ||
| − | *[[OMP]] is a still-ongoing project, unrelated to the others outside of discursive advice, providing a more in-depth framework and seeking to address the time difference problem by | + | *[[OMP]] is a still-ongoing project, unrelated to the others outside of discursive advice, providing a more in-depth framework and seeking to address the time difference problem by synchronising the PCs with the simplified Network Time Protocol. Is still under developement. |
| − | |||
*[[Project Hamac]] is a proof-of-concept technology demonstrator, offering virtually no solutions to Orbiter technical hurdles (bar docking), but addressing most logical problems by implementing a physics server-graphical thin client model. Development has transferred to the [http://openkosmos.sourceforge.net/ Kosmos project]. | *[[Project Hamac]] is a proof-of-concept technology demonstrator, offering virtually no solutions to Orbiter technical hurdles (bar docking), but addressing most logical problems by implementing a physics server-graphical thin client model. Development has transferred to the [http://openkosmos.sourceforge.net/ Kosmos project]. | ||
| − | |||
No comprehensive product has yet been produced, and consequently this area of Orbiter development should still be considered experimental. | No comprehensive product has yet been produced, and consequently this area of Orbiter development should still be considered experimental. | ||
| Line 57: | Line 55: | ||
==See also== | ==See also== | ||
| − | [[ | + | [[:Category:Multiplayer addons]] |
| − | |||