Might be connected to hardware overheating / having a too high clock. Have you tried setting the framelimiter to something else than unlimited?
forum
[Archived] Issues with Latest Cutting-edge Build (Post Here)
posted
Total Posts
2,521
Issue(s) in this thread have been addressed by the following changes:
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
- Attempt to fix null reference during cursor trail draw. (Tom94)
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
Small issue with toggleable DT in replays, if I toggle DT off and switch it to 0.5x playback and back to 1x, the replay is playing with DT but DT isn't toggled.
Same happens to me. I think it's confirmed.Smc wrote:
Small issue with toggleable DT in replays, if I toggle DT off and switch it to 0.5x playback and back to 1x, the replay is playing with DT but DT isn't toggled.
Same thing with HTSmc wrote:
Small issue with toggleable DT in replays, if I toggle DT off and switch it to 0.5x playback and back to 1x, the replay is playing with DT but DT isn't toggled.
Not sure if there's anything that can be done about this on osu!'s end, but it's been going on for a while and doesn't happen in stable.
Probably related to p/4091418
Probably related to p/4091418
Crash upon closing Dxtory after osu! has been minimized to the tray for a long period of time.
Application: osu!.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 62E5416C
Faulting application name: osu!.exe, version: 1.3.3.7, time stamp: 0x5589b04b
Faulting module name: OPENGL32.DLL, version: 6.1.7600.16385, time stamp: 0x4a5bdadb
Exception code: 0xc0000005
Fault offset: 0x0000416c
Faulting process id: 0x4ac
Faulting application start time: 0x01d0ae3f541d384d
Faulting application path: D:\Games\Osu!\osu!.exe
Faulting module path: C:\Windows\system32\OPENGL32.DLL
Report Id: b74daa59-1a62-11e5-96ba-6c626d45738a
?- watch a replay (or use auto)
- (at any moment) then press [5] (or [7] or [8] or [9] ([6] and [0] won't work because it plays at x1...)
- then quickly press [esc] (or some key to leave the replay)...
- voila, music playing at the speed of fastforward.
After a second or two... it fixes itself upon changing beatmaps. NOT leaving to menu.
Issue(s) in this thread have been addressed by the following changes:
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
- Fix replay playback speeds conflicting with each other. (peppy)
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
Topic Starter
Audio rate changing via number keys is still experimental. Don't expect it to work right.123MegaApple123 wrote:
:idea: ?
- watch a replay (or use auto)
- (at any moment) then press [5] (or [7] or [8] or [9] ([6] and [0] won't work because it plays at x1...)
- then quickly press [esc] (or some key to leave the replay)...
- voila, music playing at the speed of fastforward.
It could be stuck in this state even upon changing beatmaps, if your quick enough to press [left] or [right]
After a second or two... it fixes itself upon changing beatmaps. NOT leaving to menu.
More of a very minor imperfection but the default 'back' button aswell as the 'yellow warning bar' go 1 pixel too far out of the screen area.
Only visible when using letterboxing.
Only visible when using letterboxing.
What resolution are you using? Doesn't happen for me on 1440x900 (Maybe it has been fixed already)VeilStar wrote:
More of a very minor imperfection but the default 'back' button aswell as the 'yellow warning bar' go 1 pixel too far out of the screen area.
Only visible when using letterboxing.
VeilStar wrote:
Trosk- wrote:
What resolution are you using?
Nvm... It's still happening.
Problem Details:
It might be a bug but if you load a map and press esc instant when you started loading your status bar will disappear
osu! version: 20150626.1cuttingedge
It might be a bug but if you load a map and press esc instant when you started loading your status bar will disappear
osu! version: 20150626.1cuttingedge
Ok, this is an actual bug. I guess it's confirmed. Since it is a Cutting Edge bug problem, you should have posted it here. Please take care of that next time. Don't repost it since a Mod can merge it to the other thread, I guess.
Maeglwn
not sure if this is confirmed already, but when clicking on the ignore list and highlight list box, it doesn't interact like a normal text box; the text line will start at where the last word ended regardless of where you click on in the text box
there's also no flashy line thing that tells you where your typing begins anymore either
there's also no flashy line thing that tells you where your typing begins anymore either
Topic Starter
Text boxes have never allowed you to seek to a specific part of the text.
Maeglwn
Topic Starter
I just checked stable release and it has the same behaviour as cutting edge. How long ago were you able to do this?
Testing Tag Coop with Veilstar, and when you pick a Tag colour and start the match, my client full out crashes while Veil's starts to incorrectly render sliders. Making them white. As shown
Tested with default skin and my skin on my client. Always crashes unless I leave the Tag Color as Defualt.
Tested with default skin and my skin on my client. Always crashes unless I leave the Tag Color as Defualt.
Problem Details:
If I'm in fullscreen and I open up my friends with f9 my cursor dissapears.
osu! version: b20150627.3cuttingedge
If I'm in fullscreen and I open up my friends with f9 my cursor dissapears.
osu! version: b20150627.3cuttingedge
When you open the user list, the skin cursor is replaced by the Windows Cursor. It should show up.321jurgen wrote:
Problem Details:
If I'm in fullscreen and I open up my friends with f9 my cursor dissapears.
osu! version: b20150627.3cuttingedge
Do you happen to have set the Windows cursor trail to -1? That's what caused it when the same happened to me some months ago.321jurgen wrote:
Problem Details:
If I'm in fullscreen and I open up my friends with f9 my cursor dissapears.
(Setting your cursor trail to to -1 prevents f.lux from making your cursor blue, in case anyone is wondering.)
Yes I do. That's probably the problem. I guess I'll just have to get used to not having a cursor than xDPampel wrote:
Do you happen to have set the Windows cursor trail to -1? That's what caused it when the same happened to some months ago.321jurgen wrote:
Problem Details:
If I'm in fullscreen and I open up my friends with f9 my cursor dissapears.
(Setting your cursor trail to to -1 prevents f.lux from making your cursor blue, in case anyone is wondering.)
Problem Details:
2 Problems,
If you make a screenshot with F12+Shift (Upload) than you are not getting a picture but a empty space (In chrome) and in my waterfox it is saying that it is making errors
The Changelog menu was or is bugged.
Video or screenshot showing the problem:
http://puu.sh/iFAId/7707cdecd1.jpg
osu! version: 20150628.1cuttingedge
2 Problems,
If you make a screenshot with F12+Shift (Upload) than you are not getting a picture but a empty space (In chrome) and in my waterfox it is saying that it is making errors
The Changelog menu was or is bugged.
Video or screenshot showing the problem:
http://puu.sh/iFAId/7707cdecd1.jpg
osu! version: 20150628.1cuttingedge
Well yeah. It's listed in the OP for a reason.Shizuyi wrote:
I still have this issue.
So I found a bug and was able to reproduce ~15 times it until I restarted osu.
As you can see in this screenshot, the "Online Users" button is visible.
And that's how I replicated it:
1. open the "Online Users" screen(doesn't matter if you do it in the main menu or with a key.)
2. close it with the "Hide Chat"(!!!) button.
3. go into song select and type something to filter your beatmaps
4. press backspace and hold it down until the text is gone and "Online Users" appears. (It takes ~0.1 seconds after you deleted all the text.)
Can someone of you guys reproduce it?
Edit: I reproduced it again but this time I didn't have to use "Hide Chat".
As you can see in this screenshot, the "Online Users" button is visible.
And that's how I replicated it:
1. open the "Online Users" screen(doesn't matter if you do it in the main menu or with a key.)
2. close it with the "Hide Chat"(!!!) button.
3. go into song select and type something to filter your beatmaps
4. press backspace and hold it down until the text is gone and "Online Users" appears. (It takes ~0.1 seconds after you deleted all the text.)
Can someone of you guys reproduce it?
Edit: I reproduced it again but this time I didn't have to use "Hide Chat".
I can't... I don't know if I'm doing something wrong, but I followed your steps and I didn't get it.hadis1000 wrote:
Can someone of you guys reproduce it?
Edit: I reproduced it again but this time I didn't have to use "Hide Chat".
Hi.
On latest cutting edge, osu! is making invalid GL API calls with glScissor by giving it a negative height.
Here is an apitrace of this issue, it happens when gameplay starts: https://idontevenlift.no-ip.org/osu!.trace
Here is an example error.
2252305: message: major api error 2: GL_INVALID_VALUE in glScissor
2252305 @0 glScissor(x = 0, y = 0, width = 185, height = -266)
2252305: warning: glGetError(glScissor) = GL_INVALID_VALUE
Thanks,
sarnex
On latest cutting edge, osu! is making invalid GL API calls with glScissor by giving it a negative height.
Here is an apitrace of this issue, it happens when gameplay starts: https://idontevenlift.no-ip.org/osu!.trace
Here is an example error.
2252305: message: major api error 2: GL_INVALID_VALUE in glScissor
2252305 @0 glScissor(x = 0, y = 0, width = 185, height = -266)
2252305: warning: glGetError(glScissor) = GL_INVALID_VALUE
Thanks,
sarnex
Not that one, it was all bold and the text was bigger than the change log screen, so it went out of the box D:VeilStar wrote:
Do you mean this? p/4121624
Maeglwn
Seems like the CE Build's Recent Changes log is broken.
I believe that this has been reported before.Sulker wrote:
Seems like the CE Build's Recent Changes log is broken.
I guess it has problems with some resolutions, mine are showing, but as you can see, some text are clipped. Using 1440x900 in my case.
Yeah I can guess seeing when I turned Letterboxing on, it showed
(stupid video)
Reproduce:
Press your quick-retry bind and alt-tab while the command attempts to retry.
My quick-bind key is ` if that is ever useful.
Cutting-edge mode.
This happened to me the other day but didn't posted it because I don't know how to replicate it, but now it's the second time I get this, so I decided to post it. I have searched for cases like this and didn't find anything. I'm sorry if this is already known.
Like you can see, the user box in the bottom gets stuck on grey, like if you were selecting it (even though that box should be in grey even if you click it)
Going back to main menu fix this problem.
And like I said earlier I don't know how to replicate this yet, I will edit the post if I find a way.
Like you can see, the user box in the bottom gets stuck on grey, like if you were selecting it (even though that box should be in grey even if you click it)
Going back to main menu fix this problem.
And like I said earlier I don't know how to replicate this yet, I will edit the post if I find a way.
Quiesce wrote:
wrong forum... man. could a mod move?
Merged to the Cutting-edge thread. Anyhow, I can replicate this. And happened to break shit while doing so.abraker wrote:
This actually belongs in the cutting-edge thread. While we are waiting for a mod...
It's a known issue. Though I couldn't find the thread (queue the thread hunt), I did find a reference to the bug in this post: p/4154055
Edit: Removed both of your posts to avoid clutter.
Problem Details:
When spectating someone or watching a replay.
If you try to disable flashlight it gives an error and sometimes crashes.
osu! version: 20150629cuttingedge
When spectating someone or watching a replay.
If you try to disable flashlight it gives an error and sometimes crashes.
osu! version: 20150629cuttingedge
You should have posted this problem here, since it's a Cutting Edge issue.
Anyways, I can confirm it...
Also, here you have the crashlog:
Anyways, I can confirm it...
Also, here you have the crashlog:
Crashlog
System.NullReferenceException: Object reference not set to an instance of an object.
at #=qLFuGputbYSQmwedYaJJnalJm9HfsdbNgjxXT6kIn7IQ=.#=qfl5RmK3A6Wk6zO6hbz11Sw==(Mods #=qzQ9j9fl9Sc8R4I164TJ4NQ==, Boolean #=qK6wjgo_9TwM7yRn8h0EJ$A==)
at #=qLFuGputbYSQmwedYaJJnalJm9HfsdbNgjxXT6kIn7IQ=.#=qBmsnlBI32HJdIV$QFLlDqTT1yhLW_xZs9VnPU66iOe0=(Object #=q2Ow7utZIrbWEryWWIoH94w==, EventArgs #=qOPThJU0JyoMa0ImdyQjt0g==)
at #=qr781z3M3XbyAlCgMRh43TDow8rmt6HioC$_Y9dq904Y=.#=qH82$iT_Xlsw7nbg2Vum7_Q==(Boolean #=qgkrbx$UlOEnU3dLPaYNQUw==)
at #=qRhWXkoaAa6UaK1U77ADPk5eOggukLrMtrDt437BLqqR1lm8N84v99MgmWV4VFnev.#=qrmLHD5vu96uKd$cFqirCRw==(Boolean #=q1cLxfDLzcEyQvVCvQ3Dd3A==)
at #=qRhWXkoaAa6UaK1U77ADPk5eOggukLrMtrDt437BLqqR1lm8N84v99MgmWV4VFnev.#=qtjx4wYM8vNcSnysK5StwAg==(Boolean #=q1cLxfDLzcEyQvVCvQ3Dd3A==)
at #=qjhZLct62Uj_NbuVGi3Bhmljwv5V9J0VFpkWYe3oew27zUtwJn6tLel
I can confirm. Merging this to the cuttingedge thread.Nakuyoko wrote:
Problem Details:
When spectating someone or watching a replay.
If you try to disable flashlight it gives an error and sometimes crashes.
Crash Log
System.NullReferenceException: Object reference not set to an instance of an object.
at #=qLFuGputbYSQmwedYaJJnalJm9HfsdbNgjxXT6kIn7IQ=.#=qfl5RmK3A6Wk6zO6hbz11Sw==(Mods #=qzQ9j9fl9Sc8R4I164TJ4NQ==, Boolean #=qK6wjgo_9TwM7yRn8h0EJ$A==)
at #=qLFuGputbYSQmwedYaJJnalJm9HfsdbNgjxXT6kIn7IQ=.#=qBmsnlBI32HJdIV$QFLlDqTT1yhLW_xZs9VnPU66iOe0=(Object #=q2Ow7utZIrbWEryWWIoH94w==, EventArgs #=qOPThJU0JyoMa0ImdyQjt0g==)
at #=qr781z3M3XbyAlCgMRh43TDow8rmt6HioC$_Y9dq904Y=.#=qH82$iT_Xlsw7nbg2Vum7_Q==(Boolean #=qgkrbx$UlOEnU3dLPaYNQUw==)
at #=qRhWXkoaAa6UaK1U77ADPk5eOggukLrMtrDt437BLqqR1lm8N84v99MgmWV4VFnev.#=qrmLHD5vu96uKd$cFqirCRw==(Boolean #=q1cLxfDLzcEyQvVCvQ3Dd3A==)
at #=qRhWXkoaAa6UaK1U77ADPk5eOggukLrMtrDt437BLqqR1lm8N84v99MgmWV4VFnev.#=qtjx4wYM8vNcSnysK5StwAg==(Boolean #=q1cLxfDLzcEyQvVCvQ3Dd3A==)
at #=qjhZLct62Uj_NbuVGi3Bhmljwv5V9J0VFpkWYe3oew27zUtwJn6tLel9dOpV4809t.#=q5KW2roBYFpDnDeU8QThHIA==()
at #=qFjMzMyi1I6cfwlne_vL1Nemv5VhDutDCSPLfvQrPWJ0=.#=qwIGAIxoeGPza9K0LnzTtbg==()
at #=qnHMLssbxnNT8sO1i8w3fyQ==.#=qDLVzK5WgwVLVkLZmsZTU9Q==()
at #=qQGSxkm0tmtudPZtHfo9TRV7T2wr0l3p4zbg5da7g8Jk=.#=qu_EDTrq$a_y3Bh5WmnT4Eg==()
at #=qQGSxkm0tmtudPZtHfo9TRV7T2wr0l3p4zbg5da7g8Jk=.#=qDP7Wx6xBRC6wHQmJMVuDLw==(Object #=q2Ow7utZIrbWEryWWIoH94w==, EventArgs #=qOPThJU0JyoMa0ImdyQjt0g==)
at #=qiyZwM8I7_od8KWN5Zf3Ll1ajQ8QGobLRUDWdX_Pp_6ZdfhPH4OKTubtBC$nuf23O.#=qSNilTujZCINytPupT$dAVQ==()
at #=qJnV_tesk6Iql0m1jAPgNz0mvFL4gMzu3T8awB0qWsyJsQTSY3AbcZ1Kmur86ujXe.#=qJCtg8qhsRU3CYTFlNYSFbERBGQMRcksjKAPGUlzFZME=(Object #=q2Ow7utZIrbWEryWWIoH94w==, EventArgs #=qOPThJU0JyoMa0ImdyQjt0g==)
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 #=qJnV_tesk6Iql0m1jAPgNz0mvFL4gMzu3T8awB0qWsyJsQTSY3AbcZ1Kmur86ujXe.#=qBY9CKqUKssueoUv_EtvQtA==()
at #=qQGSxkm0tmtudPZtHfo9TRV7T2wr0l3p4zbg5da7g8Jk=.#=qBY9CKqUKssueoUv_EtvQtA==()
at #=qNMwT6UVNL4T_ENPh4ns1dw==.#=qGewpYOgH9uxfvkvP4bz0Fg==(String #=qENUoYZvnNeOEbTtC_URf7A==, Boolean #=qmL4HFGf9l1uChEJl_hN6bDqoUEvMgGBtrkcnFEyoJ3g=, Boolean #=qnR$EZ2JtToNpSzzpoxVErhPEOaHzveTpk5wBmq$36NA=, Boolean #=qZjiItrxz$3PEmJ8lpniybA==)
Well, when I was trying to replicate the Mania Flashlight crash in another game modes I noticed of this:
When you are on Spectator/Auto on Taiko and you disable the FL, the playfield is clipped (also, it isn't 100% disabled, you can see shadows (on all game modes)):
Original (without FL):
With FL disabled:
Also, the same "Shadow" appears on CTB:
And well, also happens for Standard:
I don't know if this is intended behaviour or not, if it is, I'm sorry for this post..
When you are on Spectator/Auto on Taiko and you disable the FL, the playfield is clipped (also, it isn't 100% disabled, you can see shadows (on all game modes)):
Original (without FL):
With FL disabled:
Also, the same "Shadow" appears on CTB:
And well, also happens for Standard:
I don't know if this is intended behaviour or not, if it is, I'm sorry for this post..
That's intended.Trosk- wrote:
Well, when I was trying to replicate the Mania Flashlight crash in another game modes I noticed of this:
<wall of screenshots & text>
I don't know if this is intended behaviour or not, if it is, I'm sorry for this post..
Issue(s) in this thread have been addressed by the following changes:
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
- Fix null ref when toggling flashlight mod. (TheVileOne)
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
If you (accidentally) hit "leave match" as the screen is fading out to start the match, you can end up "waiting for players" and "quit" simultaneously in a multiplayer game.
Not sure if anyone else is having the issue, but in cutting edge sometimes the "Auto" mod will automatically be selected as I find myself starting maps without mods but suddenly it's playing on "Auto".
Well, does it happen only in Cutting Edge? Make sure that you are not pressing your Ctrl key when you start a map.boysonicrevived wrote:
Not sure if anyone else is having the issue, but in cutting edge sometimes the "Auto" mod will automatically be selected as I find myself starting maps without mods but suddenly it's playing on "Auto".
Well, this hasn't much importance and I'm not sure if this was posted earlier or it's a known "issue", but I didn't find anythig about this. I'm sorry if this is a duplicate or it is already known.
It's just, when you place your cursor on the left side of the "Now Playing" buttons on the main menu, they get stuck, like if you were placing it over the button and removing it instatly. (Doesn't happen with the Play and Stop buttons.)
Also, I noticed that this only happens on resolutions that are not 16:9. On my case I tried on various resolutions, getting this result only in 16:10 and 4:3 resolutions.
This video is recorded on 1440x900 (16:10)
Release streams: This happens on Beta and Cutting Edge, but not in Stable.
It's just, when you place your cursor on the left side of the "Now Playing" buttons on the main menu, they get stuck, like if you were placing it over the button and removing it instatly. (Doesn't happen with the Play and Stop buttons.)
Also, I noticed that this only happens on resolutions that are not 16:9. On my case I tried on various resolutions, getting this result only in 16:10 and 4:3 resolutions.
This video is recorded on 1440x900 (16:10)
Release streams: This happens on Beta and Cutting Edge, but not in Stable.
Dragging a new menu background to the osu! main menu makes the cursor change to a white box.
Hotfix is a skin refresh (ctrl + alt + shift + s).
Version: b20150702cuttingedge
Hotfix is a skin refresh (ctrl + alt + shift + s).
Version: b20150702cuttingedge
Cutting edge b20150702
i found two bug:
1. https://osu.ppy.sh/ss/3334457
2.If osu selecting a song what is outside range of star filter then i click to osu! button it's disappear.
i found two bug:
1. https://osu.ppy.sh/ss/3334457
2.If osu selecting a song what is outside range of star filter then i click to osu! button it's disappear.
Thanks for reporting but you posted it in the wrong thread, so I merged your post to the appropriate thread.Sensou Shin wrote:
Cutting edge b20150702
i found two bug:
1. https://osu.ppy.sh/ss/3334457
2.If osu selecting a song what is outside range of star filter then i click to osu! button it's disappear.
I can replicate 2. - To elaborate a bit: the "range of star filter" is the one in the options menu. If you select say a 5 star map, then go to the options menu and set it to display beatmaps upto 3 stars and click the osu! button in the corner it will expand and dissapear.
Could you tell us how to replicate the first one though?
Still kinda experiencing lower-than-usual FPS on osu!cuttingedge compared to osu!stable.
Worst affected on maps with heavy SB, song select and maps with videos
I am using i3-3110M and Intel HD 4000.
EDIT: I do use a slightly older Intel GPU driver because of issues with the GPU driver keeps disabling the laptop onboard sound
Worst affected on maps with heavy SB, song select and maps with videos
I am using i3-3110M and Intel HD 4000.
EDIT: I do use a slightly older Intel GPU driver because of issues with the GPU driver keeps disabling the laptop onboard sound
Also, on the bug that Sensou Shin said, both rankings and the Beatmap status are not shown. I guess it's like osu! doesn't recognize the map at all when the filters are activated and that map doesn't need to be shown.
Also, if you wait for the song that you have selected (the one what is out of range of the filters) to end, another song will play, and this one is gonna allow you to play it, even if it's not on the Beatmap panels. (the osu! logo starts to go at the BPM rhythm and the rankings are shown.) If you change the Grouping when this song is being played is gonna bug again, but this one will replay, not like the other one.
I hope I have not explained it too badly...
Also, if you wait for the song that you have selected (the one what is out of range of the filters) to end, another song will play, and this one is gonna allow you to play it, even if it's not on the Beatmap panels. (the osu! logo starts to go at the BPM rhythm and the rankings are shown.) If you change the Grouping when this song is being played is gonna bug again, but this one will replay, not like the other one.
I hope I have not explained it too badly...
Sorry but i can't. It was a suprise to me :SVeilStar wrote:
Thanks for reporting but you posted it in the wrong thread, so I merged your post to the appropriate thread.Sensou Shin wrote:
Cutting edge b20150702
i found two bug:
1. https://osu.ppy.sh/ss/3334457
2.If osu selecting a song what is outside range of star filter then i click to osu! button it's disappear.
I can replicate 2. - To elaborate a bit: the "range of star filter" is the one in the options menu. If you select say a 5 star map, then go to the options menu and set it to display beatmaps upto 3 stars and click the osu! button in the corner it will expand and dissapear.
Could you tell us how to replicate the first one though?
Issue(s) in this thread have been addressed by the following changes:
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
- Ensure non-negative scissor rectangle. (smoogipooo)
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
Issue(s) in this thread have been addressed by the following changes:
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
- Don't allow the current beatmap to be set to none. (Tom94)
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
Just linking a post since it has been almost a month. Seriously, I have to default to stable because if this. Any map greater than around 4 stars ischong601 wrote:
Still kinda experiencing lower-than-usual FPS on osu!cuttingedge compared to osu!stable.
Worst affected on maps with heavy SB, song select and maps with videos
I am using i3-3110M and Intel HD 4000.
EDIT: I do use a slightly older Intel GPU driver because of issues with the GPU driver keeps disabling the laptop onboard sound
Alignments of mod icons are different when Auto is enabled
without Auto enabled
with Auto enabled
without Auto enabled
with Auto enabled
Click on the mods, and you'll see why this is this way
HT/DT/NC/FL are clickable
HT/DT/NC/FL are clickable
It's basicaly because of this (Auto is counted as a replay):OsuMe65 wrote:
Alignments of mod icons are different when Auto is enabled
<images>
Please check whether you can still get your cursor to corrupt when changing the background in the main menu. Also please check for other visual bugs and performance during gameplay. Could have dramatically improved. 
Seems like the cursor problem when changing backgrounds is fixed. (Fun fact: First try I was a bit scared because it happened again but I was on Beta, I'm dumb)Tom94 wrote:
Please check whether you can still get your cursor to corrupt when changing the background in the main menu. Also please check for other visual bugs and performance during gameplay. Could have dramatically improved.
Also I just checked the performance during gameplay and seems really similar to Beta, at least for me.
Forgot to read the logs. At least that one solved my own problem.Trosk- wrote:
Issue(s) in this thread have been addressed by the following changes:
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
- Fix frame time display causing errors under rare circumstances. (Tom94)
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
I have 2 monitors, monitor one is 1920x1080 (where I play osu!) and monitor two is 1280x1024. If I'm on FullScreen mode (on Monitor 1) and change to a resolution that is lower than the Monitor 2, it will detect the second monitor resolution as native (even if I am on monitor 1). I need to exit FullScreen mode and activate it again to have the Monitor 1 options available again.
Also, when I changed my resolution back to 1920x1080 (native) and I change to Windowed mode, it will hide the window borders and show it as "Custom" reolution. (Like on Tourney client windows, for example.)
This doesn't happen on Stable, only in Beta and CE.
Also, when I changed my resolution back to 1920x1080 (native) and I change to Windowed mode, it will hide the window borders and show it as "Custom" reolution. (Like on Tourney client windows, for example.)
This doesn't happen on Stable, only in Beta and CE.
Which of the 2 monitors is set as your primary monitor?
Issue(s) in this thread have been addressed by the following changes:
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
- Attempt to fix multiple screens causing issues with detected desktop resolutions. (Tom94)
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
The 1920x1080 one.Tom94 wrote:
Which of the 2 monitors is set as your primary monitor?
And with this last update (b20150708cuttingedge) seems like it's fixed, at least for me.
DeletedUser_4329079
Well.. What resolution are you using? I can't replicate any of these this you say. Tried on various resolutions and enabling/disabling FullScreen. (with FullScreen disabled, it is normal to see the cursor, just in case.)Default wrote:
With letterboxing enabled, the cursor will split from its trail iof you move it to the top of the screen.
If you move it to the bottom, you can see the desktop's cursor.
Going to the editor changes my desktop resolution to the osu! one (because the editor is not full screen). It restores after leaving the windowed song select (coming from the editor)
Some things like the numbers inside the circles will appear larger and different font (?) in the editor, as if I'm playing at a very low resolution. The editor also looks blurry (but that's normal with a lower resolution, it just looks more blurry than when not in the editor while still playing at 1280x800)
Also, I can't find the post back (it's somewhere in this thread), but the issue of things like closing an application and the resolution randomly changing to the osu! one after that is still occuring.
Some screenshots
Editor
Editor testing mode
Grid does not appear in the timing tab, not sure if this is intended. But as you can see, things like "timing setup panel" look very blurry, but I'm not sure if this is normal in windowed mode compared to full screen (both same resolutions)
Some things like the numbers inside the circles will appear larger and different font (?) in the editor, as if I'm playing at a very low resolution. The editor also looks blurry (but that's normal with a lower resolution, it just looks more blurry than when not in the editor while still playing at 1280x800)
Also, I can't find the post back (it's somewhere in this thread), but the issue of things like closing an application and the resolution randomly changing to the osu! one after that is still occuring.
Some screenshots
Editor
Editor testing mode
Grid does not appear in the timing tab, not sure if this is intended. But as you can see, things like "timing setup panel" look very blurry, but I'm not sure if this is normal in windowed mode compared to full screen (both same resolutions)
DeletedUser_4329079
Fullscreen is enabled, 1180x617. I can upload a video if necessary.Trosk- wrote:
Well.. What resolution are you using? I can't replicate any of these this you say. Tried on various resolutions and enabling/disabling FullScreen. (with FullScreen disabled, it is normal to see the cursor, just in case.)Default wrote:
With letterboxing enabled, the cursor will split from its trail iof you move it to the top of the screen.
If you move it to the bottom, you can see the desktop's cursor.
You could have said before you are using a custo resolution ;_;Default wrote:
Fullscreen is enabled, 1180x617. I can upload a video if necessary.
Seems like this issue only appears when using a Custom Resolution
I can get this effect too.
Edit: Seems like this only happens with some Custom resolutions, not all, I'm trying to figure out the reason... It's not because the aspect ratio because I tried to increase the resolution with the same aspect ratio and it doesnt happen anymore.
Edit 2: Well, I have been trying some resolutions for a long time, and I only got this result or issue with "HeightFullscreen = 617" (tried with so many different heights, and I only got this with 617, not even with 616 or 618), so, I don't know if it's because of that number in particular, but seems like it...
Issue(s) in this thread have been addressed by the following changes:
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
- Fix inconsistency with minimization behavior while in the editor and in non-native fullscreen. (Tom94)
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
Cutting edge OpenGL is just too heavy on cpu. I get half the fps ingame, 40-50 GL vs 80-90 DX. It is just limited by my cpu, on DX I get gpu utilization of 40% vs 20% on GL ingame.
The time plot of draw step is helpful, found out normal skins animation are too (cpu?) heavy, GL calls too heavy? Is vertex data even being buffered? Look at the comparison. Normal skin while playing is 40-50 fps, other skins are 70-80 fps.
osu skin vs other skin https://jii.moe/EJwEMS8u.png
effects kill the cpu https://jii.moe/4kw4zrU_.png
Have you looked on soft pagefaults? It is hitting too many here. Normally pagefaults are the main cause of stutter. DX osu hits 5 playing a replay
(video showing page faults per refresh DX) https://jii.moe/4yBIqrLd.mp4
but open GL hits 250 playing the same replay... what cpu cache do you guys have to not notice the stutter
(video showing page faults per refresh GL) https://jii.moe/NJzIcSId.mp4
Looks like I cannot move to the new version on my old laptop. I tried cutting on everything that consumes cpu on windows and it isn't enough. Maybe the new version is more gpu efficient but there is no point in that if the gpu doesn't even need to turbo because cpu is such bottleneck.
The time plot of draw step is helpful, found out normal skins animation are too (cpu?) heavy, GL calls too heavy? Is vertex data even being buffered? Look at the comparison. Normal skin while playing is 40-50 fps, other skins are 70-80 fps.
osu skin vs other skin https://jii.moe/EJwEMS8u.png
effects kill the cpu https://jii.moe/4kw4zrU_.png
Have you looked on soft pagefaults? It is hitting too many here. Normally pagefaults are the main cause of stutter. DX osu hits 5 playing a replay
(video showing page faults per refresh DX) https://jii.moe/4yBIqrLd.mp4
but open GL hits 250 playing the same replay... what cpu cache do you guys have to not notice the stutter
(video showing page faults per refresh GL) https://jii.moe/NJzIcSId.mp4
Looks like I cannot move to the new version on my old laptop. I tried cutting on everything that consumes cpu on windows and it isn't enough. Maybe the new version is more gpu efficient but there is no point in that if the gpu doesn't even need to turbo because cpu is such bottleneck.
Page faults don't have anything to do with CPU cache but with your RAM. https://en.wikipedia.org/wiki/Page_fault I'd be curious what kind of results you'd get if you'd set your virtual memory's size to 0 (assuming you can close enough background applications for RAM size not to become an issue).
Yes, not all vertex data is buffered. The difference between the default skin and custom skins you are noticing are the small, blue, particles appearing with every hit. We do plan on buffering these. We are currently rewriting a huge portion of the rendering infrastructure to allow for easier optimizations like that in the future.
What kind of CPU do you have? I haven't heard of anyone where the CPU would be the bottleneck. Even without vertex buffering osu! just doesn't have many vertices in the first place. I am baffled that you are getting CPU capped at all.
Yes, not all vertex data is buffered. The difference between the default skin and custom skins you are noticing are the small, blue, particles appearing with every hit. We do plan on buffering these. We are currently rewriting a huge portion of the rendering infrastructure to allow for easier optimizations like that in the future.
What kind of CPU do you have? I haven't heard of anyone where the CPU would be the bottleneck. Even without vertex buffering osu! just doesn't have many vertices in the first place. I am baffled that you are getting CPU capped at all.
Windows task manager counts soft ones too. Yes they are orders of magnitude faster than hard ones but they affect or are symptoms of cpu performance problems. I went to my barebones windows profile to test it with the lowest ram utilization (no shitty windows services or background tasks), didn't get any hard fault ingame. Normally with nothing on the background windows copies everything that is needed to the RAM.Tom94 wrote:
Page faults don't have anything to do with CPU cache but with your RAM. https://en.wikipedia.org/wiki/Page_fault I'd be curious what kind of results you'd get if you'd set your virtual memory's size to 0 (assuming you can close enough background applications for RAM size not to become an issue).
The cpu is a celeron m from 2008~
I realized, if I play on cutting edge I get frame drops over and over again. I play, framerate is fine at 800 or something and then suddenly it drops really low for just one second, then it's normal again, then it drops again... It seems like it's happening especially if I play doubletime. My computer is old, but i never had this on stable version.
When selecting a different release stream (such as beta) and then selecting another release stream (such as stable) the game crashes, downloads some files, and then puts you on the release stream you were on before. I think I've posted this before but I can't (be arsed to) find it right now.
once I tried changing back to stabe (as a test) Osu! won't go back to stable but to let you know Osu cutting edge is pretty nice
What happens if you switch to full-screen? Looks like one of your cards is being used for windows-level rendering, while the other is being used by the game?
Same deal. Just more usage of both GPU's. Also this problem is not related to the OpenGL or DirectX and has existed since the beginning of time ... Osu! can not decide which GPU to use. On the GPU, which is weaker than 740m - 1000 fps, and 740m - 500 fps. I think just because of that. Btw, if you're using integrated video, usage of discrete video obvious is - 0, and with intergrated video I got 500-900 fps, while with 740m only 500 max.peppy wrote:
What happens if you switch to full-screen? Looks like one of your cards is being used for windows-level rendering, while the other is being used by the game?
Does your screen flicker black when enabling and disabling fullscreen?
Yes. I'm 100% sure that full screen mode changes nothing in terms of using both GPUs. Only fps drops from 500+ to 300+Tom94 wrote:
Does your screen flicker black when enabling and disabling fullscreen?
DeletedUser_4329079
It's true, what was the chance of me using just that resolution thoTrosk- wrote:
Edit 2: Well, I have been trying some resolutions for a long time, and I only got this result or issue with "HeightFullscreen = 617" (tried with so many different heights, and I only got this with 617, not even with 616 or 618), so, I don't know if it's because of that number in particular, but seems like it...
Did you already try enforcing your dedicated GPU in the nvidia control panel? Here is a video explaining exactly how to do it:power007 wrote:
Yes. I'm 100% sure that full screen mode changes nothing in terms of using both GPUs. Only fps drops from 500+ to 300+Tom94 wrote:
Does your screen flicker black when enabling and disabling fullscreen?
Yes I've tried. Identical behavior of osu!. For example Borderland 2 using 7-10% of Intel GPU and 99% of NVidia GPU.Tom94 wrote:
Did you already try enforcing your dedicated GPU in the nvidia control panel?
DeletedUser_4329079
While on cutting edge (or beta) I can't alt-tab out of the game. It seems as if I actually do switch to another window, when i do so, but the image from osu persists and prevents me from seeing the other window i've switched too. The problem exists both when in fullscreen, or borderless
It seems the problem is only there, when I use my max resolution (1600x900), or have letterboxing activated.
My computer is a laptop, ASUS N76VJ, with windows 8.1, And here's the specs I could find about my computer
It seems the problem is only there, when I use my max resolution (1600x900), or have letterboxing activated.
My computer is a laptop, ASUS N76VJ, with windows 8.1, And here's the specs I could find about my computer
Issue(s) in this thread have been addressed by the following changes:
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
- Never minimize osu! while in the editor due to issues with child forms. (Tom94)
- Fix viewport being 1 pixel off while in forced non-exclusive fullscreen mode. (Tom94)
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
Just found out that the framedrops are gone if I restart osu!. But they are cooming back after 10-20 minutes playtimeDrayyne wrote:
I realized, if I play on cutting edge I get frame drops over and over again. I play, framerate is fine at 800 or something and then suddenly it drops really low for just one second, then it's normal again, then it drops again... It seems like it's happening especially if I play doubletime. My computer is old, but i never had this on stable version.
Can you make sure your system is not overheating and throttling down as a consequence? This is likely in case you are running on a laptop. Try using a frame limiter to reduce your framerate and see if the drops are still as severe.
If this doesn't help, please try closing all background applications while playing osu!.
If this doesn't help, please try closing all background applications while playing osu!.
I don't play on a laptop and my system is not overheating. I tried to cap fps, but it didn't help. Also closed all background applications, still didn't help. But as I said i a previous post, osu! ran perfectly fine on stable version.Tom94 wrote:
Can you make sure your system is not overheating and throttling down as a consequence? This is likely in case you are running on a laptop. Try using a frame limiter to reduce your framerate and see if the drops are still as severe.
If this doesn't help, please try closing all background applications while playing osu!.
Comparing it with stable is not valid in the case of throttling. CE makes more use of the GPU, usually resulting in higher temperatures, but also higher frame rates.
Either way, if you can rule out heat and throttling (this can also happen on desktops), then could you make a screenshot of how the frame time display looks like during the stutters and without stutters for you? You can toggle the display using Ctrl+F11.
Either way, if you can rule out heat and throttling (this can also happen on desktops), then could you make a screenshot of how the frame time display looks like during the stutters and without stutters for you? You can toggle the display using Ctrl+F11.
If you move the osu! window while it is on the welcome screen, the menu-background of the skin won't load. This gets fixed by reloading the skin.
Doesn't happen on Stable release stream.
Doesn't happen on Stable release stream.
Ok, osu! is running good again, the problem was that my computer couldnt handle some storyboard stuff (the framedrops I mentioned just happened again, disabled storyboard and it worked). But I noticed, that if I move my cursor fast the cursor is flickering. Not really a big problem, just wanted to say it.Tom94 wrote:
Comparing it with stable is not valid in the case of throttling. CE makes more use of the GPU, usually resulting in higher temperatures, but also higher frame rates.
Either way, if you can rule out heat and throttling (this can also happen on desktops), then could you make a screenshot of how the frame time display looks like during the stutters and without stutters for you? You can toggle the display using Ctrl+F11.
What do you mean by flicker? Tearing? It happens both on stable and on cuttingedge if you are running in fullscreen mode or have windows aero disabled while not using VSync. There is no way around it unfortunately.