Tree of Savior Forum

Game-breaking graphical glitches

Gameplay Bug Report Graphics
#1

Please fill in as much as you can :

Date and Time : August 9th, 1:30 am

Game Control Mode (Keyboard/Joypad/Mouse) : Keyboard

Bug Description : During all of the beta, my low end computer has encountered a number of graphical glitches that soon crash the game upon changing maps, or sometimes without any transition at all. This has heavily worsened on the last 2 days, making the game borderline unplayable for more than 10 minutes. The glitches manifest themselves in various ways:

The world map starts showing the actual screen background in place of the areas. Sometimes the whole map is removed:

UDHqsc0.jpg1280Ă—768

Icons and NPC sprites start glitching out into red squares:

ZTLl4xz.jpg1280Ă—769

Loading screen background bugs out too:

M9b4L0V.png1281Ă—768

And finally the crash (sometimes this doesn’t show up at all):

yHz1A9j.png1280Ă—767

Keep in mind that ToS was still playable though thursday/early friday. I had encountered these issues before albeit not as frequently. But since yesterday they have made it impossible to keep playing and testing ToS.

Steps to reproduce the issue :

  1. Log in.
  2. Spend a certain amount of time playing.
  3. Garbled graphics start to show up.
  4. Game suddenly crashes upon switching maps, sometimes with a Runtime error.

System

  • CPU : AMD Athlon X2 250 3.0 Ghz
  • RAM : 4 GB
  • Graphics Card : AMD Radeon 6450 HD
  • Mainboard : ASRock
  • Storage : 500 GB
  • OS : Windows 7
  • Country, Region : Argentina
#2

I have these same graphic glitches sometimes.

When you open the map through a Goddess Statue then graphic glitch #1 occurs. Using N to open the map does not cause this glitch.

The pixelated graphic bug #2 usually occurs for cinematics and dialogues.
In Overlong Bridge Valley(lvl64 area), every cinematic at one of the Stone Pillars, covered my entire screen with the pixels seen in SS #2. I could still see the map, I was still able to play and talk just fine. HP bars were still visible. But I couldn’t see the map or the characters on it.
Once the cinematic was over, the graphic glitch disappeared. It also does not occur in every cinematic, only in a few cases like on that map.

and #3 sometimes occurs when I warp into an area. The most common way to reproduce it is by warping into Klaipeda, doesn’t matter which channel or how you warp there.

#3

I have the same problem.

Date & Time: 11/12/2015. 11:33 AM (GMT+8)

Game Control: Keyboard Setting

Bug Description: Glitched Map. Sometimes those red boxes apprears as what OP has shown in 2nd and 3rd screenshots.

I was about to warp out of Klaipedia when it happened.
It happened a lot whenever I warp using Goddess Statue.

zJVLQ7l.jpg1366Ă—768

#4

Happened again. 2 hrs after my previous post.

kQzl8eZ.jpg1366Ă—768

This time I pressed “N” to check the world map. So I guess it’s not the Goddess Statue or Klaipedia at fault here.

[2 Edit] Did it again. After 2hrs+ of being able to play the error happened.

Date & Time: 11/12/2015. 4:01PM (GMT+8)

I just finished a boss fight and decided to warp back to town (overwieght at that time).

h9zWZne.jpg1366Ă—768

[3] After that error, this occured after logging in…tried to change channels but it didn’t solve the problem.
Relogged…didn’t help. It is still the same blacked out screen. :sob:

Solution: Warp to another map by using warp scroll or Klaipedia Stone, if you are not in Klaipedia. (Credits to Beanie) :heart_eyes:

GQ4mN3c.jpg1366Ă—768

@STAFF_J
@STAFF_Shawn
@STAFF_Marikim

Edit: [1] tagged the staffs.[2] another progress. another error.[3] another glitch?

#5

Thank you for bug reporting. It will be sent to our dev team to fix.

Thanks.

#6

What’s the solution for this?
I have the same problem.

#7

I had this issue through ICBT2 too, but luckily the game stopped crashing. I’d say just leave the graphic bug be unless it crashes the game.

#8

The problem is that after a few minutes (with the graphic glitch), specially after loading screens, the game does crash.
The pink/red squares don’t bother me that much.

#9

This problem is the main problem I have ever since ICBT and even right now, the problem still persists. Crashes happen very often in my low-end Laptop.

@Angres It is a problem once this pink/red square took the whole screen on cutscenes, which is what I have. =w=

#10

I’m crashing a lot more now.
After 15 minutes of gameplay the glitchy squares show up and then the next loading screen I go through, my game crashes.

1 Like
#11

Crap :confused:

I’m having bad memories of CBT1 xD. Try redownloading the game maybe, I don’t know, sorry.

#12

Same issue here. I didn’t miss it XD

#13

It’s exactly the same on my girlfriend’s machine as of now.
Random runtime errors with the strange red grainy glitch. It wasn’t a problem in iCBT2 for her and I’m sure nothing changed on her computer since then.
I tried fiddling with the graphic options in the user.xml (resolution, effects, etc.) but nothing worked so far.

#14

I hope they manage to fix it during tomorrow’s maintenance, otherwise I’ll only be able to play later in the month.
~sigh~

#15

At this point I’m fairly certain that server stress has something to do with it.

#16

Glitch.png1536Ă—864 1.69 MB

Having this glitch ever since the patch. Happens at the loading screen and ingame.

Affects anything placed on the map, eg. Buildings, trees. Does not affect characters, NPCs, or monsters

#17

:x Same issue here… any solucion? any idea? …
It wasn’t a problem in iCBT2

#18

I’ve had 6 hours of gameplay today and it crashed twice. It was annoying yet playable.
Idk, I guess it may be due to servers overpopulated or something like that because last weekend was impossible to play.

#19

Was it fixed?
I gave up playing because it was so stressful.
I’m afraid that they won’t fix it until the open access for free players.

#20

That’s wishful thinking. The graphic engine for this game is utter crap, as proven in other topics, so this will likely never get fixed. As the servers get more stable though, the occurrence of this will diminish, or so I’m guessing.