Project64: Difference between revisions
Ilyagredasov (talk | contribs) No edit summary Tags: Mobile edit Mobile web edit |
→Problems: Added screen example |
||
| (One intermediate revision by the same user not shown) | |||
| Line 44: | Line 44: | ||
|} | |} | ||
== | ==Overview== | ||
Project64 first came out as a purely experimental emulator by developers zilmar and Jabo. It quickly revolutionized the N64 emulation landscape. For many years afterward, it was considered to be the best N64 emulator, with only Mupen64 and [[1964]] posing any real competition. By version 1.6, it was touted as being not only highly compatible but also the most stable of the lot. | |||
However, upon announcing the development of version 1.7, the project became closed off to most of the public. The only way to keep up with the latest developments was to donate $20 to obtain beta testing privileges. However, there were several development version leaks, most of which turned out to be unstable, prone to crashes, and full of performance and compatibility regressions, which cast doubt upon the competency of the developers. Upon Jabo's departure from the project in 2011, most people came to regard Projec64 as being stuck in development limbo, if not completely dead. | However, upon announcing the development of version 1.7, the project became closed off to most of the public. The only way to keep up with the latest developments was to donate $20 to obtain beta testing privileges. However, there were several development version leaks, most of which turned out to be unstable, prone to crashes, and full of performance and compatibility regressions, which cast doubt upon the competency of the developers. Upon Jabo's departure from the project in 2011, most people came to regard Projec64 as being stuck in development limbo, if not completely dead. | ||
| Line 57: | Line 57: | ||
==Problems== | ==Problems== | ||
===Malware and nagware=== | ===Malware and nagware=== | ||
Up to version 2.2, the official installer for PJ64 included opt-out malware in the installer. In July of 2016, the malware was removed from both the source code and installers.<ref>https://github.com/project64/project64/issues/468</ref> However, version 2.3 introduced a benign but irritating nagware screen that pops up when launching PJ64 after starting it multiple times, which grows more persistent with successive launches as a forced waiting period is installed. You can type "'''thank you from project64'''" as the notification code, or disable it by modifying <code>project64.cfg</code> to appear as follows: <pre>[Support Project64]Run Count=-1</pre> | Up to version 2.2, the official installer for PJ64 included opt-out malware in the installer. In July of 2016, the malware was removed from both the source code and installers.<ref>https://github.com/project64/project64/issues/468</ref> However, version 2.3 introduced a benign but irritating nagware screen that pops up when launching PJ64 after starting it multiple times, which grows more persistent with successive launches as a forced waiting period is installed. You can type "'''thank you from project64'''" as the notification code, or disable it by modifying <code>project64.cfg</code> to appear as follows: <pre>[Support Project64]Run Count=-1</pre> | ||
[[File:Project64 Nagging Screen.png|thumb|350px|Project 64 Nagging Screen that plays on application open.]] | |||
Version 2.4.0.1555 introduced a new method, with a per-machine ID that gets generated on the user side and requests a confirmation code associated with it. You can avoid it thanks to [https://github.com/Rosalie241/PJ64Launcher this script] by Rosalie241. | Version 2.4.0.1555 introduced a new method, with a per-machine ID that gets generated on the user side and requests a confirmation code associated with it. You can avoid it thanks to [https://github.com/Rosalie241/PJ64Launcher this script] by Rosalie241. | ||