no problem for me, i am already lost
Notice Scan data bug fixed
- Thread starter Zac Antonaci
- Start date
Well I guess I wil play it safe, only 1600 LY's from where I parked my Anaconda but will wait a few days before I sell my infor from my Sag A trip....hoping I dont get killed by a trigger happy NPC before than.
Bit more info would be helpful, atleast enough to understand what the risks of traveling (or exploring) are.
Should be taken seriously, as the extent of damages could reach further than we think.
I'm usually happy to take FDev's side in discussions pertaining ED and any real or perceived issues; being involved in game development myself I'd like to think I have a fairly good idea of just how complex developing and maintaining a game of ED's scope is, and I do think for the most part they're doing a fine job with it.
However, I'll play devil's advocate for a moment here and say that the explorers community is already under the impression that exploration is fairly low on FD's priority list; taking this long to fix this issue (going over a week now) is not the way to dissuade a very loyal and vocal part of the community from this notion. The fact that FD stated that everything should be fine now when it wasn't doesn't exactly inspire confidence, either. It very much sounds like this matter wasn't even investigated properly until very recently when it became clear the issue won't go away by itself when the exploration server update completes, at which point they issued a warning to stop exploring while they look into it. What should have happened here is, the matter should have been given a serious look the moment it became apparent that this issue is present for everyone and not isolated to just a player or two. The warning to stop exploring should have been issued no later than day 2, and it really should have been fixed by now.
FDev, what sets your game apart is the realistically scaled galaxy; exploration is an important part of the game, even if the combat only crowd may represent a larger part of the population. The fact is the pew pew crowd can get their fix elsewhere easily and probably will after a while; you probably want to hang on to the explorers who like Elite for more than it's combat system. Next time an issue like this happens, it'd be nice if it was given some serious attention when it happens and not a week later. We have people stuck out there and unable to play the main game; those that are fine with killing that time in CQC can still have some fun, but those that don't care for it are literally unable to play and have been for a week. Like I said, I usually take FD's side but they seriously dropped the ball here. But hey, everyone makes mistakes, I just hope they take this one as a learning experience and take issues like this more seriously in the future.
However, I'll play devil's advocate for a moment here and say that the explorers community is already under the impression that exploration is fairly low on FD's priority list; taking this long to fix this issue (going over a week now) is not the way to dissuade a very loyal and vocal part of the community from this notion. The fact that FD stated that everything should be fine now when it wasn't doesn't exactly inspire confidence, either. It very much sounds like this matter wasn't even investigated properly until very recently when it became clear the issue won't go away by itself when the exploration server update completes, at which point they issued a warning to stop exploring while they look into it. What should have happened here is, the matter should have been given a serious look the moment it became apparent that this issue is present for everyone and not isolated to just a player or two. The warning to stop exploring should have been issued no later than day 2, and it really should have been fixed by now.
FDev, what sets your game apart is the realistically scaled galaxy; exploration is an important part of the game, even if the combat only crowd may represent a larger part of the population. The fact is the pew pew crowd can get their fix elsewhere easily and probably will after a while; you probably want to hang on to the explorers who like Elite for more than it's combat system. Next time an issue like this happens, it'd be nice if it was given some serious attention when it happens and not a week later. We have people stuck out there and unable to play the main game; those that are fine with killing that time in CQC can still have some fun, but those that don't care for it are literally unable to play and have been for a week. Like I said, I usually take FD's side but they seriously dropped the ball here. But hey, everyone makes mistakes, I just hope they take this one as a learning experience and take issues like this more seriously in the future.
I been stuck in starport since the 1.4 patch , there's no gameplay ,due to bugs , and i am sick of waiting for a hotfix
I had plans to play this weekend , but looking at how things go , i doubt i will even play this month because they without doubt will not hotfix anything for a while
Last edited:
thanks for letting me know I'm 22,000 ly from my home base of the founders world am heading to Saggitarius A* think I'll give my exploration a miss for now 
CQC it is then.... Cam CROW O>
CQC it is then.... Cam CROW O>
The launcher message is the only reason I found about this. I hope this will be fixed ASAP of course, but most importantly I want to thank FD for the warning in the launcher. This is a very efficient way to communicate.
Darnit! I'm on my way back from an excursion to the Statue of Liberty nebula and I'm trying to get home.
Darnit! I'm on my way back from an excursion to the Statue of Liberty nebula and I'm trying to get home.
Sings " won't be home for Xmass"
Ozric
Volunteer Moderator
FD have never yet stopped for a weekend if there's something that needs to be sorted out. To be honest I don't expect them to start now.
They just told a portion of their player base to stop playing until the issue is resolved. I hope they didn't just punch out for the weekend.