I've been playing Metroid Prime (from Trilogy) on stable release (5.0). Motion simulation config was pretty straightforward and I easily set it up so that the WiiMote cursor followed (closely enough) the mouse cursor. I was really happy with this setup.
Since I've had a few slowdown issues, I downloaded the latest dev build 11985 (to test ubershaders and stuff) and found this... new configuration system for motion simulation. After half an hour or so of trying with different values, this is complete chaos. I can't align both cursors, no matter what I do, and if I get close to aligning them (not really close, just the closer I can get), it's by sacrificing the area that the WiiMote cursor can cover.
This "Calibration" function is, of course, of no help. It just starts a new catastrophe every time I use it.
Maybe I'm not understanding this new system right. Any insight on this issue?
Since I've had a few slowdown issues, I downloaded the latest dev build 11985 (to test ubershaders and stuff) and found this... new configuration system for motion simulation. After half an hour or so of trying with different values, this is complete chaos. I can't align both cursors, no matter what I do, and if I get close to aligning them (not really close, just the closer I can get), it's by sacrificing the area that the WiiMote cursor can cover.
This "Calibration" function is, of course, of no help. It just starts a new catastrophe every time I use it.
Maybe I'm not understanding this new system right. Any insight on this issue?