Robert Sharksilver
Swashbuckler
Yeah, it was fine until I logged back in lastnight after the patch.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Are you sure it is okay to delete all of the items in the cache folder?Yes, there is a LOT of lag today and since the Meet and Greet last night. Many folks have it bad today and crashes. Maybe something to do with the amount of folks on lagging down the servers last night, somehow still is affecting us it seems, I don't know.
I remember in Potco we used to have to clear our cache folder. I hadn't heard it mentioned yet for Tlopo (I may have missed it) but I just went to my Program files, Tlopo, Cache folder and deleted 2000 items. Haven't been back in yet, but hoping it helps some.
Alright thanks!Deleting it probably isn't going to cause any issues. Worst thing I can think of is having to redo any changes you made to the game settings (graphics, audio levels, etc).
They made an entire update which caused the issue, so obviously it will take a while, they are gonna have to rewrite the entire update.The problem is something that was in the update last night. Captain Redhorn posted on the server thread that the devs know if the issue and have been working on it today.![]()
I'd delete .txo files, not sure about the others so I can't say. I'm not tech support, I'm just recalling days of Potco when lag got bad.Are you sure it is okay to delete all of the items in the cache folder?
When your frame rate drops its not anything network related its hardware/client side/graphics related.
When your fps is stable and normal but your attacks are registering slow, or taking a while to hit, or a enemy freezes and then jumps ahead almost like teleporting (some ships, or most ships) then thats server lag
There is a very distinct difference but this is definitely graphical/game client lag Im assuming they changed the way something was processed or rendered in version 1.3.3 to cause this accidentally
Im assuming they changed the way something was processed or rendered in version 1.3.3 to cause this accidentally