We won't be merging it in that state, even if rebased.
(Unofficial) Rebased Wii MotionPlus build
|
06-18-2018, 02:22 AM
06-18-2018, 02:26 AM
(06-18-2018, 02:20 AM)Helios Wrote: We won't be merging it in that state, even if rebased. Wouldn't dream of it, now that I understand the reasons behind it. Would clean, well written code for this kind of project be considered for use if developed? Or are the inherent innacuracies with this kind of emulation a total barrier? 06-18-2018, 02:44 AM
06-18-2018, 02:46 AM
06-18-2018, 05:08 AM
(06-18-2018, 02:46 AM)IICuttingEdgeII Wrote: How do I do that? https://github.com/dolphin-emu/dolphin#b...-and-macos 06-21-2018, 06:57 AM
(06-18-2018, 05:08 AM)ExtremeDude2 Wrote: https://github.com/dolphin-emu/dolphin#b...-and-macos THANKS A TON!!! 06-22-2018, 05:42 AM
Hmm, I'm having problems with building it, which file do I need to build, the original file or all of its contents individually and which configuration should I use???
Any help would be greatly appreciated 07-04-2018, 02:09 PM
(06-05-2018, 04:37 PM)MayImilae Wrote: Yet more hacking to try to make skyward sword work on a keyboard is not the way forward. The solution is VR controllers and open VR APIs. Motion controls can only be emulated well by other motion controllers. Of course we'll need to expose raw button and axis mapping as well for TAS and the odd motion controller outside of VR APIs, but the gesture by button press model is not a solution. I'm going to try and speak as both a user and a SW Engineer here. I agree the first step is having an API that exposes the controls, or at least a dummy Motion+ accessory so preliminary debuging can be accomplished. Someone should probably at least start on that so others can experiment and find the underlying bugs that will probably surface. That being said, I do slightly disagree on one point: At least in the short term, the majority of end users aren't going to have access to external motion controls (Android phones come to mind here). While proper emulation of Motion+ to emulated motion controllers should be the goal, there should also be some mechanism for those controls to be mapped to a more traditional controller as well provided it can be done in such as way as to not impact code maintainability/testibility/stability. Yes it would be a cludge, but it would be a cludge that the majority of the Dolphin userbase ends up using. [And yes, I completed Skyward Sword using the old 3.5 build; it was painful, especially the drawing part. The current cludge is horrible from an end-user perspective and shouldn't be merged into master, but I believe a more workable solution is possible once proper implementation is done. You might need an external device like a 3-axis joystick just for the Motion+, but I have to imaging *something* is doable on this front that isn't a complete mess.] |
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)