![]() ![]() In this guide, we will walk you through the process of setting up controllers and joysticks with Project 64. Whether you prefer a keyboard and mouse, console controllers, or even retro USB options, we have you covered. In this article, we'll delve into the world of controllers in Project 64, covering everything from connecting various controllers to troubleshooting common issues. To fully enjoy the gaming experience, it's crucial to have the right controller setup. So no, 1.7 isn't newer than 1.6.1, just different.Project 64, the beloved Nintendo 64 emulator, allows gamers to relive the magic of classic N64 titles on their computers. That's basically the reason the plugin spec for the Jabo 1.7 plugins existed. All the 1.7 plugins are is just a private plugin spec invented to keep the plugins from being usable outside of paid versions of Project64 1.7 really. The 1.7 plugins are the older ones though, not the 1.6.1 plugins. I never use the 1.7 plugins anymore except Jabo's Direct3D8 1.7. Tell me one thing that's better about Jabo's DirectSound 1.7 or DirectInput 1.7, over 1.6.1 plugins? Because the version number is higher, which makes them not "older"? Actually, I always use Jabo's DirectSound 1.6.1. This makes all binary pull requests redundant, along with hosting binary files on GitHub.Īs for the Jabo plugins, I see no reason to keep the "older" (1.6.1) Audio and Input ones. Or even just download them directly and commit them.Įxactly. ![]() Zilmar can download them from the links and compare the SHA-1 (for absolute certainty),īy the time zilmar goes through the process of downloading the official binary files himself, there was no longer a reason for you to have sent a pull request in the first place. Just speaking fundamentally: Git is not a reliable solution for binary files. Those are all of my thoughts on what could be done for graphics, audio, and input plugins. anyway delete this post if it's too long, it wont bother me tbhĮither way XInput should belong to 1 DLL and DirectInput should belong to a separate DLL.otherwise why even have a controller plugin spec if all the dependencies collide? He did this with plenty other developers as well. I also don't like that he kissed up to Shunyuan just because he was a developer just for the simple-minded goal of "N64 progress", an event leading to Shunyuan's violation of many open-source plugins and emulators. It's kind of like he's doing his own project64 repository except exclusively to N-Rage. What actually happened was squall credited somebody else he hired to add the XInput code for him, along with most of the changes since 2.1 which generally was him crediting other people for as well. Now if the XInput code was written by squall himself then I could understand shying away from moving from N-Rage 2.3 to 2.1 and hurting his feelings or something. N-Rage 2.3 has XInput support, higher system requirements, larger code size and dependency hell and that's about it. 2.1 rc3 already has all the improvements, and I've never had any problems with that. The whole attitude behind squalls' 2.2-2.3 continuation is just ridiculous. Sometime after that, I guess rabid vanished off the interwebz, and now squall mood switches from missing him and wanting him back to bashing him as an inept coder who just screwed things up. rabiddeity never agreed with that and neither could I in his shoes. He had a disagreement with rabiddeity back when he (rab) was the developer of the overhaul on whether N-Rage DirectInput should become a DirectInput + XInput plugin, mixing 2 APIs together in a single DLL. squall himself confessed to the Project64 fork of 2.3 being "no longer my problem", so I doubt he has any intention to work on it or help with this repository (if he did then I might change my perspective on his attitude). Pretty sure Azimer's XAudio2 plugin should also be included, but I know he's not happy with it yet in its present state, and he has a lot of ideas about how to stream the audio more accurately over most plugins, also wants to modify the audio plugin spec.I would like it if he helped you change Audio #1.2 specs with his improvements before they become too permanently established/official. (Rumor has it that GLideN64 will also support both HLE and LLE.) For that reason I would like Jabo D3D8 1.7 to continue to remain the default graphics plugin. ![]() I really like that Jabo D3D8 1.7 is flexible to either LLE or HLE gfx though, in case I have constant issues remembering RSP settings and just don't care which one is set. Often times the 1.6.1 plugins are >= what you get from the 1.7 ones, as he didn't purposely backport any regressions from 1.7. Personally, I would get rid of all Jabo 1.6 plugins and include all Jabo 1.6.1 plugins. I don't think it's that important to decide, at least right now. I guess I'm not answering the question tho, even though I don't think it's relevant to pj64 source. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |