* Disable waitForTick and waitBlanking
* Initial frame interpolation implementation
* Initial batch of speed fixes
* Fix Iron Boots
* Strip dead code once used for debugging
* Interpolate shadows
* Revert overzealous/redundant lookups
* Fix JUTFader
* Fix field map cursor
* Fix various particle effects
* Fix Midna when riding Wolf Link
* Fix title logo
* Title Logo 2: Electric Boogaloo
* Fixed grass and flowers
* "Unlock Framerate" config option (WIP)
* Wrap more things in TARGET_PC
* Finish wrapping things in TARGET_PC
* Missed one
* Disable dComIfGd_drawXluListInvisible when interpolating
---------
Co-authored-by: Luke Street <luke@street.dev>
* CI attempt
* syntax
* fix cmake for linux
* fix include directories and merge main
* fix PDB fighting
* fix gcc compiling
* fix SSCACHE for windows
* try and fix gcc
* more CI presets
* remove the android target for now
* bump cmake minimum to fix debug information format
* yet another attempt at fixing gcc
* yet another attempt at fixing gcc
* better CI matrixing
* yet another attempt at fixing GCC
* fix arm
* fix CI
* placeholder icons
* compile dawn from source for windows arm64
* fix icons and linker warnings
* fix cmake
* fetch libjpegturbo
---------
Co-authored-by: Luke Street <luke@street.dev>
Caused by a size that should've been sizeof(CMemBlock).
Simple way to repro was to open and close the full map on dpad, afterwards heap check would fail.
From my reading of the code this assert is likely incorrect. This throws on cases where usize has a sane-looking value (the length of the pContent null-terminated string), and from my understanding of how the data is parsed, this length is needed to figure out the location of the next "paragraph".
Happens for me when loading a save in Death Mountain Twilight. Confirmed in Dolphin with the same save file.
PowerPC does not raise an exception on division by zero, so I assume this is an original game "bug"
This fixes crashes when first entering North Faaron cave and
Renado's Sanctuary due to system heap exhaustion resulting from
multiple threads allocating on the heap at once.
There's some sort of weird contention going on - for some reason the
game gobbles up seemingly any amount of memory you throw at it when
the two threads are competing for heap space. Using a separate heap
in the async thread sidesteps the issue.
PJB3005