lwho / pioneer Goto Github PK

• Lines, fuel consumption, duration for selected systems and hyperjump target
• Print sector in detail box
• Filter uninhabited systems

Allow systems to become explored in game and persist that state in save game.

Mentioned in http://spacesimcentral.com/ssc/topic/3924-there-is-a-way-to-map-update-info-the-unexplored-systems/?p=43415

Branch lwho/no_global_galaxy

• Hold a local RefCounted<Galaxy> where needed
  • Custom system database
  • Factions database
  • Galaxy caches
  • Galaxy generator
  • StarSystems
  • Sector
  • Space
• Make Galaxy object part of Game
• Views
• Lua API
• Do not hold a global Galaxy object (get rid of Pi::GetGalaxy())

Create a third kind of target indicator (additional to nav and combat target) to be used for missions.

See http://pioneerspacesim.net/forum/viewtopic.php?f=3&t=16&start=60#p776

with Lua event hooks onCargoTransfered

Would be nice for out-of-fuel and similar missions.

For example, for random star type selection

1. Space has a SectorCache::Slave
2. StarSystemCache::Slave is part of Galaxy, but updated by Space

Galaxy having a StarSystemCache::Slave causes some complications. Furthermore, it does not seem correct that Sector and StarSystem are treated differently. I think the correct solution is to

• Move StarSystemCache::Slave from Galaxy to Space
• Unify the slave fillers in Space as much as possible

Currently you can only select a system to be the target of the hyperjump and the primary star is automatically selected in multi-star systems.

With this PR you will be able to select any star in the destination system.

Should intra-system jumps be possible that way, too?
No, at least not in first implementation.

...based ob whether they are in front or behind their parent body.

Related to upstream issue 154

Core systems should be connected by point-to-point stargates that allow hyperjumps without a hyperdrive. So, new players could start without a hyperdrive and still have a limited mobility among core systems.

• Docking sequence like for orbital space stations
• No fuel needed
• Cost a fee

lwho/factions_cleanup

Game speed acceleration should be automatically changed based on speed and distance to bodies.

See http://pioneerspacesim.net/forum/viewtopic.php?f=3&t=59

Second try

Record player events and show them in a filterable logbook.

Mentioned in http://spacesimcentral.com/ssc/topic/3875-galatic-exploration/?p=42937

Allow to specify time of game start (e.g. to start in daylight).

http://pioneerspacesim.net/forum/viewtopic.php?f=3&t=267

Migration steps for a class

1. Derive class from std::enable_shared_from_this
2. RefCountedPtr<Class> to std::shared_ptr<Class>
3. shared = bare_ptr->shared_from_this(); where necessary (there must already be a shared_ptr for the object.

Current RefCounted classes

• CameraContext
• CollMesh
• FileSystem::FileData
• Galaxy
• GalaxyGenerator
• GalaxyObjectCache::Slave
• GasPatchContext
• GeoPatchContext
• Graphics::GL2::RenderBuffer
• Graphics::IndexBuffer
• Graphics::Material
• Graphics::Texture
• Graphics::VertexBuffer
• Random
• SceneGraph::Node
• Sector
• StarSystem
• SystemBody
• Terrain
• Text::DistanceFieldFont
• Text::TextureFont
• UI::Animation
• UI::Widget

Generating sectors and star systems in Lua.

A star is still shown as hyperjump target when already in the system. It should be de-selected then.

Maybe in single-star systems there should not be a hyperjump target selection at all?

• Cubic root
• Multiplications
• Put more sanity checks in the galaxy dumper
• Soft-Floats?

Systems with mission destinations should be visible and easily selectable as hyperjump target in the sector view.

Maybe the same for destination planets/orbital stations in system view.

See http://spacesimcentral.com/ssc/topic/3933-how-you-calculate-full-stop-distance/ and http://pioneerspacesim.net/forum/viewtopic.php?f=3&t=62

http://pioneerspacesim.net/forum/viewtopic.php?f=3&t=268#p3145

This is issue is for implementing no. 2 of the above post:

Selectively exploring bodies of a system (e.g. by Andrew's exploration probes). This would require giving each body its own exploration flag (or levels). More complex than no. 1, but probably not so much. Actually, having this, we don't need no. 1 anymore, as Lua could automatically mark every gas giant in the system explored etc.

• Exploration flag for SystemBody
• Properly integrate with system exploration (partially explored?)
• Show only bodies that are explored in system views
• Making it accessible from Lua
• Persisting exploration state

lwho/galgen_systembodies

Configurable keyboard shortcuts for filters;

• Draw vertical lines (V)
• Label out-of-range systems (O)
• Label uninhabited systems (U)
• Maximum zoom-in (Ctrl-+)
• Maximum zoom-out (Ctrl--)

Gas giants have a to shallow atmosphere because they use the gas constants of air. Make them use a hydrogen/helium mixture.

The fuel reserve for autopilot is currently hard-coded. It would be nice if this was configurable.

• At least in config.ini
• Later maybe from F3 screen per-game?