![new 3ds retroarch new 3ds retroarch](https://i.ebayimg.com/images/g/-h0AAOSwCFhh37fH/s-l640.jpg)
When enabled (by default on consoles), the current existing behaviour is maintained. This kind of ‘reload’ is required when changing cores (since each is a stand-alone application) – but if the core we want to launch is already loaded, then it’s wasted effort.ġ.9.3 adds a new Always Reload Core on Run Content option under Settings > Cores on statically built platforms. This basically means that RetroArch in it’s entirety is reloaded, which can be quite slow. most of the console ports), a new process is forked. (Static Platforms) Add option to not restart RetroArch when launching content with the currently loaded coreīefore, whenever content was loaded using a static build of RetroArch (i.e.
![new 3ds retroarch new 3ds retroarch](https://i.ytimg.com/vi/3bBzDjRX62Q/maxresdefault.jpg)
This minimises file I/O, and greatly improves performance on devices with slow storage The ‘core is locked’ status is now determined on core info initialisation by parsing the core directory listing, rather than by performing individual ‘lock file exists’ checks.The core info cache no longer contains ‘core is locked’ and ‘firmware missing’ data fields these are ‘dynamic’ properties that must be determined at runtime.This file is generated automatically when toggling on the Cache Core Info Files option, and we will also add it to core info file packaging such that updating info files (either manually or via the online updater) will force a refresh The presence of a core_info.refresh file in the core info directory will force a one-time refresh of the info cache.The core info cache file is compressed (rzip) to further reduce disk I/O.Core info cache file are stored as core_info.cache.Core info cache can now be enabled/disabled on all platforms via a new Settings > Core > Cache Core Info Files option.Things you should know about the core info file caching With the core info file cache, it only takes 12 seconds. An anecdotal report from the person who implemented this – previously without core info file caching t took 29 seconds just to boot XMB. This reality is what has led to a new feature called ‘core info file cache’.
![new 3ds retroarch new 3ds retroarch](https://www.picclickimg.com/d/l400/pict/284398726114_/?-Console-New-3DS-XL-DUAL-IPS-come.jpg)
Loading ~80 info files takes forever – and basically constitutes almost all the startup time on these systems. It seems that on platforms with slow disk I/O (mostly all game consoles), it takes the same amount of time to load a file no matter how large it is (within reason) – so ~300 ms to load one info file, and the same ~300 ms to load everything stored in one cache file. WiiU users get a couple of new cores, such as bk (the Oberon RISC emu), xRick (the Rick Dangerous game engine reimplementation), and REminiscence (the Flashback game engine reimplementation). PSP/Vita and 3DS users in particular will definitely notice these improvements. This used to take a very long time on platforms with slow disk I/O (such as game consoles). After that though, it only has one cached file it has to load at startup instead of having to sequentially read every single core info file. The first time RetroArch starts up (and/or new core info files are added), it will need to build/rebuild the cache. This should lead to significantly reduced startup times and content loading after the first initial startup. We have implemented core info file caching and enabled this by default for the console platforms. We are definitely aiming to have a new Lakka version ready with future releases of RetroArch though. We were initially aiming to have the Lakka version ready to be released concurrently with this version, but had to postpone it. We are aiming for a new version every two weeks. We have a roadmap now (see here), and you can expect more frequent releases from this point on. In addition to being able to support us on Patreon, there is now also the option to sponsor us on Github Sponsors! You can also help us out by buying some of our merch on our Teespring store! If you’d like to show your support, consider donating to us. This project exists because of your support and belief in us to keep going doing great things. Remember that this project exists for the benefit of our users, and that we wouldn’t keep doing this were it not for spreading the love with our users.