If you delete the last (only) photo in the Photos part of the Datapad, it gets "stuck" on the Photos screen: it's still displayed as if it was an existing photo but the Edit menu no longer works as the photo doesn't actually exit anymore.
Additionally, every time you make a single photo then delete it, the photo counter will get increased but never reset to 0 when the (last) photo is deleted. Eg.: take one photo, it will read 001. Delete it, it will still read 001 even though you have no photos. Take another photo, now it will read 002, even though it's the first and only photo you currently have. Delete it and take another one, now it will be 003, while again actually being the only photo you have.
When the heart rate display is visible, jumping or getting airborne in any other way causes it to disappear for the duration of not being in contact with the ground, then it reappears on touchdown.
It only happens when standing still or walking, but not while running.
(On a side not not related to the issue itself: it could be useful to add a category here for "User Interface" or something similar, since these kinds of issues are not really graphics nor control related, but currently there's no really suitable category for them.)
When you select the "Edit" button (at least I guess that the one with a pencil represents that) on the right hand button column while viewing a photo, it opens a submenu of the sort towards the center of the Datapad screen. These new buttons, however, are displayed behind the photo itself, so only the right half of the first button is visible, and the rest aren't at all.
There may be further display/functionlaity issues here, as moving the selection twice to the left (first being the half visible new button, then moving it further to the left) then hitting Enter either activates something that's not visible (also behind the photo?) and awaiting further user input, or simply locks the Datapad in an unresponsive state until the Esc key is used to dismiss it.
There is no "tilde" key on many non-English keyboard layouts, so the current "autowalk" key assigment is effectively non-functional for non-English users.
Datapad controls (arrow keys + enter) may get locked in an unresponsive state at times: the selection highlight is missing, but you can hear the sound made when moving it as you press the arrow keys, however, hitting Enter doesn't activate anything so it's not just a visibility issue. You have to hit Esc to dismiss the datapad, then bring it up again and then it'll work correctly.
I couldn't yet find a clear pattern or reproduction method, but three times it happened after a failed world object interaction (left click on something which then produces an error message): once when I tried to access a "buried container" cache without an excavation tool and thus getting a message telling me that, and twice when I tried to pick up a deployed solar panel with not enough inventory space, again with a message about it. Opening the datapad after these events had it in this "locked" state. However, unlocking it and then trying the previous interaction again did not trigger the issue a second time, so there seems to be some other factor to it too.
(My current hunch is that it happens only on the first such failed interaction per play session, and I have a test case in my playthrough which did it once, so I'll try to fiddle with it to see if I can get it to trigger on purpose by some combination of actions.)
The Documents / Equipment and Documents / Crafting Plans sections of the datapad don't scroll their entry list when there are more items on them than what fits on the screen, but the selection higlight moves down to the non-displayed, offscreen entries and they can be opened by hitting Enter. Given how two areas are affected, it's likely that neither of theses kind of views can actually scroll properly, except the other ones don't have enough entries to need scrolling.
When repairing system slots and solar panels, the controls remain frozen for about another second after the "repair blackout" already ended, which gets really annoying after a while. I think this control lock should be removed when the "fade in from black" begins, not with a delay after it has already ended.
Customer support service by UserEcho