Change Stellar Forge generation of POIs when FSS-scanning planets

Kzak · Feb 28, 2019

As it is right now, the Stellar Forge is being contacted by the client to determine the number and type of POIs, if any, when a planet is FSS-scanned. This leads to the wait-circle which has annoyed many.

I suggest that the FSS scan does *not* determine the number of POIs, only the type of POIs, if any.

The number of POIs should rather be determined when the planet is being mapped with probes, as that takes a number of seconds anyway, and with the final number of POIs being revealed when the planet is 100% mapped. This 'hides' the Stellar Forge response time better and lets people know right away if a planet has anything interesting with less waiting than the current mechanics, while the details are found out by mapping with probes.

EDIT: To be more detailed - when the first probe is launched that's going to hit the planet, that's when Stellar Forge should be contacted for determining the number of POIs/details thereof. This hides the server response time much better.

Thatchinho · Mar 6, 2019

Have already suggested the same thing for other reasons as part as my overall feedback and suggestion for planet based discovery in the Beta:

https://forums.frontier.co.uk/showt...o-the-other-Detailed-Feedback-and-Suggestions

Hence I support this proposal in principle!

I don't think that the timing is correct in the proposal though, as all the POIs still need to be there if someone doesn't use the probes. That's something FD can work out though!

aries_four · Mar 7, 2019

Yeah this is a great idea, if it can work with however they've set up the mapping process.

Captain Willard · Mar 7, 2019

LOLOLOOOL Buy FD a used cray computer. I bet none of you have any idea how many lines of code are in the forge.
It's not some cheap coding like ded red indigestion or cod.

Nirn Root Access · Mar 7, 2019

I too have noticed that searching for points of interest takes forever, so much so that I've simply stopped looking for them. It's a shame because POIs are such a cool part of exploration. I'm really curious how other commanders deal with this issue. You could visit the POIs listed in the galactic map on EDSM.net, for example, but that's definitely more sightseeing (also fun!) and less exploring.

Thatchinho · Mar 7, 2019

Captain Willard said:
LOLOLOOOL Buy FD a used cray computer. I bet none of you have any idea how many lines of code are in the forge.
It's not some cheap coding like ded red indigestion or cod.

You’re misunderstanding. The suggestion itself doesn’t really actually ask for a change to the SF.

The issue is the hold up in the FSS to detect numbers of Geological Signals.

All that’s really being asked for is to drop the number but from the FSSand shift it to the DSS.

That’s a pretty simple shift. It’s obviously doable. Here’s why:

- Geological POIs were there before the FSS was introduced so their generation isn’t tied to the FSS and they can be flown to without the FSS.

- DSS probing a body will identify the POIs even if you haven’t FSS scanned it.

DSS probing a body takes longer than an FSS scan, plus there’s the approach time before being able to use the DSS probes. So, just have the FSS say that there’s signals detected, and move the bit that takes the time to instead take place where there’s time already being occupied with other things and the time taken will be unnoticed.

MoonRacer · Mar 7, 2019

Nirn Root Access said:
I too have noticed that searching for points of interest takes forever, so much so that I've simply stopped looking for them. It's a shame because POIs are such a cool part of exploration. I'm really curious how other commanders deal with this issue. You could visit the POIs listed in the galactic map on EDSM.net, for example, but that's definitely more sightseeing (also fun!) and less exploring.

Hmmm. I just yesterday did a lot of FSS scans in systems. All of them were pre-discovered, nothing new for me, but some first mappings, I think. That said, I found several planets with POI (geological features). They never once had a time delay while FSS scanning them.

Is this delay only for systems that were not discovered previously? Because I just never see this problem, but I have only one 'first discovered system' and I do not remember any delays there.

Nirn Root Access · Mar 7, 2019

MoonRacer said:
Hmmm. I just yesterday did a lot of FSS scans in systems. All of them were pre-discovered, nothing new for me, but some first mappings, I think. That said, I found several planets with POI (geological features). They never once had a time delay while FSS scanning them.

Is this delay only for systems that were not discovered previously? Because I just never see this problem, but I have only one 'first discovered system' and I do not remember any delays there.

Yes, the problem is with first discovered system, I think because the points of interest have to be procedurally generated by the server when someone first discovers them. So you point the FSS scanner at a planet and now the server has to figure out if the planet has any POIs, and if so, how many, what type, where they are located, and possibly even how the individual Sinous Tubers or Gas Vents are arranged on site. Calculating all of this takes real server time that the player has to sit through, looking at a swirly loading icon. No server-side calculations would have to be changed in order to bring the suggestions in this thread to effect. Instead of the server reporting back to the player what POIs are present once all calculations are completed, report back when only the POI's type has been calculated (e.g. Geolocial phenomena, Biological phenomena, etc). The player quickly sees the result of the scan and can choose to move on or investigate, meanwhile the server continues churning in the background to finish all the calculations.

MoonRacer · Mar 7, 2019

Nirn Root Access said:
Yes, the problem is with first discovered system, I think because the points of interest have to be procedurally generated by the server when someone first discovers them. So you point the FSS scanner at a planet and now the server has to figure out if the planet has any POIs, and if so, how many, what type, where they are located, and possibly even how the individual Sinous Tubers or Gas Vents are arranged on site. Calculating all of this takes real server time that the player has to sit through, looking at a swirly loading icon. No server-side calculations would have to be changed in order to bring the suggestions in this thread to effect. Instead of the server reporting back to the player what POIs are present once all calculations are completed, report back when only the POI's type has been calculated (e.g. Geolocial phenomena, Biological phenomena, etc). The player quickly sees the result of the scan and can choose to move on or investigate, meanwhile the server continues churning in the background to finish all the calculations.

It seems I spoke too soon

Just now - scanning a previously discovered system - the game lost its nerve and dropped all, including my connection

Two systems before that I had a curious error, where the FSS could scan, normally fast, but it did not load in planet pictures when zooming in. The rest seems to have worked normally. But logging to the menu and later on logging out completely (and restarting the game) did not fix it. In the next system it again worked. Until now, when the game 'Could not connect to the matchmaking server' and gave my the option to quit to the menu. (Why it asks is everybody's question, since there is no other possibility). Btw. why matchmaking? I am playing solo...

So - I think the entire problem is a server/connection problem - again...