Tree of Savior Forum

Loadscreen stays over game after it finishes

Date and Time: Any time.
Game Control Mode (Keyboard/Joypad/Mouse): Any control mode.

Bug Description: This has been happening sporadically (once or twice a week) since beta started. The game’s loadscreen display won’t go away after the game has finished loading. You’ll be able to play normally (other players can see you, if you attack/use skills you can hear them happening), but will be completely blind since the loadscreen is stuck over everything. For some reason though, if you manage to mouse over items/skills in your keybinds or inventory/skill window, their descriptions will show up above the loadscreen.
The only way I’ve figured to make it go away was to close down the game and restart it.

Steps to reproduce the issue :

  1. Change maps or log in, it has happened to me on both circumstances.
  2. Most of the times the game finishes loading as normal.
  3. If you’re unlucky, the loadscreen won’t go away after the game finishes loading the zone.
  4. Game keeps functioning normally, but you’re completely blinded.

Screenshots / Video:

You can see here that the game is running normally behind the loadscreen, as I managed to pass the cursor over an item. I can move and try to attack things, but it won’t be much use since I can’t see anything.

System:

  • CPU: Intel i5
  • RAM: 8 GB
  • Graphics Card: GTS 250
  • Mainboard: H55H-M
  • Storage: 2TB
  • OS: Windows 7 64-bit
  • Internet Connection: 15MB download, 1MB upload

+1
happends pretty often for me too

Well, I searched the graphics section specifically and found nothing, so I went ahead and posted it. It’s my bad then, I should have searched the whole bug report section. Thanks for letting me know.

Good to see the devs are already aware of it, though.

Hi Saviors. Thanks for letting us know. As mentioned, the devs are aware about this issue. Unfortunately, an exact date of when they can implement a fix appears to be a blur. Rest assured that they are working hard to get this issue resolved.

Still having this issue.