https://emulation.gametechwiki.com/api.php?action=feedcontributions&user=87.123.201.116&feedformat=atomEmulation General Wiki - User contributions [en]2024-03-28T11:45:39ZUser contributionsMediaWiki 1.32.0https://emulation.gametechwiki.com/index.php?title=Support_emulation_projects&diff=25068Support emulation projects2019-01-10T01:40:42Z<p>87.123.201.116: /* Help with technical documentation */</p>
<hr />
<div>'''''WIP page, help wanted.'''''<br />
<br />
There are several ways to support or contribute to an emulation project (or similar projects such as [[Compatibility layers]], [[Game engine recreations]] or simulators). Explained here are different ways you can get involved, even if you have low technical skill and no money.<br />
<br />
==Testing & bug reporting==<br />
''more text here...''<br />
<br />
=== Compatibility reporting ===<br />
<br />
A compatibility report communicates the emulation quality. It is aimed at other users.<br />
<br />
<!-- Sending users to GitHub is dangerous - you should only do it if the project has a simplified compatibility list which doesn't require technical understanding / writing; most projects actually uses wikis or custom tools / websites for compatibility reporting --><br />
<br />
Some emulators use GitHub for their compatibility list.<br />
Create a GitHub account, most projects have instructions on how bug reports should be written, make sure you search to see if the issues is already brought up by another user, in that case just add your observation to that report.<br />
<br />
''more text here...''<br />
<br />
<br />
=== Bug reporting ===<br />
<br />
A bug report is about one specific problem. It is aimed at emulator developers.<br />
<br />
Because bug reports are meant for developers, they are expected to be more technical than a compatibility report.<br />
Bug reports are typically expected to include details about specific situations when the problem arises, but also technical details as to why it happens.<br />
Developers also read compatibility reports and create respective bug reports themselves.<br />
<br />
''If you are not a software developer, you probably shouldn't do bug reports.''<br />
<br />
Generally you should chat to other developers / maintainers (via IRC or Discord) before creating a bug report.<br />
Often they are aware of issues and have grouped them under a technical term.<br />
<br />
''more text here...''<br />
<br />
=== Console verification ===<br />
<br />
Despite being aimed at developers, users should read / follow bug reports they care about.<br />
<br />
Many emulators not only need games tested in the emulator, but also on real hardware.<br />
Sometimes it looks like there's a bug in the emulator, but it might be a bug in the game, so it also happens on the console.<br />
So you can possibly prevent developers from wasting time on bugs which aren't really bugs in the emulator.<br />
Ideally, you have a capture card to record footage as proof.<br />
<br />
Also, during the research and documentation phase, some developers will write small programs to test hardware behaviour.<br />
In some cases the developers don't have access to the physical hardware or they need test results from many users.<br />
You can follow developer chat-rooms, so you can offer your help with running tests and collecting data from real hardware.<br />
<br />
==Provide support for end users==<br />
Discord, IRC, forums<br />
<br />
<br />
<br />
==Write & promotion==<br />
Write blog posts, promote news, provide information, make videos on YouTube, explain change logs, etc.<br />
<br />
== Archival and hardware donations ==<br />
<br />
Optical discs like CD or DVDs have a limited lifespan, they degrade over time and will eventually be unreadable.<br />
There is projects like [http://wiki.redump.org/index.php?title=Redump.org redump.org] which are focused on identifying all officially released discs.<br />
Each known disc is stored with information which makes it possible for users to verify the correctness of their disc.<br />
Contributing to these databases (by dumping your discs and contributing metadata) helps to build a full-set for testing emulators.<br />
It also encourages users to make legal backups of their discs before they break.<br />
<br />
Game databases like [https://www.mobygames.com/ MobyGames] can be used find additional information for each game. Launchers can use the uploaded descriptions and cover-artwork. You can contribute by scanning you game artwork, finding and adding game information (such as release dates).<br />
MobyGames also stores barcodes and serial numbers which can be used to find releases in redump.org.<br />
You can look at the existing cover artwork and extract such information.<br />
<br />
Alternatively, you can also donate games or hardware to developers or other volunteers who are accepting such donations.<br />
Donated games can then be analyzed by the recipient and their information can be added to databases such as those listed above.<br />
Emulator developers usually require a large number of consoles, games and peripherals (controllers, memory cards, ..), so donations are typically welcome.<br />
Depending on the project structure these will be forwarded to people who are in need of such hardware.<br />
Contact project maintainers to find out more.<br />
<br />
== Help with technical documentation ==<br />
<br />
Emulators depend on technical emulation about the systems they emulate.<br />
Typically, there are dedicated communities (often includes people from emulation, homebrew and piracy scene) for these research and documentation tasks.<br />
<br />
These research communities often uses Wikis which need to be maintained.<br />
Beginners can help by fixing typos or formatting. For some of these tasks, no coding skills are required.<br />
Advanced users and developers can contribute their own research, or participate in technical discussions.<br />
<br />
Many of these communities also maintain their own tools which can be helpful for ROM dumping or testing emulation.<br />
These tools are often written in beginner-friendl programming languages (such as C# or Python) and can be stepping-stone for moving towards actual emulator development.<br />
<br />
=== Communities ===<br />
<br />
* [https://github.com/xboxdev/xboxdev XboxDev] for original Xbox and SEGA Chihiro<br />
* [https://www.3dbrew.org/ 3DBrew] for 3DS<br />
<br />
== Learn how to code and help out ==<br />
WIP<br />
<br />
==Donate money==<br />
<br />
Emulation development is a time intensive task. It's only fair to reward the contributors.<br />
<br />
However, emulator development is often a group effort and there is no fair way to distribute money.<br />
Often developers of emulators can only do their work because research has been done by other people - unfortunately, that work often goes unrewarded.<br />
It's therefore important to understand who you donate to, and how that money will be shared or how it will be used.<br />
<br />
Especially for Open-Source projects, there can also be problems with only supporting the core developer group: it might actively discourage other contributors because of the unfair reward system ("Why should I work for free, but XYZ is getting paid on a monthly bases?").<br />
This can quickly lead to one "hero" developer - if they ever disappear the project is essentially dead because nobody else is familiar with the source-code.<br />
<br />
For some projects, there is also no practical use for money: money doesn't write code.<br />
There's also a lot of free services for Open-Source projects, so many projects don't have any expenses.<br />
<br />
<br />
=== Patreon ===<br />
Several emulators have a Patreon. [[Emulators on Patreon|Here is a list]]<br />
<br />
=== BountySource ===<br />
BountySource let's you directly donate money to certain features or improvements you wish for<br />
* [https://www.bountysource.com/teams/libretro Libretro]<br />
* [https://www.bountysource.com/teams/reicast Reicast]<br />
<br />
=== PayPal and other ways to donate ===<br />
Some emulators have PayPal addresses and such on their homepages.<br />
<br />
== Big projects ==<br />
<br />
<!-- This list is only intended for the four or five biggest projects in emulation/compability layers, and is intended as an example of ways to help out/getting involved --><br />
<br />
=== MAME ===<br />
It is not possible to donate directly to MAME, but several other projects that help MAME's development can be supported.<br />
<br />
* [http://www.mameworld.info/ubbthreads/showthreaded.php?Number=311481 The Dumping Union] - Accepts donations from PayPal.<br />
<br />
* [https://team-europe.blogspot.com/ Team Europe] - Accepts donations from PayPal. [https://www.reddit.com/r/emulation/comments/9txdsz/mame_team_europe_would_like_help_funding_some/ See info here on how to donate].<br />
<br />
* [https://caps0ff.blogspot.com/ CAPS0ff] - [https://www.patreon.com/user?u=4805718 Has a Patreon].<br />
<br />
<br />
<br />
=== Libretro / RetroArch ===<br />
* Has a [https://www.libretro.com/index.php/contributions/ contribute page] with wish lists for hardware and other info. <br />
* Has a [https://www.patreon.com/libretro Patreon].<br />
* Has a [https://www.bountysource.com/teams/libretro Bountysource] where you can donate money directly to functions and improvements you wish to see.<br />
<br />
<br />
<br />
=== ScummVM / ResidualVM ===<br />
* ScummVM has a [http://sourceforge.net/donate/index.php?group_id=37116 PayPal]<br />
* ScummVM Has a [https://bugs.scummvm.org/ Bug tracker]<br />
* You can [https://translations.scummvm.org/projects/scummvm/scummvm/ help translate] ScummVM<br />
* ScummVM has a [https://wiki.scummvm.org/index.php?title=Developer_Central devolper instruction] on how to contribute code<br />
* ResidualVM has a [http://wiki.residualvm.org/index.php/Getting_Involved getting involved page] and a [http://wiki.residualvm.org/index.php/Reporting_Bugs Bug reporting page].<br />
<br />
<br />
<br />
=== WINE ===<br />
* Has a [https://www.winehq.org/donate donate page] where you find information on how to donate with Paypal and other ways to send money, you can also support them by buying merch. Another option is to buy [https://www.codeweavers.com/about/support-wine CrossOver] which is a commercialized, supported version of Wine from CodeWeavers. They contribute all of their work on Wine back to the Wine Project and make up for 2/3 of the Wine commits.</div>87.123.201.116https://emulation.gametechwiki.com/index.php?title=Talk:Emulators_on_Patreon&diff=25047Talk:Emulators on Patreon2019-01-09T13:11:24Z<p>87.123.201.116: /* Generalize donations / payment */ new section</p>
<hr />
<div>In response to: "I don't think Romhacking is related to emulation here at all - it's just game hacks & translations" - ObiKKa<br />
I feel the opposite way :) Rom hacking was made available thru emulation. Emulation is on one hand the preservation of hardware and software, on the the other hand it's improving the experience. This can be done with increasing the resolution, sprite limits, hd packs but also rom hacking such as fixing bugs, removing western censoring, widescreen, new game modes, translations, etc. /Jpx<br />
<br />
== Generalize donations / payment ==<br />
<br />
I think this should be generalized into projects accepting monetary or hardware donations + possibly info who gets the money (and who doesn't get it) + what it's used for (and if there's proof for it) + ...<br />
So I think this should also list PayPal and contacts for project maintainers (regarding hardware donations or other means of donations)<br />
<br />
This could possibly also be mixed with each projects article, by having a section (templated), and adding all projects to a category (which would auto generate the list).<br />
<br />
--JFR 08:10, 9 January 2019 (EST)</div>87.123.201.116https://emulation.gametechwiki.com/index.php?title=Support_emulation_projects&diff=25046Support emulation projects2019-01-09T13:05:59Z<p>87.123.201.116: Archival and hardware donations</p>
<hr />
<div>'''''WIP page, help wanted.'''''<br />
<br />
There are several ways to support or contribute to an emulation project (or similar projects such as [[Compatibility layers]], [[Game engine recreations]] or simulators). Explained here are different ways you can get involved, even if you have low technical skill and no money.<br />
<br />
==Testing & bug reporting==<br />
''more text here...''<br />
<br />
=== Compatibility reporting ===<br />
<br />
A compatibility report communicates the emulation quality. It is aimed at other users.<br />
<br />
<!-- Sending users to GitHub is dangerous - you should only do it if the project has a simplified compatibility list which doesn't require technical understanding / writing; most projects actually uses wikis or custom tools / websites for compatibility reporting --><br />
<br />
Some emulators use GitHub for their compatibility list.<br />
Create a GitHub account, most projects have instructions on how bug reports should be written, make sure you search to see if the issues is already brought up by another user, in that case just add your observation to that report.<br />
<br />
''more text here...''<br />
<br />
<br />
=== Bug reporting ===<br />
<br />
A bug report is about one specific problem. It is aimed at emulator developers.<br />
<br />
Because bug reports are meant for developers, they are expected to be more technical than a compatibility report.<br />
Bug reports are typically expected to include details about specific situations when the problem arises, but also technical details as to why it happens.<br />
Developers also read compatibility reports and create respective bug reports themselves.<br />
<br />
''If you are not a software developer, you probably shouldn't do bug reports.''<br />
<br />
Generally you should chat to other developers / maintainers (via IRC or Discord) before creating a bug report.<br />
Often they are aware of issues and have grouped them under a technical term.<br />
<br />
''more text here...''<br />
<br />
=== Console verification ===<br />
<br />
Despite being aimed at developers, users should read / follow bug reports they care about.<br />
<br />
Many emulators not only need games tested in the emulator, but also on real hardware.<br />
Sometimes it looks like there's a bug in the emulator, but it might be a bug in the game, so it also happens on the console.<br />
So you can possibly prevent developers from wasting time on bugs which aren't really bugs in the emulator.<br />
Ideally, you have a capture card to record footage as proof.<br />
<br />
Also, during the research and documentation phase, some developers will write small programs to test hardware behaviour.<br />
In some cases the developers don't have access to the physical hardware or they need test results from many users.<br />
You can follow developer chat-rooms, so you can offer your help with running tests and collecting data from real hardware.<br />
<br />
==Provide support for end users==<br />
Discord, IRC, forums<br />
<br />
<br />
<br />
==Write & promotion==<br />
Write blog posts, promote news, provide information, make videos on YouTube, explain change logs, etc.<br />
<br />
== Archival and hardware donations ==<br />
<br />
Optical discs like CD or DVDs have a limited lifespan, they degrade over time and will eventually be unreadable.<br />
There is projects like [http://wiki.redump.org/index.php?title=Redump.org redump.org] which are focused on identifying all officially released discs.<br />
Each known disc is stored with information which makes it possible for users to verify the correctness of their disc.<br />
Contributing to these databases (by dumping your discs and contributing metadata) helps to build a full-set for testing emulators.<br />
It also encourages users to make legal backups of their discs before they break.<br />
<br />
Game databases like [https://www.mobygames.com/ MobyGames] can be used find additional information for each game. Launchers can use the uploaded descriptions and cover-artwork. You can contribute by scanning you game artwork, finding and adding game information (such as release dates).<br />
MobyGames also stores barcodes and serial numbers which can be used to find releases in redump.org.<br />
You can look at the existing cover artwork and extract such information.<br />
<br />
Alternatively, you can also donate games or hardware to developers or other volunteers who are accepting such donations.<br />
Donated games can then be analyzed by the recipient and their information can be added to databases such as those listed above.<br />
Emulator developers usually require a large number of consoles, games and peripherals (controllers, memory cards, ..), so donations are typically welcome.<br />
Depending on the project structure these will be forwarded to people who are in need of such hardware.<br />
Contact project maintainers to find out more.<br />
<br />
== Help with technical documentation ==<br />
<br />
Emulators depend on technical emulation about the systems they emulate.<br />
Typically, there are dedicated communities (often includes people from emulation, homebrew and piracy scene) for these research and documentation tasks.<br />
<br />
These research communities often uses Wikis which need to be maintained.<br />
Beginners can help by fixing typos or formatting. For some of these tasks, no coding skills are required.<br />
Advanced users and developers can contribute their own research, or participate in technical discussions.<br />
<br />
Many of these communities also maintain their own tools which can be helpful for testing emulation or ROM dumping.<br />
These tools are often written in beginner-friendl programming languages (such as C# or Python) and can be stepping-stone for moving towards actual emulator development.<br />
<br />
=== Communities ===<br />
<br />
* [https://github.com/xboxdev/xboxdev XboxDev] for original Xbox and SEGA Chihiro<br />
* [https://www.3dbrew.org/ 3DBrew] for 3DS<br />
<br />
== Learn how to code and help out ==<br />
WIP<br />
<br />
==Donate money==<br />
<br />
Emulation development is a time intensive task. It's only fair to reward the contributors.<br />
<br />
However, emulator development is often a group effort and there is no fair way to distribute money.<br />
Often developers of emulators can only do their work because research has been done by other people - unfortunately, that work often goes unrewarded.<br />
It's therefore important to understand who you donate to, and how that money will be shared or how it will be used.<br />
<br />
Especially for Open-Source projects, there can also be problems with only supporting the core developer group: it might actively discourage other contributors because of the unfair reward system ("Why should I work for free, but XYZ is getting paid on a monthly bases?").<br />
This can quickly lead to one "hero" developer - if they ever disappear the project is essentially dead because nobody else is familiar with the source-code.<br />
<br />
For some projects, there is also no practical use for money: money doesn't write code.<br />
There's also a lot of free services for Open-Source projects, so many projects don't have any expenses.<br />
<br />
<br />
=== Patreon ===<br />
Several emulators have a Patreon. [[Emulators on Patreon|Here is a list]]<br />
<br />
=== BountySource ===<br />
BountySource let's you directly donate money to certain features or improvements you wish for<br />
* [https://www.bountysource.com/teams/libretro Libretro]<br />
* [https://www.bountysource.com/teams/reicast Reicast]<br />
<br />
=== PayPal and other ways to donate ===<br />
Some emulators have PayPal addresses and such on their homepages.<br />
<br />
== Big projects ==<br />
<br />
<!-- This list is only intended for the four or five biggest projects in emulation/compability layers, and is intended as an example of ways to help out/getting involved --><br />
<br />
=== MAME ===<br />
It is not possible to donate directly to MAME, but several other projects that help MAME's development can be supported.<br />
<br />
* [http://www.mameworld.info/ubbthreads/showthreaded.php?Number=311481 The Dumping Union] - Accepts donations from PayPal.<br />
<br />
* [https://team-europe.blogspot.com/ Team Europe] - Accepts donations from PayPal. [https://www.reddit.com/r/emulation/comments/9txdsz/mame_team_europe_would_like_help_funding_some/ See info here on how to donate].<br />
<br />
* [https://caps0ff.blogspot.com/ CAPS0ff] - [https://www.patreon.com/user?u=4805718 Has a Patreon].<br />
<br />
<br />
<br />
=== Libretro / RetroArch ===<br />
* Has a [https://www.libretro.com/index.php/contributions/ contribute page] with wish lists for hardware and other info. <br />
* Has a [https://www.patreon.com/libretro Patreon].<br />
* Has a [https://www.bountysource.com/teams/libretro Bountysource] where you can donate money directly to functions and improvements you wish to see.<br />
<br />
<br />
<br />
=== ScummVM / ResidualVM ===<br />
* ScummVM has a [http://sourceforge.net/donate/index.php?group_id=37116 PayPal]<br />
* ScummVM Has a [https://bugs.scummvm.org/ Bug tracker]<br />
* You can [https://translations.scummvm.org/projects/scummvm/scummvm/ help translate] ScummVM<br />
* ScummVM has a [https://wiki.scummvm.org/index.php?title=Developer_Central devolper instruction] on how to contribute code<br />
* ResidualVM has a [http://wiki.residualvm.org/index.php/Getting_Involved getting involved page] and a [http://wiki.residualvm.org/index.php/Reporting_Bugs Bug reporting page].<br />
<br />
<br />
<br />
=== WINE ===<br />
* Has a [https://www.winehq.org/donate donate page] where you find information on how to donate with Paypal and other ways to send money, you can also support them by buying merch. Another option is to buy [https://www.codeweavers.com/about/support-wine CrossOver] which is a commercialized, supported version of Wine from CodeWeavers. They contribute all of their work on Wine back to the Wine Project and make up for 2/3 of the Wine commits.</div>87.123.201.116https://emulation.gametechwiki.com/index.php?title=Support_emulation_projects&diff=25045Support emulation projects2019-01-09T12:51:10Z<p>87.123.201.116: /* Bug reporting = */</p>
<hr />
<div>'''''WIP page, help wanted.'''''<br />
<br />
There are several ways to support or contribute to an emulation project (or similar projects such as [[Compatibility layers]], [[Game engine recreations]] or simulators). Explained here are different ways you can get involved, even if you have low technical skill and no money.<br />
<br />
==Testing & bug reporting==<br />
''more text here...''<br />
<br />
=== Compatibility reporting ===<br />
<br />
A compatibility report communicates the emulation quality. It is aimed at other users.<br />
<br />
<!-- Sending users to GitHub is dangerous - you should only do it if the project has a simplified compatibility list which doesn't require technical understanding / writing; most projects actually uses wikis or custom tools / websites for compatibility reporting --><br />
<br />
Some emulators use GitHub for their compatibility list.<br />
Create a GitHub account, most projects have instructions on how bug reports should be written, make sure you search to see if the issues is already brought up by another user, in that case just add your observation to that report.<br />
<br />
''more text here...''<br />
<br />
<br />
=== Bug reporting ===<br />
<br />
A bug report is about one specific problem. It is aimed at emulator developers.<br />
<br />
Because bug reports are meant for developers, they are expected to be more technical than a compatibility report.<br />
Bug reports are typically expected to include details about specific situations when the problem arises, but also technical details as to why it happens.<br />
Developers also read compatibility reports and create respective bug reports themselves.<br />
<br />
''If you are not a software developer, you probably shouldn't do bug reports.''<br />
<br />
Generally you should chat to other developers / maintainers (via IRC or Discord) before creating a bug report.<br />
Often they are aware of issues and have grouped them under a technical term.<br />
<br />
''more text here...''<br />
<br />
=== Console verification ===<br />
<br />
Despite being aimed at developers, users should read / follow bug reports they care about.<br />
<br />
Many emulators not only need games tested in the emulator, but also on real hardware.<br />
Sometimes it looks like there's a bug in the emulator, but it might be a bug in the game, so it also happens on the console.<br />
So you can possibly prevent developers from wasting time on bugs which aren't really bugs in the emulator.<br />
Ideally, you have a capture card to record footage as proof.<br />
<br />
Also, during the research and documentation phase, some developers will write small programs to test hardware behaviour.<br />
In some cases the developers don't have access to the physical hardware or they need test results from many users.<br />
You can follow developer chat-rooms, so you can offer your help with running tests and collecting data from real hardware.<br />
<br />
==Provide support for end users==<br />
Discord, IRC, forums<br />
<br />
<br />
<br />
==Write & promotion==<br />
Write blog posts, promote news, provide information, make videos on YouTube, explain change logs, etc.<br />
<br />
<br />
<br />
== Help with technical documentation ==<br />
<br />
Emulators depend on technical emulation about the systems they emulate.<br />
Typically, there are dedicated communities (often includes people from emulation, homebrew and piracy scene) for these research and documentation tasks.<br />
<br />
These research communities often uses Wikis which need to be maintained.<br />
Beginners can help by fixing typos or formatting. For some of these tasks, no coding skills are required.<br />
Advanced users and developers can contribute their own research, or participate in technical discussions.<br />
<br />
Many of these communities also maintain their own tools which can be helpful for testing emulation or ROM dumping.<br />
These tools are often written in beginner-friendl programming languages (such as C# or Python) and can be stepping-stone for moving towards actual emulator development.<br />
<br />
=== Communities ===<br />
<br />
* [https://github.com/xboxdev/xboxdev XboxDev] for original Xbox and SEGA Chihiro<br />
* [https://www.3dbrew.org/ 3DBrew] for 3DS<br />
<br />
== Learn how to code and help out ==<br />
WIP<br />
<br />
==Donate money==<br />
<br />
Emulation development is a time intensive task. It's only fair to reward the contributors.<br />
<br />
However, emulator development is often a group effort and there is no fair way to distribute money.<br />
Often developers of emulators can only do their work because research has been done by other people - unfortunately, that work often goes unrewarded.<br />
It's therefore important to understand who you donate to, and how that money will be shared or how it will be used.<br />
<br />
Especially for Open-Source projects, there can also be problems with only supporting the core developer group: it might actively discourage other contributors because of the unfair reward system ("Why should I work for free, but XYZ is getting paid on a monthly bases?").<br />
This can quickly lead to one "hero" developer - if they ever disappear the project is essentially dead because nobody else is familiar with the source-code.<br />
<br />
For some projects, there is also no practical use for money: money doesn't write code.<br />
There's also a lot of free services for Open-Source projects, so many projects don't have any expenses.<br />
<br />
<br />
=== Patreon ===<br />
Several emulators have a Patreon. [[Emulators on Patreon|Here is a list]]<br />
<br />
=== BountySource ===<br />
BountySource let's you directly donate money to certain features or improvements you wish for<br />
* [https://www.bountysource.com/teams/libretro Libretro]<br />
* [https://www.bountysource.com/teams/reicast Reicast]<br />
<br />
=== PayPal and other ways to donate ===<br />
Some emulators have PayPal addresses and such on their homepages.<br />
<br />
== Big projects ==<br />
<br />
<!-- This list is only intended for the four or five biggest projects in emulation/compability layers, and is intended as an example of ways to help out/getting involved --><br />
<br />
=== MAME ===<br />
It is not possible to donate directly to MAME, but several other projects that help MAME's development can be supported.<br />
<br />
* [http://www.mameworld.info/ubbthreads/showthreaded.php?Number=311481 The Dumping Union] - Accepts donations from PayPal.<br />
<br />
* [https://team-europe.blogspot.com/ Team Europe] - Accepts donations from PayPal. [https://www.reddit.com/r/emulation/comments/9txdsz/mame_team_europe_would_like_help_funding_some/ See info here on how to donate].<br />
<br />
* [https://caps0ff.blogspot.com/ CAPS0ff] - [https://www.patreon.com/user?u=4805718 Has a Patreon].<br />
<br />
<br />
<br />
=== Libretro / RetroArch ===<br />
* Has a [https://www.libretro.com/index.php/contributions/ contribute page] with wish lists for hardware and other info. <br />
* Has a [https://www.patreon.com/libretro Patreon].<br />
* Has a [https://www.bountysource.com/teams/libretro Bountysource] where you can donate money directly to functions and improvements you wish to see.<br />
<br />
<br />
<br />
=== ScummVM / ResidualVM ===<br />
* ScummVM has a [http://sourceforge.net/donate/index.php?group_id=37116 PayPal]<br />
* ScummVM Has a [https://bugs.scummvm.org/ Bug tracker]<br />
* You can [https://translations.scummvm.org/projects/scummvm/scummvm/ help translate] ScummVM<br />
* ScummVM has a [https://wiki.scummvm.org/index.php?title=Developer_Central devolper instruction] on how to contribute code<br />
* ResidualVM has a [http://wiki.residualvm.org/index.php/Getting_Involved getting involved page] and a [http://wiki.residualvm.org/index.php/Reporting_Bugs Bug reporting page].<br />
<br />
<br />
<br />
=== WINE ===<br />
* Has a [https://www.winehq.org/donate donate page] where you find information on how to donate with Paypal and other ways to send money, you can also support them by buying merch. Another option is to buy [https://www.codeweavers.com/about/support-wine CrossOver] which is a commercialized, supported version of Wine from CodeWeavers. They contribute all of their work on Wine back to the Wine Project and make up for 2/3 of the Wine commits.</div>87.123.201.116https://emulation.gametechwiki.com/index.php?title=Support_emulation_projects&diff=25044Support emulation projects2019-01-09T12:50:15Z<p>87.123.201.116: Game testing & bug reporting</p>
<hr />
<div>'''''WIP page, help wanted.'''''<br />
<br />
There are several ways to support or contribute to an emulation project (or similar projects such as [[Compatibility layers]], [[Game engine recreations]] or simulators). Explained here are different ways you can get involved, even if you have low technical skill and no money.<br />
<br />
==Testing & bug reporting==<br />
''more text here...''<br />
<br />
=== Compatibility reporting ===<br />
<br />
A compatibility report communicates the emulation quality. It is aimed at other users.<br />
<br />
<!-- Sending users to GitHub is dangerous - you should only do it if the project has a simplified compatibility list which doesn't require technical understanding / writing; most projects actually uses wikis or custom tools / websites for compatibility reporting --><br />
<br />
Some emulators use GitHub for their compatibility list.<br />
Create a GitHub account, most projects have instructions on how bug reports should be written, make sure you search to see if the issues is already brought up by another user, in that case just add your observation to that report.<br />
<br />
''more text here...''<br />
<br />
<br />
=== Bug reporting ====<br />
<br />
A bug report is about one specific problem. It is aimed at emulator developers.<br />
<br />
Because bug reports are meant for developers, they are expected to be more technical than a compatibility report.<br />
Bug reports are typically expected to include details about specific situations when the problem arises, but also technical details as to why it happens.<br />
Developers also read compatibility reports and create respective bug reports themselves.<br />
<br />
''If you are not a software developer, you probably shouldn't do bug reports.''<br />
<br />
Generally you should chat to other developers / maintainers (via IRC or Discord) before creating a bug report.<br />
Often they are aware of issues and have grouped them under a technical term.<br />
<br />
''more text here...''<br />
<br />
=== Console verification ===<br />
<br />
Despite being aimed at developers, users should read / follow bug reports they care about.<br />
<br />
Many emulators not only need games tested in the emulator, but also on real hardware.<br />
Sometimes it looks like there's a bug in the emulator, but it might be a bug in the game, so it also happens on the console.<br />
So you can possibly prevent developers from wasting time on bugs which aren't really bugs in the emulator.<br />
Ideally, you have a capture card to record footage as proof.<br />
<br />
Also, during the research and documentation phase, some developers will write small programs to test hardware behaviour.<br />
In some cases the developers don't have access to the physical hardware or they need test results from many users.<br />
You can follow developer chat-rooms, so you can offer your help with running tests and collecting data from real hardware.<br />
<br />
==Provide support for end users==<br />
Discord, IRC, forums<br />
<br />
<br />
<br />
==Write & promotion==<br />
Write blog posts, promote news, provide information, make videos on YouTube, explain change logs, etc.<br />
<br />
<br />
<br />
== Help with technical documentation ==<br />
<br />
Emulators depend on technical emulation about the systems they emulate.<br />
Typically, there are dedicated communities (often includes people from emulation, homebrew and piracy scene) for these research and documentation tasks.<br />
<br />
These research communities often uses Wikis which need to be maintained.<br />
Beginners can help by fixing typos or formatting. For some of these tasks, no coding skills are required.<br />
Advanced users and developers can contribute their own research, or participate in technical discussions.<br />
<br />
Many of these communities also maintain their own tools which can be helpful for testing emulation or ROM dumping.<br />
These tools are often written in beginner-friendl programming languages (such as C# or Python) and can be stepping-stone for moving towards actual emulator development.<br />
<br />
=== Communities ===<br />
<br />
* [https://github.com/xboxdev/xboxdev XboxDev] for original Xbox and SEGA Chihiro<br />
* [https://www.3dbrew.org/ 3DBrew] for 3DS<br />
<br />
== Learn how to code and help out ==<br />
WIP<br />
<br />
==Donate money==<br />
<br />
Emulation development is a time intensive task. It's only fair to reward the contributors.<br />
<br />
However, emulator development is often a group effort and there is no fair way to distribute money.<br />
Often developers of emulators can only do their work because research has been done by other people - unfortunately, that work often goes unrewarded.<br />
It's therefore important to understand who you donate to, and how that money will be shared or how it will be used.<br />
<br />
Especially for Open-Source projects, there can also be problems with only supporting the core developer group: it might actively discourage other contributors because of the unfair reward system ("Why should I work for free, but XYZ is getting paid on a monthly bases?").<br />
This can quickly lead to one "hero" developer - if they ever disappear the project is essentially dead because nobody else is familiar with the source-code.<br />
<br />
For some projects, there is also no practical use for money: money doesn't write code.<br />
There's also a lot of free services for Open-Source projects, so many projects don't have any expenses.<br />
<br />
<br />
=== Patreon ===<br />
Several emulators have a Patreon. [[Emulators on Patreon|Here is a list]]<br />
<br />
=== BountySource ===<br />
BountySource let's you directly donate money to certain features or improvements you wish for<br />
* [https://www.bountysource.com/teams/libretro Libretro]<br />
* [https://www.bountysource.com/teams/reicast Reicast]<br />
<br />
=== PayPal and other ways to donate ===<br />
Some emulators have PayPal addresses and such on their homepages.<br />
<br />
== Big projects ==<br />
<br />
<!-- This list is only intended for the four or five biggest projects in emulation/compability layers, and is intended as an example of ways to help out/getting involved --><br />
<br />
=== MAME ===<br />
It is not possible to donate directly to MAME, but several other projects that help MAME's development can be supported.<br />
<br />
* [http://www.mameworld.info/ubbthreads/showthreaded.php?Number=311481 The Dumping Union] - Accepts donations from PayPal.<br />
<br />
* [https://team-europe.blogspot.com/ Team Europe] - Accepts donations from PayPal. [https://www.reddit.com/r/emulation/comments/9txdsz/mame_team_europe_would_like_help_funding_some/ See info here on how to donate].<br />
<br />
* [https://caps0ff.blogspot.com/ CAPS0ff] - [https://www.patreon.com/user?u=4805718 Has a Patreon].<br />
<br />
<br />
<br />
=== Libretro / RetroArch ===<br />
* Has a [https://www.libretro.com/index.php/contributions/ contribute page] with wish lists for hardware and other info. <br />
* Has a [https://www.patreon.com/libretro Patreon].<br />
* Has a [https://www.bountysource.com/teams/libretro Bountysource] where you can donate money directly to functions and improvements you wish to see.<br />
<br />
<br />
<br />
=== ScummVM / ResidualVM ===<br />
* ScummVM has a [http://sourceforge.net/donate/index.php?group_id=37116 PayPal]<br />
* ScummVM Has a [https://bugs.scummvm.org/ Bug tracker]<br />
* You can [https://translations.scummvm.org/projects/scummvm/scummvm/ help translate] ScummVM<br />
* ScummVM has a [https://wiki.scummvm.org/index.php?title=Developer_Central devolper instruction] on how to contribute code<br />
* ResidualVM has a [http://wiki.residualvm.org/index.php/Getting_Involved getting involved page] and a [http://wiki.residualvm.org/index.php/Reporting_Bugs Bug reporting page].<br />
<br />
<br />
<br />
=== WINE ===<br />
* Has a [https://www.winehq.org/donate donate page] where you find information on how to donate with Paypal and other ways to send money, you can also support them by buying merch. Another option is to buy [https://www.codeweavers.com/about/support-wine CrossOver] which is a commercialized, supported version of Wine from CodeWeavers. They contribute all of their work on Wine back to the Wine Project and make up for 2/3 of the Wine commits.</div>87.123.201.116https://emulation.gametechwiki.com/index.php?title=Support_emulation_projects&diff=25043Support emulation projects2019-01-09T12:29:47Z<p>87.123.201.116: Adding some words of caution (should be made more concise)</p>
<hr />
<div>'''''WIP page, help wanted.'''''<br />
<br />
There are several ways to support or contribute to an emulation project (or similar projects such as [[Compatibility layers]], [[Game engine recreations]] or simulators). Explained here are different ways you can get involved, even if you have low technical skill and no money.<br />
<br />
==Game testing & bug reporting==<br />
''more text here...''<br />
Create a GitHub account, most projects have instructions on how bug reports should be written, make sure you search to see if the issues is already brought up by another user, in that case just add your observation to that report.<br />
<br />
<br />
<br />
==Provide support for end users==<br />
Discord, IRC, forums<br />
<br />
<br />
<br />
==Write & promotion==<br />
Write blog posts, promote news, provide information, make videos on YouTube, explain change logs, etc.<br />
<br />
<br />
<br />
== Help with technical documentation ==<br />
<br />
Emulators depend on technical emulation about the systems they emulate.<br />
Typically, there are dedicated communities (often includes people from emulation, homebrew and piracy scene) for these research and documentation tasks.<br />
<br />
These research communities often uses Wikis which need to be maintained.<br />
Beginners can help by fixing typos or formatting. For some of these tasks, no coding skills are required.<br />
Advanced users and developers can contribute their own research, or participate in technical discussions.<br />
<br />
Many of these communities also maintain their own tools which can be helpful for testing emulation or ROM dumping.<br />
These tools are often written in beginner-friendl programming languages (such as C# or Python) and can be stepping-stone for moving towards actual emulator development.<br />
<br />
=== Communities ===<br />
<br />
* [https://github.com/xboxdev/xboxdev XboxDev] for original Xbox and SEGA Chihiro<br />
* [https://www.3dbrew.org/ 3DBrew] for 3DS<br />
<br />
== Learn how to code and help out ==<br />
WIP<br />
<br />
==Donate money==<br />
<br />
Emulation development is a time intensive task. It's only fair to reward the contributors.<br />
<br />
However, emulator development is often a group effort and there is no fair way to distribute money.<br />
Often developers of emulators can only do their work because research has been done by other people - unfortunately, that work often goes unrewarded.<br />
It's therefore important to understand who you donate to, and how that money will be shared or how it will be used.<br />
<br />
Especially for Open-Source projects, there can also be problems with only supporting the core developer group: it might actively discourage other contributors because of the unfair reward system ("Why should I work for free, but XYZ is getting paid on a monthly bases?").<br />
This can quickly lead to one "hero" developer - if they ever disappear the project is essentially dead because nobody else is familiar with the source-code.<br />
<br />
For some projects, there is also no practical use for money: money doesn't write code.<br />
There's also a lot of free services for Open-Source projects, so many projects don't have any expenses.<br />
<br />
<br />
=== Patreon ===<br />
Several emulators have a Patreon. [[Emulators on Patreon|Here is a list]]<br />
<br />
=== BountySource ===<br />
BountySource let's you directly donate money to certain features or improvements you wish for<br />
* [https://www.bountysource.com/teams/libretro Libretro]<br />
* [https://www.bountysource.com/teams/reicast Reicast]<br />
<br />
=== PayPal and other ways to donate ===<br />
Some emulators have PayPal addresses and such on their homepages.<br />
<br />
== Big projects ==<br />
<br />
<!-- This list is only intended for the four or five biggest projects in emulation/compability layers, and is intended as an example of ways to help out/getting involved --><br />
<br />
=== MAME ===<br />
It is not possible to donate directly to MAME, but several other projects that help MAME's development can be supported.<br />
<br />
* [http://www.mameworld.info/ubbthreads/showthreaded.php?Number=311481 The Dumping Union] - Accepts donations from PayPal.<br />
<br />
* [https://team-europe.blogspot.com/ Team Europe] - Accepts donations from PayPal. [https://www.reddit.com/r/emulation/comments/9txdsz/mame_team_europe_would_like_help_funding_some/ See info here on how to donate].<br />
<br />
* [https://caps0ff.blogspot.com/ CAPS0ff] - [https://www.patreon.com/user?u=4805718 Has a Patreon].<br />
<br />
<br />
<br />
=== Libretro / RetroArch ===<br />
* Has a [https://www.libretro.com/index.php/contributions/ contribute page] with wish lists for hardware and other info. <br />
* Has a [https://www.patreon.com/libretro Patreon].<br />
* Has a [https://www.bountysource.com/teams/libretro Bountysource] where you can donate money directly to functions and improvements you wish to see.<br />
<br />
<br />
<br />
=== ScummVM / ResidualVM ===<br />
* ScummVM has a [http://sourceforge.net/donate/index.php?group_id=37116 PayPal]<br />
* ScummVM Has a [https://bugs.scummvm.org/ Bug tracker]<br />
* You can [https://translations.scummvm.org/projects/scummvm/scummvm/ help translate] ScummVM<br />
* ScummVM has a [https://wiki.scummvm.org/index.php?title=Developer_Central devolper instruction] on how to contribute code<br />
* ResidualVM has a [http://wiki.residualvm.org/index.php/Getting_Involved getting involved page] and a [http://wiki.residualvm.org/index.php/Reporting_Bugs Bug reporting page].<br />
<br />
<br />
<br />
=== WINE ===<br />
* Has a [https://www.winehq.org/donate donate page] where you find information on how to donate with Paypal and other ways to send money, you can also support them by buying merch. Another option is to buy [https://www.codeweavers.com/about/support-wine CrossOver] which is a commercialized, supported version of Wine from CodeWeavers. They contribute all of their work on Wine back to the Wine Project and make up for 2/3 of the Wine commits.</div>87.123.201.116https://emulation.gametechwiki.com/index.php?title=Support_emulation_projects&diff=25042Support emulation projects2019-01-09T12:19:23Z<p>87.123.201.116: Add section about documentation</p>
<hr />
<div>'''''WIP page, help wanted.'''''<br />
<br />
There are several ways to support or contribute to an emulation project (or similar projects such as [[Compatibility layers]], [[Game engine recreations]] or simulators). Explained here are different ways you can get involved, even if you have low technical skill and no money.<br />
<br />
==Game testing & bug reporting==<br />
''more text here...''<br />
Create a GitHub account, most projects have instructions on how bug reports should be written, make sure you search to see if the issues is already brought up by another user, in that case just add your observation to that report.<br />
<br />
<br />
<br />
==Provide support for end users==<br />
Discord, IRC, forums<br />
<br />
<br />
<br />
==Write & promotion==<br />
Write blog posts, promote news, provide information, make videos on YouTube, explain change logs, etc.<br />
<br />
<br />
<br />
== Help with technical documentation ==<br />
<br />
Emulators depend on technical emulation about the systems they emulate.<br />
Typically, there are dedicated communities (often includes people from emulation, homebrew and piracy scene) for these research and documentation tasks.<br />
<br />
These research communities often uses Wikis which need to be maintained.<br />
Beginners can help by fixing typos or formatting. For some of these tasks, no coding skills are required.<br />
Advanced users and developers can contribute their own research, or participate in technical discussions.<br />
<br />
Many of these communities also maintain their own tools which can be helpful for testing emulation or ROM dumping.<br />
These tools are often written in beginner-friendl programming languages (such as C# or Python) and can be stepping-stone for moving towards actual emulator development.<br />
<br />
=== Communities ===<br />
<br />
* [https://github.com/xboxdev/xboxdev XboxDev] for original Xbox and SEGA Chihiro<br />
* [https://www.3dbrew.org/ 3DBrew] for 3DS<br />
<br />
== Learn how to code and help out ==<br />
WIP<br />
<br />
==Donate money==<br />
<br />
=== Patreon ===<br />
Several emulators have a Patreon. [[Emulators on Patreon|Here is a list]]<br />
<br />
=== BountySource ===<br />
BountySource let's you directly donate money to certain features or improvements you wish for<br />
* [https://www.bountysource.com/teams/libretro Libretro]<br />
* [https://www.bountysource.com/teams/reicast Reicast]<br />
<br />
=== PayPal and other ways to donate ===<br />
Some emulators have PayPal addresses and such on their homepages.<br />
<br />
<br />
== Big projects ==<br />
<br />
<!-- This list is only intended for the four or five biggest projects in emulation/compability layers, and is intended as an example of ways to help out/getting involved --><br />
<br />
=== MAME ===<br />
It is not possible to donate directly to MAME, but several other projects that help MAME's development can be supported.<br />
<br />
* [http://www.mameworld.info/ubbthreads/showthreaded.php?Number=311481 The Dumping Union] - Accepts donations from PayPal.<br />
<br />
* [https://team-europe.blogspot.com/ Team Europe] - Accepts donations from PayPal. [https://www.reddit.com/r/emulation/comments/9txdsz/mame_team_europe_would_like_help_funding_some/ See info here on how to donate].<br />
<br />
* [https://caps0ff.blogspot.com/ CAPS0ff] - [https://www.patreon.com/user?u=4805718 Has a Patreon].<br />
<br />
<br />
<br />
=== Libretro / RetroArch ===<br />
* Has a [https://www.libretro.com/index.php/contributions/ contribute page] with wish lists for hardware and other info. <br />
* Has a [https://www.patreon.com/libretro Patreon].<br />
* Has a [https://www.bountysource.com/teams/libretro Bountysource] where you can donate money directly to functions and improvements you wish to see.<br />
<br />
<br />
<br />
=== ScummVM / ResidualVM ===<br />
* ScummVM has a [http://sourceforge.net/donate/index.php?group_id=37116 PayPal]<br />
* ScummVM Has a [https://bugs.scummvm.org/ Bug tracker]<br />
* You can [https://translations.scummvm.org/projects/scummvm/scummvm/ help translate] ScummVM<br />
* ScummVM has a [https://wiki.scummvm.org/index.php?title=Developer_Central devolper instruction] on how to contribute code<br />
* ResidualVM has a [http://wiki.residualvm.org/index.php/Getting_Involved getting involved page] and a [http://wiki.residualvm.org/index.php/Reporting_Bugs Bug reporting page].<br />
<br />
<br />
<br />
=== WINE ===<br />
* Has a [https://www.winehq.org/donate donate page] where you find information on how to donate with Paypal and other ways to send money, you can also support them by buying merch. Another option is to buy [https://www.codeweavers.com/about/support-wine CrossOver] which is a commercialized, supported version of Wine from CodeWeavers. They contribute all of their work on Wine back to the Wine Project and make up for 2/3 of the Wine commits.</div>87.123.201.116