This map right here. https://osu.ppy.sh/b/622407
This one actually.Rickput wrote:
Another instance of the (still occuring) ghost sliders: http://puu.sh/lbj7d/d9e7b7952b.mp4
On Cutting Edge b20151106.7
Map: https://osu.ppy.sh/b/256499 During the first kiai time.
Make sure that you didn't move your Universal offset in the options.mrks wrote:
Map files kinda "start" to early. not sure if this got reported before.
https://www.youtube.com/watch?v=cPFmXdVe0Xw
it is set to 0Trosk- wrote:
Make sure that you didn't move your Universal offset in the options.mrks wrote:
Map files kinda "start" to early. not sure if this got reported before.
https://www.youtube.com/watch?v=cPFmXdVe0Xw
Fatal3ty wrote:
New problem is back. FPS Lag is back, red dots in Game. I cant play this. Please Check and Fix.
http://puu.sh/lbBMk/3749bbbbfa.log here is my logTrosk- wrote:
Provide your performance.log please. You will find it in the Logs folder of your installation.
I was just reporting by how it felt in-game, but since you asked: I took out my DSLR and (rather hastily/sloppily) recorded 60fps footage of myself snapping my cursor back and forth with it enabled (and again with it disabled), and examined the footage frame-by-frame. The cursor indeed seemed to match my hand movements more closely with the NoAsyncReads option enabled. It's a rather unscientific way of measuring, but it does show a difference in responsiveness.peppy wrote:
how are you testing? that sounds impossible to be true.
Nagamine Tomoki wrote:
In other words, the screen has a slightly lag through the whole beatmap playing, and I can't predict when the lag happens..
Sorrypeppy wrote:
if you're using cutting edge, please learn how to report issues. need performance.log and frame graph screenshots at very least.Nagamine Tomoki wrote:
In other words, the screen has a slightly lag through the whole beatmap playing, and I can't predict when the lag happens..
Yeah it´s fixed, at least for me. Got no more broken chains since yesterday and had them frequently before. Thank you.peppy wrote:
@Denro: are you sure you are on the latest build? I made a fix which should 99.9999999% fix this yesterday.