• ✨ ARCHIVE MODE ✨
    The forum has now been set to read-only mode, no new posts, resources, replies etc will not be possible.
    We recommend you join our Discord server to get real-time response: Discord Invite Link

Fixed [0.22] Pokédex Scroll Crash

Status
Not open for further replies.

Tornado9797

Content Developer
P3D Developer
Global Moderator
To trigger this crash, one has to scroll too fast in the Pokédex (to achieve this speed, you pretty much need to hit down arrow and S at the same time). This doesn't always happen, but it did happen to me a few minutes ago. This may also have to do with the fact that all the Pokémon in there were registered as caught.

Oh yea, no error report came up upon its crashing. So I unfortunately don't have any true proof.
 

nilllzz

Original Developer
Administrator
P3D Developer
can you remember which Pokémon you had selected when the crash occurred?
 

Tornado9797

Content Developer
P3D Developer
Global Moderator
can you remember which Pokémon you had selected when the crash occurred?
All I recall was that it occured around #210. It didn't happen any more times. So I think it might've been a one-time deal.
 

Splint

Champion
Seems to be related to memory usage rather then a specific pokémon.

I just recorded myself going trough the pokédex in various rows and various amounts and it does not matter which pokémon i choose.

When you scroll trough the pokédex it caches the pokémon u already looked at causing the memory to rapidly fill up.

For me the game crashed the moment it reached a certain amount of memory used.
The amount it crashed on was when it hit 1,600,000k memory.

U can check the memory usage if u open up the Windows Task Manager and go to the tab Processes.
Look up Pokemon3D.exe and keep notice of the Memory tab as you scroll trough the pokédex keep a note at how it goes up.

Am currently rendering the video and uploading it as soon as it is done.

Edit:
Both versions up

Keep checking the memory usage on the right i waited moving to the next pokémon when it nearly hit 1,600,000 it then crashed trying to cache in the next pokémon.

Short Version:

Full Version:
 

DracoHouston

Kolben Developer
Contributor
i tried to fix this tonight and its really weird. the textures used by the pokedex keep piling up, and no matter how i tried to store or retrieve the textures the memory would just keep going up. my theory is the garbage collector doesnt clean up xna texture2ds
 

DracoHouston

Kolben Developer
Contributor
i asked around and i think i have found the problem, no ETA on fix. requires a big change to the game i will have to clear with nilllzz
 

DracoHouston

Kolben Developer
Contributor
Tornado9797

yeah, we've deffo found a way to fix it. dunno if it'll be ready by friday but it shouldn't be an issue on tuesday. just don't scroll through the pokedex like that till then.

thank you a LOT for bringing this to our attention, you wont notice a thing but you have been a much bigger help than you could ever imagine :p
 

DracoHouston

Kolben Developer
Contributor
lol the fix ended up being really tiny in the end. nils like changed 1 function and now its down to 66 meg of ram in the pokedex no matter how fast your scroll though it :D
 

nilllzz

Original Developer
Administrator
P3D Developer
It was alot of work!
I added 6 lines of code. 6 LINES!!!
:D
It was a really easy fix at all :p
 
Status
Not open for further replies.
Top