issues/bugs we've had since launch thread

Was idling looking through the bug forum, and noticed a bunch of things which have never been fixed since the PS4 launch / 2.4. Just wondering what else have people noticed still aren't fixed?

Note: this is not new items, just the ones we've had since 2017 around launch time and shortly after, to the first big update(s). Just a bit of fun, don't dog-pile onto FDev.

So I've noticed these:

"Unable to assign NPC crew". I first reported it 4/10/2017, but positive it had happened earlier and i'd waited until I could get footage, and noticed it again 23/1/2019.
https://forums.frontier.co.uk/showthread.php/474065-active-NPC-crew-unavailable-to-deploy-into-SLF

"Menu scrolling to top". Reported 26/9/2017 (first example I could find), someone just posted it again today 10/3/2019.
https://forums.frontier.co.uk/showthread.php/470877-Mission-menus-scroll-in-a-really-weird-way

Route plotting issues. A bunch of maybe different items, but it's that thing where for some reason it won't plot in the gal map, you fiddle a setting or swap from Realistic to Map, and suddenly it works.

Hostile NPC flag states. Where NPCs are hostile to you, but shooting them gets you wanted; or your NPC crew wont attack a enemy; or the cops wont attack; just the general "is this NPC hostile or not" and the game getting it wrong.

Landing pad backwards. The thing where it hasn't reset, so you either need to land the wrong way, or cancel/rquest to a different pad.
NPCs on your pad. Ditto like above.

Python cargo scoop. Often denied as a problem, but every so often it just seems to go weird, and not scoop properly, like it's misaligned with the scooping crosshairs. I first noticed this on PC way before the PS4 launch, but once I got a Python I did notice it off and on here too.


What else have we got? Was EBL introduced, or there from the start, and we were too poor to notice until later?
 
Last edited:
What else have we got? Was EBL introduced, or there from the start, and we were too poor to notice until later?

As I recall, the "flashing disco shadows", which predates EBL, was introduced when the infamous "Minecraft Textures" bug was patched. I sometimes wonder if Frontier just traded one problem for another, allocating resources that were once dedicated to shadows over to textures. Ironically, both textures and shadows were great in 3.3.

EBL is the ugly moving moire-pattern created by broken self-shading of ship interiors (and exteriors as well). It is triggered when entering orbital cruise and remains for the duration of one's time down on a planet's surface. This horrible visual glitch was added by one of the minor 3.0.? updates over a year ago. Since then it has gotten worse, to the point I also see this in space on occasion as well. To make matters worse, the new lighting system really amplifies this awful effect.

Long story short, the graphics shaders tied to the main light source (primary star) have been broken since 2.4.?, and they continue to get worse over time. The result visually ruins assets like stations, outposts, even our own cockpit when exposed to sunlight. These same assets look amazing in the dark, however. I'm very tempted to call this whole overarching problem the "Vampire Shader", as it "melts" in sunlight :p
 
Last edited:
Route planning still sucks.

Edit: I was extremely disappointed when I couldn't plot route to visited stars after I lost valuable data from a 28k ly trip the day before new years. The next day all of my visited stars reset to red.

2 months later I have a ton of data towards beagle point but looking back at that situation makes me upset.
 
Last edited:
Back on topic, a small bug that recently has become more of a hindrance is the two-finger salute with the L2 / R2 buttons. So for example, I've got zero throttle mapped to X+L2, which now is handy because the FSS requires zero throttle (yay). However, unlike X+L1, any "modifier" button combined with a number two trigger causes that modifier button to act as if it were the only button pressed. So in my case, X+L2 not only goes to zero throttle, but it also deselects my current target (which is usually the next system in a route). Not good.

This bug has been in the game since it released. I think Stormy tried to get some love for the L2 / R2 buttons, but nothing ever came of it.
 
Last edited:

stormyuk

Volunteer Moderator
@OP didn't stormy do a thread of the full list of persistent bugs somewhere....?

Did I? I honestly can't remember. It might be lost in the sands of time. The longest "issue" (as I think it might be something to do with the way Elite is programmed) is the "SC Judder" when you transition from one orbital body to another you often get a screen judder while in SC, which clearly can't be fixed. I reported that pretty much since day one. The odd thing about it is doesn't always happen, which would imply it IS a bug.

Anti-aliasing has always been awful too with lots of screen flicker, but that again, not really a bug, just an issue with the engine.
 
Last edited:
I landed backwards yesterday at Explorer's Anchorage. I thought that I had surpassed my beer limit and was wandering into drunk territory. It was rather unsettling actually. This is an actual bug, first time experiencing it but I can attest it does exist.

Gary
 
Back on topic, a small bug that recently has become more of a hindrance is the two-finger salute with the L2 / R2 buttons. So for example, I've got zero throttle mapped to X+L2, which now is handy because the FSS requires zero throttle (yay). However, unlike X+L1, any "modifier" button combined with a number two trigger causes that modifier button to act as if it were the only button pressed. So in my case, X+L2 not only goes to zero throttle, but it also deselects my current target (which is usually the next system in a route). Not good.

This bug has been in the game since it released. I think Stormy tried to get some love for the L2 / R2 buttons, but nothing ever came of it.

This affects L3 and R3 as well. As I use O + L3 to mode switch. If I’m in normal space I mode switch and boost at the same time. Very dangerous on surfaces.
 
Don't really know if somebody else got this problem also, when i buy something in a station and i log off (save the game first!!) then when i am going to play again i notice that the stuff i bought are gone and get my "old" slots back. Did bought a amfu because i wanted to try that neutron highway and when i needed to repair the FSD i notice it was gone.
 
Don't really know if somebody else got this problem also, when i buy something in a station and i log off (save the game first!!) then when i am going to play again i notice that the stuff i bought are gone and get my "old" slots back. Did bought a amfu because i wanted to try that neutron highway and when i needed to repair the FSD i notice it was gone.

It saves when you log off properly.
 
I haven't run missions or passengers in ages, but today I started working for a faction again, and I see the ridiculously-long wait time for the mission board to load is still a thing all these many months later. :(
 
I haven't run missions or passengers in ages, but today I started working for a faction again, and I see the ridiculously-long wait time for the mission board to load is still a thing all these many months later. :(

That's more server issues instead of the game being glitchy now since Mission Boards have their own separate server now.
 
That's more server issues instead of the game being glitchy now since Mission Boards have their own separate server now.

I dunno about that - seems like mission board loading times were always crap on PS4 after the 2.4 update. One thing that definitely is "game glitchy" is the bouncing highlighter that makes selecting a mission further down the list a real pain. This is a very "amateur" bug that's been in the game since like forever...
 
Back
Top Bottom