Update only if you know what you are doing
Since these revisions, the configuration settings mode is completely changed. Have a look at this topic to learn more:
http://psx-scene.com/forums/f150/per...ig-file-97397/ (Per-game config file)
If you want to try it, you will have to re-enter your game config settings.
Configuration related to DNAS/VMC/DMA/COMPAT are now saved in single per game files on each media.
* per-game settings files are stored on each device. You can take your portable device everywhere, and keep the settings with the game easily.
* per-game settings files are stored on each device. Not a duplicate These devices are a lot faster to read/write than the MC (which is the location for the current global settings files).
* per-game settings files are stored on each device. Again That means for USB/ETH you can easily modify/backup/restore them on your personal computer.
* we won't read a single byte of these files until we really need it. For example, we will read one single game config file only when displaying the compatibility settings, or before running the game. Whereas global settings file are read at startup from the MC, and the whole file is saved on MC again when you modify a single game.
* each information contained into the new per-game config files can be used into the information screen. Thus you would be able to add a widget to display the compatibility flag on screen quickly, or displaying the DNAS id or VMC path, ...
* it require a migration tool to convert the old global setting file to the new scheme (see below)
* in the case, we ever add a feature that require to know the whole game list information, it will require to build it dynamically at will (but then it can be cached). However, as said before, as these files are stored on devices, it will not be that slow.
WARNING: ADDITIONAL SETUP REQUIRED
For network mode, you have to set your share in read/write to allow the creation/modification on configuration files.
Please report me HERE any bugs.
To use the convert tool, download the oplconvert_bin.zip, unzip and read the README
By the way, if you had already some config files with your own attributes definition (to use in the info page of the new themes), you can copy these files in their corresponding folder (related to the README, put them in either USB/ETH/HDD folders that you should create yourself), before running the convert tool. In that case the tool will merge them.
Note: thinner proposition to handle demo (or other uncommon case) is integrated. There is a new configuration item for each game (compatibility screen, use triangle) called "Custom ELF". You can enter whatever elf name is required to launch the demo/game. This is only needed when the startup ELF inside the ISO is NOT THE SAME as the game prefix (ex: SCES_xxx_xx). For example, the well known 4 Edges demo have a startup elf named "4EDGES.ELF'. In that case, name the ISO like this (for example):
Open the game compatibility screen, and put "4EDGES.ELF" as custom ELF. Now you can run it !
DEMO_001.00.The Black Lotus - 4 Edges.iso