Changes between Initial Version and Version 1 of Ticket #14407
- Timestamp:
- Apr 14, 2023, 8:13:42 PM (19 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #14407
- Property Summary 3DS: Utilize linear heap for handling heavy data amounts → 3DS: make use of linear heap to make resource-intensive games playable
-
Ticket #14407 – Description
initial v1 3 3 On the O3DS (Original 3DS), the main program memory, the regular heap, and the linear heap combined can be no greater than 64MB by default; this can be increased up to 96MB when building ScummVM as a .cia file by [https://github.com/scummvm/scummvm/blob/master/backends/platform/3ds/app/scummvm.rsf#L62 editing the .rsf file]. Similarly, on the N3DS (New 3DS), the combined memory cannot exceed 124MB by default, but can be increased to 178 by [https://github.com/scummvm/scummvm/blob/master/backends/platform/3ds/app/scummvm.rsf#L79 editing the .rsf file]. However, per internal 3DS documentation from the Nintendo gigaleaks (find it yourself), the regular heap is capped to 96MB, even on the N3DS. 4 4 5 Currently, the 3DS port of ScummVM uses the default regular and linear heap sizes [https://github.com/devkitPro/libctru/blob/master/libctru/source/system/allocateHeaps.c as defined in ctrulib] (<=24MB and <=32MB, respectively). Not only does it mean that there is tons of available memory currently being unused (up to 152+MB, not accounting for stack memory and screen buffers in the linear heap), but it also means the TinyGL-powered games all segfault during initial loading, if not immediately. As far as I know, the only 3D game that can be run on the 3DS port is Blade Runner, and that's only because it uses voxel-based character models.5 Currently, the 3DS port of ScummVM uses the default regular and linear heap sizes [https://github.com/devkitPro/libctru/blob/master/libctru/source/system/allocateHeaps.c as defined in ctrulib] (<=24MB and <=32MB, respectively). Not only does it mean that there is tons of available memory currently being unused (up to 152+MB, not accounting for stack memory and screen buffers in the linear heap), but it also means the TinyGL-powered games all segfault during initial loading, if not immediately. As far as I know, the only 3D game that can currently be run on the 3DS port is Blade Runner, and that's only because it uses voxel-based character models. 6 6 7 I have experimented with maxxing out the regular heap to its 96MB cap, and in both Grim Fandango and The Longest Journey, the intro cutscenes play sin their entirety and the starting areas load up successfully (most of Manny's office in GF, and the Arcadia cliffside in TLJ). Attempting to progress beyond this (accessing Manny's inventory, moving right to the screen with his computer, or leaving his office in GF; walking right to the White Dragon's nest or further in TLJ) causes a segfault.7 I have experimented with maxxing out the regular heap to its 96MB cap, and in both Grim Fandango and The Longest Journey, the intro cutscenes play in their entirety and the starting areas load up successfully (most of Manny's office in GF, and the Arcadia cliffside in TLJ). Attempting to progress beyond this (accessing Manny's inventory, moving right to the screen with his computer, or leaving his office in GF; walking right to the White Dragon's nest or further in TLJ) causes a segfault. 8 8 9 9 If the 3DS's linear heap could be used to hold memory-intensive data, such as textures, streaming data, etc., it might very well be possible to get all the 3D games to run in the 3DS port. Except for Penumbra Overture, of course. That would be a fool's errand.
