Ok, I haven't had much time to work on this because of exams. I did take a look into OoT's behaviour. The mapping table ING supplies in the first post is almost always correct. The mapping only changes when you are holding the analog stick diagonal and very far from its center. With far I mean that N64 values that are diagonal (so N64 X and Y values are about the same) and have a distance longer than 80 from the center (basically you hold your analog stick in a maximum position diagonally) don't have the same GC values as the mapping table that was used before. 80 Is a pretty high value for an N64 controller, I am pretty sure the one I use doesn't reach this value and others barely. This would basically mean that the only place where the mapping could feel off (the rest of the mapping is probably as good as it can be, it's on VC, so ofcourse it's gonna still feel a little different from N64) and be improved is on the really high diagonal values.
Pheenoh, could you try to describe what feels strange about OoT? Because making a big mapping table doesn't change a lot, except that it could potentially fix the really high diagonal values. Due to the fact that an N64 controller barely reaches these and I doubt you would feel a real difference, I don't know if it's worth it, because it would also mean that the code doesn't fit on a Raphnet adapter anymore. Also, the behaviour of the mapping is really weird on the high diagonals, which makes it really hard to find the best GC values for N64 data that never occurs.
Pheenoh, could you try to describe what feels strange about OoT? Because making a big mapping table doesn't change a lot, except that it could potentially fix the really high diagonal values. Due to the fact that an N64 controller barely reaches these and I doubt you would feel a real difference, I don't know if it's worth it, because it would also mean that the code doesn't fit on a Raphnet adapter anymore. Also, the behaviour of the mapping is really weird on the high diagonals, which makes it really hard to find the best GC values for N64 data that never occurs.
