Getting kicked out of Dune: Awakening with a “Network error: connection lost generic” message has been recently causing problems for players. This issue has been on the rise mainly after the patch update 1.1.10.00 on 2nd July. Many players took the issue to Steam and Reddit and reported endless loading screens with the pop-up message of Network error connection lost generic. In this article we will cover everything you need to know about the Dune Awakening Network error connection lost generic: how to fix it.
This repetitive “Connection Lost Generic” is triggered for players who were last seen/logged out in the northern area of Hagga Basin. Just simply logging off at that location will put you right up in a problem. Well, the good news is that developers were quick in addressing the issue in their official Twitter account. They also have provided a workaround until they fix this issue. So let’s dive in to know how to fix this issue.
Dune: Awakening Network error connection lost generic: How to fix it
Fix 1
If you’re facing an infinite load screen, a Steam player discovered a method that tricks the game into loading your character into a more stable, less populated area first. You’ll need to try loading your character into a different sietch on your current server. Just pick any available sietch on the list and keep trying until one finally lets you in. You might see messages saying your character didn’t log out correctly and needs time; just be persistent. Once you successfully load in, you’ll likely find yourself in the default starting zone. From there, log out of the game normally. When you go back to try logging into your usual sietch, hit the Escape key, then select “Respawn.” This will kill your character and allow you to load into a fresh, stable point closer to your base.
Note: Do NOT pick the exact sietch where you were originally stuck, as this will likely get you locked out again, forcing you to repeat the process.
Fix 2
A similar and short workaround is also suggested by the game devs in the Twitter post. To get this issue resolved, simply “log into another Sietch, go to Griffin’s Reach tradepost, log out, wait 30 seconds, then log back into your original Sietch.” Since this workaround is shared by the game devs, you will most likely succeed at this point.
After trying both workarounds, you will surely find your way in the game with no further issue. That’s all we recommend until an official patch is released. That being said, we hope you find this guide helpful. Also, be sure to check out DigiStatement, as we post many gaming-related articles daily.
