These results revealed that the default, no-attempted-solution version of my code was returning the same values as dolphin. I stared at the input values in dolphin, and concluded that I was missing something.īanging my head up against a wall for a solution, I tried to obtain samples of analogue input on several different environments, including dolphin's built-in adapter support, my code with and without it's attempted solution, and a real gamecube ports, via homebrewed wii. After some testing, I could feel that this wasn't correct. The first solution I tried had some method of "scaling" the analogue values based on the extrapolated purposes of some constants in wii-u-gc-adapter, as well as some investigation within dolphin. I couldn't tell exactly what caused this, because ToadKing's wii-u-gc-adapter linux driver (which is what I based the code off of) seemed to be "calibrating" things using uinput, which I'm not familiar with at all. Lightshielding was much touchier, making shielding strangely uncomfortable. What I mean by "screwing up," is that the behaviour of the triggers seemed REALLY off at the time, when using the hack. (commit de6c9404fc43f82d6ec33629d6a2ab3a5317c9e2) No idea whether or not they've fixed it by now, but I concluded at the time (June) that dolphin was screwing up in the same way as Wii GCA Inject. The dolphin build I tested that on is from March of 2017. I wrote those notes so long ago! Forgive me if I go into too much detail. (Again, this is a beta)Ĭlick to expand.Oh, goodness. I haven't confirmed the cause of thisīug, or even if it's affecting anyone but me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |