\0/
Patch Notes Update Update 3.3.03
Yep. Getting that myself. Oh welll.....
I wouldn't put it quite so forcibly, but it's a bit worrying that this was passed. It says a great deal about FD's QA unfortunately.
Five minutes playing with the game should have told any FD dev that it wasn't fit for release. It's not like any of these bugs are hard to find - they are literally in your face.
This build shouldn't have got anywhere near the live servers.
Hoping for a quick hotfix tomorrow.
Is this fix for the bug listed here? (Crashing to Desktop when a Prospector limpit lands on an asteroid with a core)
If not, then it will probably need some more testing, but I'm not going to spend time getting more info if it's already been fixed.
They should. But they’re not. I’m in Finland (GMT+2 hours) and they are still as broken as they ever were. This is on PS4. For an event that happened just moments ago, the log says ”4 hours ago” and the timestamp shown is 6 hours before the real time in Finland and 4 hours before UTC. Neither of those matches the ”4 hours ago”, which in itself is all wrong as it’s actually more like 1 minute ago. In the details view for an event, right next to the sesion log list it shows a timestamp that’s 2 hours later than the incorrect timestamp for the same event in the list. That time is also wrong. So you have three different ways to indicate the time there in one view and they are all wrong and not even wrong in the same way.
Or when, despite tested successfully internally, it is uncertain to whether the fix will be good in production.
Many developers will have come across a bug that cannot be easily tested in a test environment.
Last edited:
In the new update mapping a planet seems to make it disappear from the system map and the navigation tree view on the left panel in the cockpit. Sorry if this was already reported in this thread. There are so many issues that it’s hard to keep track. Maybe us players should open a Jira of our own so we can track all the issues.
It looks to me like they fixed the bug where factions would have self-massacre missions while at war.
At least for me, I had accepted two such missions, and today the mission giver was changed to the other warring faction and my progress erased.
When I checked the station, the self-massacre style missions that were available last night are now gone, replaced with missions to massacre the other warring faction.
So a good fix, but they should have put in notes and also wish I knew it was coming before I accepted missions from both factions.
At least for me, I had accepted two such missions, and today the mission giver was changed to the other warring faction and my progress erased.
When I checked the station, the self-massacre style missions that were available last night are now gone, replaced with missions to massacre the other warring faction.
So a good fix, but they should have put in notes and also wish I knew it was coming before I accepted missions from both factions.
Last edited:
Also, for me, 'Y' stars are not scanned until I target it and honk a 2nd time. (In addition to the looped belt cluster bug)
Undoubtedly true, but this particular feature pops up at the drop of a hat.
The bug where the message telling me I discovered asteroid belts (in a system 10 jumps ago) is still there. Please fix it...
Since the new patch I have noticed in FSS scanner continuous repeats of cluster scans (the same cluster is reported as discovered over and over again). Slightly annoying for large clusters as the reported discovery continues for minutes on end.
Literally the 3rd planet I've "scanned" since the patch.
Come on Frontier - do better!
T_T
Unfortunately, this is still happening to me sometimes.
And please fix the discovery repetition soon. I'm out exploring and that is very annoying for it to be looping through discoveries from a previous system.
Last edited: