I personally don't have experience with that, but hopefully this can help a few people out, if they're confused about. The whole process is a little more involved if you're running older firmwares that don't require Cobra. config file into the same directory as your ISO (i.e. Pay attention to capitalization and whether or not the ISO extension on your game is capitalized or not. For example, if your game ISO is TonyHawksAmericanWasteland.ISO, name the file. Once you have all the lines you need and have everything copy and pasted to them, save the file with a name matching the game's name, with file extension ".ISO.CONFIG".Then you'll need to insert 30 bytes to fill those 3 lines that you can then replace with the codes you need. Do this for every line you need, as indicated by the data found on the wiki.įor example, if you're looking at a config file that consists of 3 lines, such as: Inserting 10 bytes will insert 1 entire line of data. If you have to create a new line of data, do so by selecting Edit and then selecting Insert Bytes. ![]() 00000010) and copy and paste that data into the corresponding line in the hex editor. ![]() Do the same for each of the lines of data (i.e. config file for, and paste it into the hex editor. config example chart that lies between "00000000" and "=" next to the game you want to create a. Download and install a hex editor such as HXD, open it, and create a new file.config file they can't find and have to write their own, it goes like this. Though I'm sure the resource you posted will end up saving people a lot of time (I know it will for me), for future reference in case anyone runs into a. config file isn't that difficult, assuming you have the codes given to you found at the psdevwiki linked earlier in this thread. I've messed around with a good deal of these in the past few weeks playing PS2 games on PS3, and as it turns out, creating a. config file collection, those will definitely come in handy. Hey, I'm new here, but hopefully I can shed a little light on the subject. self) or from an external file (this feature is supported only by ps2_lf) And can be loaded from hardcoded data (inside the. In short, the "game configs" can modify the game image (by patching it) and can be used to configure the virtual PS2 (the emulated machine). self), and at the time the "PS2 classics" emulator (ps2_lf) was developed this config can be loaded from an external file This "game config" data seems to work in the same way for all the PS2 emulator types but can be located in different places, some are hardcoded inside the emulators itself (inside the. The concept of "game patches" is not technically correct because some of the commands does patching functions but others does other things (not patching), and other commands works as switches or sets a value that are enviromental settings for the emulator (not for the game) but because are applyed "by game" should be considered enviromental settings for that specific game, so for simplification purposes you can think in all this data as "game configs" Some of the PS2 emulator types (such ps2_lf, lf) are able to load config commands that are applyed "by game ID". I've never messed with these before, from the second link I see the following though: Game CONFIG
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |