yeah the office politics and egos to conquer would be astronomically big :(

Haha I have to admit, that is a better life choice. Eh it was worth a shot, but I fully agree, I'd opt for that as well instead of MS. :)

Maybe @scott.hanselman.com can convince the internal powers that be that you'd be the ideal person to fix everything windows :) Make it happen, Scott!

Oh how I wish Microsoft would hire you (no matter the price) to simply fix shit in windows. Free reign. "Bruce, we don't want to see you, just the commits, fix stuff. We'll pay whatever you want" It'll be beneficial for all.

One of the most deceptive box covers ever. :P

WinRT is a nice effort but ultimately not what people want.

hahaha :D That might be a wise choice :P

I for one didn't know! :) Have you tried Windows.Gaming.Input's Gamepad class btw? It's their next version of the xinput mess. No idea if it suffers from the same problem. they don't wrap xinput in that library so that's a plus at least.

Ugh :( I don't think that 20% can cause a delta that big. Sorry I can't be of more help, but you got this! :) Keep up the good work!

I'm not sure if you use floats vs doubles, but it could be as simple as that: over the course of the interpolation, the loss of precision with floats might cause it to fail in the end? I had that in my catmull rom implementation for camera paths, when distances were small, floats caused issues

I had the exact same issue! What I did was call my unwrapper (which basically removes the Convert calls) at those locations which gives you the right object to work with and the code will proceed as normal. perhaps that helps you
But yeah it sucks big time. :(

Look at this guy with his fancy Real Time Raytracing puddle. :P