Talk:Getting involved

VE extension

Why EMUGEN wiki doesn't add Visual Editor extension ? That way it would be easy to add edit and expand articles. Chipsum _(✉️)

TAS features section

Don't see a better place to put this, nor do I have the desire to update every article, but I want to note this. The "TAS features" section of many articles (e.g. Nintendo Entertainment System emulators#Enhancements) lists useful features. But it misses one crucial thing: Re-recording. For example, Mesen has every feature listed in the table. But while recording a movie, you cannot make or load savestates; this makes it effectively useless for creating an optimised tool-assisted speedrun. 172.71.178.224 13:36, 28 May 2024 (UTC)

How long does it take to become autconfimred?

Help:Protection gives no hints as to how long it takes to become autoconfirmed. It links to wikipedia which is 10 edits and 4 days, but I have made more than 10 edits and have an account more than 4 days yet cannot edit PS4, which is autoconfirmed protected (see https://emulation.gametechwiki.com/index.php?title=PlayStation_4_emulators&oldid=28192). I would like to make some small changes there but I cannot. Any hint as to how to become autoconfirmed would be appreciated.

In order to become auto-confirmed on Emugen, you must have an account that is at least 2 weeks old and have made at least 20 edits to the wiki [source]. Hope this helps. --CruiserKitten673 (talk) 08:30, 24 September 2025 (UTC)

Comparison table v2

Following the completion of the task mentioned in this section -> Talk:Main Page#win9x.2C dos or other .22ancient.22 emulators, I think we should also consider updating the comparison tables.

Feel free to change the tables to your liking.

Option 1

Before making any changes, make sure to read Getting involved and Recommended pages first. See system requirements page for performance demand of the emulators.
For details on Sega Titan Video, Enhancements, and Hardware features and peripherals, see their respective tables.
Legend: 🟢🟩 Active · 🔴🟥 Inactive · 🟡 Unknown · 🏆 Gold rank · ⚪ Silver rank

Stats	Name	x86 platforms	ARM platforms	Consoles	FPGA	Frontend cores	Forks	Latest version	Compatibility	License
Multi-system emulators
🏆	Mednafen 🟢				✗	🟩	🟩 🟥	x86: 1.32.1 ARM: libretro core Consoles: libretro core	? JAP PAL USA	GPLv2 (Copyleft)
⚪	CDi_MiSTer 🟢	✗	✗	✗	MiSTer	✗	✗	dvc_rc0	?	?
System-specific emulators
⚪	Ymir 🟢			✗	✗	✗	✗	x86/ARM: 0.3.3 x86/ARM: latest nightly	90.95% 2162 out of 2377 reported titles	GPLv3 (Copyleft)

Option 2

Before making any changes, make sure to read Getting involved and Recommended pages first. See system requirements page for performance demand of the emulators.
For details on Sega Titan Video, Enhancements, and Hardware features and peripherals, see their respective tables.

Rec	Active	Name	x86 platforms	ARM platforms	Consoles	FPGA	Frontend cores	Multi-system emulator ports	Forks	Latest version	Compatibility	License
✓	✓			✗	✗	✗			example	x86: 1.32.1	? JAP PAL USA	GPLv2 (Copyleft)
~	✓			✗	✗	✗		✗	✗	x86: 2.11.1 x86: Dev Builds	?	MIT GPL
~	✓					✗	‡	✗	✗	x86: [https://www.yabasanshiro.com/download This page is a candidate for deletion. The reason is: "typo in title" If you disagree with the candidate, explain why at the talk page or improve the page and remove the {{delete}} tag. Remember to check for any active links to the page and its history before deleting. (Windows)] x86: 2.12.0 (Linux) ARM: 1.20.5 (Android) ARM: 1.18.15 (iOS) Consoles: 2.2.0	?	GPLv2 (Copyleft)
~	✓	CDi_MiSTer (example)	✗	✗	✗	MiSTer	✗	✗	✗	dvc_rc0	?	?

Option 3

Before editing, review Getting involved and Recommended pages. See system requirements page for performance demand of the emulators.
See tables for arcade hardware variants, PSX DVR, enhancements, hardware features and peripherals.
For details on Licensing, programming language, emulation method, development status, or latest versions visit each emulator’s dedicated page via its name link.

System specific	Architecture → Platform(s)	Compatibility
✅ PCSX2	💻 —	99.14% 2667 out of 2690 reported titles
⚠️ Play!	💻 — 📱 —	47.44% 1253 out of 2641 reported titles
✅ NetherSX2	📱 —	74.06% 451 out of 609 reported titles
✅ XBSX2	🎮 —	99.14% 2667 out of 2690 reported titles
Multi-system
❌ e	💻 —	e
Frontend cores
⚠️ LRPS2	💻📱🎮 —	97.39% 2572 out of 2641 reported titles
FPGA
❌ corename	icon MiSTer	e

Option 3a

Before editing, review Getting involved and Recommended pages. See system requirements page for performance demand of the emulators.
See tables for arcade hardware variants, PSX DVR, enhancements, hardware features and peripherals.
For details on Licensing, programming language, emulation method, development status, or latest versions visit each emulator’s dedicated page via its name link.

System specific	Architecture → Platform(s)	Compatibility
✅ PCSX2	💻 —	99.14% 2667 out of 2690 reported titles
⚠️ Play!	💻 — 📱 —	47.44% 1253 out of 2641 reported titles
✅ NetherSX2	📱 —	74.06% 451 out of 609 reported titles
✅ XBSX2	🎮 —	99.14% 2667 out of 2690 reported titles
Multi-system
❌ e	💻 —	e
Frontend cores
⚠️ LRPS2	💻📱🎮 —	97.39% 2572 out of 2641 reported titles
FPGA
❌ corename	icon MiSTer	e

Option 3b

The hardware features and enhancement tables require wiki syntax formatting, though this may reduce some visual elements.

PlayStation 2 Emulators — Compatibility Overview

Before editing, review the Getting involved and Recommended pages.
See system requirements page for performance demand of the emulators.
See tables for arcade hardware variants, PSX DVR, enhancements, hardware features and peripherals.
For details on latest versions, licensing, programming language, emulation method, visit each emulator’s dedicated page.

System specific	Architecture → Platform(s)	Compatibility
✅ PCSX2	💻 —	99.14% 2667 out of 2690 reported titles
⚠️ Play!	💻 — 📱 —	47.44% 1253 out of 2641 reported titles
✅ NetherSX2	📱 —	74.06% 451 out of 609 reported titles
✅ XBSX2	🎮 —	99.14% 2667 out of 2690 reported titles
Multi-system
❌ e	💻 —	e
Frontend cores
⚠️ LRPS2	💻 📱 🎮 —	97.39% 2572 out of 2641 reported titles
FPGA
❌ corename	icon MiSTer	e

🎮 Hardware features and peripherals

Comprehensive list of PS2 features and their support across recommended emulators.

Category	Feature	PCSX2	LRPS2	Play!
DualShock 2	Pressure-sensitive inputs	✅*	❌	❌
	Vibration	✅	❓	✅
Hardware	Alternative display modes	✅	❓	❓
	System BIOS	✅	✅	❌
	PS1 Backwards Compatibility	~	❓	❌
	DTS/Dolby Digital Audio	~	❓	❓
Controller Port	Multitap	✅	✅	❌
	Jogcon / NeGcon / Pop'n Music	✅*	❌	❌
	Namco GunCon / Konami Justifier	❌*	❌	❌
Storage/Networking	Ethernet / LAN tunneling	✅	❓	❓
	Hard Disk Drive (HDD)	❌*	❓	❌
	Memory card	~	❓	❓
	Modem / PocketStation / PSP Link	❌	❌	❌
USB Controllers	Buzz! / GunCon 2 / Racing Wheel	✅	❌	❌/✅/❌
	Densha de Go! Controller	~	❌	❌
	DJ Hero Turntable / Drum Kit	~	❌	❌
	KeyboardMania / Gametrak	✅	❌	❌
USB Misc.	Microphone (Logitech/SingStar)	✅	❌	❌/❓
	EyeToy / Konami Capture Eye	✅	❌	❌
	USB Mass Storage / PictureParadise	✅	❌	❌
	USB Printers (Epson/GamePrint)	❌*	❌	❌
Miscellaneous	Linux for PS2	❌	❌	❌
	DVD Remote Control	❌*	❌	❌
	Development Kits	~	❌	❌

🛠️ Enhancements

Comprehensive list of enhancements features and their support across recommended emulators.

Category	Feature	PCSX2	LRPS2	Play!
Controls	Disguise peripheral support through passthrough ⓘ	❓	❓	❓
	Input lag-mitigating technique ⓘ	🚫	❓	🚫
	Mouse injector compatible ⓘ	✅ *	❓	🚫
	Real peripheral support (passthrough) ⓘ	❓	❓	❓
	Turbo button ⓘ	✅ [1]	❓	❓
Graphics	Better texture filtering ⓘ	✅	❓	❓
	Force LOD / enhanced mipmap modes ⓘ	✅/❓
	Pre-rendering anti-aliasing (MSAA, SSAA) ⓘ	~	❓	🚫
	Ray tracing ⓘ	🚫
	Resizable internal resolution ⓘ	✅	❓	✅
	RTX Remix ⓘ	🚫
	Texture replacement ⓘ	✅	❓	🚫
	Widescreen hack ⓘ	✅	❓	🚫

Notes:

1. SSAA is possible with paraLLEl-GS builds. Also see PCSX2 Forum Thread: "Future anti-aliasing implementations?" (forum link).
2. Evidence and discussion: RTX HDR compatibility demonstration (YouTube video ID WG8YHh4BT88), plus PCSX2 feature request and pull request for direct HDR output support similar to Dolphin and RetroArch implementations.
3. Exclusive / special note: Variable refresh rate compatibility noted in libretro core; see issue comment: https://github.com/PCSX2/pcsx2/issues/312#issuecomment-1264483185.
4. Pull requests and issues related to PCSX2 debug features — see PCSX2 repository issues/PR list for details.

Emulation Issues

EE timing, VU parallelism, and FPU accuracy make CPU-intensive emulation necessary. GS hardware rendering differs from modern GPUs; software rendering is often required. Peripheral chips (IOP, DEV9C, MechaCon) require careful emulation or keys. CRT-specific visual tricks necessitate post-processing enhancements for modern displays.

Option 4

PlayStation 2 emulators — Windows 98 Edition

_ ▢ X

Before editing, review Getting involved and Recommended pages. See system requirements page for performance demand of the emulators.
See tables for arcade hardware variants, PSX DVR, enhancements, hardware features and peripherals.
For details on Licensing, programming language, emulation method, development status, or latest versions visit each emulator’s dedicated page via its name link.

System specific	Architecture → Platform(s)	Compatibility
✅ PCSX2	💻 —	99.14% 2667 out of 2690 reported titles
⚠️ Play!	💻 — 📱 —	47.44% 1253 out of 2641 reported titles
✅ NetherSX2	📱 —	74.06% 451 out of 609 reported titles
✅ XBSX2	🎮 —	99.14% 2667 out of 2690 reported titles
Multi-system
❌ e	💻 —	e
Frontend cores
⚠️ LRPS2	💻📱🎮 —	97.39% 2572 out of 2641 reported titles
FPGA
❌ corename	icon MiSTer	e

Option 5

Before making any changes, make sure to read Getting involved and Recommended pages first. See system requirements page for performance demand of the emulators.
For details on Sega Titan Video, Enhancements, and Hardware features and peripherals, see their respective tables.
Legend: 🟢🟩 Active · 🔴🟥 Inactive · 🟡 Unknown · 🏆 Rank Gold · ⚪ Rank Silver · 🔶 Rank Bronze
🔍 Accuracy-focused · 🚀 Performance-focused · 🥇 Accuracy Gold · 🥈 Accuracy Silver · 🥉 Accuracy Bronze ⬆️ High-level approach · ⬇️ Low-level approach · 🔄 Hybrid approach
🅰️ Assembly · 🅻 Low-level language · 🅼 Mid-level language · 🅷 High-level language · ⚡ Performance Gold · 🔌 Performance Silver · 🔋 Performance Bronze · 🕹️ Input Delay Good · ⏳ Input Delay Bad

Name	x86 platforms	ARM platforms	Consoles	FPGA	Frontend cores	Multi-system emulator ports	Forks	Latest version	Compatibility	Accuracy	Perf	License
🏆🟢				❌	🏆🟩	🏆🟩 ⚪🟩	🏆🟩 ⚪🟥	x86: 1.32.1 ARM: libretro core Consoles: libretro core	? JAP PAL USA	🥇🔍⬇️	🔋🅼⏳	GPLv2 (Copyleft)
⚪🟢				❌	⚪🟩	❌	❌	x86: 2.11.1 x86: Dev Builds ARM: libretro core Consoles: libretro core	?	🥈🚀🔄	🔌🅷🕹️	MIT GPL
🔶🟢				❌	🟥	❌	❌	x86: [https://www.yabasanshiro.com/download This page is a candidate for deletion. The reason is: "typo in title" If you disagree with the candidate, explain why at the talk page or improve the page and remove the {{delete}} tag. Remember to check for any active links to the page and its history before deleting. (Windows)] x86: 2.12.0 (Linux) ARM: 1.20.5 (Android) ARM: 1.18.15 (iOS) Consoles: 2.2.0	?	🥉🚀⬆️	⚡🅷🕹️	GPLv2 (Copyleft)

Option 5b

Before making any changes, make sure to read Getting involved and Recommended pages first. See system requirements page for performance demand of the emulators.
For details on Sega Titan Video, Enhancements, and Hardware features and peripherals, see their respective tables.
Legend: 🟢🟩 Active · 🔴🟥 Inactive · 🟡 Unknown · 🏆 Rank Gold · ⚪ Rank Silver · 🔶 Rank Bronze · 🖥️ Good with LCD · 📺 Good with CRT · 🎮 XInput supported · ⌨️ SDL supported ·
🔍 Accuracy-focused · 🚀 Performance-focused · 🥇 Accuracy Gold · 🥈 Accuracy Silver · 🥉 Accuracy Bronze ⬆️ High-level approach · ⬇️ Low-level approach · 🔄 Hybrid approach
🅰️ Assembly · 🅻 Low-level language · 🅼 Mid-level language · 🅷 High-level language · ⚡ Performance Gold · 🔌 Performance Silver · 🔋 Performance Bronze · 🕹️ Input Delay Good · ⏳ Input Delay Bad

Name	x86 platforms	ARM platforms	Consoles	FPGA	Frontend cores	Multi-system emulator ports	Forks	Latest version	Compatibility	Traits	License
🏆🟢				❌	🏆🟩	🏆🟩 ⚪🟩	🏆🟩 ⚪🟥	x86: 1.32.1 ARM: libretro core Consoles: libretro core	? JAP PAL USA	🥇🔍⬇️ 🔋🅼⏳📺🎮⌨️	GPLv2 (Copyleft)
⚪🟢				❌	⚪🟩	❌	❌	x86: 2.11.1 x86: Dev Builds ARM: libretro core Consoles: libretro core	?	🥈🚀🔄 🔌🅷🕹️🖥️🎮⌨️	MIT GPL
🔶🟢				❌	🟥	❌	❌	x86: [https://www.yabasanshiro.com/download This page is a candidate for deletion. The reason is: "typo in title" If you disagree with the candidate, explain why at the talk page or improve the page and remove the {{delete}} tag. Remember to check for any active links to the page and its history before deleting. (Windows)] x86: 2.12.0 (Linux) ARM: 1.20.5 (Android) ARM: 1.18.15 (iOS) Consoles: 2.2.0	?	🥉🚀⬆️ ⚡🅷🕹️🖥️🎮⌨️	GPLv2 (Copyleft)

or we can use these smaller versions;
■ ●
■ ●
■ ●

If one of the table in option 5 is selected a special guide section will be added to the Getting involved page to address performance and accuracy categorizing situtation; I think using the icons such as 🔍 · 🚀 · ⬆️ · ⬇️ · 🔄 · 🅰️ · 🅻 alongside the accuracy medals and transparency percentages, as shown, makes sense. However, I’m unsure how the style commands (e.g., background gradients) should be applied to or influenced by the those icons. Could other wiki users suggest how this should be handled? We probably need to use templates for all of those unicode icons. Ahayri (talk) 11:41, 20 September 2025 (UTC)

---

Any of these options will be better than the old incosistent mess (f*ck the old tables, incosistent column order, sometimes keeping ARM/x64/consoles as 3 separate tables, sometimes putting everything together into 1 table). Just a few notes:

• 1) Not all emulators have an official logo icon
• 2) Also some emulators will have outdated versions (e.g. Ymir has Windows UDP port for Xbox One/Series by the author himself, no brainer it has different compatibility no one tested)
• 3) Also sometimes a core in multiemu based on who knows which fork exactly. I don't know, for one, which option Manic will add as DOSBox core: Pure? X? Staging? I only know the DOSBox is in the works. Sometimes unless one checks multi-emu cores by himself, he won't know
• 4) Some forks may have their own separate articles and some will not. How handle this?
• 5) Some forks significantly outgrew their original scope (look at Folium's supported platforms besides 3DS)
• 6) Speaking of FPGA since you made it into a separate column, look at the icon/icon2 template. This raspberry image is fetched by simply using LinuxARM argument. And by argument rpi. See the confusion? There should be a differentiation between emulators with generic Linux ARM builds and builds compiled specifically for FPGA like Raspberry Pi, you'll also have to take care of it with the icon/icon2 template. Same for MacOS: shouldn't older MacOS on x86-64 and newer on Apple Silicon be differentiated? Older Windows?
• 7) I see no Titan Video mentioned in the separate column. If you decide to exclude a dedicated mention of arcades and other hardware variants (e.g. Adam for Coleco, Game Gear for SMS, TeraDrive PC/32x/Mega/Mega 32x for MD, SuperGrafx for TurboGrafx-16 and so on), it might be very dangerous. If anything, they should be differentiated whenever possible, I think. I recall seing GB emulators which don't emulate GBC, only the original monochrome console, a rarity but things do happen, and even some old inactive GG emulator which didn't emulate SMS. Ilyagredasov (talk) 09:51, 2 October 2025 (UTC)

---

I agree with your suggestion and I prefer option 2. I have some suggestions. Replace "x86 platforms" with "Intel (x86-64) platforms, because some emulators are 64-bit, and add in an "other platforms" column because what if the emulator can run on AmigaOS or PowerPC Mac OS X? Also, display the platforms for the forks. Gorilli09 (talk) 17:45, 8 October 2025 (UTC)

---

I replaced Option 3 with a more minimalistic table (style-wise, that linear-gradient transparency and italic font hit like Im launching an old EA Sports game, with EA Sans Bold Italic and some Y2K aesthetics), since there hasn’t been much interest in the previous version. Click here if you want to see the older one.

       "what if an emulator also runs on something like AmigaOS or PowerPC Mac OS X)?"

As I mentioned earlier, older or long-inactive emulators (those not updated for years) should be listed on the Older Emulators pages that we already have. Dedicated system pages should focus only on active and widely used emulators. That’s just my take, at least. Ahayri (talk) 16:18, 19 October 2025 (UTC)

---

I personally already like the general look of tables on the most used pages, in my opinion it would be best to remove the two columns for hardware features/peripherals and enhancements since it's detailed below anyways, give the compatibility a background as well based on percentage (for example 0-25% red, 25-50% yellow and 50-100 green, whatever numbers make sense) and most importantly have a set order for the columns. The switch page probably has it done well, with general information (name, platforms, version) first, compatibility, then the "status" of the project with license and if it's active and whether it's recommended last. For things like the New 3DS, DSi or Arcade versions I believe the column should be to the left of compatibility. Lastly, I don't like the row sectioning in x86, Arm and sometimes console, since it might cause confusion on what systems are supported for some people, it would be best to put all the supported systems together, and in case there are too many, perhaps it could only show Win, Linux, Mac, iOS and Android and add a link to the page for the emulator where all systems are listed.

I edited (and mostly shortened) the 3DS table below as an example. I believe this shows all general information in an easily digestable form with the exception of whether Mac support is Arm, Intel or PowerPC, but that should probably be handled using seperate icons like Win/Linux on Arm or it could use the same icon but have a different text on hover (for example using icon MacArm shows the same icon as MacIntel but has the hover text "MacOS on Apple Silicon" instead of "MacOS on Intel x86".

- 40608

Name	Platform(s)	Latest version	New 3DS	Compatibility	License	Active	Recommended
Citra and forks		Citra forks (recommended) libretro core	✓	63.01% 327 out of 519 reported titles	GPLv2 (Copyleft)	~	✓
Panda3DS		nightly [2] libretro core	✓	40.29% 56 out of 139 reported titles (Most might need retesting/remarking)	GPLv3 (Copyleft)	✓	~
Tanuki3DS		[3]	?	?	GPLv3	✓	~

---

A question

Where did the patriotic man go? - Tukutu (talk) 16:05, 29 January 2026 (UTC)

Dont know if place to say 2026-03-28

A system not on the wiki is the Benesse Pocket Challenge W.

Only emulator i know for it is: https://www.crazysmart.net.au/kindred/

Also would it be a good idea to add an untested section into the compatability boxes on console pages?

I agree that the system should be added. For the untested section, we already use the tilde (~) and (TBD) or even the question mark (?) in the Recommended column, to indicate unknown or unverified status, so adding another category might be redundant. - - R-K (talk) 22:28, 27 March 2026 (UTC)

Sorry what i meant was should we have something like "78.39% -- 2753 out of 3512 reported titles. -- 110 untested" in the compatibility box in tables with the "110 tested" part being the new addition?

Compatibility	63.01% 327 out of 519 reported titles 110 untested out of 432320

I see what you mean now. This could actually be a good idea to clarify how complete the compatibility data is. As long as it stays readable and not too cluttered, I think it could work. I Wonder what others think about it. - - R-K (talk) 15:31, 1 April 2026 (UTC)

Please no. The less shit user has to manually type himself, the better. Think of usability (some of us peasants contribute to the Wiki via tablets or mobile phones with touchscreen). I don't propose anything particular, but just for the sake of example I've created one: Template:Emulator compatibility/Sandbox. You enter 3 values: playable titles (perfect + imperfect but finishable) + tested titles + total titles (including untested games/apps/homebrew). I used PPSSPP as an example. Everything else is auto-calculated by the sandboxed template from these 3 user-entered values. Once again: it's not a particular pattern I propose (some values may be excessive and may be removed to make a rendered template take less space in a table, some maybe implemented differently, e.g. we can calculate total number of titles by adding tested + untested together instead of calculating untested by substracting tested from total, background color may be calculated from percentage of either tested or total titles with tone gradations, i.e. the better compatibility is, the greener, the worse, the redder; you can think of tons of ideas if you want). Just an example of what may be. But it should be convenient in terms of usability. Manually typing "</small><br>" every time on every single entry on every single emulator table isn't convenient, that's for sure. Ilyagredasov (talk) 16:27, 1 April 2026 (UTC)

Update News Aggregators

We have a number of news aggregators listed, some key ones missing, and some with inaccurate descriptions.

For example: Mr. Sujano is a youtuber who puts out emulation news every single day. Often times, other news sites - including reddit Emulation - utilize his videos to source their news. There are emulator developers that message Sujano with updates, and he even has a section of his discord for it. (https://www.youtube.com/mrsujano)

Another example: "r/emulation (Reddit) – the primary source for breaking news, often reporting major releases, GitHub commits, and key compatibility breakthroughs first." - this is factually incorrect. Reddit emulation gets updated every few days and often lags behind other sources. Today is April 30, and the last time it was updated was April 27.

Another example: "r/emulationonandroid" is not even listed and has a lot of new and up to date information that is often cross-posted to reddit emulation (that shows up days later after admin approval). (https://www.reddit.com/r/EmulationOnAndroid/?f=flair_name:%22News/Release%22)

Another example: There are discord groups dedicated to emulation news, and not one is listed - even reddit Emulation has one that is very active and more active than their actual reddit page. We don't have a singly discord group listed. The only drawback is that discord requires a login/account. I think we should entertain listing discord groups as it's similar to a forum, especially since there are specific "announcement" pages within discord groups that are not live chats. Thoughts?

My ideas

New emulator table

The current emulator table is a mess. I created a new emulator table. It is sortable and more organized.

Before editing, review the getting involved and recommended pages. See system requirements page for performance demand of the emulators.
See tables for enhancements, hardware features & peripherals, and hardware variants.
For more details such as licensing, programming language, emulation method, visit each emulator’s dedicated page.

Software							Emulation		Recommended? (overall)
Name	Platform(s)			Active?	Latest version	License	Compatibility	Has libretro core
	PC	Mobile	Other
(emulator name)

Remove unnecessary rows that have unsupported features in all columns

The rows of unsupported features in every column need to be removed, because it feels like spam.

Example

Before

Name	emulator 1	emulator 2	emulator 3	emulator 4
supported feature	✓	?	?	?
unsupported feature	✗	✗	✗	✗

After

Name	emulator 1	emulator 2	emulator 3	emulator 4
supported feature	✓	?	?	?

Create a bot

This wiki needs a bot. Me doing all of the minor corrections can be a hassle.

Gorilli09 (talk) 16:25, 24 June 2026 (UTC)

If you really want to remove them, these features/peripherals still should be mentioned elsewhere as a reference point (in order not to lost track of them) in order to be easily back-movable later to the table whenever a supporting emulator appears, and users should know which functionality is lacking anyway.

Just for example, a simplified mini-table under the main table, like this:

Peripherals/features at least partially supported by at least a single emulator

Name		BigPEmu	BizHawk
Jaguar CD		✓	~
Controller	Driving controller	✓	✗

Completely unsupported peripherals/features

Name
Ultra Vortek Voice Modem
Controller	Light gun

Or maybe even a simple text list:

• Ultra Vortek Voice Modem
• Controllers:
  • Light gun

Or:

1. Ultra Vortek Voice Modem
2. Controllers:
   1. Light gun

I've spent some time digging out stuff for GB(C), GBA, NDS, Jaguar, Genesis/Mega Drive, NES, SNES and other hardware tables and don't want the effort to go waste (and I still sometimes find new stuff from time to time, like Virtual i-glasses for Amiga PCs. I found out that there're 2 Amiga games with support their head-tracking feature by pure luck. It was mentioned on a 3DO-dedicated "3do.world" wiki as I was browsing it. I wasn't even looking for Amiga peripherals, I was looking for 3DO peripherals specifically, but luckily in the article dedicated to these glasses, its text mentioned Amiga compatibility for 2 games as a side note. I aslo didn't know about the existence of Tutorvision until read about it on AtariAge. Once again, I found out about this prototyped education console by accident, wasn't looking for it specifically, just wanted to know users' experiences with Intellivision as I was considering to purchase a second-hand one with some games). As you see, unless you REALLY know what you're looking for, know where to find it, then it's extremely easy to miss some obscure peripherals and hardware quirks because info is really scarce and/or very hard to find by pure chance. So a mention is still a must even if omitted from the main table. Info must always be readily available at hand for convenience. And if something new no emulator supports is found again, it can be easily added to the second table/text list. Ilyagredasov (talk) 23:43, 24 June 2026 (UTC)

Yeah, I disagree with adding a "Has libretro core" column to the main table, as well as removing unsupported features. Instead, I believe that separating frontend cores, standalone emulators, multi-system emulators and emulators on other hardware (Nintendo Entertainment System emulators#Comparisons page) is the best option. Ahayri (talk) 11:28, 25 June 2026 (UTC)

Japanese word processor emulators

Seems like some old Japanese word processors used to have game software. I haven't found anything else after some googling except this pic of Tetris for different systems, this article on Toshiba J-3100 with incomplete list of some games and this mention of a Bomberman release for Toshiba Rupo and a a single gameplay video of Arabian Kid on Panasonic Slala. It certainly fits the scope of the Wiki (we even have articles about microcalculators) as the devices are potentially emulatable (though seems like the only emulated one in practice is Toshiba J-3100 emulated by DOSBox-X), but I have no idea how to even approach the topic, I don't know Japanese, the available information looks extremely scarce , there're no even game library lists (let alone game dumps themselves, lost forever). Any ideas? Or it's not even worth trying. Ilyagredasov (talk) 22:12, 26 June 2026 (UTC)