Are you running osu! in window mode? While in window mode osu! framerate is affected by other windows, so try to minimize the things you have open. This is likely caused by one of them.Lemmmy wrote:
#help told me to post this here, therefore I am not sure if this is an issue on my end. When playing, the game seems to skip a frame, causing the hitobjects to reverse by a few milliseconds. This happens every few seconds.
Screenshot with Ctrl + F11 related:
Only snaking sliders are enabled.
No and no. I am in native fullscreen with letterboxing. No external applications have been known to cause this for me. It seems to be with the latest few builds.Tom94 wrote:
Are you running osu! in window mode? While in window mode osu! framerate is affected by other windows, so try to minimize the things you have open. This is likely caused by one of them.Lemmmy wrote:
#help told me to post this here, therefore I am not sure if this is an issue on my end. When playing, the game seems to skip a frame, causing the hitobjects to reverse by a few milliseconds. This happens every few seconds.
Screenshot with Ctrl + F11 related:
Only snaking sliders are enabled.
Another possibility is that you have a background application open which affects your desktop, such as f.lux. It is known to cause spikes every few seconds.
This sounds like correct behaviour to me. Fullscreen and Letterboxing will always open on your main screen, if I'm not wrong.Kon wrote:
It's been a couple of weeks since I posted this so I'll post again in case it wasn't seen.
When launching osu! with letterboxing enabled, osu! doesn't open on the monitor where your cursor is. However, when launching in windowed mode it does open on the correct monitor.
Also, for what it's worth, the updater and the osu! sprite are shown on the correct monitor with letterboxing on.
I'm unable to replicate. Do you have any specific steps?marcostudios wrote:
if I change the volume on the results screen it doesn't not change the volume of the applause sound. On stable it works tho
Can't replicate neither. Are you changing a specific volume or Master volume?marcostudios wrote:
if I change the volume on the results screen it doesn't not change the volume of the applause sound. On stable it works tho
Then could you specify what type of applause? I mean, is a custom applause from a beatmap, a custom applause from your skin, the default applause... I don't actually know if it could matter or not, but I couldn't replicate what you said.marcostudios wrote:
master volume
Do you get them while playing? I have some of these on Song Selection screen and not while playing (They are barely noticeable). Check it with the Auto mod so you can see the performance graph._index wrote:
It seems like SwapBuffer lag spikes are back on cutting edge version for some previous builds and current one
Random stuttering every 3-5 seconds, every 7-15 seconds after osu! reload.
AMD 8150, gtx 970, win 8.1
yes, exactly same lag spikes, just did SS in menu because its easier to catch itTrosk- wrote:
Do you get them while playing? I have some of these on Song Selection screen and not while playing (They are barely noticeable). Check it with the Auto mod so you can see the performance graph._index wrote:
It seems like SwapBuffer lag spikes are back on cutting edge version for some previous builds and current one
Random stuttering every 3-5 seconds, every 7-15 seconds after osu! reload.
AMD 8150, gtx 970, win 8.1
It's still intended, I guess.chong601 wrote:
Oh forgot to add that the fps value position changes when the chat console is up and the cursor enters and exits the chat interface.
Well, if you are saying that Stable has input lag, maybe you are using OpenGL renderer, playing with VSync, or on Windowed mode. Anyways, I think he knows that the new renderer is better, that's why osu! is moving to it.power007 wrote:
Hello peppy, a lot of people saying "Please don't push experimental build to stable". I would say - don't stop doing what you're doing! OpenGL consumes about 10% more of computer power (CPU, GPU) but its much more stable, fluent and lagless then DirectX. For example Experimental build does't have input lag on Windows 8 but Stable build - has.
No, I'm advanced player, monitoring cpu, gpu loads and temps. And I 100% sure I have same settings. Stable build has more input lag in full-screen and windowed mode as well. And writing here because I've seen peppy here, he is reading this thread time to time. Also mail is not coming from osu!dev Slack group do my email address.Trosk- wrote:
Well, if you are saying that Stable has input lag, maybe you are using OpenGL renderer, playing with VSync, or on Windowed mode. Anyways, I think he knows that the new renderer is better, that's why osu! is moving to it.
And well, I don't know if this is the correct place to make this comment, maybe you should have posted this in a comment on one of his blog entries, or even on the osu!dev Slack group instead.
Could you copy the crashlog and paste it here? (Click on the girl, on the "osu! crashed" window)DexFrild wrote:
Hello.
I have one problem with editor. I can't create a slider. osu! is crashing when I move cursor back.
<video>
I have the same issue, here's my crashlog:Trosk- wrote:
Could you copy the crashlog and paste it here? (Click on the girl, on the "osu! crashed" window)DexFrild wrote:
Hello.
I have one problem with editor. I can't create a slider. osu! is crashing when I move cursor back.
<video>
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at System.Collections.Generic.List`1.get_Item(Int32 index)
at #=q6IXhrC$mQfqPYwMdZUbZ80v$QJk$3_hzWIcM9yG19dsHQEGOYQ8ei$3dKjAyWhrh. ()
at #=qPJzNflyJ02VVE71K6$yal9RzSaC$JMDWIAHWianGGmpfNCbqwdBnfUKF86pa9Idv.#=qUwUBXun0rLqS$AtYWmL4Fw==()
at #=qnG0GnN0cfijcUy7s$dJDeA==.#=qKgl$DSIqV9WdWTn$1xM1xg==()
at #=qoQokdtSJzeBsSoydDXws1ficaov3lfUwWPe14F26hQA=.#=q9MMbY$7us5Q0U4_YmlFDRQ==()
at #=qoQokdtSJzeBsSoydDXws1ficaov3lfUwWPe14F26hQA=.#=qYUbnloU3IqqDE0EKW8De7Q==(Object #=q0uK$pwOmC9AVBz$8WoN2hA==, EventArgs #=qJRFYCsgJYpEglwbVHgcMng==)
at #=q0pqRh6sPtnAUog3K$vFn7WZ76Q57p3nFNWCTgRgm9GjHpjf6uVjPGnB9oAxEcX9D.#=ql8bzNZYeqTMI4oZPm9NAwQ==()
at #=q4lPYQR1rNVcvus2Dx1J7n25iMeU8CIEVC45pbj8UkQ6yA6bij2BSg34cbnz3VWt4.#=qN69kwiwUVTK0y9SzB87sq86EUPIQsgP7vr0Fq1jca24=(Object #=q0uK$pwOmC9AVBz$8WoN2hA==, EventArgs #=qJRFYCsgJYpEglwbVHgcMng==)
at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at #=q4lPYQR1rNVcvus2Dx1J7n25iMeU8CIEVC45pbj8UkQ6yA6bij2BSg34cbnz3VWt4.#=qGwPIz9JtU4MFtDodhpsbEg==()
at #=qoQokdtSJzeBsSoydDXws1ficaov3lfUwWPe14F26hQA=.#=qGwPIz9JtU4MFtDodhpsbEg==()
at #=qqI_cDBXyzvlJ1x5uw8DP0A==.#=qcCIVZO00d1r2WZ01ZOHTCQ==(String #=qiZE2W7LTDP0JO4nV4pZvcw==, Boolean #=qQ2zGyEw_tm9$D757SBvxHr3DGWTw85CS_cjU2cMHqC0=, Boolean #=qWbRzV5WeaDhc6rEEcGRD89d3BcOgr7$VVXHcz_rRbmI=, Boolean #=qI2qDyM$NOXO_8MDDFyYBZw==)
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at System.Collections.Generic.List`1.get_Item(Int32 index)
at #=q6IXhrC$mQfqPYwMdZUbZ80v$QJk$3_hzWIcM9yG19dsHQEGOYQ8ei$3dKjAyWhrh. ()
at #=qPJzNflyJ02VVE71K6$yal9RzSaC$JMDWIAHWianGGmpfNCbqwdBnfUKF86pa9Idv.#=qUwUBXun0rLqS$AtYWmL4Fw==()
at #=qnG0GnN0cfijcUy7s$dJDeA==.#=qKgl$DSIqV9WdWTn$1xM1xg==()
at #=qoQokdtSJzeBsSoydDXws1ficaov3lfUwWPe14F26hQA=.#=q9MMbY$7us5Q0U4_YmlFDRQ==()
at #=qoQokdtSJzeBsSoydDXws1ficaov3lfUwWPe14F26hQA=.#=qYUbnloU3IqqDE0EKW8De7Q==(Object #=q0uK$pwOmC9AVBz$8WoN2hA==, EventArgs #=qJRFYCsgJYpEglwbVHgcMng==)
at #=q0pqRh6sPtnAUog3K$vFn7WZ76Q57p3nFNWCTgRgm9GjHpjf6uVjPGnB9oAxEcX9D.#=ql8bzNZYeqTMI4oZPm9NAwQ==()
at #=q4lPYQR1rNVcvus2Dx1J7n25iMeU8CIEVC45pbj8UkQ6yA6bij2BSg34cbnz3VWt4.#=qN69kwiwUVTK0y9SzB87sq86EUPIQsgP7vr0Fq1jca24=(Object #=q0uK$pwOmC9AVBz$8WoN2hA==, EventArgs #=qJRFYCsgJYpEglwbVHgcMng==)
at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at #=q4lPYQR1rNVcvus2Dx1J7n25iMeU8CIEVC45pbj8UkQ6yA6bij2BSg34cbnz3VWt4.#=qGwPIz9JtU4MFtDodhpsbEg==()
at #=qoQokdtSJzeBsSoydDXws1ficaov3lfUwWPe14F26hQA=.#=qGwPIz9JtU4MFtDodhpsbEg==()
at #=qqI_cDBXyzvlJ1x5uw8DP0A==.#=qcCIVZO00d1r2WZ01ZOHTCQ==(String #=qiZE2W7LTDP0JO4nV4pZvcw==, Boolean #=qQ2zGyEw_tm9$D757SBvxHr3DGWTw85CS_cjU2cMHqC0=, Boolean #=qWbRzV5WeaDhc6rEEcGRD89d3BcOgr7$VVXHcz_rRbmI=, Boolean #=qI2qDyM$NOXO_8MDDFyYBZw==)
Please, add a spoilerbox to the Code.tuddster wrote:
I have the same issue, here's my crashlog: