Finally after so long, so happy to keep farming again. Great works guys.
Congratulations to all AMD users!
Iâm so curious⌠How did they solve it?
Stack overflow is not a place to ask something like that, youâre wrong. Iâm just saying âOh, itâs cool! It must have been difficult to understand this problemâ
I hope youâre not just trying to be annoying, because that would make you an complete idiot
They probably simply solved it by changing the code path that caused the lags to something else, after using profiling tools.
They could have achieved the same results (probably background stuff that the new HG have and other maps doesnât?) by different methods, or maybe reduced the amount of effects or increased the size of something instead of using various smaller pieces or simply removed the code path entirely since itâs only for aesthetics.
You canât be sure at all unless you try to jump into reverse engineering the previous and the current client on the native/engine side. We donât know the source of the problem.
what i mean is, dev ask at stack for the troubleshooting
and yes, im just trying to be annoying xD
another thing to note could be IMCâs âfixâ might not work for all. We have players having various BIOS version etc⌠This just make the variables a whole lot more. Aside from the the affected CPU models, we still have to account for BIOS version dont we?
I could be wrong here, just hinting IMC. Maybe make a fix for XXX Chip for version XXX for a start.
For those who find success with the âfixâ, i suggest you list your CPU model, with the BIOS version or smth.
Make things abit easier for IMC
I donât think you need to worry with BIOS version though.
Itâs more likely that they used some instructions (or functions that leads to these) that arenât well implemented/optimized on AMD processors.
Not sure on what exactly, Iâd guess either some more complex/specific instruction sets differences and/or something due to high number of calculations of floating points.
It can even be an inconsistency between both processors that leads to an infinite loop on AMD cpus due to a bad written IF condition >_<.
Altho the more information the better, I doubt BIOS have any role in actual instructions running on cpus >_<
Hello @STAFF_Amy @STAFF_Letitia @STAFF_YuriâŚ
the FPS drop issue returned after i did verify integrity of game files⌠is there anything i could do to fix it? Thanks
Iâm not sure if this fixes it but current release version is: 191615.
Latest patches released were 191405 and 191453.
Could you try testing this?
0) Close Tree of Savior.
1) Open the file:
C:/Program Files/Steam/steamapps/common/TreeOfSavior/release/release.revision.txt
2) Note down the number you see.
3) Now clear the file content and write:
191453
4) Save and close the file.
5) Try to run ToS again from Steam and check if you still have the FPS drops.
Please reply with the previous release.revision number you noted down and if it worked or not >_<
P.S.: After checking the 191615 pak file, it does edit Client_tos.exe. So Iâm quite sure this will fix the problem for you. They should update this on Steam soon, I think.
Ahhhhhh!!! @LunarRabbit its ok now!! Thats very helpful of you!! THANK YOUUU SO MUCH !!
So i opened the file and i saw 191615 then changed it to 191453⌠it worked!! Im so happy we have you here! 
Hi @LunarRabbit, I remember you providing an add-on for us when there was hook64 (or something like that) that made us all crashing. Now you even provided a solution to Jomanâs problem.
Just wondering, how do you know these stuff?
The addon was pretty easy (and a little ugly), it was simply trying to close whispers from strangers fast enough then a friend started to help some other users and told me what was happening. Shortly after that IMC actually patched the bug.
The solution to Jomanâs problem is quite simple, itâs the same as previous errors where you can get a file thatâs corrupted or not downloaded correctly, then revert the release.revision to the older number.
Long story:
Wall of text - read at your own risk
Messing with coding/C++ as a hobby since ~8 months after getting my first computer back when I was 14. Always liked to understand how things works. Also always loved to debug stuff and play a bit with reverse engineering when itâs for fun.
Before ToS I used to play a certain flash game via browser where I get into staff team from the community (country/language) I played. Got an opportunity to write custom a client with tools for moderators. As the game developed and enforced security this was harder. I got to learn a lot how the game organized the code and in the end I had to write a procedure to search for patterns within obfuscated code and call functions based on my previous code/packets documentation. They enforced the security too much and eventually caused most of the functionality to be impossible without deobfuscation due to good method and heavy randomization.
This last game gave me a pretty nice introduction on a lot of things related to online gaming. In addition to that I had to always search for functions and new things, so also by knowing how to code, but along with messing with files from a decently big game you can get used to guess how certain pieces of code will work or look with decent accuracy and then you can use that to find what you want or make good guesses.
Before we go to ToS, on this previous game I was on the âillegalâ side of things. Not as to gain advantage but to write bots with for fun features in game like some moderators used to have other bots from staffs.
Bots on that game mostly responded to commands and did some fun stuff via packets like placing objects where you couldnât by normal gameplay - you couldnât even automate gameplay with ease since it was platforming with box2d, I actually tried as a side project after being a moderator already but thatâs too much for me at current level of knowledge :x
Anyway, it was illegal for players to do so and I unknowingly annoyed the moderators A LOT due to the amount of warning log entries I generated :â). I was actually lucky to get called to be a staff on that game instead of getting banned permanently. lol
So we get into ToS. Always liked the base game and didnât even know too much about it. Suddenly, during kToS, I PMâd someone to ask about some things I saw here on forums.
Turns out this guy had a great idea after talking with me and even though I wouldnât use it he gave me a way he found to read IPF files for easier reading compared to other tools back then. What happens when youâre too curious + suddenly got access to parts of the source of a game you like? :â) reads reads
Some time after that I started to learn more how addon works due to ending up in Excrulonâs guild. And later started coding again and thinking more on how ToS works on code side rather than only playing like before. Got to know a few more things, especially from seeing other people talking, game issues and fixes, reading code from other addons and actually trying myself to find ideas to make my very first public addons.
After this you probably already know, I simply kept learning more and getting more used to how ToS works.
Yet I still didnât do anything big mostly because I really lack more experience and Iâd need to put more time into it, as well I get lazy pretty fast and I end up playing more than coding. Iâm still the hacky-ish guy that enjoys more taking some hard challenges than writing a big and useful thing. I gotta fix this some day.
Short story:
By being a nerd. And actually by being lucky to be at the right place and find the right people multiple times that ended up teaching or helping me to start to learn these stuff.
I read the whole thing.
Well, glad that you are here to help us out. Thanks.
Np! Just keep in mind that editing the release.revision number simply redownloads the last patch STAFF_Yuri announced along with the Additional Maintenance earlier this week. Itâs used to fix other issues, I just assumed itâd work here since Steam could have overwritten Client_tos.exe after verifying files >_<
Well, itâs great HG340 is fixed. But I donât believe the cataphract 2H spear fps drop is fixed yet (tried this Wednesday).
This topic was automatically closed after 60 days. New replies are no longer allowed.

