I understand that, and as I said I like the feature, but it only works with windowed mode and not with letterboxing/fullscreen. The osu! circle shows up on the correct monitor pre-launch, but when the game actually launches it does so on the main monitor.Trosk- wrote: 6k5648
Well... That's not a bug at all. p/4264899Kon wrote: 711xp
I found a bug when playing with multiple monitors. When you launch the game in windowed mode it will launch osu! on whichever screen your mouse is on. However, when you launch osu! in fullscreen or letterboxing it launches on your main monitor. I like the way it works in windowed mode, because I personally play on my middle monitor but I use my left one as my main one, so I think that should stay but be compatible with letterboxing and even fullscreen.
Sorry for the double post, but I've noticed that sometimes star rating is not affected by hardrock at all
Pretty sure this is a duplicate,Default wrote: 2d276a
:cry: Sorry for the double post, but I've noticed that sometimes star rating is not affected by hardrock at all
This one has been happening rarely and randomly since years ago, including stable. Would be awesome if you'd find a semi-reliable way of triggering it.Trosk- wrote: 6k5648
Problem Details: Cursor trail expands if osu! has been minimized for a while. The longer you had osu! minimized, the longer this effect will last.
It doesn't happen always, I'm trying to figure out when it happens.
Posting this on CE thread because I couldn't replicate it on Stable.
Sorry if this is a duplicate, I didn't find anything about this. I don't think that anyone didn't noticed of this before tho, so, maybe it's a duplicate.
Didn't notice that this happens on Stable too, I think it didn't happen to me on it (or, at least, I didn't notice of it). Next time I get this effect I will try to think about what I did on that session to try to figure out what could trigger this problem...Tom94 wrote: 56z3w
This one has been happening rarely and randomly since years ago, including stable. Would be awesome if you'd find a semi-reliable way of triggering it.
How can you be not sure if this issue has been addressed? Did you not test? If so, please do so as soon as possible. If right now on cutting edge you get way lower FPS than stable with the same settings (this is important), then please post more information about your machine, such as which U, graphics chip and operating system you are using. Please also post the contents of gl_info.txt which should be in your osu! folder after running cutting edge once.abrian159 wrote: t616f
fps dropping too low during gameplay (around 200-400)
For taiko mode this is a huge issue, not sure about other modes.
On stable I usually get ~900fps on average (direct X)
I'm not sure if this issue has been addressed already but I will post here anyway.
I have reported the problem before directly in twitter. Anyway I will test again now to check.Tom94 wrote: 56z3w
How can you be not sure if this issue has been addressed? Did you not test? If so, please do so as soon as possible. If right now on cutting edge you get way lower FPS than stable with the same settings (this is important), then please post more information about your machine, such as which U, graphics chip and operating system you are using. Please also post the contents of gl_info.txt which should be in your osu! folder after running cutting edge once.
That I was replying to Tom as I was not sure if the problem is known.Trosk- wrote: 6k5648
Twitter? Twitter is not the correct place to report this... Just post it here.
You can change this on Nvidia's setting pannel haha though your method works too.Tom94 wrote: 56z3w
Yeah, osu! shouldn't run from your integrated graphics. Chances are your and your friend's results have cutting edge running on integrated while stable runs on discrete.
Could you switch to cutting edge again, then close osu!, then rename in your osu! folder "osu!.exe" to "bf3.exe"? This should fool NVIDIA optimus to run osu! from your discrete graphics card. Please let me know if it makes a difference.
And I already answered this, we can unfortunately not avoid doing this as long as the editor is using windows forms. This is something that will have to stay until osu!next along with its editor revamp comes along.A Mystery wrote: 14284t
I already posted this issue, but opening the editor (or just pressing "edit" to go to the song select) still causes the desktop resolution to change to whatever osu! is running at, causing this (and this is a full capture, everything you see on that image is everything I see on my monitor when alt-tabbing).
When letterboxing is enable, I can alt-tab normally though, but full screen has to be enabled.
The resolution used in the example is 1280x800, while my native is 1650x1080
Because I changed all my hardware yesterday, and this is still happening, I suppose my specs are not important.
Really? I don't think you ever said that though, but alright, sorry for postingTom94 wrote: 56z3w
And I already answered this, we can unfortunately not avoid doing this as long as the editor is using windows forms. This is something that will have to stay until osu!next along with its editor revamp comes along.A Mystery wrote: 14284t
I already posted this issue, but opening the editor (or just pressing "edit" to go to the song select) still causes the desktop resolution to change to whatever osu! is running at, causing this (and this is a full capture, everything you see on that image is everything I see on my monitor when alt-tabbing).
When letterboxing is enable, I can alt-tab normally though, but full screen has to be enabled.
The resolution used in the example is 1280x800, while my native is 1650x1080
Because I changed all my hardware yesterday, and this is still happening, I suppose my specs are not important.
Thanks a lot for testing. I'll see if I can get ahold of hardware capable of replicating the performance degradations you are experiencing. On my laptop with intel integrated graphics I get higher performance with opengl than with directx. :/abrian159 wrote: t616f
I get an average of 1400 fps with the GPU on stable
So this should have proven something..?
Hope the issue is being worked on
The fps drop maybe not seem a lot but its actually quite noticable during gameplay.
Slightly lower fps in cutting edge but not significant at allTom94 wrote: 56z3w
Thanks a lot for testing. I'll see if I can get ahold of hardware capable of replicating the performance degradations you are experiencing. On my laptop with intel integrated graphics I get higher performance with opengl than with directx. :/abrian159 wrote: t616f
I get an average of 1400 fps with the GPU on stable
So this should have proven something..?
Hope the issue is being worked on
The fps drop maybe not seem a lot but its actually quite noticable during gameplay.
Out of curiosity, how does cutting edge compare to stable when using the GPU?
The graphs suggest, that it's something external causing the frame spikes. SwapBuffers is openGLs function for displaying the next frame to the screen, which most programs which want those frames such as OBS simply hook. Thus it seems to me like OBS does some unnecessary and huge processing within its hooked SwapBuffers function. It'd be good to report this to the OBS guys so they can check whether it is something at their end.Piotrekol wrote: 5v4al
There seems to be an issuse with Letterboxing when recording using obs on intel HD4600.
when letterboxing is disabled recording works just fine (~600+fps with 1280x720) but when you enable letterboxing again - it just becomes unplayable.
same thing seems to happen in fullscreen and "windowed" letterbox
fullscreen letterboxing on:
http://i.imgur.com/GL5v7B3.png
fullscreen with no letterboxing:
https://osu-ppy-sh.tvgratuite.org/ss/3440689
windowed with letterboxing:
https://osu-ppy-sh.tvgratuite.org/ss/3440802
This happens on Stable too, so, this post doesn't belong here. You should have made a new thread._ Hatsune Miku wrote: 551y2t
Cutting-edge in mania ,trun on Co-op mods it can't see Star Difficulty
> Not on http://osu-ppy-sh.tvgratuite.org/ss/3443905
> On Co-op mods http://osu-ppy-sh.tvgratuite.org/ss/3443907
Jun 25, 2015I'm not entirely sure what that fix was for but in both Cutting Edge & Beta the replay speed modifier (that box at the right of the screen when viewing a replay.) is no longer correct.
[peppy] Fix replay playback speeds conflicting with each other. (fixes /t/259747)
Seems to be the lack of additive blending, which combines colors to approach white.ShyeartFanGirl wrote: 623e1y
Hi, I found a difference between DirectX and OpenGl while playing ctb, it's about glowing effect.
http://screenshotcomparison.com/comparison/136761
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: 4c6o4s
#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: 56z3w
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: 4c6o4s
#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: 711xp
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.
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: 5w2s1k
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: 6k5648
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: 5w2s1k
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
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: 1b5t3w
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 (U, 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 u, 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: 6k5648
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.
I have the same issue, here's my crashlog:Trosk- wrote: 6k5648
Could you copy the crashlog and paste it here? (Click on the girl, on the "osu! crashed" window)DexFrild wrote: 246v5y
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: 306bx
I have the same issue, here's my crashlog:
http://puu.sh/jpTHM/8e1ca525b1.oskpeppy wrote: 73101g
Include your full skin.
- DT - wrote: 1a1f3c
Problem Details:
If you toggle fast enough HT/DT at the start of a replay (before the animation ends), it'll cause the icon to look disabled, but the mod will still be active gameplay-wise. If you toggle it again, it will just double the effect of the mod.
Merged to CE thread.Trosk- wrote: 6k5648
Can replicate.
And well, I think you should have posted this on the Cutting Edge thread, since this feature is not on Stable yet.
, updated it
