I don't use any of those. So that wouldn't be the problem.
I don't use any of those. So that wouldn't be the problem.
Lol. So. I have an error.log file, at C:\Users\Martel\AppData\Roaming\Wayward Gamers\KParser\1.6.6.0 that is 7.6 GB in size. Notepad and notepad++ can't even open the thing. <,<; I guess I left a parse open and it spammed the log.
So. note to self, don't leave the parser running if it's not working.
Well, you can delete it and try a shorter parse, and check that log to get an idea of what's going on. So not a total loss.
Anyone have the new memloc, post oct update?
1.6.7 release should fix the signature searching to work again, so as not to need the constant memloc updates. It's managed to work for me for the last couple updates, so I'm treating it as 'valid'.
Google Drive folder
I wrote a quick tool to auto-find the memloc that kParser needs for previous versions here:
http://www.elitemmonetwork.com/forum....php?f=11&t=28
Someone had requested me to make it for them since it was breaking every update. Unsure if it is still needed given that you mentioned now that the signature scanning is working again.
But if not this app will find the memloc.
Cant seem to get kparser to parse my char even with the updated memloc Kparser not working anymore at all or what?