I think he's going to count them... Just to check...
How many systems are there presently?
- Thread starter EUS
- Start date
I think he's going to count them... Just to check...
I think last check a few months/weeks ago was that we had explored like 0.0002% of the Milky way or something ridiculously low like that
Actually, not even that. You only need the seed number of the system and the engine does the rest.
Same seed will always bring off the same result. You just load it through the engine.
So it's even less of a memory required.
The engine was developed exactly for those such requirements of the game. Which is why planetary exploration in every single planet is perfectly within its capabilities as well and it's only a matter of when the refinement of the engine to extend to that is done and delivered.
I'm a pencil neck, not a CompSci guy, so bear with me.
So the server(s) care about a system only when a player enters said system, does some type of DB lookup, sends that info the the client's machine, and it's the client's machine that renders (if the right terminology) the instance?
Once I move on to a new system, the old system is just *gone*, unless some other player is in it?
So the server(s) care about a system only when a player enters said system, does some type of DB lookup, sends that info the the client's machine, and it's the client's machine that renders (if the right terminology) the instance?
Once I move on to a new system, the old system is just *gone*, unless some other player is in it?
well sorta.
If someone has already been there to trigger the system into generating then that's what that system is forever, its set in stone
But until then its just a set of procedural generation code which is sent to your machine, which your machine then renders and you jump into the system
at least that's my best interpretation of it, some other boffin will most likely clarify this further
If someone has already been there to trigger the system into generating then that's what that system is forever, its set in stone
But until then its just a set of procedural generation code which is sent to your machine, which your machine then renders and you jump into the system
at least that's my best interpretation of it, some other boffin will most likely clarify this further
More or less, yes, only that the DB look up is really small. It's only a seed that is then put into the engine and that gives out an outcome. Same seed will always give the same outcome. Sort of like a very complex equation. Regardless of the amount of input numbers, the same input will always have the same result. f(x,y,z,...,n) will have the same result for the same (x,y,z,...,n),no matter the amount of times it is repeated.
I'm not sure if the rendering is done on the client's end, but I doubt it. (that would allow too much exploiting) It still takes a lot less resources this way. And there's no exaggeration to that "A LOT".
The only DB required would be the whole "first discovery" attachment. Everything else is just an input seed.
Last edited:
< chortles >
You can only see a certain area at once. If every system was viewable at once... It would he really hard to click anything.
400 billion is not a lie. To even look at every single system in the map would take a long time. Just by zooming out with a scroll wheel you are skipping over thousands upon millions upon billions of areas...
400 billion is not a lie. To even look at every single system in the map would take a long time. Just by zooming out with a scroll wheel you are skipping over thousands upon millions upon billions of areas...
Last edited:
That's like 800,000 systems visited/explored.
Guess the Explorers among us have been pretty busy,,,,,,,,,,,,,,,,,,
