Patch Notes Update April Update - Patch Notes

baqar79

baqar79
LEAMMO said:
Unfortunately this doesn't seem to have been fixed. :(

unknown.png
Click to expand...

Yeah, I've added my contribution to the issue tracker there:

webapp

issues.frontierstore.net issues.frontierstore.net

Voted as well, as far as important issues goes, this is more important to me than the FSS bug.
 

Zaphod Beeblebrox IV

Zaphod Beeblebrox IV
Skeffin_Amtikshaw said:
The pattern for me at the moment is that mapping planets requiring 2 probes (or low mass 4-probe planets) 'sets' the bug - after that any subsequent planet in the system will be marked as 'Mapped' (and you can check this in the left hand nav panel). However, if you then go on to scan a high-mass six, or a seven probe planet, it re-sets the bug. Jumping to the next system also re-sets the bug for the new system, but if you go back it's still the same. Logging out altogether or to Main Menu does not reset the bug.
Also, if you scan a low mass planet with a moon in close proximity (or vice versa) the image of the probe landing on the target planet is replicated on the companion planet. Amusing as it may be, it's still a bug, and gives us a clue as to how it affects other planets in the system. In other words, it would appear that under certain circumstances the game to set the status of all the planets in the system to 'Mapped' for graphical display purposes, but in the commanders personal inventory the planet is still 'UnMapped'.

Btw I can't find the reference to this in the issues tracker - if anyone can point me to the right thread, it be grateful - thanks ! For now, I'm developing my memory skills as well

:rolleyes:
Click to expand...
Interesting. I have been doing some research too and my conclusion was that it's landable bodies, probe one landable body and you've put the probed gird on all of them. I've only tried this on a few systems but it happens every time. Of course testing this now is a bit of issue in itself as Fdev have introduced a patch to fix it in some cases. The patch appears to be to suppress the display of the overlay system wide after you have left the vicinity of the most recently probed body.
 

Greyza Badger

Greyza Badger
Zaphod Beeblebrox IV said:
Interesting. I have been doing some research too and my conclusion was that it's landable bodies, probe one landable body and you've put the probed gird on all of them. I've only tried this on a few systems but it happens every time. Of course testing this now is a bit of issue in itself as Fdev have introduced a patch to fix it in some cases. The patch appears to be to suppress the display of the overlay system wide after you have left the vicinity of the most recently probed body.
Click to expand...
Before you probe a landable, or even approach it, select it on the nav panel so you get the extra info. You will find that it is already listed as 'mapped'. It's pretty consistent for me on Xbox, even for undiscovered systems way out of the bubble that I'm pretty sure I am the first to enter.
 
Last edited:

Zaphod Beeblebrox IV

Zaphod Beeblebrox IV
Greyza Badger said:
Before you probe a landable, or even approach it, select it on the nav panel so you get the extra info. You will find that it is already listed as 'mapped'. It's pretty consistent for me on Xbox, even for undiscovered systems way out of the bubble that I'm pretty sure I am the first to enter.
Click to expand...
Next time I drop into an undiscovered system I'll try that an dget back to oyu
 

CaptainSeriousFun

CaptainSeriousFun
Where do I report that since the update my executable is moody when exiting to desktop, sometimes terminating the program (mostly when I exit to desktop in a station), sometimes not (almost never if I'm in an SRV at a Guardian site, forcing me to task manager/end task the program)?
 

MoonRacer

MoonRacer
Wobblin-Gobblin said:
So, any word from FD about fixing the FSS?
Click to expand...
Last week I think they acknowledged the FSS bugs. But I could be wrong. This week they are in the usual 'Sit It Out' mode. And - AFAIK - Page Harvey is on vacation or at least absent this week.
The FSS fix would be important for me, but there is a boatload of other serious problems, which hinder gameplay. Just look at the issue tracker, there ar lots of duplicates (10 reports for the same problem), which makes it hard to read. Also it is not cleaned up, since some bug reports are clearly issues for support, and not bugs. Nobody seems to read other reports before opening a new report. Acknowledgement of bug reports from the side of FDev is also missing now, on the old bug forums this still existed.
The Issue Tracker seems be sort of a Black Hole where you stuff in reports never to be seen again. Or maybe in billions of years when the Black Hole decays (Hawking) :p
An Issue Tracker - and I have seen my share - is not a write only memory, where you may input things of relevance or not, with no reaction. But the Issue Tracker is not maintained, nothing is confirmed by the owners of the bug (not us players), nothing is rejected, edited, duplicates are not marked or joined, and so on. I am not sure if it makes any sense to input things there. I still do, as good as I can, but I have not much hope for this thing. It seems to be there only to 'pacify the masses' - us.

So - bug fixes will come, I expect, but in no way timely and certainly not complete. And since the FSS is a major element of the game, even for non explorers who need it to hunt for USS, the game is severely blocked now. One can use the FSS, but it is annoying, especially if you used it often before the update, where it worked flawlessly. And a crashing game, when you kill skimmers, or a game which hangs on logout so that you have to kill it with the task manager are bugs too. It is uncomfortable to play now which is a pity, since in my impression the developers truly tried to give us nice things in very limited time...
 
You must log in or register to reply here.
Back
Top Bottom