File size? It should be about 4MB. Download it correctly before you report a problem.You telling me it works doesn't help the situation
Last edited by BullyWiiPlaza,
File size? It should be about 4MB. Download it correctly before you report a problem.You telling me it works doesn't help the situation
You have to use the tcpgecko installer in bully's jgecko u setup guide thread.Ok I've connected buy the memory viewer isn't showing anything
That's how it's supposed to be like. WorkWhy doesn't it freeze the game when I search?
Yeah. It doesn't freeze like that on Wii U, it just continues while searching.If you don't freeze the game than the memory can change while it's searching
Get used to it, it's fine most of the time anyway so pause the game using the official in-game function or don't press anything. It can't "instantly" dump.But that jeopardizes the accuracy of the searches, unless it somehow does an instant dump of the memory range and then searches through that
Just toggle the state of the core thread. Jeez louise.But that jeopardizes the accuracy of the searches, unless it somehow does an instant dump of the memory range and then searches through that
Are you saying it can't be fixed? in game pausing is not going to be sufficient for everythingGet used to it, it's fine most of the time anyway so pause the game using the official in-game function or don't press anything. It can't "instantly" dump.
What?Just toggle the state of the core thread. Jeez louise.
It can be, there is a threads tab and you can pause the game there by pausing the main thread (or whatever thread is needed). It's still not very stable how it seems.Are you saying it can't be fixed? in game pausing is not going to be sufficient for everything
No, it reads OutOfMemoryError and that's what it is. Make a smaller search range or assign more RAM if you are able to:So I stopped core 1 or whatever it was called in order to search the memory while shieldboarding in BotW and got a notification that a bunch of errorsoccurred when it got to 76% is this likely due to the instability of the thread feature?
It doesn't get stuck, it just gets very slow because it's out of memory again. Especially at that stage.So I searched a much smaller memory range(about half the size of the Wii's mem1) and it then got stuck during the evaluating bytes stage but there was no error message, is it likely the same problem? was it just not coded to give error messages during the evaluating bytes stage?
WIth paging or similar but it does on WindowsHow's it going to continue at any speed if it's out of memory?