However, I believe the issue might still stem from our svcGetInfo returns for a few values as noted above. Our scheduler could also be a cause for some issues as the addresses which are being mapped aren't consistent as previously discussed in development. This will also need to be looked into and checked. Currently, I believe this is the main issue to why MapPhysicalMemory games are throwing as what we call internally "Ascii Addr Reads". Games tend to start mapping at MapRegionBaseAddr. TotalPhysicalMemoryAvailableWithoutMmHeap and TotalPhysicalMemoryUsedWithoutMmHeap will also need to be updated as we require to store the personal_mn_heap size. MapPhysicalMemory should stay in canary for a while whilst we test all previous 3.0.0+ games we have known to work before to make sure we don't have any regressions. Notable examples of games which could be affected are games like Super Mario Odyssey. When implementing this cmd, games which were originally stubbed to 0, will now stop working. The info is pulled from the npdm, under the field System resource size. With MapPhysicalMemory, we also need to implement PersonalMnHeapSize which is at the time of writing(IsVirtualAddressMemoryEnabled).
The actual implementation of this svc is not exactly the issue of it not working.
0 kommentar(er)
