forum

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

posted
Total Posts
2,521
show more
nns1337

peppy wrote:

update_log.txt please
I don't have one.
Tom94

Miracle wrote:

It seems on certain maps, slider ticks are being generated where they aren't supposed to. So far, I've only found one, but I can confirm that this isn't an issue on stable and beta builds, only Cutting Edge. And it was not a problem yesterday. Just started today.

The map in question is https://osu.ppy.sh/s/311013 Difficulty name is "Ouroboros Division".

Here are screenshots, with screenshots under that of how they should normally look, as well as timing points for each underneath that. There are probably a lot more in this map, but these are the ones I noticed immediately.



00:07:968 (1) -



00:08:352 (2) -



00:15:660 (3) -

So far, this is the only map I've seen this happen, but if I find any more while playing, I will edit my post with more examples.
Should be fixed now, please try again, and please keep reporting in case you find another case.
Trosk-

Smc wrote:

Whenever I'm playing a map and enter the pause menu, there's a weird visual glitch that appears for 1-2 frames and disappears.
Video
Only happens in the newest cutting-edge build.
Windows 10, GTX 970 with 355.60 driver
Ok, I just had the same effect. Without Shaders tho.
Damnae
Linear parts of sliders aren't selectable anymore in the editor: http://puu.sh/jGjL1/b28d6b3501.mp4
agubelu
I don't know if it's just me but sometimes my computer freezes for a couple of seconds when I minimize/close osu
Lyra

Tom94 wrote:

Miracle wrote:

It seems on certain maps, slider ticks are being generated where they aren't supposed to. So far, I've only found one, but I can confirm that this isn't an issue on stable and beta builds, only Cutting Edge. And it was not a problem yesterday. Just started today.

The map in question is https://osu.ppy.sh/s/311013 Difficulty name is "Ouroboros Division".

Here are screenshots, with screenshots under that of how they should normally look, as well as timing points for each underneath that. There are probably a lot more in this map, but these are the ones I noticed immediately.



00:07:968 (1) -



00:08:352 (2) -



00:15:660 (3) -

So far, this is the only map I've seen this happen, but if I find any more while playing, I will edit my post with more examples.
Should be fixed now, please try again, and please keep reporting in case you find another case.
Tested. Everything checks out fine now.

Unforunately, I have to leave elsewhere for the time being, so I won't be able to test some more maps out for a while. But most of the other maps I played didn't have this issue.
nns1337
http://hastebin.com/foyejikibo.pas

Got the latest osu!.exe , this is the result.


This comes out when I move osu!.exe to its own folder: http://hastebin.com/econivufeh.vhdl
DeletedUser_4329079

Damnae wrote:

Linear parts of sliders aren't selectable anymore in the editor: http://puu.sh/jGjL1/b28d6b3501.mp4
Can confirm
Topic Starter
TheVileOne
I have a fix submitted for the sliders. Please be patient.
BanchoBot
Issue(s) in this thread have been addressed by the following changes:
  1. Fix linear sliders being unable to be selected. (TheVileOne)
The changes will be applied to builds newer than b20150818.14cuttingedge.

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.
hard to freeze
"Snaking sliders" seems to be of no use to some linear-shape sliders, but it works pretty well on curve-shape sliders.
The build is b20150819.3cuttingedge.
Tom94
I already pushed a fix for that, just gotta wait until it's merged in.
Morbon
Any response for p/4431432 ? It still crashes
Tom94
Doesn't crash for me. Are you on latest drivers? If yes, please check if it happens with different skins or maps.
Morbon

Tom94 wrote:

Doesn't crash for me. Are you on latest drivers? If yes, please check if it happens with different skins or maps.
It crashes only with "always use default skin" option.
Tom94

Morbon wrote:

Tom94 wrote:

Doesn't crash for me. Are you on latest drivers? If yes, please check if it happens with different skins or maps.
It crashes only with "always use default skin" option.
Even with that option on I don't get crashes. Can you please tell me on which map with which skin (despite using the "Always use default skin" option) you reproduce it?

It would also help if you could tinker with your options to see whether anything else affects the crashing behavior. Thanks a lot!
Morbon

Tom94 wrote:

Even with that option on I don't get crashes. Can you please tell me on which map with which skin (despite using the "Always use default skin" option) you reproduce it?

It would also help if you could tinker with your options to see whether anything else affects the crashing behavior. Thanks a lot!
Well, it happens on all maps with this option, with or without custom map skins. The only thing, that I can add here: osu! crashes immediately with custom skin (for example on this map)
I'll try to change some options, will post later.


Edit: It's not the options. I get crashes even on same options as the ones which have ppl who don't crashing.
MillhioreF
Clicking an osu!direct link in chat while spectating someone or watching a replay causes the interface and map to fade away and the replay to completely stop.

Video
BeatBreakerS
Beatmaps ( that have Skip ) are Auto skipping themselves if CTRL+R is used

b20150820.1CE


i'm stupid
peppy

BeatBreakerS wrote:

Beatmaps ( that have Skip ) are Auto skipping themselves if CTRL+R is used

b20150820.1CE
That is how ctrl-r workd. and has always worked. PLEASE compare to stable before reporting issues.
mazei


The changelog text box cuts off part of the text. I realized this happening from the 19th August build, but not sure exactly when it began. Still an issue with the current build.
Shizuyi
Its like this since forever.
Trosk-

mazei wrote:


The changelog text box cuts off part of the text. I realized this happening from the 19th August build, but not sure exactly when it began. Still an issue with the current build.
-> p/4121624
mazei
Ah thought it was recent, only checked a few pages back.
Quichey
There seems to be an issue with brightness values on the sliders. Opacity seems to be the offender here, most likely caused by the sprite being drawn twice on a slider start circle after testing.

This test skin, which has hit circles set at 50% opacity, a slightly larger sliderstartcircle set at 50% opacity, sliderendcircle set at 50% opacity, and skin-ini values to give maximum contrast, should highlight the problem.
Test Skin

These two images nicely show the effect.


After failing,
Shimu-
This random bar in the right corner which I dont know how to "disable" shows up only in Beta and Cutting-Edge

https://osu.ppy.sh/ss/3563695
Trosk-

ChrillMeister wrote:

This random bar in the right corner which I dont know how to "disable" shows up only in Beta and Cutting-Edge

https://osu.ppy.sh/ss/3563695
Ctrl + F11.
Shimu-

Trosk- wrote:

ChrillMeister wrote:

This random bar in the right corner which I dont know how to "disable" shows up only in Beta and Cutting-Edge

https://osu.ppy.sh/ss/3563695
Ctrl + F11.
Ahh Thanks mate ;)
Mykaterasu
Much like Quiesce above me, I have found a transparency inconsistancy of the slider hit circles between the stable/beta patches and the Cutting-edge build. I do not know the cause for sure.
Reproduction:
In the Stable/Beta patch, a skin with a slider track override of [0,0,0] and a transparent hitcircle will show no colour difference between the normal hit circle and the slider hit circle when the background dim is set to 100%.


In the Cutting Edge patch, a skin with a slider track override of [0,0,0], (an invisible sliderendcircle) and a transparent hitcircle will show a colour difference between the normal hit circle and the slider hit circle when the background dim is set to 100% - most likely due to transparency. As Quiesce mentions, this looks a lot like the sliderhitcircle has had its transparency value doubled; or in other words the hitcircle is being placed ontop of itself twice.
Fatal3ty
HitCircleOverlayAboveNumber: 1 is not working with newest update:



Before the update with looked better, but Sliderstartcircle were brighter. I want Hitcircle stays on, without making it bright.



And hitcircleoverlay-0.png is not working with newest update (Many Skins has a hitcircleoverlay-0.png, old Features, HitCircleOverlayAboveNumber: 1 is important for hitcircleoverlay-0.png)


Please Fix. :(
encryptik

Fatal3ty wrote:

And hitcircleoverlay-0.png is not working with newest update (Many Skins has a hitcircleoverlay-0.png, old Features, HitCircleOverlayAboveNumber: 1 is important for hitcircleoverlay-0.png)
Also getting this problem, somewhat relates to the bug I posted here p/3907488/
BanchoBot
Issue(s) in this thread have been addressed by the following changes:
  1. Avoid cursor trail becoming unresponsive after a while at high frame rates. (Tom94)
The changes will be applied to builds newer than b20150821.2cuttingedge.

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.
Toggeni
this is probably a minor issue but wanted to post it anyway.
It seems to only affect the cutting edge version as I had a friend who did not have the problem on the stable version but got it when he switched to cutting edge. It also seem to only affect this map on the tatoe difficulty. Possibly also only on catch the beat but I have not tried any of the other modes.

The issue is that for some reason that hyper appears there. It should not be there and it is not in the map.

As you can see the note does not exist. It just appears out of nowhere when you play it/ spectate it/ watch a replay of it. Also should be noted if I spectate someone playing the map on the stable version the note still appears but the player does not miss if they don't catch it.

A screenshot of my friend getting the same issue on cutting edge.
Trosk-

Toggeni wrote:

<stuff>
Most likely related to this: p/4443052

MillhioreF wrote:

Cuttingedge is actually the correct behaviour; the slider's length is a bit messed up, and rerunning slider calculations fixes it. Stable is a bit less accurate and a bit less picky, so it works correctly there.

I'll try to talk to Tom about this, but I think the map will have to be DQ'd.
iTaSou
My old GMA3150 seems to have issue with OpenTK/OpenGL ES
When I click continue it'll show osu! crash dialog.
Try on Windows 10 / Windows 7 and it won't run either.
But working fine on stable/beta stream.

Error code
SPOILER
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
OpenTK.Graphics.GraphicsContextException: Failed to initialize EGL, error NOT_INITIALIZED.
at OpenTK.Platform.Egl.EglWindowInfo..ctor(IntPtr handle, IntPtr display, IntPtr surface)
at OpenTK.Platform.Egl.EglAnglePlatformFactory.CreateWindowInfo(IAngleWindowInfoInternal window_info, Int32 major, GraphicsContextFlags flags)
at OpenTK.Platform.Egl.EglAnglePlatformFactory.CreateGLContext(GraphicsMode mode, IWindowInfo window, IGraphicsContext shareContext, Boolean directRendering, Int32 major, Int32 minor, GraphicsContextFlags flags)
at OpenTK.Graphics.GraphicsContext..ctor(GraphicsMode mode, IWindowInfo window, IGraphicsContext shareContext, Int32 major, Int32 minor, GraphicsContextFlags flags)
at #=qmUEsUpQftaConAlufUlFvhcq$zVe1LvyAK$0IhGPvvE=.#=qJcWLSNfKrB9ncod0VYDscg==(Int32 #=qcFYwDvzgLtg2viWXNodAJA==, Int32 #=qpmpj5XStpZNtlpuiOXyvgA==, GraphicsContextFlags #=qeIFmJkgMXNuYPuzdqfD5rA==)
at #=q0OnCfYPUs7gKlg2OEm4yU1EcO5zcqJHiN_tFmYGVm9M=.#=qf$ERlCaOP$LCyvWogbvxbA==()
at #=q0OnCfYPUs7gKlg2OEm4yU1EcO5zcqJHiN_tFmYGVm9M=.#=qf$ERlCaOP$LCyvWogbvxbA==()
at #=q0OnCfYPUs7gKlg2OEm4yU1EcO5zcqJHiN_tFmYGVm9M=.#=qf$ERlCaOP$LCyvWogbvxbA==()
at #=q0OnCfYPUs7gKlg2OEm4yU1EcO5zcqJHiN_tFmYGVm9M=.OnHandleCreated(EventArgs #=qkXxd8mqPTYbyko8cG9nZrg==)
at System.Windows.Forms.Control.WmCreate(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmCreate(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at #=q7qBnCIqG1iyFwj9JSy3ptnlgqunD2veUWFm5Qk_Diqlic7zPOzR_sMQe0UlEbAtr.WndProc(Message& #=qbA6fL2BJwVHDOWsjq0_EYQ==)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.6.96.0 built by: NETFXREL2STAGE
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
osu!
Assembly Version: 0.0.0.0
Win32 Version: 1.3.3.7
CodeBase: file:///D:/souHTPC/Games/osu!/osu!.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
OpenTK
Assembly Version: 1.1.0.0
Win32 Version: 1.1.2049.0
CodeBase: file:///D:/souHTPC/Games/osu!/OpenTK.DLL
----------------------------------------
zx_032c19f25a9b4578abb8f32476cc8193
Assembly Version: 0.0.0.0
Win32 Version: 1.3.3.7
CodeBase: file:///D:/souHTPC/Games/osu!/osu!.exe
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

VeilStar
I finally got around to replicating this 'white box' issue on the chat.

Here's the thread for the issue that happens on all release streams: t/359904

Most of it happens on all release streams but in cuttingedge it's possible to have the 'white box' not dissapear after closing the chat once.
(It re-appears when re-opening the chat.)

https://www.youtube.com/watch?v=izuyjAFAp7E


The issue is that the selection box doesn't get disposed correctly, or something along those lines.

Replication steps:
-Open the chat by pressing F8
-Type something
-Press CTRL+A to select the text
-Press the + button to join a new channel (or recieve a PM while the text is selected)
-Join a new channel
-Close the chat and open it again as many times as you want
VeilStar

BeatBreakerS wrote:

issue
Okay so when i open osu and rapidly click on my desk top or a windows it starts as minimized, but it doesn't Start as in "Welcome to osu" is not played.

so while it was in minimized form i clicked a .ozs to Export it

Osu starts up as in the Song Selection and Welcome to osu is played like so http://puu.sh/jiFHx/a7c95ddb75.png

Then is Stays there and my Profile Signature(Or details) and the Song Forward and back ward thing is displayed as an overlay like so http://puu.sh/jiFIr/6cb811d6b2.png
( look at the top right and top left)
And yes you can interact with them

It goes away when you back and re enter the song selection

Edit: I am on win 7 currently win10 and i run osu Full Screen Letter boxed mode i haven't tested it out in windowed mode but i guess it wont cause a problem there it's not there in windowed mode

Steps To Reproduce

  1. While opening osu!beta or CE repeatedly click on your Desktop, it make osu minimized and not show "Welcome to osu" nor will the sound be played
  2. Click a osz file to import into osu
  3. Welcome is played on Song selection with broken interactions/Overlays provided in above Screenshot
this was Replicated By Trosk- here p/4382374
Can you still replicate this? (I can't.)
BeatBreakerS

VeilStar wrote:

BeatBreakerS wrote:

issue
Okay so when i open osu and rapidly click on my desk top or a windows it starts as minimized, but it doesn't Start as in "Welcome to osu" is not played.

so while it was in minimized form i clicked a .ozs to Export it

Osu starts up as in the Song Selection and Welcome to osu is played like so http://puu.sh/jiFHx/a7c95ddb75.png

Then is Stays there and my Profile Signature(Or details) and the Song Forward and back ward thing is displayed as an overlay like so http://puu.sh/jiFIr/6cb811d6b2.png
( look at the top right and top left)
And yes you can interact with them

It goes away when you back and re enter the song selection

Edit: I am on win 7 currently win10 and i run osu Full Screen Letter boxed mode i haven't tested it out in windowed mode but i guess it wont cause a problem there it's not there in windowed mode

Steps To Reproduce

  1. While opening osu!beta or CE repeatedly click on your Desktop, it make osu minimized and not show "Welcome to osu" nor will the sound be played
  2. Click a osz file to import into osu
  3. Welcome is played on Song selection with broken interactions/Overlays provided in above Screenshot
this was Replicated By Trosk- here p/4382374
Can you still replicate this? (I can't.)
yes i Can HERE i made a video for it too :D

Also on a side VeilStar this issue Still persists on both Beta and CE

have fun osu!Dev's :>

EDIT:
Gl_info.txt
gpu is AMD Radeon HD 6520G
Drivers are upto date
Trosk-

VeilStar wrote:

BeatBreakerS wrote:

issue
Okay so when i open osu and rapidly click on my desk top or a windows it starts as minimized, but it doesn't Start as in "Welcome to osu" is not played.

so while it was in minimized form i clicked a .ozs to Export it

Osu starts up as in the Song Selection and Welcome to osu is played like so http://puu.sh/jiFHx/a7c95ddb75.png

Then is Stays there and my Profile Signature(Or details) and the Song Forward and back ward thing is displayed as an overlay like so http://puu.sh/jiFIr/6cb811d6b2.png
( look at the top right and top left)
And yes you can interact with them

It goes away when you back and re enter the song selection

Edit: I am on win 7 currently win10 and i run osu Full Screen Letter boxed mode i haven't tested it out in windowed mode but i guess it wont cause a problem there it's not there in windowed mode

Steps To Reproduce

  1. While opening osu!beta or CE repeatedly click on your Desktop, it make osu minimized and not show "Welcome to osu" nor will the sound be played
  2. Click a osz file to import into osu
  3. Welcome is played on Song selection with broken interactions/Overlays provided in above Screenshot
this was Replicated By Trosk- here p/4382374
Can you still replicate this? (I can't.)
Seems like it keeps happening.

BanchoBot
Issue(s) in this thread have been addressed by the following changes:
  1. Disallow slider ticks closer than 10ms to slider ends. (Tom94)
The changes will be applied to builds newer than b20150821.3cuttingedge.

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.
show more
Please sign in to reply.

New reply