KCCacheProxy icon indicating copy to clipboard operation
KCCacheProxy copied to clipboard

Game randomly stuck at loading assets with Poi and need force F5

Open MisakaMikoto52 opened this issue 4 years ago • 3 comments

Describe the bug Game would randomly stuck at loading assets(whetherbe pvp, picture, images, and weddings) with Poi(viewer) and need to force F5 every time thus loosing connection to any current battle, marriage and etc....

To Reproduce Steps to reproduce the behavior:

  1. Try any function that have not being used before, eg: marriage
  2. KCCP stuck at GET, game stuck
  3. See screenshot that marriage assets failed to load despite having them in cache. Test connection to Google works fine. No issue with internet/connection, pre-block by using cookie settings direct connection to server works fine, VPN works fine too.

https://imgur.com/rwjXfiP

Desktop (please complete the following information):

  • Windows 8.1
  • Poi 10.6.0
  • KCCacheProxy version v2.6.3

This will get stuck on any new asset, thus include all event maps, all last dance kills, all new rewards pages, not safe to use for events because F5 is the only way.

MisakaMikoto52 avatar Dec 19 '20 06:12 MisakaMikoto52

I would also like to report that I have the same issue on Windows 10.

Startoku avatar Dec 30 '20 00:12 Startoku

I would like to report the same issue on Windows 10. I have tried reload the cache and reinstall the app, it doesn't help.

frostyfest avatar Jan 10 '21 13:01 frostyfest

I would also like to report that I have the same issue on Windows 10.

I've found a work-around to the issue. What worked for me was the following:

  1. Uninstall KCCacheProxy
  2. Go into both my Local and Roaming folder under C:\Users\<user account name>\AppData and delete any KCCacheProxy folders found and its contents.
  3. I then reinstalled the executable.
  4. Redid the instructions provided again, but skipped the instructions involving the full cache dump.
  5. For extra measure, I cleared my cache and cookies on Poi.

Following the above allowed me to access and play the game as normal. I'm not sure if the issue lies in the full cache dump, or how the proxy handles the cache.

I would like to say that I personally found this issue when I first set up the proxy with the full cache dump.

Startoku avatar Jan 17 '21 09:01 Startoku