![]() ![]() Plugin wise, I can't really help you since I don't play much these days. What is your goal? If it's simply performance, than Pj64 or 1964 are the best emulators for those. ![]() My advice is to try out many different plugins and mess with the emulator settings. To answer your question, there is no definitive emulator for n64. You were probably just using different plugins for each one. ![]() I have not seen a noticeable difference in graphics between the PJ64 versions. Sounds like you need to learn more about the different plugins out there. Pretty much any emulator for 32bit and up game systems have obvious flaws. Lol idk why so many people criticize n64 emulation. I know I probably cant eliminate this all together (due to the nature of N64 emulation), but I would like to know which version deals with this issue the best. Some textures I find are transparent and others don't load at all. What does everyone use to get the best balance of graphics and frame rate? One thing also very important to me is keeping graphic errors and glitches down to a minimum. I know this is the one console that has had issues getting emulation to work over the years. So what would people recommend as THE definitive N64 emulator. One of the main reasons I upgraded to the newest version in the first place was because my video card couldn't run Glide (however, I'm in the process of upgrading to a GTX series Nvida card soon). A noticeable drop is seen when I play the same game in both emulators. However, the frame rate is MUCH slower on many games that in 1.6. I find that the newer version has a better display driver (up scaling things to HD is nice in the newer version by default). I am torn between which should actually be my primary emulator for N64. ![]() Plugins are already dependencies in order to get Project64 to initialize, and there can be infinitely many plugins, so better to have 1 DirectInput, 1 XInput plugin, than to have 1 merged DLL which requires both to be installed.I have experimented with both PJ64 1.6 and the new latest version that was taken over development from the old team (2.1.0.1). So I like to minimize dependencies not maximize them. Bear in mind though that this isn't necessarily true for everyone, and if the assumption breaks, there will be no valid controller plugins installed to Project64 which are aning no usable input plugins and no way to start emulation without making people figure out plugins and how to change them. However, it could be reasoned that most people today, who have DirectX installed to support DirectInput8, probably could get N-Rage 2.3 (with its XInput dependencies) to initialize as well. N-Rage 2.3 can double the amount of code we'd have to maintain, because it merges in XInput dependency within a single plugin. N-Rage 2.1 = all of N-Rage and rabiddeity overhaul DirectInput code. Ignoring some more.fundamental issues, what I don't like about N-Rage 2.3 as a DLL in itself is that it is twice the code to maintain as the original N-Rage plugin before squall was left alone to work on it. I know at least a couple people who prefer Jabo's DirectInput over N-Rage DirectInput, for some reason. So I'm not too qualified to opine on this topic. I would not be any more comfortable with any other device. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |