Flip asked me to also post my experience with this exact same thing happening to me.
System: Windows 10 (recently updated) version 1809 x64 2019-04
Intel Core i5-4430 CPU @ 3.00 GHz
12.0 GB RAM
NVIDIA GeForce GTX 1080 6GB
Atlas: NA PVE Patch 104.75 (Rev. 113867)
Attempted troubleshooting steps:
- Press Backspace button
- Attempt to access inventory with "i" key to change HUD options (pressing i resulted in the inventory flashing on my screen for one second before disappearing)
- Relog
- Die and respawn somewhere else (this didn't work out since I got a blank map with no options on where to respawn, so I had to force close and try again)
- Log onto EU server first (where I saw names and could interact)
- Log onto PVE server first (also able to interact)
- Validate files through Steam (twice, both with one file noticed)
- Attempt to log in without BattlEye (can't do this on official servers)
- Delete BattlEye folder and reopen game to force reinstall
- Uninstall BattlEye with uninstall option and reinstall using run as administrator
- Update video card driver
- Check for Windows Updates
- Restart computer
- Uninstall and reinstall Atlas
Approximately 1/10 relogs, I was actually able to interact with items, only to have the Network Failure error Flip screenshoted above occur. When no names appeared over anything, inventory wouldn't open, ect, I was able to collect materials using E, hit things with the left mouse button, and mount creatures (sort of, my character raised up and to the left and I could move the tame but not accurately). Most of those times, I exited to main menu or killed the program with Task Manager and restarted, but I sometimes let it time out to the BattlEye error. I actually lost count of how many times I logged in/out. Each time with the "create a new Atlas" because the reconnect option was only available if I logged out of a server other than NA PvE. I will also mention that I encounter the Host Time Out error when I first log in and must wait for that error to pop up and then for the program to start responding again so I can hit OK for it to progress to actually connecting (if I kill the task/program it goes through the same process again), which has been an issue for several weeks (on various internet connections).