I don't know if it's just me but sometimes my computer freezes for a couple of seconds when I minimize/close osu
forum
[Archived] Issues with Latest Cutting-edge Build (Post Here) 5z1i67
posted
Total Posts
2,521
Tested. Everything checks out fine now.Tom94 wrote: 56z3w
Should be fixed now, please try again, and please keep reporting in case you find another case.Miracle wrote: 5y1o50
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.tvgratuite.org/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.
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.
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
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
Deleted_4329079
Can confirmDamnae wrote: hz1r
Linear parts of sliders aren't selectable anymore in the editor: http://puu.sh/jGjL1/b28d6b3501.mp4
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 linear sliders being unable to be selected. (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.
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?Morbon wrote: 1468r
It crashes only with "always use default skin" option.Tom94 wrote: 56z3w
Doesn't crash for me. Are you on latest drivers? If yes, please check if it happens with different skins or maps.
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)Tom94 wrote: 56z3w
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!
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.
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
Video
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,
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,
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.tvgratuite.org/ss/3563695
https://osu-ppy-sh.tvgratuite.org/ss/3563695
Ctrl + F11.ChrillMeister wrote: 412t1c
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.tvgratuite.org/ss/3563695
Ahh Thanks mateTrosk- wrote: 6k5648
Ctrl + F11.ChrillMeister wrote: 412t1c
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.tvgratuite.org/ss/3563695
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.
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.
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.
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.
Also getting this problem, somewhat relates to the bug I posted here p/3907488/Fatal3ty wrote: 2r6f33
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)
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.
- Avoid cursor trail becoming unresponsive after a while at high frame rates. (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.
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.
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.
Most likely related to this: p/4443052Toggeni wrote: 6z3u6j
<stuff>
MillhioreF wrote: 2k1855
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.
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
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 ed on the computer
rather than be handled by this dialog box.
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 ed on the computer
rather than be handled by this dialog box.
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 a new channel (or recieve a PM while the text is selected)
- a new channel
-Close the chat and open it again as many times as you want
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 a new channel (or recieve a PM while the text is selected)
- a new channel
-Close the chat and open it again as many times as you want
Can you still replicate this? (I can't.)BeatBreakerS wrote: 3h334e
issueOkay 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 onwin 7currently win10 and i run osu Full Screen Letter boxed modei haven't tested it out in windowed mode but i guess it wont cause a problem thereit's not there in windowed mode
Steps To Reproduce 2s5x2r
this was Replicated By Trosk- here p/4382374
- 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
- Click a osz file to import into osu
- Welcome is played on Song selection with broken interactions/Overlays provided in above Screenshot
yes i Can HERE i made a video for it tooVeilStar wrote: 74923
Can you still replicate this? (I can't.)BeatBreakerS wrote: 3h334e
issueOkay 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 onwin 7currently win10 and i run osu Full Screen Letter boxed modei haven't tested it out in windowed mode but i guess it wont cause a problem thereit's not there in windowed mode
Steps To Reproduce 2s5x2r
this was Replicated By Trosk- here p/4382374
- 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
- Click a osz file to import into osu
- Welcome is played on Song selection with broken interactions/Overlays provided in above Screenshot
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
Seems like it keeps happening.VeilStar wrote: 74923
Can you still replicate this? (I can't.)BeatBreakerS wrote: 3h334e
issueOkay 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 onwin 7currently win10 and i run osu Full Screen Letter boxed modei haven't tested it out in windowed mode but i guess it wont cause a problem thereit's not there in windowed mode
Steps To Reproduce 2s5x2r
this was Replicated By Trosk- here p/4382374
- 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
- Click a osz file to import into osu
- Welcome is played on Song selection with broken interactions/Overlays provided in above Screenshot
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.
- Disallow slider ticks closer than 10ms to slider ends. (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.
Regarding Background and other elements can get out of proportion/position after alt+tab'ing out and back in posted here.
After having a chat with BeatBreakerS it seems that there's a few requirements to replicate this:
-Raw Input has to be enabled.
-Parallax has to be enabled.
-osu! has to be running in dedicated fullscreen, even in the main menu.
-You must use a device with absolute positioning (such as a tablet).
Once those requirements are met you can replicate it by doing the following:
-Move your cursor around on the main menu with your tablet.
-ALT+TAB out of osu! and do whatever, just move the cursor around a bit.
-ALT+TAB back in.
I guess that this is caused by osu! being unable to apply the parallax transformations while its minimized due to running in dedicated fullscreen, upon maximizing it again you get this messed up transformation.
(Huge thanks to BeatBreakerS!)
After having a chat with BeatBreakerS it seems that there's a few requirements to replicate this:
-Raw Input has to be enabled.
-Parallax has to be enabled.
-osu! has to be running in dedicated fullscreen, even in the main menu.
-You must use a device with absolute positioning (such as a tablet).
Once those requirements are met you can replicate it by doing the following:
-Move your cursor around on the main menu with your tablet.
-ALT+TAB out of osu! and do whatever, just move the cursor around a bit.
-ALT+TAB back in.
I guess that this is caused by osu! being unable to apply the parallax transformations while its minimized due to running in dedicated fullscreen, upon maximizing it again you get this messed up transformation.
(Huge thanks to BeatBreakerS!)
Even with that conditions I can't replicate it. Tried with many resolutions, Letterboxing enabled and disabled, Shaders enabled and disabled, on the menu, on song selection.. Tried even restating osu! with that setting and it's still not happening for me.VeilStar wrote: 74923
Regarding Background and other elements can get out of proportion/position after alt+tab'ing out and back in posted here.
Stuff.After having a chat with BeatBreakerS it seems that there's a few requirements to replicate this:
-Raw Input has to be enabled.
-Parallax has to be enabled.
-osu! has to be running in dedicated fullscreen, even in the main menu.
-You must use a device with absolute positioning (such as a tablet).
Once those requirements are met you can replicate it by doing the following:
-Move your cursor around on the main menu with your tablet.
-ALT+TAB out of osu! and do whatever, just move the cursor around a bit.
-ALT+TAB back in.
I guess that this is caused by osu! being unable to apply the parallax transformations while its minimized due to running in dedicated fullscreen, upon maximizing it again you get this messed up transformation.
(Huge thanks to BeatBreakerS!)
Edit: Well, after I don't know how many tries I could get this effect.
i can replicate the Parallax issue 24/7Shizuyi wrote: 65u31
I tried to replicate about 10-15 times but only happend 1 time even when all conditions are met.
gl_info.txt
nns1337 wrote: 71425c
nns1337 wrote: 71425c
My osu! won't update since the 29th of July, It just says there's a problem with my internet connection but there isn't. Ingame it wont the stuff either, it just says there's an error ing the files. Doesn't work when running osu! in mode aswell.
Bancho disconnected me today saying my osu! version is too old aswell.
Windows 10, Cutting Edge from 29th of July 2015, 20150729.2
Anyone got a fix for me?
Issue still the case. I got the version 20150810.3 from a friend, not updating from that also. Antivir and Windows Defender off, no other program which could cause the issue.
Issue is STILL there, now osu! isn't even booting up after I close the updater, and it just keeps being in a loop saying I have connection problems.
update_log.txt : http://hastebin.com/foyejikibo.pas
This comes out when I move osu!.exe to its own folder: http://hastebin.com/econivufeh.vhdl
That's odd... Maybe the options are some kind of "bugged", because if you have the cap at 1000, it should go up to 1000.nallar wrote: 4i3m
After updating osu!, FPS seems to be capped to monitor framerate.
Frame limiter is set to 1000FPS, vsync is set to always off in nvidia control . Any ideas?
OS: Windows 10
GPU: GTX 980
Driver version: 355.60
Refresh rate: 144Hz
Selected FPS cap: 1000FPS
Actual FPS cap: 144FPS
Go to your osu!<name>.cfg archive, and search for the line "FrameSync". It should say "Custom" if it's correct (or at least it shouldn't say VSync).
found bug with replays in Cutting-edge https://www.youtube.com/watch?v=JCg4GAxZluU
Thanks for the help.Trosk- wrote: 6k5648
That's odd... Maybe the options are some kind of "bugged", because if you have the cap at 1000, it should go up to 1000.
Go to your osu!<name>.cfg archive, and search for the line "FrameSync". It should say "Custom" if it's correct (or at least it shouldn't say VSync).
"FrameSync" is set to "Custom". I'll try a clean install of the graphics drivers just in case that fixes it.
Well, the replays are not 100% corect, but the thing of it missing on Cutting Edge and being ok on Stable is weird...FInist wrote: 1l3m71
found bug with replays in Cutting-edge https://www.youtube.com/watch?v=JCg4GAxZluU
No problem.. Do you know if it happens with other games or it is happening just on osu!?nallar wrote: 4i3m
Thanks for the help.
"FrameSync" is set to "Custom". I'll try a clean install of the graphics drivers just in case that fixes it.
If it doesn't work, post here again (If it's only happening on Cutting Edge/Beta and not on Stable) or send me a PM to try another thing.
Is your screen GSync capable? Turning off VSync might not be enough then. I needed to specifically add osu!.exe and configure it to use a fixed refresh rate, so it'd by my screen's refresh rate cap.nallar wrote: 4i3m
After updating osu!, FPS seems to be capped to monitor framerate.
Frame limiter is set to 1000FPS, vsync is set to always off in nvidia control . Any ideas?
OS: Windows 10
GPU: GTX 980
Driver version: 355.60
Refresh rate: 144Hz
Selected FPS cap: 1000FPS
Actual FPS cap: 144FPS
The bold settings are relevant.
Clean driver install fixed it - not sure what exactly the issue was, just happy that it's fixed.Trosk- wrote: 6k5648
Well, the replays are not 100% corect, but the thing of it missing on Cutting Edge and being ok on Stable is weird...FInist wrote: 1l3m71
found bug with replays in Cutting-edge https://www.youtube.com/watch?v=JCg4GAxZluU
No problem.. Do you know if it happens with other games or it is happening just on osu!?nallar wrote: 4i3m
Thanks for the help.
"FrameSync" is set to "Custom". I'll try a clean install of the graphics drivers just in case that fixes it.
If it doesn't work, post here again (If it's only happening on Cutting Edge/Beta and not on Stable) or send me a PM to try another thing.
Deleted_4329079
Deleted_4329079
You need to die while clicking on the slider (hitting it too late on an hp10 map helps). A very fast map with a lot of slider ticks makes replicating it way easier (such as isogu's 999bpm difficulty, but with a long slider instead)Trosk- wrote: 6k5648
I can't replicate this issue.Default wrote: 2d276a
When you die while on a slider tick you get earraped by a million slider ticks sounding at the same time
Why am I being ignored? I've posted the update_log.txt as soon as I got it and I got no answer for daysnns1337 wrote: 71425c
nns1337 wrote: 71425c
My osu! won't update since the 29th of July, It just says there's a problem with my internet connection but there isn't. Ingame it wont the stuff either, it just says there's an error ing the files. Doesn't work when running osu! in mode aswell.
Bancho disconnected me today saying my osu! version is too old aswell.
Windows 10, Cutting Edge from 29th of July 2015, 20150729.2
Issue still the case. I got the version 20150810.3 from a friend, not updating from that also. Antivir and Windows Defender off, no other program which could cause the issue.
Issue is STILL there, now osu! isn't even booting up after I close the updater, and it just keeps being in a loop saying I have connection problems.
update_log.txt : http://hastebin.com/foyejikibo.pas
This comes out when I move osu!.exe to its own folder: http://hastebin.com/econivufeh.vhdl
several days?! FUCK MAN i'm sorry. i forgot the world revolves around you.
* you can still run osu!, so it's not top priority.
* i haven't had a chance to look yet (i've been busy with many other things).
* please be patient. you have not been forgotten. alternatively wire me $200 to [email protected] and i'll give you a full day of one on one .
* you can still run osu!, so it's not top priority.
* i haven't had a chance to look yet (i've been busy with many other things).
* please be patient. you have not been forgotten. alternatively wire me $200 to [email protected] and i'll give you a full day of one on one .
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 regression with fading out slider start circles. (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.
OT: Ill take you on that offer one day.peppy wrote: 73101g
* please be patient. you have not been forgotten. alternatively wire me $200 to [email protected] and i'll give you a full day of one on one .
Little update on a bug I reported before regarding big lag while recording with letterboxing p/4368736
Same thing happens with dxtory/bandicam capturing and I've reinstalled my whole system since last time so I believe this is osu! issue
obs:
https://osu-ppy-sh.tvgratuite.org/ss/3576715
capturing "fullscreen" instead of game window(I'm using game capture): http://i.imgur.com/6WIqtIV.png
dxtory:
https://osu-ppy-sh.tvgratuite.org/ss/3576700
bandicam:
https://osu-ppy-sh.tvgratuite.org/ss/3576738
note that after disabling letterboxing fps becomes "normal" again
gl_info: http://puu.sh/jLx3F.txt
Same thing happens with dxtory/bandicam capturing and I've reinstalled my whole system since last time so I believe this is osu! issue
obs:
https://osu-ppy-sh.tvgratuite.org/ss/3576715
capturing "fullscreen" instead of game window(I'm using game capture): http://i.imgur.com/6WIqtIV.png
dxtory:
https://osu-ppy-sh.tvgratuite.org/ss/3576700
bandicam:
https://osu-ppy-sh.tvgratuite.org/ss/3576738
note that after disabling letterboxing fps becomes "normal" again
gl_info: http://puu.sh/jLx3F.txt
I can't run it. Earlier it started when I closed the updater, but now it doesn't do that aswell.peppy wrote: 73101g
several days?! FUCK MAN i'm sorry. i forgot the world revolves around you.
* you can still run osu!, so it's not top priority.
* i haven't had a chance to look yet (i've been busy with many other things).
* please be patient. you have not been forgotten. alternatively wire me $200 to [email protected] and i'll give you a full day of one on one .
I understand that you have many other thins to do, this is quite obvious., it's just that I asked for help 17 days ago and still haven't gotten a solution to this
Try to this osu!.exe and replace it with your current one. Then try to run it and if it's still on loop, try closing the updater and see if it runs.nns1337 wrote: 71425c
I can't run it. Earlier it started when I closed the updater, but now it doesn't do that aswell.
I understand that you have many other thins to do, this is quite obvious., it's just that I asked for help 17 days ago and still haven't gotten a solution to this
osu! does not work anymore. Classic windows response. Actually the first time this happens, the installer brings me this error for a while now aswell, the older osu!.exe versions I have here (from the 18th and the 10th) don't give that errorTrosk- wrote: 6k5648
Try to this osu!.exe and replace it with your current one. Then try to run it and if it's still on loop, try closing the updater and see if it runs.nns1337 wrote: 71425c
I can't run it. Earlier it started when I closed the updater, but now it doesn't do that aswell.
I understand that you have many other thins to do, this is quite obvious., it's just that I asked for help 17 days ago and still haven't gotten a solution to this
On this beatmap,
Trakker - Trail of Dust
At 00:35:00 to 02:00:00 (roughly), there is heavy frame lag. I investigated in MSI Afterburner and found that at roughly the same time when the FPS drops, the memory usage drops as well. When the frame rate recovers, so does too the memory. Will do more testing with other skins. I notice this problem is more pronounced when it's the first time playing the beatmap on your session of osu!.
Edit1: Skin does not matter. Tried with 2 different skins and the default skin, each replicate the problem almost exactly.
FPS seems to drop to 60, meaning the problem can only be noticed when you have a higher framerate monitor. In my case I have a 144hz monitor.
Edit2: Osu! Settings are 1920x1080, Fullscreen Letterbox(0,0). Framerate: Unlimited. Snaking Sliders, Background Video, Storyboards, Combobursts activated. 80% background dim. Ignore all beatmap skins and use skin's sound samples.
Edit3: VSync does not change the effect.
Edit4: gl_info: http://pastebin.com/hkhQgGyK
This problem only happens on this beatmap as far as I'm aware.
Edit5: Problem seems worse when you have transparent hit300s.
Edit6: Cannot replicate anymore, most likely due to the transparent fix.
Edit7: It is back.
Trakker - Trail of Dust
At 00:35:00 to 02:00:00 (roughly), there is heavy frame lag. I investigated in MSI Afterburner and found that at roughly the same time when the FPS drops, the memory usage drops as well. When the frame rate recovers, so does too the memory. Will do more testing with other skins. I notice this problem is more pronounced when it's the first time playing the beatmap on your session of osu!.
Edit1: Skin does not matter. Tried with 2 different skins and the default skin, each replicate the problem almost exactly.
FPS seems to drop to 60, meaning the problem can only be noticed when you have a higher framerate monitor. In my case I have a 144hz monitor.
Edit2: Osu! Settings are 1920x1080, Fullscreen Letterbox(0,0). Framerate: Unlimited. Snaking Sliders, Background Video, Storyboards, Combobursts activated. 80% background dim. Ignore all beatmap skins and use skin's sound samples.
Edit3: VSync does not change the effect.
Edit4: gl_info: http://pastebin.com/hkhQgGyK
This problem only happens on this beatmap as far as I'm aware.
Edit5: Problem seems worse when you have transparent hit300s.
Edit6: Cannot replicate anymore, most likely due to the transparent fix.
Edit7: It is back.
I have tried that map and I don't get any drop performance or memory/GPU usage drop. Usually, this type of drops are caused because of the GPU drivers.Quiesce wrote: 2q6dl
On this beatmap,
Trakker - Trail of Dust
At 00:35:00 to 02:00:00 (roughly), there is heavy frame lag. I investigated in MSI Afterburner and found that at roughly the same time when the FPS drops, the memory usage drops as well. When the frame rate recovers, so does too the memory. Will do more testing with other skins. I notice this problem is more pronounced when it's the first time playing the beatmap on your session of osu!.
Edit1: Skin does not matter. Tried with 2 different skins and the default skin, each replicate the problem almost exactly.
FPS seems to drop to 60, meaning the problem can only be noticed when you have a higher framerate monitor. In my case I have a 144hz monitor.
Maybe could be nice to provide your gl_info.
My gl_info
A minor issue that I've noticed:
Whenever switching from song select to in-game and whenever pausing (there may be other triggers too), the bottom right triangle of the overlay flashes white. I'm assuming it's the overlay texture, it might be the background.
In other words, a triangle that covers the bottom right corner of the screen appears for about one frame.
Whenever switching from song select to in-game and whenever pausing (there may be other triggers too), the bottom right triangle of the overlay flashes white. I'm assuming it's the overlay texture, it might be the background.
In other words, a triangle that covers the bottom right corner of the screen appears for about one frame.
Sounds like it's the same as what is said here: p/4434938Lemmmy wrote: 4c6o4s
A minor issue that I've noticed:
Whenever switching from song select to in-game and whenever pausing (there may be other triggers too), the bottom right triangle of the overlay flashes white. I'm assuming it's the overlay texture, it might be the background.
In other words, a triangle that covers the bottom right corner of the screen appears for about one frame.
The hitcircleoverlay of sliders is now showing up during the fail animation.
Current behaviour from my debug build.
Beta build
Also there is something that seems weird that happens in both builds and maybe stable as well is that hitobjects that are immediately in front of the place you died just suddenly disappear while later objects just appear and fall until the end of the animation. It looks quite unusual since the object goes from clearly visible to gone immediately. You can see what I mean just by trying to replicate this issue.
Here is the map I used to test with.
https://osu-ppy-sh.tvgratuite.org/b/652793
I used sudden death and decided to miss the note after 00:03:480 (3) - .
Current behaviour from my debug build.
Beta build
Also there is something that seems weird that happens in both builds and maybe stable as well is that hitobjects that are immediately in front of the place you died just suddenly disappear while later objects just appear and fall until the end of the animation. It looks quite unusual since the object goes from clearly visible to gone immediately. You can see what I mean just by trying to replicate this issue.
Here is the map I used to test with.
https://osu-ppy-sh.tvgratuite.org/b/652793
I used sudden death and decided to miss the note after 00:03:480 (3) - .
Could it be just the object dissappearing because you missed it (didn't click on it)? Because if you don't click on an object it will dissappear.TheVileOne wrote: p102h
Also there is something that seems weird that happens in both builds and maybe stable as well is that hitobjects that are immediately in front of the place you died just suddenly disappear while later objects just appear and fall until the end of the animation. It looks quite unusual since the object goes from clearly visible to gone immediately. You can see what I mean just by trying to replicate this issue.
By the way, you didn't actually link the beatmap. (Or I'm blind.)
Regarding the hitcircleoverlay thingy, maybe it could be caused because of the new sliderstartcircle, sliderstartcircleoverlay, etc., but I don't actually know.
Fixed.Trosk- wrote: 6k5648
Could it be just the object dissappearing because you missed it (didn't click on it)?TheVileOne wrote: p102h
Also there is something that seems weird that happens in both builds and maybe stable as well is that hitobjects that are immediately in front of the place you died just suddenly disappear while later objects just appear and fall until the end of the animation. It looks quite unusual since the object goes from clearly visible to gone immediately. You can see what I mean just by trying to replicate this issue.
By the way, you didn't actually link the beatmap. (Or I'm blind.)
It's weird, because the objects themselves don't disappear, just the overlay sprites do. A slider body remains visible, but it's combo number and now the hitcircle overlay sprite just suddenly disappear entirely. It doesn't fade out at all. It only happens to the object right in front of the failure as later sprites stay visible the entire time.
Oh.. then that's a different story. I thought you were saying that the whole object dissappears.TheVileOne wrote: p102h
It's weird, because the objects themselves don't disappear, just the overlay sprites do. A slider body remains visible, but it's combo number and now the hitcircle overlay sprite just suddenly disappear entirely. It doesn't fade out at all. It only happens to the object right in front of the failure as later sprites stay visible the entire time.
I don't actually know what to think about this to be honest.
It might be related to failing, but I'm not sure. The note that causes the failure just disappears, which is okay I guess. But the spriteoverlay of the slider after this object is disappearing too. Seems to be just how the fail animation works. It clears objects immediately after, but keeps objects that are a certain distance away, but it can just suddenly get rid of the objects.
Are you getting a crash message, error or something? If so, could you copy and paste the crashlog here?ZirexY wrote: 6yo69
Not sure if this has been resolved or not already, every time i finish playing a beatmap or watching a replay, my osu! crashes(This only happens on cutting edge, i can play fine on other release streams.)
No crash log or message, the screen goes black and windows tells me osu! has stopped working. Then it closes and i have to reopen it.Trosk- wrote: 6k5648
Are you getting a crash message, error or something? If so, could you copy and paste the crashlog here?ZirexY wrote: 6yo69
Not sure if this has been resolved or not already, every time i finish playing a beatmap or watching a replay, my osu! crashes(This only happens on cutting edge, i can play fine on other release streams.)
Did you already try to update your graphics drivers? Chances are they are causing this.ZirexY wrote: 6yo69
Not sure if this has been resolved or not already, every time i finish playing a beatmap or watching a replay, my osu! crashes(This only happens on cutting edge, i can play fine on other release streams.)
I updated them the other day, could just be the cutting edge doesn't agree with my toaster.Tom94 wrote: 56z3w
Did you already try to update your graphics drivers? Chances are they are causing this.ZirexY wrote: 6yo69
Not sure if this has been resolved or not already, every time i finish playing a beatmap or watching a replay, my osu! crashes(This only happens on cutting edge, i can play fine on other release streams.)
I haven't used cutting edge in a few months, but it crashed for me then as well. I tried it just a second ago, and it crashes after beatmaps.Tom94 wrote: 56z3w
I just re-read your first post. How can you be "not sure" if this has been resolved already? When did you last test? Please test now and make sure it's still happening.
Sure that beta doesn't crash for you, too, then? Or did you test that a few months ago, too?
Thing is, a few months ago, there was nothing especially new on cutting edge. Your graphics card is most likely being overtaxed if you had crashes even back then, so try to use an FPS limiter within osu! and see if that helps, please.
Thing is, a few months ago, there was nothing especially new on cutting edge. Your graphics card is most likely being overtaxed if you had crashes even back then, so try to use an FPS limiter within osu! and see if that helps, please.
Beta is running just fine for me, i'll try the FPS limiter and get back to you!Tom94 wrote: 56z3w
Sure that beta doesn't crash for you, too, then? Or did you test that a few months ago, too?
Thing is, a few months ago, there was nothing especially new on cutting edge. Your graphics card is most likely being overtaxed if you had crashes even back then, so try to use an FPS limiter within osu! and see if that helps, please.
If you run osu://spectate/Reesespuffs in your browser while osu! is closed it will not able able to spectate that person unless you hit F9 (to bring up the extended chat) or have that person on your friend's list already. Otherwise you'll keep getting a "The is not currently online" error. VeilStar was saying that the problem possibly might be presence.db?
ReesesPuffs wrote: 3e6q9
If you run osu://spectate/Reesespuffs in your browser while osu! is closed it will not able able to spectate that person unless you hit F9 (to bring up the extended chat) or have that person on your friend's list already. Otherwise you'll keep getting a "The is not currently online" error. VeilStar was saying that the problem possibly might be presence.db?
Please your _id instead of name.
^ Auto can fail on some ridiculous maps, so that's not really a bug. It's also not exclusive to cuttingedge.
Speaking of bugs, though: osu! hard crashes with a windows "osu! has stopped working" popup when playing super ridiculous maps that cause osu! to drop below 1 FPS (example map). In Stable, the map eventually does complete, so I'd still consider this a regression.
Speaking of bugs, though: osu! hard crashes with a windows "osu! has stopped working" popup when playing super ridiculous maps that cause osu! to drop below 1 FPS (example map). In Stable, the map eventually does complete, so I'd still consider this a regression.
Event Viewer log
Application: osu!.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at OpenTK.Graphics.ES20.GL.CopyTexImage2D(OpenTK.Graphics.ES20.TextureTarget2d, Int32, OpenTK.Graphics.ES20.TextureCopyComponentCount, Int32, Int32, Int32, Int32, Int32)
at #=q_H6qC6EFl9mIeJdJO_tLz0sIdkbzLMv1s2GRTnCn_fxFs0znQW0$TVm4aeUo2s.#=qP61m82Er3Xzl14jC2Fkd8A==()
at #=q_H6qC6EFl9mIeJdJO_tLz0sIdkbzLMv1s2GRTnCn_fxFs0znQW0$TVm4aeUo2s.#=qxqkza9JMyGGK6Yl2EjF8gg==(Boolean)
at #=q_H6qC6EFl9mIeJdJO_tLz0sIdkbzLMv1s2GRTnCn_fxFs0znQW0$TVm4aeUo2s.Dispose()
at #=quQ8gt5b006f_xQ$DBYgOLR$2K6$O2AtPbYb8_vi0geXvd9AweTsuFMWf7yoMdnOY. ()
at #=qxkncGnjLwNIX_RYeTzDiGTahObKmW5sPtFzlU9HDWn6EAhs2GX3kJtinB3ilrnZ3.#=q$RM8z20YkPvcHguSFV7Lcw==()
at #=qB4Rhvmn0r8qZNbRHkmZFqA==.#=qz3rcf1aoPp_5I5y8a88ypw==()
at #=qC_ievGvTmp$8E78o4rRIBQX7xLfFT4hTaKaiZSgaIRA=.#=qCvoanJYDBgCTRITUGgNHAg==()
at #=qC_ievGvTmp$8E78o4rRIBQX7xLfFT4hTaKaiZSgaIRA=.#=qJBoOURsJBCyBau9FefoxMw==(System.Object, System.EventArgs)
at #=qDn9184XH_7mg0W4iwIOJNW0lklQ7dOfDlD28cg8CAPfPExVx12TjQuqVeSIgEz_K.#=q3IuNrJEi6jKLZAEgQsRGxg==()
at #=qNkrrF9uoy2bTyhfQ6OYBUwzIduEi9k2$Fu34k_EbPpTJFR7LHRUmE$oTH3cCjU1w.#=qR6sNcN3CHhTHAL7db9OVXinQsTbnmS5Wj4BFxmIB2Zo=(System.Object, System.EventArgs)
at System.Windows.Forms.Application+ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32)
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application.Run(System.Windows.Forms.Form)
at #=qNkrrF9uoy2bTyhfQ6OYBUwzIduEi9k2$Fu34k_EbPpTJFR7LHRUmE$oTH3cCjU1w.#=qBY9CKqUKssueoUv_EtvQtA==()
at #=qC_ievGvTmp$8E78o4rRIBQX7xLfFT4hTaKaiZSgaIRA=.#=qBY9CKqUKssueoUv_EtvQtA==()
at #=qhkUBwUvBEyWPy7L9B3BjEA==.#=qPb6N69oxtNkcXrLci7qEkw==(System.String, Boolean, Boolean, Boolean)
at #=qhkUBwUvBEyWPy7L9B3BjEA==.#=qt_3TT5LatVdJACiyU8TAXg==(System.String[])
at #=qhkUBwUvBEyWPy7L9B3BjEA==.#=qBKaWNIGqVe8LcJ04S66Q==()
at #=qBDg47fKHtQF_u7pMKEQM9tuZJqmayDk9$4mg_BsxaAI=.#=q0ucUxoLhKfBD8Afru_ga9w==()
Multi seems to be bugged. I tried twice to start a multiplayer match with someone (https://osu-ppy-sh.tvgratuite.org/s/186911 with EZ on and freemod not enabled). The first time, my osu! window went black and the multiplayer game went without me. I had to close osu! through the task manager becuase I couldn't find a way to close it manually. The second time, both of our osu! windows went black. We were both using cutting-edge.
Hi there 
i dunno how to explain this but i have a problem with cuttingedge build T.T Maybe it just me or anyone have experienced this but my problem is "Screen goes blank if a skin didn't have an SD element..."
Here how to replicate it:
- Make sure you have skin without SD element then open osu! and aply the skin
- Go to options and change your screen to maximum size first (if your maximum screen is 1366x768 this will not work) then enable fullscreen and letterboxing and re-size the screen again to 1024x768 or 800x600
- Make sure you do the step one and go to song selection... TADA!!!!!!! my screen blank -_-
From what i know osu! force me to use external SD element and that's make my osu! goes blank rather than using default/internal SD element.
Sorry for my bad english T.T and hope this gonna fix soon because i din't make any skin in SD element
EDIT: here the log
i dunno how to explain this but i have a problem with cuttingedge build T.T Maybe it just me or anyone have experienced this but my problem is "Screen goes blank if a skin didn't have an SD element..."Here how to replicate it:
- Make sure you have skin without SD element then open osu! and aply the skin
- Go to options and change your screen to maximum size first (if your maximum screen is 1366x768 this will not work) then enable fullscreen and letterboxing and re-size the screen again to 1024x768 or 800x600
- Make sure you do the step one and go to song selection... TADA!!!!!!! my screen blank -_-
From what i know osu! force me to use external SD element and that's make my osu! goes blank rather than using default/internal SD element.
Sorry for my bad english T.T and hope this gonna fix soon because i din't make any skin in SD element
EDIT: here the log
System.NullReferenceException: Object reference not set to an instance of an object.
at #=qwh_dl9jju5wI0R7F6bEZo4Ns2dsbaAZ$udNzTavE1Vo=.#=qsIRl8HF1xTAZLRXKChA9O2zaZi4jo4wMVF133cJ5VVo=()
at #=qwh_dl9jju5wI0R7F6bEZo4Ns2dsbaAZ$udNzTavE1Vo=..ctor(#=qhYhzB9x6rYCsxV7_hqgCXnZChdWSjS6KcaVjcSYuGP0= #=q4fDiay2ixkqNYhy6Z$URjA==, #=qIDqqDiL9srB2h0NLvNJMEol7_7wMzVrRtY5cjcFWQ= #=qld7DexQzvNuMoywMqZbKdw==, Origins #=qnBIkSbxjhfkka9a57TuL0w==, #=qIDqqDiL9srB2h0NLvNJFlBLHS_nXahEWqy5c$B6jc= #=q4rjQXEOZN8HQmBpj76RiKQ==, Vector2 #=qsf03KAVFJ8axYJy0XADnAw==, Single #=qOZPqn_fu4PSYJzC8LrSM2w==, Boolean #=qjYtTGuXT79$zco5G4VVcIg==, Color #=qkdMlapmqOTY06z2NoK4VJg==, Object #=qRiAeB0MALS5$KPXSk94QQA==)
at #=qv9H6rDsgoR4iFRgLZjD_gGjJu9WE0zkzeHMO4HJOAIc=..ctor(Vector2 #=qH6W$8sEUrg_e2XkTj8T5cA==, Mods[] #=q$76sBrXTKWEGkzTC_Bp4YQ==)
at #=qFa1Y8zdgXAQxB73Xwb_Fpi$OYiUFajOK9ZGQm8Zip2HV1A_9ZP8JiTLZwn__gr..ctor(#=qqILcVcUzXV0e2P5GuqR0IdD2OsdplE8H7CJtrJ9gFJS1o5z$tri85U9PfHv9FFdj #=qv6aHlJf8oAT$jk6dL0xqEA==)
at #=qCdnCeVqZYCIkYbAu7yDBIG6S91EmZjW8kq$TyzxUvLZuV8Fs3DsUNDgQVk$k4a45.#=qId$sl6Qldo2WiXfCffdJd1_KG1V6ixHoE1DHRENGvpc=(Object #=qGnUBuicG_jHgS_JGZgbakQ==, EventArgs #=qdFCss9O2xxED8OnY_fOdHw==)
at #=qs8x1YAKIIMbcxnvrwxKnCnSyZ1Jsl1YxAnUYcBFJXp4=.#=qPba5CF3peUadaCSolrmyHA==(Boolean #=qiqDUu1bgNXFiWLpJNTqSWw==)
at #=qtc5RGLsmFg8NlHJ9$XCdG569q1ivs$sijEziFVI2kS_ySan9msi$N32U9ECSWvWq.#=qiUOwYyOGh2iQCsGRlTbiKQ==(Boolean #=qmOcZ0qL7$fc6rCgDZaSR3Q==)
at #=qtc5RGLsmFg8NlHJ9$XCdG569q1ivs$sijEziFVI2kS_ySan9msi$N32U9ECSWvWq.#=qQigzqCfNDu6_NCd_1u4uDQ==(Boolean #=qmOcZ0qL7$fc6rCgDZaSR3Q==)
at #=qAockle7h5yHf6FaKqnxXRj0Q7rOR5w58xcxBxjqmN1g_V$DVy6gSQws0TQ0RoMn5.#=qd6VfwAOAmVuOqwRZTaZp$Q==()
at #=q_sakg1jmXpWP9p3bPbqWByBTBQuIYibKJLFS_i_Wdfs=.#=qmZeib3f9txGoaVF463UZLA==()
at #=qs4t3_C4j4WxxHYOvfRQkvw==.#=qOp$krqg_WfFlXmBR2svGeQ==()
at #=qCxbBjeaun_eXJoMUHOfH$IElRKu9ogMvSj5NlZ5RY=.#=qFJm9EyNFRZChpDmkSH0dlA==()
at #=qCxbBjeaun_eXJoMUHOfH$IElRKu9ogMvSj5NlZ5RY=.#=qHnXQmLCtK0C$o$CYDNJhng==(Object #=qGnUBuicG_jHgS_JGZgbakQ==, EventArgs #=qdFCss9O2xxED8OnY_fOdHw==)
at #=q4YTDIaMCMu_vs$FsiEaQYLYLw2ITTuvbWqr6Ku7Mu_Ib8Y9ro17oJLaCv4o7uCMr.#=q7ION9qSKRBE2XWL6Ul_JBQ==()
at #=qjduyf0ZT3QE2XPAMsMpVujl96VaoJoiyi9xnCApTUsHuAlFql$B3d1_dpxX3C2Ar.#=qrlk8wKPldYGnvrkJ6seiAbO9svKl1acLbYD5RUhk3xo=(Object #=qGnUBuicG_jHgS_JGZgbakQ==, EventArgs #=qdFCss9O2xxED8OnY_fOdHw==)
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 #=qjduyf0ZT3QE2XPAMsMpVujl96VaoJoiyi9xnCApTUsHuAlFql$B3d1_dpxX3C2Ar.#=q25qGlGy5onJoSJYpbbgmTw==()
at #=qCxbBjeaun_eXJoMUHOfH$IElRKu9ogMvSj5NlZ5RY=.#=q25qGlGy5onJoSJYpbbgmTw==()
at #=qfsBR1LcaSgOF3SfgFKKibA==.#=qEpe0BQk62z_xg7F0ULzgSg==(String #=q8SjgbJh6yGBD$7q3Wc5F6g==, Boolean #=qbnsg74hxZuGeJNTXkCQJqUHsOXwu_$64zENyvGkuSlY=, Boolean #=q_7VSw6fxfx8tsy1Nu72v2Wp5m$F9w$6y1WILOxekVLU=, Boolean #=qHlJCW6ooxZSn$jrXy3OjHA==)
Can replicate... After the crash you can run osu! again with the same skin without getting the crash, but the thing of it crashing by changing the resolution seems to not be ok at all.-Chitose- wrote: 42q12
StuffHi there
Here how to replicate it:
- Make sure you have skin without SD element then open osu! and aply the skin
- Go to options and change your screen to maximum size first (if your maximum screen is 1366x768 this will not work) then enable fullscreen and letterboxing and re-size the screen again to 1024x768 or 800x600
- Make sure you do the step one and go to song selection... TADA!!!!!!! my screen blank -_-
From what i know osu! force me to use external SD element and that's make my osu! goes blank rather than using default/internal SD element.
Sorry for my bad english T.T and hope this gonna fix soon because i din't make any skin in SD element
EDIT: here the log
System.NullReferenceException: Object reference not set to an instance of an object.
at #=qwh_dl9jju5wI0R7F6bEZo4Ns2dsbaAZ$udNzTavE1Vo=.#=qsIRl8HF1xTAZLRXKChA9O2zaZi4jo4wMVF133cJ5VVo=()
at #=qwh_dl9jju5wI0R7F6bEZo4Ns2dsbaAZ$udNzTavE1Vo=..ctor(#=qhYhzB9x6rYCsxV7_hqgCXnZChdWSjS6KcaVjcSYuGP0= #=q4fDiay2ixkqNYhy6Z$URjA==, #=qIDqqDiL9srB2h0NLvNJMEol7_7wMzVrRtY5cjcFWQ= #=qld7DexQzvNuMoywMqZbKdw==, Origins #=qnBIkSbxjhfkka9a57TuL0w==, #=qIDqqDiL9srB2h0NLvNJFlBLHS_nXahEWqy5c$B6jc= #=q4rjQXEOZN8HQmBpj76RiKQ==, Vector2 #=qsf03KAVFJ8axYJy0XADnAw==, Single #=qOZPqn_fu4PSYJzC8LrSM2w==, Boolean #=qjYtTGuXT79$zco5G4VVcIg==, Color #=qkdMlapmqOTY06z2NoK4VJg==, Object #=qRiAeB0MALS5$KPXSk94QQA==)
at #=qv9H6rDsgoR4iFRgLZjD_gGjJu9WE0zkzeHMO4HJOAIc=..ctor(Vector2 #=qH6W$8sEUrg_e2XkTj8T5cA==, Mods[] #=q$76sBrXTKWEGkzTC_Bp4YQ==)
at #=qFa1Y8zdgXAQxB73Xwb_Fpi$OYiUFajOK9ZGQm8Zip2HV1A_9ZP8JiTLZwn__gr..ctor(#=qqILcVcUzXV0e2P5GuqR0IdD2OsdplE8H7CJtrJ9gFJS1o5z$tri85U9PfHv9FFdj #=qv6aHlJf8oAT$jk6dL0xqEA==)
at #=qCdnCeVqZYCIkYbAu7yDBIG6S91EmZjW8kq$TyzxUvLZuV8Fs3DsUNDgQVk$k4a45.#=qId$sl6Qldo2WiXfCffdJd1_KG1V6ixHoE1DHRENGvpc=(Object #=qGnUBuicG_jHgS_JGZgbakQ==, EventArgs #=qdFCss9O2xxED8OnY_fOdHw==)
at #=qs8x1YAKIIMbcxnvrwxKnCnSyZ1Jsl1YxAnUYcBFJXp4=.#=qPba5CF3peUadaCSolrmyHA==(Boolean #=qiqDUu1bgNXFiWLpJNTqSWw==)
at #=qtc5RGLsmFg8NlHJ9$XCdG569q1ivs$sijEziFVI2kS_ySan9msi$N32U9ECSWvWq.#=qiUOwYyOGh2iQCsGRlTbiKQ==(Boolean #=qmOcZ0qL7$fc6rCgDZaSR3Q==)
at #=qtc5RGLsmFg8NlHJ9$XCdG569q1ivs$sijEziFVI2kS_ySan9msi$N32U9ECSWvWq.#=qQigzqCfNDu6_NCd_1u4uDQ==(Boolean #=qmOcZ0qL7$fc6rCgDZaSR3Q==)
at #=qAockle7h5yHf6FaKqnxXRj0Q7rOR5w58xcxBxjqmN1g_V$DVy6gSQws0TQ0RoMn5.#=qd6VfwAOAmVuOqwRZTaZp$Q==()
at #=q_sakg1jmXpWP9p3bPbqWByBTBQuIYibKJLFS_i_Wdfs=.#=qmZeib3f9txGoaVF463UZLA==()
at #=qs4t3_C4j4WxxHYOvfRQkvw==.#=qOp$krqg_WfFlXmBR2svGeQ==()
at #=qCxbBjeaun_eXJoMUHOfH$IElRKu9ogMvSj5NlZ5RY=.#=qFJm9EyNFRZChpDmkSH0dlA==()
at #=qCxbBjeaun_eXJoMUHOfH$IElRKu9ogMvSj5NlZ5RY=.#=qHnXQmLCtK0C$o$CYDNJhng==(Object #=qGnUBuicG_jHgS_JGZgbakQ==, EventArgs #=qdFCss9O2xxED8OnY_fOdHw==)
at #=q4YTDIaMCMu_vs$FsiEaQYLYLw2ITTuvbWqr6Ku7Mu_Ib8Y9ro17oJLaCv4o7uCMr.#=q7ION9qSKRBE2XWL6Ul_JBQ==()
at #=qjduyf0ZT3QE2XPAMsMpVujl96VaoJoiyi9xnCApTUsHuAlFql$B3d1_dpxX3C2Ar.#=qrlk8wKPldYGnvrkJ6seiAbO9svKl1acLbYD5RUhk3xo=(Object #=qGnUBuicG_jHgS_JGZgbakQ==, EventArgs #=qdFCss9O2xxED8OnY_fOdHw==)
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 #=qjduyf0ZT3QE2XPAMsMpVujl96VaoJoiyi9xnCApTUsHuAlFql$B3d1_dpxX3C2Ar.#=q25qGlGy5onJoSJYpbbgmTw==()
at #=qCxbBjeaun_eXJoMUHOfH$IElRKu9ogMvSj5NlZ5RY=.#=q25qGlGy5onJoSJYpbbgmTw==()
at #=qfsBR1LcaSgOF3SfgFKKibA==.#=qEpe0BQk62z_xg7F0ULzgSg==(String #=q8SjgbJh6yGBD$7q3Wc5F6g==, Boolean #=qbnsg74hxZuGeJNTXkCQJqUHsOXwu_$64zENyvGkuSlY=, Boolean #=q_7VSw6fxfx8tsy1Nu72v2Wp5m$F9w$6y1WILOxekVLU=, Boolean #=qHlJCW6ooxZSn$jrXy3OjHA==)
Also, I noticed that if you start the game on a resolution lower than xxxxX800, and then you change to a higher resolution, the @2x elements will not be loaded until you refresh the skin.
Crashlog.
System.NullReferenceException: Object reference not set to an instance of an object.
at #=qrrdseSQXLNHFZZETWlA4jemNoZKxFC_lOlcg1$Kocnk=.#=qjLv5VKtX$F_7aSFABbE0dcfLafuq8Do$qTnKQXZ9U=()
at #=qrrdseSQXLNHFZZETWlA4jemNoZKxFC_lOlcg1$Kocnk=.#=q8GWIrDSAg_Qql46JQrElQQ==()
at #=qrcichG30zBtt_G6yILwABw==.#=qcu$3dzRLIdl5dzh7ZyMShQ==()
at #=qT$dqKCvtgrcwXFmhfHQ2ezJoqBUEvKeXP3FiI7KUEVo=.#=qrNydkoy6UCVUHHahuohIOQ==()
at #=qT$dqKCvtgrcwXFmhfHQ2ezJoqBUEvKeXP3FiI7KUEVo=.#=qkhzONiOEcisl_uMRyjmUNw==(Object #=qS4qw8e6D3aPRvECK91OAtQ==, EventArgs #=qUxZU$LYqSjV_qdSIjiq3Aw==)
at #=qTK3t1vpxOpD4Xv5jz84hIeMoy3uid8d1NyuoOqgA_Gonvga1vPjXCjEuDX7o$96R.#=qcgtKVA3BSGP$fqYyfMCEzw==()
at #=qCmfq2BCbj9Crp0WvKzvWvcw0fcbUXNH91XgVGUbbbcvUOJ0iAUg4pmanRrVjtUPC.#=q2qBOCIKHVbZT4hlXb4NSx2uDFAXFY00moS3nPhbgPYU=(Object #=qS4qw8e6D3aPRvECK91OAtQ==, EventArgs #=qUxZU$LYqSjV_qdSIjiq3Aw==)
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 #=qCmfq2BCbj9Crp0WvKzvWvcw0fcbUXNH91XgVGUbbbcvUOJ0iAUg4pmanRrVjtUPC.#=qJy1JVYxnALYVr3vRIjlJKA==()
at #=qT$dqKCvtgrcwXFmhfHQ2ezJoqBUEvKeXP3FiI7KUEVo=.#=qJy1JVYxnALYVr3vRIjlJKA==()
at #=qk483M0qEmAbdGLoF$Hys_g==.#=qFCdFHMCh6UklljivWuNDwA==(String #=qcgL9nlH78iEvM$DYZweRHg==, Boolean #=qdCHS8sYKMSQa2Lq71aKmuwTutZJlJfNJBBFN49PqO2g=, Boolean #=qSNiCQML2zAz$uPGVjF4eQAfr0SpahAS487sWFVSqvg0=, Boolean #=qczTZgXypGYAM3hZF_Xk2xA==)
In response to yesterday, this issue remains in cutting edge and after the latest update, it crashes in beta as well, even with a frame limiter. I have a feeling it might be my video card thoughZirexY wrote: 6yo69
Beta is running just fine for me, i'll try the FPS limiter and get back to you!Tom94 wrote: 56z3w
Sure that beta doesn't crash for you, too, then? Or did you test that a few months ago, too?
Thing is, a few months ago, there was nothing especially new on cutting edge. Your graphics card is most likely being overtaxed if you had crashes even back then, so try to use an FPS limiter within osu! and see if that helps, please.
GL Version: OpenGL ES 2.0 (ANGLE 2.1.0.8afe1e1b8397)Tom94 wrote: 56z3w
Can you please post gl_info.txt which you can find in your osu! folder? Please also try the new "Compatibility mode" option and see if it helps with the crashes.
GL Renderer: ANGLE (NVIDIA GeForce 6150SE nForce 430 Direct3D9Ex vs_3_0 ps_3_0)
GL Shader Language version: OpenGL ES GLSL ES 1.00 (ANGLE 2.1.0.8afe1e1b8397)
GL Vendor: Google Inc.
GL Extensions: GL_OES_element_index_uint GL_OES_packed_depth_stencil GL_OES_get_program_binary GL_OES_rgb8_rgba8 GL_EXT_texture_format_BGRA8888 GL_EXT_read_format_bgra GL_OES_texture_half_float GL_OES_texture_float GL_EXT_texture_compression_dxt1 GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_EXT_texture_storage GL_OES_texture_npot GL_EXT_texture_filter_anisotropic GL_EXT_occlusion_query_boolean GL_NV_fence GL_EXT_robustness GL_EXT_blend_minmax GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_pack_reverse_row_order GL_OES_standard_derivatives GL_EXT_shader_texture_lod GL_EXT_frag_depth GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_EXT_debug_marker
GL Context: Index: 101762020, Color: 32 (8888), Depth: 16, Stencil: 0, Samples: 0, Accum: 0 (0000), Buffers: 2, Stereo: False
Will do, thanks for the help!Tom94 wrote: 56z3w
Awesome. My best guess is that your (old) graphics card and corresponding drivers don't OpenGL 2.0 properly which is required with our most recent advances in the rendering engine. Compatibility mode doesn't need that new . Let me know if you have any further issues.
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.
- Use ANGLE if the GL context fails to create/validate. (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.
- Fix crash when starting a game. (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.
This happens to me as well on every multi match I , I get a crashlog after quitting from the black screen.GhostFrog wrote: 4e5a4q
Multi seems to be bugged. I tried twice to start a multiplayer match with someone (https://osu-ppy-sh.tvgratuite.org/s/186911 with EZ on and freemod not enabled). The first time, my osu! window went black and the multiplayer game went without me. I had to close osu! through the task manager becuase I couldn't find a way to close it manually. The second time, both of our osu! windows went black. We were both using cutting-edge.
It happens with and without compatibility mode and default skin.
System.NullReferenceException: Object reference not set to an instance of an object.OS: Windows 10
at #=qHtHzwYEjfz7AA4RvQgBRTt_qoDd3X60alRj1YMS3ouY=.#=qkpfcdgIAzzJsuE7pUPWvnn_MsbOKPSbZXPqV2olLqKQ=()
at #=qHtHzwYEjfz7AA4RvQgBRTt_qoDd3X60alRj1YMS3ouY=.#=qRLWLl6ApwsHO1GyXufMylA==(Boolean #=qTIbwRcwSlHB1DRIudzC6JA==)
at #=qrcichG30zBtt_G6yILwABw==.#=qeyvGG0p$NNbEPhdFzQ7SAQ==(Int32 #=qORmpExzBuVEZL1B$VspXUg==)
at #=qrcichG30zBtt_G6yILwABw==.#=qj7ToMKs3Yxnlh7H5neiOOg==(Object #=qaU4BCwLo_0jvjqLQI5wc$w==, EventArgs #=q3yeKVymRYmRVUP0llRP_dQ==)
at #=qrcichG30zBtt_G6yILwABw==.#=qlQ9hiN3H7DfOKv6Z$Jx_uI2Uu10K8yXuY6A4Ka9fKsk=()
at #=qrcichG30zBtt_G6yILwABw==.#=qcu$3dzRLIdl5dzh7ZyMShQ==()
at #=qT$dqKCvtgrcwXFmhfHQ2ezJoqBUEvKeXP3FiI7KUEVo=.#=qrNydkoy6UCVUHHahuohIOQ==()
at #=qT$dqKCvtgrcwXFmhfHQ2ezJoqBUEvKeXP3FiI7KUEVo=.#=qkhzONiOEcisl_uMRyjmUNw==(Object #=qS4qw8e6D3aPRvECK91OAtQ==, EventArgs #=qUxZU$LYqSjV_qdSIjiq3Aw==)
at #=qTK3t1vpxOpD4Xv5jz84hIeMoy3uid8d1NyuoOqgA_Gonvga1vPjXCjEuDX7o$96R.#=qcgtKVA3BSGP$fqYyfMCEzw==()
at #=qCmfq2BCbj9Crp0WvKzvWvcw0fcbUXNH91XgVGUbbbcvUOJ0iAUg4pmanRrVjtUPC.#=q2qBOCIKHVbZT4hlXb4NSx2uDFAXFY00moS3nPhbgPYU=(Object #=qS4qw8e6D3aPRvECK91OAtQ==, EventArgs #=qUxZU$LYqSjV_qdSIjiq3Aw==)
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 #=qCmfq2BCbj9Crp0WvKzvWvcw0fcbUXNH91XgVGUbbbcvUOJ0iAUg4pmanRrVjtUPC.#=qJy1JVYxnALYVr3vRIjlJKA==()
at #=qT$dqKCvtgrcwXFmhfHQ2ezJoqBUEvKeXP3FiI7KUEVo=.#=qJy1JVYxnALYVr3vRIjlJKA==()
at #=qk483M0qEmAbdGLoF$Hys_g==.#=qFCdFHMCh6UklljivWuNDwA==(String #=qcgL9nlH78iEvM$DYZweRHg==, Boolean #=qdCHS8sYKMSQa2Lq71aKmuwTutZJlJfNJBBFN49PqO2g=, Boolean #=qSNiCQML2zAz$uPGVjF4eQAfr0SpahAS487sWFVSqvg0=, Boolean #=qczTZgXypGYAM3hZF_Xk2xA==)
GPU: Nvidia GTX 780Ti
U: Intel Core i7 2600K
Exact same issue here. As soon as a map starts on MP, my screen goes black. I can still press F9, and I hear the sound of the chat opening, but nothing appears.theguy159 wrote: 4p2z6o
This happens to me as well on every multi match I , I get a crashlog after quitting from the black screen.GhostFrog wrote: 4e5a4q
Multi seems to be bugged. I tried twice to start a multiplayer match with someone (https://osu-ppy-sh.tvgratuite.org/s/186911 with EZ on and freemod not enabled). The first time, my osu! window went black and the multiplayer game went without me. I had to close osu! through the task manager becuase I couldn't find a way to close it manually. The second time, both of our osu! windows went black. We were both using cutting-edge.
It happens with and without compatibility mode and default skin.
OS: Windows 10
GPU: Nvidia GTX 780Ti
U: Intel Core i7 2600K
When I use the frame limiter, and let the dialog disappear, and then use frame limiter again and spam it the previous dialogs will stay a lot longer than usual.
Well I think you can see what happens
Another thing: Whenever the game is alt-tabbed for a while the cursor trail becomes different (video). Very minor thing
http://puu.sh/jPoOA/6b0591fd05.mp4
I just noticed the new update (like, it just appeared when I made the video), sorry if it has been fixed now (the frame limiter thing hasn't though)
Well I think you can see what happens
Another thing: Whenever the game is alt-tabbed for a while the cursor trail becomes different (video). Very minor thing
http://puu.sh/jPoOA/6b0591fd05.mp4
I just noticed the new update (like, it just appeared when I made the video), sorry if it has been fixed now (the frame limiter thing hasn't though)