From: Darren W. <dd...@gm...> - 2016-08-25 02:57:32
|
I'm on on my linux computer right now so I can't validate my preferences for sure, but yes I am using the mouse, and I typically uncheck the box to accelerate the mouse. Assuming that build was using the regular preferences file, it was probably not accelerating the mouse. What I saw was far more than 15ms. The input lag seemed pretty random and seemed to go anywhere from 30-1000 ms. I think on a number of occasions I pushed the mouse button and the gun did not fire at all, or there was a delay of 1-2 seconds. It's hard to say for sure, because usually when it didn't fire, I'd instinctively click the button again. On Wed, Aug 24, 2016 at 8:25 PM, Solra Bizna <sb...@te...> wrote: > On Tue, Aug 23, 2016 at 7:18 PM, Darren Watts <dd...@gm...> wrote: > > I was holding off on saying anything, because I don't know how far into > > development it is, yet. So far I was able to get 60fps, but the controls > > were very unresponsive, and I'd call it "unplayable" in its current > state. > > I tried it about a week ago though, so maybe there have been updates > since > > then. > I've logged over 12 hours of testing since I did the first push. I > haven't experienced unresponsiveness of any kind, other than an > imperceptible (and expected) ~15ms perceived input latency. What I > _have_ experienced is the occasional freeze, which I'm still working > on. By any chance, are you using a mouse to aim, and if you are, do > you have Accelerate Mouse on? I've been playing keyboard-only, because > my "work" machine has a trackpad, and trackpad Marathon is > intolerable... > > ------------------------------------------------------------ > ------------------ > _______________________________________________ > Marathon-devel mailing list > Mar...@li... > https://lists.sourceforge.net/lists/listinfo/marathon-devel > |