How to make the First Footfall, Armstrong Moment special (the easier version - not an obvious gripe)

GraphicEqualizer

GraphicEqualizer
Not sure if I have suggested this before or not...

When you get first footfall, that location should be permanently marked as a DSS discoverable POI beacon (like the other tourist surface beacons) and attributed to your commander name and date.

It might not seem like much, but it would be a fantastic community spirit thing. Especially for families and friends of players we have tragically lost IRL, we could visit the exact spot they stepped out and looked around in wonder and awe, see these places through their eyes and pay our respects as a kind of shrine. How beautiful would that be?!

It would also be the equivalent of the Eagle Lander's spot on the moon being a heritage site.

I don't think this would be too much work - I always try to keep my suggestions and wishes really low key and reasonable from a workload POV. Others may of course rant about the blue circle and wanting interiors etc., etc.
 

alexzk

A
GraphicEqualizer said:
When you get first footfall, that location should be permanently marked as a DSS discoverable POI beacon
Click to expand...
Beacons cannot be procedural generated. Those are stored in DB. That's why you see 1000s of them while you have billions of planets.
If everybody will do that, number of beacons will step out of tens millions easy in 1-2 months.

Question, who will pay for server storage room to keep those beacons? Game does not have subs.
 

GraphicEqualizer

GraphicEqualizer
Agreed. Though it's worth noting that first footfall is already tracked by player name... So I don't think adding a poi marker to the location would add much more data bloat. Also as a side bonus it would act as a way players could effectively bookmark locations on the surface (at least for the first visitor).

Fly around a world looking for a cool place, get first footfall... Always have that spot effectively bookmarked for future visits and meetups
 
Last edited:

GraphicEqualizer

GraphicEqualizer
Also, if this is not doable because data reasons then we must also be saying that users bookmarking surface areas will never be able to be done either... Which would be doubly sad
 

alexzk

A
GraphicEqualizer said:
Where are bookmarks stored currently? and where are the current first footfall attributions stored? If they are server side then I'd argue data storage is not an issue. It's all academic anyway really. lol
Click to expand...
Have no idea, but as we have limit 200, it is on server. And limit of 200 tells us that they keep storage low.
 

GraphicEqualizer

GraphicEqualizer
alexzk said:
Have no idea, but as we have limit 200, it is on server. And limit of 200 tells us that they keep storage low.
Click to expand...
Maybe for bookmarks, but the first footfall cmdr and planet is stored on the server and must be numbering in the hundreds of thousands already, so it wouldn't be hard to include a lat/long -- and for that to spawn a POI at that location
 

alexzk

A
GraphicEqualizer said:
so it wouldn't be hard to include a lat/long
Click to expand...
1st fall - index of commander - 8 bytes.
Lat/long - extra 16 bytes (or 8 if floats).
So it is double or triple size.

If you want do that correct, then you add "1st fall" table with
comander id + planet id = 8 + many bytes
then coordinates = 16 bytes.
 

GraphicEqualizer

GraphicEqualizer
A second slightly more work suggestion would be to have a brief cut scene-like disembark process, like the SRV has.
alexzk said:
1st fall - index of commander - 8 bytes.
Lat/long - extra 16 bytes (or 8 if floats).
So it is double or triple size.

If you want do that correct, then you add "1st fall" table with
comander id + planet id = 8 + many bytes
then coordinates = 16 bytes.
Click to expand...
I'll take the byte count analysis as agreement that its not too much to ask ;)
 

alexzk

A
GraphicEqualizer said:
I'll take the byte count analysis as agreement that its not too much to ask ;)
Click to expand...
No, key word is "double or triple amount" even if it was 1 to 3 change. On Galaxy scale this means a lot. For example I visited 50000 stars in 3 years. Lets say 15000 /y. If I land 1 planet per star this means 15000 new marks per year for 1 avr player. Somebody could do ONLY exploring, for them you can triple amounts visited.
Start multiply all and count expenses.

Also count CPU of the server. Once you get to table of 1000 000 records and bigger (i.e. record = 1 mark) you can't use cheap CPU, because it will respond slow. So you need buy more expensive one too.
 
Last edited:

GraphicEqualizer

GraphicEqualizer
Double or triple the already tiny byte count also sounds like an agreement that its not too much to ask ;)

As for the optimisation issues or reading their data, well FDev should be improving that anyway.
 
You must log in or register to reply here.
Back
Top Bottom