I think the problem may be related to the time when the rewind function was added, but having the rewind turned off and even lowering the buffer to the minimum (in case it could still affect even if it is off) does not change the size of the states. In the early days of the hack of snes classic mini it seems that similar problems were reported with retroarch, apparently, cluster solved these problems in its version of retroarch 1.0c, in these commits 1.0c.master, in the file retroarch.hmod/bin/retroarch-clover-child, but it seems that there is talk about compression of screenshots and I do not know if those changes would help solve the problem in 3ds. In 1.3.3 and 1.3.6 it did not happen in any core, in the current 1.7.7 it happens and I don't know from what version this has been happening, but looking for the forums it seems that the problems of time in creating and loading save states take reporting since 2017, around the release of versions 1.4.0 and 1.6.0. Being such heavy states, they also take a long time to load. ![]() Observe how a huge save state is created (of 5000 kb in the mentioned core of snes9x2002 and that takes 20 seconds or more to be done).Open the quick menu of retroarch and take a save state.Load one core (for example, snes9x2002).Launch retroarch 3ds 1.7.7 via cia in the main console menu.Save states are too heavy in all cores (so it must be a problem with retroarch) and consequently, they take a long time to be made and loaded, even in lighter cores like those of nes or gbc. Smallest save states size, equaling it with the use of platforms such as pc or snes classic mini and thus recovering the performance they had in previous versions of 3ds. In my PC with retroarch 1.7.7, the savestates are much lighter than in 3ds, similar to the one described above of 500 kb for the cores of snes and 150 kb for the cores of genesis, so something goes wrong in the operation of the savestates in 3ds. In 1.3.3, the savestates of the Snes cores occupied around 500 kb and now in 1.7.7 they occupy about 5 MB, in the cores Picodrive / Genesis plus gx the states were around 150 kb and now 1 MB. However, there is a problem that wasn't present in version 1.3.3: in version 1.7.7, in all cores the saves states take a long time to be done and loaded, and this happens because the saves states have an abnormal size compared to retroarch in other platforms and in previous versions in 3ds, they are too heavy. All the updates of menu rgui work really well in 3ds, with no impact on the emulation and maintaining the same performance as version 1.3.3 / 1.3.6 (which were said to be the most stable in operation), even with some improvements like the filter support in some cores that did not allow it. I recently updated retroarch in my 3ds from version 1.3.3 to the latest 1.7.7, mainly motivated by the addition of Boxarts in the rgui menu.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |