Talk:Emulation: Difference between revisions
m (→Wiki main page templates restructuring: Cummulating configs in "talk" pages or in generic "emulation" pages is condemned to overflow at some point. We need specific pages dedicated to the configs) |
|||
Line 6: | Line 6: | ||
==Wiki main page templates restructuring== | ==Wiki main page templates restructuring== | ||
I think we need a new template on main page for the game compatibility lists, right now are inside a "revere engineering" category and thats not right. Additionally we have the page OFW2CFW game compatibility list that doesnt fits in any other category... so in few words we need a '''<nowiki>{{Games}}</nowiki>''' template for the main page with his own category... or something like that (any idea is welcome)--[[User:Sandungas|Sandungas]] ([[User talk:Sandungas|talk]]) 13:58, 7 October 2017 (UTC) | I think we need a new template on main page for the game compatibility lists, right now are inside a "revere engineering" category and thats not right. Additionally we have the page OFW2CFW game compatibility list that doesnt fits in any other category... so in few words we need a '''<nowiki>{{Games}}</nowiki>''' template for the main page with his own category... or something like that (any idea is welcome)--[[User:Sandungas|Sandungas]] ([[User talk:Sandungas|talk]]) 13:58, 7 October 2017 (UTC)<br> | ||
I been doing some preparations for an important change related with the game configs, the problem is we have been publishing the configs in general pages (like "PS2 Emulation"), or in talk pages (like in PS4 wiki), and even inside the compatibility lists (like the ones inside "PSP Emulator Compatibility List"), and all that has been bad practises, also the long lists with configs increases the page sizes a lot, the best solution i see is to create new pages dedicated to the configs, the first experiment has been made with the PSP configs, see [https://www.psdevwiki.com/ps3/index.php?title=PSP_Configs&diff=61654&oldid=61653 this snapshot] (it have 65 configs and a page size of 15.000 characters), i prepared 2 templates <nowiki>{{boxcode}} and {{boxcodelite}}</nowiki> for them, as an initial design imo is fine, the configs are well organized and there is lot of room to add descriptions at left about what the config does, it also allows to display examples with the dissassembled code, etc... but there is a huge problem... in long term (and specially in the pages dedicated to the PS2 configs) is going to be needed to add hundreds of configs... is needed to keep an eye at the total page sizes later, but by now we can use the 250.000 characters of the "PS2 classic emulator compatibility list" as a reference of how much we can increase them in size, i dont know whats the limit but lets say 400.000 or 500.000 probably are not going to make wiki to explode... anyway... another problem derivated from this huge amount of configs displayed in the same page is the TOC (at top of the page) is going to become excesivelly annoying... and the only solution to that is to use the magic word <nowiki>__NOTOC__</nowiki>... yeah... pretty much like what the compatibility list does where we need to navigate the page with the <nowiki>{{jumptoletter}}</nowiki> template... so im thinking in using an style a bit similar than the compatibility pages using the <nowiki>{{jumptoletter}}</nowiki>... but this presents a new problem we cant "jump" in between different sections of the page for "official" or "custom" configs... so... the best solution (that also is very preventive because allows to add more conffigs) is to split them in specific pages... a page for "PSP Official Configs" and other for "PSP Custom Configs" (and the PS2 pages for configs will follow the same rule... not sure yet what to do with the net/gx/soft versions of the officials though)--[[User:Sandungas|Sandungas]] ([[User talk:Sandungas|talk]]) 05:27, 1 September 2021 (UTC) | |||
{{Navbox | {{Navbox |
Revision as of 06:27, 1 September 2021
Discussion, ideas, brainstormings goes here
No hurry this rebuilding take days, weeks or more in the way i see, at this day (october 7 2017) the emulation frontpage and talk pages has been splitted and cleaned up completly, the reason for this carnage is because i think is better to start from scratch without any restriction in how are going to look and his purposes, there are a lot fo details needed to be mentioned but this is just an introductory explain of the discussion that goes under this line, feel free to join the party by giving your ideas and oppinions and help to solve the problems
Bringing back some moved texts
Probably there are lot of small sentences or sections that has been moved to the other pages... but could fit well here because are general concepts or could work as an introduction... the rule of gold now is this page is "noob oriented" and the others are "technically oriented", im not experienced in emulators so much to make this changes rewriting and moving texts back and forth and i fear to "break" something though--Sandungas (talk) 13:58, 7 October 2017 (UTC)
Wiki main page templates restructuring
I think we need a new template on main page for the game compatibility lists, right now are inside a "revere engineering" category and thats not right. Additionally we have the page OFW2CFW game compatibility list that doesnt fits in any other category... so in few words we need a {{Games}} template for the main page with his own category... or something like that (any idea is welcome)--Sandungas (talk) 13:58, 7 October 2017 (UTC)
I been doing some preparations for an important change related with the game configs, the problem is we have been publishing the configs in general pages (like "PS2 Emulation"), or in talk pages (like in PS4 wiki), and even inside the compatibility lists (like the ones inside "PSP Emulator Compatibility List"), and all that has been bad practises, also the long lists with configs increases the page sizes a lot, the best solution i see is to create new pages dedicated to the configs, the first experiment has been made with the PSP configs, see this snapshot (it have 65 configs and a page size of 15.000 characters), i prepared 2 templates {{boxcode}} and {{boxcodelite}} for them, as an initial design imo is fine, the configs are well organized and there is lot of room to add descriptions at left about what the config does, it also allows to display examples with the dissassembled code, etc... but there is a huge problem... in long term (and specially in the pages dedicated to the PS2 configs) is going to be needed to add hundreds of configs... is needed to keep an eye at the total page sizes later, but by now we can use the 250.000 characters of the "PS2 classic emulator compatibility list" as a reference of how much we can increase them in size, i dont know whats the limit but lets say 400.000 or 500.000 probably are not going to make wiki to explode... anyway... another problem derivated from this huge amount of configs displayed in the same page is the TOC (at top of the page) is going to become excesivelly annoying... and the only solution to that is to use the magic word __NOTOC__... yeah... pretty much like what the compatibility list does where we need to navigate the page with the {{jumptoletter}} template... so im thinking in using an style a bit similar than the compatibility pages using the {{jumptoletter}}... but this presents a new problem we cant "jump" in between different sections of the page for "official" or "custom" configs... so... the best solution (that also is very preventive because allows to add more conffigs) is to split them in specific pages... a page for "PSP Official Configs" and other for "PSP Custom Configs" (and the PS2 pages for configs will follow the same rule... not sure yet what to do with the net/gx/soft versions of the officials though)--Sandungas (talk) 05:27, 1 September 2021 (UTC)
|
- ps1_emu.self
- available for PS3 models - all
- available in firmwares - since 1.02
- game format - original CD inserted in the drive
- savedata format (hdd) - dev_hdd0/savedata/vmc/<virtual_memcard>.VM1
- savedata format (usb) - dev_usb0/PS3/EXPORT/PSV/<Save_ID>.PSV
- savedata format (mc) - mc_root/ (by using a memory card adapter)
- technical page - PS1 Emulation
- game compatibility list - NEEDED
- ps1_netemu.self
- available for PS3 models - all (PS1 classics)
- available in firmwares - since 1.70
- game format - ISO.BIN.EDAT (officially), BIN/CUE (unofficially)
- savedata format (hdd) - ?
- savedata format (usb) - dev_usb0/PSP/SAVEDATA/<SAVEDATA_DIRECTORY>/SCEVMC0.VMP
- savedata format (mc) - allowed ?
- technical page - PS1 Emulation
- game compatibility list - PS1 Classics Emulator Compatibility List
- ps1_newemu.self
- available for PS3 models - ?
- available in firmwares - since 2.10
- game format - ?
- savedata format/path - ?
- technical page - PS1 Emulation
- game compatibility list - needed ?
- ps2_emu.self
- available for PS3 models - CECHA and CECHB (COK-001)
- available in firmwares - since 1.02
- game format - original CD/DVD inserted in the drive
- savedata format (hdd) - dev_hdd0/savedata/vmc/<virtual_memcard>.VM2
- savedata format (usb) - dev_usb0/PS3/EXPORT/PSV/<Save_ID>.PSV
- savedata format (mc) - mc_root/ (by using a memory card adapter)
- game install - yes (only few games, by using a PS2 virtual hdd IMAGE.DAT)
- savedata format/path - ?
- technical page - PS2 Emulation
- game compatibility list - NEEDED
- ps2_gxemu.self
- available for PS3 models - CECHC (COK-002)
- available in firmwares - since 1.50
- game format - original CD/DVD inserted in the drive
- game install - yes (only few games, by using a PS2 virtual hdd IMAGE.DAT)
- savedata format/path - ?
- technical page - PS2 Emulation
- game compatibility list - NEEDED
- ps2_softemu.self
- available for PS3 models - fats/slim newer than CECHC
- available in firmwares - since 1.90 then blocked in 3.50 and removed in 4.21 ?
- game format - original CD/DVD inserted in the drive
- savedata format/path - ?
- technical page - PS2 Emulation
- game compatibility list - not needed (abandoned officially and superseded by netemu)
- ps2_netemu.self
- available for PS3 models - all (PS2 classics)
- available in firmwares - since 3.70
- game format - ISO.BIN.EDAT ISO.BIN.ENC (officially), BIN CUE (unofficially)
- savedata format/path - APPDIR/USRDIR/SAVEDATA/SCEVMC0.VME and SCEVMC1.VME
- settings - by using CONFIG files
- technical page - PS2 Emulation
- game compatibility list - PS2 Classics Emulator Compatibility List
- psp_emulator.elf
- available for PS3 models - all but CECHB ? (PSP Remasters ?)
- available in firmwares - since 3.15
- game format - ISO.BIN.EDAT and APPDIR/USRDIR/CONTENT/EBOOT.PBP/DATA.PSAR ? (PSP minis)
- savedata format (hdd) - dev_hdd0/home/<userid>/minis_savedata/<SAVEDATA_DIRECTORY>/Files
- savedata format (usb) - dev_usb0/PSP/SAVEDATA/<SAVEDATA_DIRECTORY>/Files
- savedata format/path - ?
- technical page - PSP Emulation
- game compatibility list - PSP Emulator Compatibility List
- psp_translator.elf
- available for PS3 models - all but CECHB ? (PSP Minis ?)
- available in firmwares - since 3.15
- game format - ?
- savedata format/path - ?
- technical page - PSP Emulation
- game compatibility list - Needed ? (for minis ?)