Patch Notes Update April Update - Patch Notes

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.
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:
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.
Next time I drop into an undiscovered system I'll try that an dget back to oyu
 
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)?
 
So, any word from FD about fixing the FSS?
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...
 
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...
Well, developers are giving us things in a limited time. Let's be honest, none of us expected so many bugs fixed in a single patch, as was the latest one. The list was quite long for a single, week long patch. Sure, they did break new things (fss), but still, it's better than before, overall.

As yourself, I too have the same problem with new issue tracker, but maybe it's easier for developers. We don't know.
I remember the old bug report, there were many moderators there. They were friendly, thanked and asked for followups. But eventually, the speed of bug fixes wasn't good. Just because moderator said "well done, thanks, we'll be looking at it!", didn't mean it would be fixed anytime soon. And miles long debug logs sent to them didn't seem to speed it up either.
 
Top Bottom