Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashes when booting installed vpk #2

Open
TheSmallBlue opened this issue Sep 27, 2021 · 3 comments
Open

Crashes when booting installed vpk #2

TheSmallBlue opened this issue Sep 27, 2021 · 3 comments
Assignees
Labels
memory allocation For anything with a Memory Error

Comments

@TheSmallBlue
Copy link

We're trying to port the game MetaWare High-School (Demo) (here's a link if you wanna check the code out) via the distribution tool, once installed, however, we found that when booting it'd crash right after the developer's logo would show up. (For context, when you boot up the game the developer logo shows up, fades out, then 5 character icons move slowly through the screen before going into the actual main menu shortly after they stop moving. If this makes no sense I can record it off of my pc and upload it here later)

The log file mentions an Out of memory error which will probably not be a surprise since you do say some games will run into memory issues. You also mention tweaking them as necessary though so we were wondering if you could do that?

I'd like to think I'm somewhat decent at Python and Ren'py, but actual vita development is something I can't understand at ALL, so sorry if I didn't provide enough info. Here's the log file that mentions the out of memory thingie.

log.txt

@SonicMastr
Copy link
Owner

Tried myself and ended up with the same crash. Normally the first thing to look at if you get an out of memory error are the assets. So, I took a quick look at the assets myself and it looks as though there are icons (for character heads) that are 2000x2000 in resolution, which is decently sized. It's either an issue with the allocation for the newlib heap for surfaces (that renpy by itself uses) or the SceLibc heap (that the OpenGL ES 2.0 driver uses). HOPEFULLY a tweaking of those allocations should fix the issue. Until then, I'll keep this open, but if those changes fix it, I'll update it soon afterwards and keep you posted.

@SonicMastr SonicMastr self-assigned this Sep 29, 2021
@SonicMastr SonicMastr added the memory allocation For anything with a Memory Error label Sep 29, 2021
@TheSmallBlue
Copy link
Author

Gotcha, thank you so much

@TheSmallBlue
Copy link
Author

Any update on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
memory allocation For anything with a Memory Error
Projects
None yet
Development

No branches or pull requests

2 participants