forum

[Archived] Issues with Latest Cutting-edge Build (Post Here)

posted
Total Posts
2,521
show more
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
Topic Starter
TheVileOne
Text boxes have never allowed you to seek to a specific part of the text.
Maeglwn

TheVileOne wrote:

Text boxes have never allowed you to seek to a specific part of the text.
they DEFINITELY were able to. I was able to before some time ago
Topic Starter
TheVileOne
I just checked stable release and it has the same behaviour as cutting edge. How long ago were you able to do this?
Diony
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.
321jurgen
Problem Details:
If I'm in fullscreen and I open up my friends with f9 my cursor dissapears.


osu! version: b20150627.3cuttingedge
Trosk-

321jurgen wrote:

Problem Details:
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.
Pampel

321jurgen wrote:

Problem Details:
If I'm in fullscreen and I open up my friends with f9 my cursor dissapears.
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.

(Setting your cursor trail to to -1 prevents f.lux from making your cursor blue, in case anyone is wondering.)
321jurgen

Pampel wrote:

321jurgen wrote:

Problem Details:
If I'm in fullscreen and I open up my friends with f9 my cursor dissapears.
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.

(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 xD
CakeAndBanana
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 :o
The Changelog menu was or is bugged.


Video or screenshot showing the problem:
http://puu.sh/iFAId/7707cdecd1.jpg

osu! version: 20150628.1cuttingedge
VeilStar

CakeAndBanana wrote:

If you make a screenshot with F12+Shift (Upload) than you are not getting a picture but a empty space
This is a temporary web issue. It's not cutting-edge specific.

CakeAndBanana wrote:

The Changelog menu was or is bugged.
Do you mean this? p/4121624
Shizuyi

VeilStar wrote:

CakeAndBanana wrote:

The Changelog menu was or is bugged.
Do you mean this? p/4121624
I still have this issue.
VeilStar

Shizuyi wrote:

I still have this issue.
Well yeah. It's listed in the OP for a reason.
Hadis
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".
Trosk-

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".
I can't... I don't know if I'm doing something wrong, but I followed your steps and I didn't get it.
sarnex
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
CakeAndBanana

VeilStar wrote:

Do you mean this? p/4121624
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:
Maeglwn

TheVileOne wrote:

I just checked stable release and it has the same behaviour as cutting edge. How long ago were you able to do this?
I guess like 3 months ago or so now now that I think about it, I haven't edited my HLs in quite some time
Piine
Seems like the CE Build's Recent Changes log is broken.

Trosk-

Sulker wrote:

Seems like the CE Build's Recent Changes log is broken.

I believe that this has been reported before.
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.

Piine
Yeah I can guess seeing when I turned Letterboxing on, it showed
Quichey

(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.
Trosk-
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.

VeilStar

Quiesce wrote:

wrong forum... man. could a mod move?

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
Merged to the Cutting-edge thread. Anyhow, I can replicate this. And happened to break shit while doing so.

Edit: Removed both of your posts to avoid clutter.
ruruxz
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
Trosk-
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:

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


VeilStar

Nakuyoko wrote:

Problem Details:
When spectating someone or watching a replay.
If you try to disable flashlight it gives an error and sometimes crashes.
I can confirm. Merging this to the cuttingedge thread.
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==)
Trosk-
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..
VeilStar

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..
That's intended.
BanchoBot
Issue(s) in this thread have been addressed by the following changes:
  1. Fix null ref when toggling flashlight mod. (TheVileOne)
The changes will be applied to builds newer than b20150629cuttingedge.

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.
Score_Under


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.
BoySanic
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".
Trosk-

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, does it happen only in Cutting Edge? Make sure that you are not pressing your Ctrl key when you start a map.
Trosk-
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.
Nathanael
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
Sensou Shin
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.
VeilStar

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.
Thanks for reporting but you posted it in the wrong thread, so I merged your post to the appropriate thread.

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?
chong601
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
Trosk-
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...

Sensou Shin

VeilStar wrote:

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.
Thanks for reporting but you posted it in the wrong thread, so I merged your post to the appropriate thread.

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?
Sorry but i can't. It was a suprise to me :S
show more
Please sign in to reply.

New reply