Does turning off Shaders in the options menu help? If not, does enabling the compatibility mode help?
forum
[Archived] Issues with Latest Cutting-edge Build (Post Here) 5z1i67
posted
Total Posts
2,521
If you put the following files into your skin, do you still crash? http://puu.sh/jDt0W/2d2b760b82.zip
(It should show you different images for 100s and 50s.)
(It should show you different images for 100s and 50s.)
Could you try ing http://www.nvidia.de/object/geforce-experience-de.html and updating your graphics card driver to the latest one? I don't see any immediate issue with the relevant code and my particular card (which is also by nVidia) does not experience such crashes.
Yesterday it was working completely fine but today i cant even see songs http://webmup.com/a71ad/vid.webm
That is completely screwed... Close osu!, hold Shift while opening osu!, select Stable release stream and click on repair osu!. Let's see if that helps. If it doesn't, probably something is screwed on your osu! installation. If it does, try to go back to Cutting Edge and see if it's still happening.Anglachel4 wrote: 2e234q
Yesterday it was working completely fine but today i cant even see songs http://webmup.com/a71ad/vid.webm
If it's happening on any release stream, probably you will need to make a new osu! installation.
in stable mode it works fine but when i choose cutting edge that happens againTrosk- wrote: 6k5648
That is completely screwed... Close osu!, hold Shift while opening osu!, select Stable release stream and click on repair osu!. Let's see if that helps. If it doesn't, probably something is screwed on your osu! installation. If it does, try to go back to Cutting Edge and see if it's still happening.Anglachel4 wrote: 2e234q
Yesterday it was working completely fine but today i cant even see songs http://webmup.com/a71ad/vid.webm
If it's happening on any release stream, probably you will need to make a new osu! installation.
Hmm, is it happening on Beta? If it is happening on Beta too, could you try to change the release stream to Cutting Edge again and enable the Compatibility mode? If you can't from inside the game (because everything is screwed) try to hold Shift while opening osu! again and enable Compatibility mode from the configuration window.Anglachel4 wrote: 2e234q
in stable mode it works fine but when i choose cutting edge that happens again
Trosk- wrote: 6k5648
Hmm, is it happening on Beta? If it is happening on Beta too, could you try to change the release stream to Cutting Edge again and enable the Compatibility mode? If you can't from inside the game (because everything is screwed) try to hold Shift while opening osu! again and enable Compatibility mode from the configuration window.Anglachel4 wrote: 2e234q
in stable mode it works fine but when i choose cutting edge that happens again
Everything is fine in beta too tried changing to cutting edge after beta but it is still like that
Deleted_4329079
Movement looks stuttery on the editor when playing a song, and I get considerably less fps while on the editor (800) than while playing (3400).
Also noticed that missing/sliderbreaking sprites are still often missing, so I can only hear the combo break sound with no visual clue of what happened but a note with no numbers at all (they just dissapear with no animation). This happens on like a 20-30% of the combo breaks. It happens on beta too, but not on stable.
Also noticed that missing/sliderbreaking sprites are still often missing, so I can only hear the combo break sound with no visual clue of what happened but a note with no numbers at all (they just dissapear with no animation). This happens on like a 20-30% of the combo breaks. It happens on beta too, but not on stable.
Is there a way to use plain ol' OpenGL now? With WINE, the new GLES+ANGLE combination is really putting a damper on everything, probably because of ANGLE. Cutting Edge has the same bad performance as Stable now since both use DirectX 
Also, why move from just straight GL to having "GLES -> ANGLE-> DirectX"? Could it possible to make it so we can switch between the two, or a switch between ANGLE and the built-in EGL or WGL libraries if you can't switch between GL and GLES? That would really help us WINE s a lot!
Also, why move from just straight GL to having "GLES -> ANGLE-> DirectX"? Could it possible to make it so we can switch between the two, or a switch between ANGLE and the built-in EGL or WGL libraries if you can't switch between GL and GLES? That would really help us WINE s a lot!
I think you're misunderstanding. We moved from OpenGL to OpenGL ES, which guaranteed more compatibility across platforms. Angle is not even activated unless you turn on compatibility mode. If you're getting worse performance, you'll need to fix your wine environment or wait for our official release on linux.aus4000 wrote: 1z62u
Is there a way to use plain ol' OpenGL now? With WINE, the new GLES+ANGLE combination is really putting a damper on everything, probably because of ANGLE. Cutting Edge has the same bad performance as Stable now since both use DirectX
Also, why move from just straight GL to having "GLES -> ANGLE-> DirectX"? Could it possible to make it so we can switch between the two, or a switch between ANGLE and the built-in EGL or WGL libraries if you can't switch between GL and GLES? That would really help us WINE s a lot!
I am having an issue, whenever I try and set my osu! to cutting edge, it doesn't it.
This is my "update_log_lastsuccess.txt"
Nothing really happens, it just stays on stable and says that osu! is up to date.
This is my "update_log_lastsuccess.txt"
8/17/2015 8:20:47 AM: Running cleanup..
8/17/2015 8:20:47 AM: Cleanup successful!
8/17/2015 8:20:47 AM: Resetting update process
8/17/2015 8:20:47 AM: CallbackStatus updated to Checking
8/17/2015 8:20:47 AM:
8/17/2015 8:20:47 AM: Beginning update thread
8/17/2015 8:20:47 AM: Stream: CuttingEdge
8/17/2015 8:20:47 AM:
8/17/2015 8:20:47 AM: Serious error occurred in update thread: System.InvalidProgramException: Common Language Runtime detected an invalid program.
at #Fe.#Ee.#nG()
at #Fe.#Ee.#R3b()
8/17/2015 8:20:47 AM: Returning NoUpdate state to caller
8/17/2015 8:20:47 AM: CallbackStatus updated to NoUpdate
Nothing really happens, it just stays on stable and says that osu! is up to date.
Difference is pretty clear though, not sure why this suddenly happens (is something changed about skin settings). Don't really know how to edit the cursor trail duration, but I disabled it for now.Trosk- wrote: 6k5648
I don't feel that effect on my skins, as well as on Default skin. Probably I'm wrong, but I think it's still the same.A Mystery wrote: 14284t
Is it just me, or is the cursor trail suddenly staying a lot longer since the very last CE update?
CE
Stable
What even though I'm subscribed to this topic it didn't tell me there was a reply
Thanks for clarifying!MillhioreF wrote: 2k1855
Due to huge particle optimizations in a recent patch, the cursor trail's length is no longer capped and can become much longer during fast movements. I see what you mean, though, and a skin.ini setting sounds pretty nice.
Yeah I would love to be able to edit it, it's really destracting to play with it now (at least to me)
@Nobot: you need to manually a new build of osu! and replace your existing one.
Here's a link: http://m1.ppy.sh/r/osu!.exe
Here's a link: http://m1.ppy.sh/r/osu!.exe
It worked! Thank you.peppy wrote: 73101g
@Nobot: you need to manually a new build of osu! and replace your existing one.
Here's a link: http://m1.ppy.sh/r/osu!.exe
That is intended I believe. t/347919
BanchoBot wrote: 5l6ig
Issue(s) in this thread have been addressed by the following changes:
The changes will be applied to builds newer than b20150818.2cuttingedge
- Fix hit error display using incorrect colour on borderline 100s. Make slider initial clicks white (they don't affect accuracy). (peppy)
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.
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
Video
Only happens in the newest cutting-edge build.
Windows 10, GTX 970 with 355.60 driver
Can't replicate and I have the same GPU with the same drivers. What are your osu! settings?Smc wrote: 4w5o6w
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
It only seems to happen once in a while, 5-10% chance or so.Trosk- wrote: 6k5648
Can't replicate and I have the same GPU with the same drivers. What are your osu! settings?Smc wrote: 4w5o6w
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
http://www.smcmax.me/s/2015-08-18_11-21-23.png
http://www.smcmax.me/s/2015-08-18_11-21-46.png
http://www.smcmax.me/s/2015-08-18_11-22-30.png
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.
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.
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.
Ok, I just had the same effect. Without Shaders tho.Smc wrote: 4w5o6w
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
Linear parts of sliders aren't selectable anymore in the editor: http://puu.sh/jGjL1/b28d6b3501.mp4
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