Yes. Read the blog post about it.
forum
[Archived] Issues with Latest Cutting-edge Build (Post Here)
posted
Total Posts
2,521
Okay thank you.peppy wrote:
Yes. Read the blog post about it.
Cutting edge beatmap submission destroys unicode in the beatmap description post.
http://puu.sh/kjrGQ/f95d105f26.png
http://puu.sh/kjrGQ/f95d105f26.png
Your discrete card won't work with cutting edge. nVidia optimus (what your laptop uses to combine discrete and integrated) doesn't support OpenGL properly. Configure your laptop to use the integrated graphics for osu! and it should run more smoothly, albeit most likely not quite at 400fps.Moosqueak wrote:
I've done a bit of experimentation on Cutting-edge, and I'm not sure that this is the right place to post this, but...
Huge lag issues:
CE (240 cap): http://puu.sh/kEzxk/49ec4c3c04.jpg
Stable w/ DX (Unlimited): http://puu.sh/kEzy5/d0c48285a8.jpg
Stable w/ OpenGL (Unlimited): http://puu.sh/kEzK6/6ae7790884.jpg
Random frame drops/lagspikes:
http://puu.sh/kEzAv/7bdd9a3dac.jpg
Lag when I switch mapsets:
http://puu.sh/kEzBK/5dd37b36d0.jpg
http://puu.sh/kEzCv/05067e1573.jpg
In addition to this, the cursor simply feels weird, as though there is mouse acceleration or some other factor messing with it. This may or may not be some form of increased input lag; I am unsure. It also happens on stable with OpenGL, but to a lesser extent than cutting edge.
Edit: I'm using an MSI Apache-012 running on the dedicated graphics card, which is a GTX 860M if I recall correctly.
So. Since a few days as soon as osu loses connection to the server the whole game freezes. Is there any fix besides exiting the process, because I am sure that someone already mentioned that.
Looks like I wasn't the only one who had 'stuttering every 5-6 seconds', which is the major reason why I'm sticking with stable for now...
Not sure where this would be posted.
Currently on experimental I'm getting 80 or so CPU usage coupled with a lot of game lag.
I'm aware it's cutting edge and there will be bugs but I'd just like to put this out there just in case the devs are not aware.
https://gyazo.com/a202cdd342cfc3f9c69057a44dec0b32
This issue is happening on this CPU, have not tested it on any others: AMD FX-8150 8 core
Currently on experimental I'm getting 80 or so CPU usage coupled with a lot of game lag.
I'm aware it's cutting edge and there will be bugs but I'd just like to put this out there just in case the devs are not aware.
https://gyazo.com/a202cdd342cfc3f9c69057a44dec0b32
This issue is happening on this CPU, have not tested it on any others: AMD FX-8150 8 core
Seems like entering the beatmap selection screen in Stable with a Cutting Edge scores database is screwing it, converting it to a .bak file. So, after that, a new database needs to be created.
-------
-------
Moved your post from Development to Help/CE thread. This is a known issue. CPU usage sometimes goes crazy since a few days ago. I guess it will be fixed soon.JHatter wrote:
Not sure where this would be posted.
Currently on experimental I'm getting 80 or so CPU usage coupled with a lot of game lag.
I'm aware it's cutting edge and there will be bugs but I'd just like to put this out there just in case the devs are not aware.
https://gyazo.com/a202cdd342cfc3f9c69057a44dec0b32
This issue is happening on this CPU, have not tested it on any others: AMD FX-8150 8 core
Problem Details: I can play the game perfectly fine, then all of a sudden, Osu takes up 100% (and keeps it there) of the CPU, thus causing my PC to lag, then in most cases, freeze, forcing me to hard shutdown.
Video or screenshot showing the problem: I cannot show a screenshot as the lagspike lags the PC too badly before I can screenshot it.
osu! version: 20151009.7cuttingedge
Video or screenshot showing the problem: I cannot show a screenshot as the lagspike lags the PC too badly before I can screenshot it.
osu! version: 20151009.7cuttingedge
I merged your post to the Cutting Edge thread. Anyways, this is known, and it's only happening in Cutting Edge. I think it's going to be fixed soon. Until that, if it's really bothering you, change to Beta or Stable.FailureAtOsu wrote:
Problem Details: I can play the game perfectly fine, then all of a sudden, Osu takes up 100% (and keeps it there) of the CPU, thus causing my PC to lag, then in most cases, freeze, forcing me to hard shutdown.
Video or screenshot showing the problem: I cannot show a screenshot as the lagspike lags the PC too badly before I can screenshot it.
osu! version: 20151009.7cuttingedge
Here is the gl_info.txt you were talking about : http://puu.sh/kF5uA/1c1e3bc337.txtTrosk- wrote:
Merged your post to the CE thread, since you are saying it is only in Beta and CE. Also, would be nice if you could provide your "gl_info.txt". You will find it in your installation folder.PixelRedstoner wrote:
Problem Details:
While playing any map, i get a random lag spike which lasts for 1 second and always makes me fail. It happens every 4-5 minutes.
This happens on beta and Cutting Edge but not on Stable.
Video or screenshot showing the problem:
http://puu.sh/kEiyx/62e130d355.jpg
EDIT: Another screenshot: http://puu.sh/kEiN8/f29e31a35f.jpg
Well, after switching to integrated, I did get some frame rate improvements, though they are still under 240 if I have anything beyond a static background. This may simply be due to the poor quality of my integrated graphics.Tom94 wrote:
Your discrete card won't work with cutting edge. nVidia optimus (what your laptop uses to combine discrete and integrated) doesn't support OpenGL properly. Configure your laptop to use the integrated graphics for osu! and it should run more smoothly, albeit most likely not quite at 400fps.
The issue is that I am still suffering from what I presume to be the aforementioned input lag(?) on my cursor, as well as the random frame drops/lagspikes, which are seemingly occurring with the same frequency.
The input lag shouldn't be noticeable assuming you play in fullscreen mode. If you see your screen flicker black for a split second while toggling fullscreen mode, then it works as expected.Moosqueak wrote:
Well, after switching to integrated, I did get some frame rate improvements, though they are still under 240 if I have anything beyond a static background. This may simply be due to the poor quality of my integrated graphics.Tom94 wrote:
Your discrete card won't work with cutting edge. nVidia optimus (what your laptop uses to combine discrete and integrated) doesn't support OpenGL properly. Configure your laptop to use the integrated graphics for osu! and it should run more smoothly, albeit most likely not quite at 400fps.
The issue is that I am still suffering from what I presume to be the aforementioned input lag(?) on my cursor, as well as the random frame drops/lagspikes, which are seemingly occurring with the same frequency.
Regarding the frame drops. Can you try closing all background applications you have open? Things like f.lux are known to cause periodic spikes.
I get a small stutter every few seconds in cutting edge. It doesn't happen on stable though, so I'm guessing it's an OpenGL problem, maybe?
Really annoying since I can't play fullscreen properly, I need letterboxing. ;_;
Really annoying since I can't play fullscreen properly, I need letterboxing. ;_;
Good call, my client somehow ended up in borderless windowed, but switching to fullscreen seems to have removed the input lag issue. After closing background programs, (firefox in this case) I did notice a considerable decrease in the frame drops. They now only occur once or twice per song, usually near the beginning, or when intense storyboard elements appear in maps that have them. Interestingly, after reopening firefox, the frame drops don't increase again, so I'm unsure as to the actual cause. All things considered, though, the game is much more playable.Tom94 wrote:
The input lag shouldn't be noticeable assuming you play in fullscreen mode. If you see your screen flicker black for a split second while toggling fullscreen mode, then it works as expected.
Regarding the frame drops. Can you try closing all background applications you have open? Things like f.lux are known to cause periodic spikes.
When the corrected finally the FPS lag after indefinite time? I have repeatedly restart the game when the red dots at the bottom right (ms Display) appears. The is always unplayable once the are there. That makes no more fun. 
3 days ago everything was fine.
3 days ago everything was fine.
Do you know if you are having a high CPU Load when you get that lag?Fatal3ty wrote:
When the corrected finally the FPS lag after indefinite time? I have repeatedly restart the game when the red dots at the bottom right (ms Display) appears. The is always unplayable once the are there. That makes no more fun.
3 days ago everything was fine.
Good to hear.Moosqueak wrote:
Good call, my client somehow ended up in borderless windowed, but switching to fullscreen seems to have removed the input lag issue. After closing background programs, (firefox in this case) I did notice a considerable decrease in the frame drops. They now only occur once or twice per song, usually near the beginning, or when intense storyboard elements appear in maps that have them. Interestingly, after reopening firefox, the frame drops don't increase again, so I'm unsure as to the actual cause. All things considered, though, the game is much more playable.
I'm sorry for the inconveniences. Sadly we can't do much about nVidia's optimus not adequately supporting OpenGL/fullscreen and the lag caused by background applications. This lag is related to how windows inherently treats DirectX windows differently from all others, making them less affected by other applications hogging GPU / desktop resources.
We do have a DirectX fallback mode called "Compatibility mode" in the options in case you absolutely want or need to use your discrete GPU and get higher FPS, but it doesn't support exclusive fullscreen and thus comes at the cost of increased input latency.
I have the latest Intel i7 and up 3 days ago everything went perfectly until it came the new update of Osu 3 days ago. Before that I had never had a problem.Trosk- wrote:
Do you know if you are having a high CPU Load when you get that lag?Fatal3ty wrote:
When the corrected finally the FPS lag after indefinite time? I have repeatedly restart the game when the red dots at the bottom right (ms Display) appears. The is always unplayable once the are there. That makes no more fun.
3 days ago everything was fine.
Sorry for English, is not my native Language.
Today I switched to cutting edge because I was planning on trying out the new score v2 system, since very few of my friends who would bother to multiplayer with me at the time were online I decided to play some solo instead, the game ran smoothly for a while but eventually started to lag to the point where I was probably getting 1 frame per 5 seconds, waiting did not resolve the issue and attempting to get to main menu to quit didn't work either. I was forced to end the process using task manager and when I reopened osu! I got a pop up telling me my local beatmap database is corrupted and needs to be recreated from scratch. I let osu! process all my beatmaps, then played a little and osu! freezes on me again, local beatmap database also corrupted again, I gave up on CE and went back to stable, processed beatmaps again, and now I notice a LOT of my local replays and scores are missing, I am missing replays from 2011-2014 and even some from 2015. As a player who has played quite a long time, looking back at old replays is similar to how adults would look back at their old photo albums. Is there anyway I can restore these replays?
Just pasteShina Kokomi wrote:
Is there anyway I can restore these replays?
FOR %I IN ("Data/r/*.osr") Do "Data/r/%I" in cmd after navigating to your osu! folder.If you don't know how to do that you could alternatively just put this batch file in your osu! folder and double-click it. (right click on the link, then select "Save Link As...", or whatever your browser calls it, to download the batch)
This should reload all your replays one by one, which will probably take some time but is the only way to do it, AFAIK.
EDIT: Make sure osu! is running before starting it, else it's only going to load one replay for each time it starts osu!.
Also, it didn't seem to work for Shina Kokomi because his osu! somehow deleted some of his replays, but after running it on a backup of his osu! folder he got them back.
thanks, i just ran that batch file but it didn't bring back the replays that i noticed were missing. It was worth trying tho.Pampel wrote:
Just pasteShina Kokomi wrote:
Is there anyway I can restore these replays?FOR %I IN ("Data/r/*.osr") Do "Data/r/%I"in cmd after navigating to your osu! folder.
If you don't know how to do that you could alternatively just put this batch file in your osu! folder and double-click it. (right click on the link, then select "Save Link As...", or whatever your browser calls it, to download the batch)
This should reload all your replays one by one, which will probably take some time but is the only way to do it, AFAIK.
its weird because i have only some 2011 replays, its like theres holes in the middle of my replay time line, missing a ton here and there for every year.
I was meaning that how is your CPU usage when the lag starts to happen. You can check it in the Task Manager.Fatal3ty wrote:
I have the latest Intel i7 and up 3 days ago everything went perfectly until it came the new update of Osu 3 days ago. Before that I had never had a problem.
Sorry for English, is not my native Language.
Hey, since newest update immediately crashes Osu once I open the Skin .osk-File. Please times fix the errors.
I have no other programs running in the background, had previously also always had. I have changed nothing there. There must be at Cutting Edge since latest update.
I have no other programs running in the background, had previously also always had. I have changed nothing there. There must be at Cutting Edge since latest update.
Problem Details: I've just finished the storyboard for ktgster's "Speed of Link" map (https://osu.ppy.sh/s/359173); the problem here is that the storyboard only shows up on the cutting-edge build, and does not show any signs of being on the stable build (except for the .osb being present). Myself, ktgster, Hula, and Spaghetti have noticed this problem.
Yes, the storyboard was made in the cutting-edge build.
Video or screenshot showing the problem: Not Needed
osu! version: b20151011cuttingedge
Yes, the storyboard was made in the cutting-edge build.
Video or screenshot showing the problem: Not Needed
osu! version: b20151011cuttingedge
i've noticed that my country flag is wrong only in the cutting edge verion (currently using b20151011).
What i mean by that is that when i select the "country" filter it shows me as a player from United States ( https://osu.ppy.sh/ss/3801400 ).
I though that maybe i could have some sort of VPN or proxy activated but doesen't seem to be be case since in the stable version it shows me as a player from Portugal ( https://osu.ppy.sh/ss/3801383 ).
I've registered in portugal and have always been playing in portugal.
IGN: beltonpaka
What i mean by that is that when i select the "country" filter it shows me as a player from United States ( https://osu.ppy.sh/ss/3801400 ).
I though that maybe i could have some sort of VPN or proxy activated but doesen't seem to be be case since in the stable version it shows me as a player from Portugal ( https://osu.ppy.sh/ss/3801383 ).
I've registered in portugal and have always been playing in portugal.
IGN: beltonpaka
Cutting edge has a fix for storyboards not being found when diff names contain [ ]. Don't use these characters if you want the storyboard to work for everyone.ComfyWolf wrote:
...
ThanksDamnae wrote:
Cutting edge has a fix for storyboards not being found when diff names contain [ ]. Don't use these characters if you want the storyboard to work for everyone.ComfyWolf wrote:
...
Well, yes, if you create a "map" with this song, you will not be able to play it and it will say "Beatmap could not beloaded successfully", but the beatmap selection screen doesn't go crazy for me. That's probably happening because your beatmap database is not in a good state.Christianabc wrote:
Video of bug: https://vimeo.com/142119013
When you first start the game, it will select the intro song. If you click enter, it will try to open it, but it will fail. You are able to edit it, but if you then try to open the edited version, your osu! will freeze / go crazy.
First time it also did that to me but now i can play the map using the test feature on the editorChristianabc wrote:
Video of bug: https://vimeo.com/142119013
When you first start the game, it will select the intro song. If you click enter, it will try to open it, but it will fail. You are able to edit it, but if you then try to open the edited version, your osu! will freeze / go crazy.
So I originally posted this a while ago:
The problem was "semi-fixed" on cuttingedge, meaning that I no longer had performance issues and could connect to bancho after waiting for some time and/or restarting osu!, but since the new cuttingedge update (20151012.5) today I can't connect to bancho at all.Bloody wrote:
Problem Details:
Connection error and performance problems (song select) in beta and cutting edge.
No problems with the current stable version (20150901)
The problem first occured on September 22nd (when bancho had some troubles, don't think this problem is related though)
I played on beta during that time so i don't know if this problem already existed on cutting edge before.
I reinstalled osu afterwards but that did not help either
Win7, NVIDIA GeForce GTX 960
Video or screenshot showing the problem:
https://youtu.be/kcaRkWkkrmI (in case the embedded video doesn't work)
osu! version: 201509024.4 (latest beta)
anything in network.log?
SPOILER
12.10.2015 13:54:27: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 failed with unknown error (retrying).
12.10.2015 13:54:30: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 failed with unknown error (retrying).
12.10.2015 13:54:37: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 failed with unknown error (retrying).
12.10.2015 13:54:42: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 complete with unknown error (retrying).
12.10.2015 13:54:43: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 complete with unknown error (retrying).
12.10.2015 13:54:43: Request to https://141.101.112.193/thumb/3756l.jpg failed with unknown error (retrying).
12.10.2015 13:54:46: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 complete with unknown error (retrying).
12.10.2015 13:54:51: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 failed with unknown error (retrying).
12.10.2015 13:55:08: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 complete with unknown error (retrying).
12.10.2015 13:55:12: Request to https://141.101.112.193/thumb/3756l.jpg complete with unknown error (retrying).
12.10.2015 13:55:33: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 failed with unknown error (retrying).
12.10.2015 13:55:54: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 complete with unknown error (retrying).
12.10.2015 13:56:10: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 13:56:15: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 13:56:31: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 13:56:36: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 13:56:57: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 13:57:18: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 13:57:22: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 13:57:34: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 13:57:39: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 13:57:39: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 13:57:45: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 13:57:51: Request to https://141.101.113.193/web/osu-error.php complete with unknown error (retrying).
12.10.2015 13:57:56: Request to https://141.101.113.193/web/osu-error.php complete with unknown error (retrying).
12.10.2015 13:58:00: Request to https://141.101.113.193/web/osu-error.php complete with unknown error (retrying).
12.10.2015 13:58:17: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 13:58:21: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 13:58:33: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 13:58:38: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 13:58:40: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 13:58:42: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 13:58:56: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 13:58:59: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 13:59:02: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 13:59:03: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 13:59:20: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 13:59:24: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 13:59:31: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 13:59:36: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 13:59:45: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 14:00:02: Request to https://141.101.112.193/ complete with unknown error (retrying).
12.10.2015 14:00:06: Request to https://141.101.113.193/thumb/128622l.jpg complete with unknown error (retrying).
12.10.2015 14:00:27: Request to https://141.101.112.193/ failed with unknown error (retrying).
12.10.2015 14:00:44: Request to https://141.101.112.193/ complete with unknown error (retrying).
12.10.2015 14:00:48: Request to https://141.101.112.193/ failed with unknown error (retrying).
12.10.2015 14:01:05: Request to https://141.101.112.193/ complete with unknown error (retrying).
12.10.2015 14:01:09: Request to https://141.101.113.193/thumb/128622l.jpg failed with unknown error (retrying).
12.10.2015 14:01:15: Request to https://141.101.112.193/ failed with unknown error (retrying).
12.10.2015 14:01:21: Request to https://141.101.112.193/ complete with unknown error (retrying).
12.10.2015 14:01:26: Request to https://141.101.113.193/thumb/128622l.jpg complete with unknown error (retrying).
12.10.2015 14:01:30: Request to https://141.101.113.193/thumb/128622l.jpg failed with unknown error (retrying).
12.10.2015 14:01:51: Request to https://141.101.113.193/thumb/152l.jpg complete with unknown error (retrying).
12.10.2015 14:02:08: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:02:12: Request to https://141.101.113.193/thumb/152l.jpg failed with unknown error (retrying).
12.10.2015 14:02:29: Request to https://141.101.113.193/thumb/152l.jpg complete with unknown error (retrying).
12.10.2015 14:02:33: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:02:54: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:03:13: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:03:15: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:03:32: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 failed with unknown error (retrying).
12.10.2015 14:03:36: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:03:57: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 complete with unknown error (retrying).
12.10.2015 14:04:18: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 failed with unknown error (retrying).
12.10.2015 14:04:35: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 complete with unknown error (retrying).
12.10.2015 14:04:39: Request to https://141.101.112.193/ failed with unknown error (retrying).
12.10.2015 14:04:56: Request to https://141.101.112.193/ complete with unknown error (retrying).
12.10.2015 14:05:00: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 failed with unknown error (retrying).
12.10.2015 14:05:17: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 14:05:21: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 14:05:38: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 14:05:42: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 14:05:59: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 14:05:59: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 14:06:03: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 14:06:15: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 14:06:20: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 14:06:24: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 14:06:45: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 14:07:06: Request to https://141.101.113.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:07:23: Request to https://141.101.113.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:07:27: Request to https://141.101.113.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:07:44: Request to https://141.101.113.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:07:48: Request to https://141.101.113.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:08:09: Request to https://141.101.113.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:08:30: Request to https://141.101.113.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:08:47: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:08:51: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:09:08: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:09:12: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:09:33: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:09:53: Request to https://141.101.113.193/ failed with unknown error (retrying).
12.10.2015 14:09:54: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:10:11: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:10:11: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:10:15: Request to https://141.101.113.193/ complete with unknown error (retrying).
12.10.2015 14:10:36: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 14:10:53: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 14:10:57: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 14:11:08: Request to https://141.101.113.193/ failed with unknown error (retrying).
12.10.2015 14:11:10: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 14:11:14: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 14:11:18: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 14:11:24: Request to https://141.101.113.193/ complete with unknown error (retrying).
12.10.2015 14:11:32: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 14:11:35: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 13:54:30: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 failed with unknown error (retrying).
12.10.2015 13:54:37: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 failed with unknown error (retrying).
12.10.2015 13:54:42: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 complete with unknown error (retrying).
12.10.2015 13:54:43: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 complete with unknown error (retrying).
12.10.2015 13:54:43: Request to https://141.101.112.193/thumb/3756l.jpg failed with unknown error (retrying).
12.10.2015 13:54:46: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 complete with unknown error (retrying).
12.10.2015 13:54:51: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 failed with unknown error (retrying).
12.10.2015 13:55:08: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 complete with unknown error (retrying).
12.10.2015 13:55:12: Request to https://141.101.112.193/thumb/3756l.jpg complete with unknown error (retrying).
12.10.2015 13:55:33: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 failed with unknown error (retrying).
12.10.2015 13:55:54: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 complete with unknown error (retrying).
12.10.2015 13:56:10: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 13:56:15: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 13:56:31: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 13:56:36: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 13:56:57: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 13:57:18: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 13:57:22: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 13:57:34: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 13:57:39: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 13:57:39: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 13:57:45: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 13:57:51: Request to https://141.101.113.193/web/osu-error.php complete with unknown error (retrying).
12.10.2015 13:57:56: Request to https://141.101.113.193/web/osu-error.php complete with unknown error (retrying).
12.10.2015 13:58:00: Request to https://141.101.113.193/web/osu-error.php complete with unknown error (retrying).
12.10.2015 13:58:17: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 13:58:21: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 13:58:33: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 13:58:38: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 13:58:40: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 13:58:42: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 13:58:56: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 13:58:59: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 13:59:02: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 13:59:03: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 13:59:20: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 13:59:24: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 13:59:31: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 13:59:36: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 13:59:45: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 14:00:02: Request to https://141.101.112.193/ complete with unknown error (retrying).
12.10.2015 14:00:06: Request to https://141.101.113.193/thumb/128622l.jpg complete with unknown error (retrying).
12.10.2015 14:00:27: Request to https://141.101.112.193/ failed with unknown error (retrying).
12.10.2015 14:00:44: Request to https://141.101.112.193/ complete with unknown error (retrying).
12.10.2015 14:00:48: Request to https://141.101.112.193/ failed with unknown error (retrying).
12.10.2015 14:01:05: Request to https://141.101.112.193/ complete with unknown error (retrying).
12.10.2015 14:01:09: Request to https://141.101.113.193/thumb/128622l.jpg failed with unknown error (retrying).
12.10.2015 14:01:15: Request to https://141.101.112.193/ failed with unknown error (retrying).
12.10.2015 14:01:21: Request to https://141.101.112.193/ complete with unknown error (retrying).
12.10.2015 14:01:26: Request to https://141.101.113.193/thumb/128622l.jpg complete with unknown error (retrying).
12.10.2015 14:01:30: Request to https://141.101.113.193/thumb/128622l.jpg failed with unknown error (retrying).
12.10.2015 14:01:51: Request to https://141.101.113.193/thumb/152l.jpg complete with unknown error (retrying).
12.10.2015 14:02:08: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:02:12: Request to https://141.101.113.193/thumb/152l.jpg failed with unknown error (retrying).
12.10.2015 14:02:29: Request to https://141.101.113.193/thumb/152l.jpg complete with unknown error (retrying).
12.10.2015 14:02:33: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:02:54: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:03:13: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:03:15: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:03:32: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 failed with unknown error (retrying).
12.10.2015 14:03:36: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:03:57: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 complete with unknown error (retrying).
12.10.2015 14:04:18: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 failed with unknown error (retrying).
12.10.2015 14:04:35: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 complete with unknown error (retrying).
12.10.2015 14:04:39: Request to https://141.101.112.193/ failed with unknown error (retrying).
12.10.2015 14:04:56: Request to https://141.101.112.193/ complete with unknown error (retrying).
12.10.2015 14:05:00: Request to https://141.101.113.193/web/bancho_conn ... 45|dotnet4 failed with unknown error (retrying).
12.10.2015 14:05:17: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 14:05:21: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 14:05:38: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 14:05:42: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 14:05:59: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 14:05:59: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 14:06:03: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 14:06:15: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 14:06:20: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 14:06:24: Request to https://141.101.113.193/web/osu-checktweets.php failed with unknown error (retrying).
12.10.2015 14:06:45: Request to https://141.101.113.193/web/osu-checktweets.php complete with unknown error (retrying).
12.10.2015 14:07:06: Request to https://141.101.113.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:07:23: Request to https://141.101.113.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:07:27: Request to https://141.101.113.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:07:44: Request to https://141.101.113.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:07:48: Request to https://141.101.113.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:08:09: Request to https://141.101.113.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:08:30: Request to https://141.101.113.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:08:47: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:08:51: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:09:08: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:09:12: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:09:33: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:09:53: Request to https://141.101.113.193/ failed with unknown error (retrying).
12.10.2015 14:09:54: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:10:11: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh failed with unknown error (retrying).
12.10.2015 14:10:11: Request to https://141.101.112.193/web/bancho_conn ... //c.ppy.sh complete with unknown error (retrying).
12.10.2015 14:10:15: Request to https://141.101.113.193/ complete with unknown error (retrying).
12.10.2015 14:10:36: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 14:10:53: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 14:10:57: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 14:11:08: Request to https://141.101.113.193/ failed with unknown error (retrying).
12.10.2015 14:11:10: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 14:11:14: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
12.10.2015 14:11:18: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 14:11:24: Request to https://141.101.113.193/ complete with unknown error (retrying).
12.10.2015 14:11:32: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh failed with unknown error (retrying).
12.10.2015 14:11:35: Request to https://141.101.112.193/web/bancho_conn ... /c1.ppy.sh complete with unknown error (retrying).
Are you on public slack? Will have to follow this up with you tomorrow.
http://puu.sh/kHBvh/424f874a98.jpg Tried going on osu, but after going to song select, this popped up. The song is still playing, and i can assure you i didn't have it in my library, i only had the ranked version.
RandomGamerLv wrote:
http://puu.sh/kHBvh/424f874a98.jpg Tried going on osu, but after going to song select, this popped up. The song is still playing, and i can assure you i didn't have it in my library, i only had the ranked version.
Can confirm this also. http://osu.ppy.sh/ss/3806535
I actually have a performance problem on Beta and Cutting Edge. The longer I play Osu, the higher my frametimes are, more fps drops and overall less FPS. And it's not like heating is the problem or anything, because it gets gradually worse after an hour or so, not in 10 minutes, when you could already say osu is already pushing computer far. Also, all I have to do is restart osu and everything is back to normal again, but then the performance problems kicks in faster.
Processor: AMD FX-4100 4-core 3.6gHz.
osu! version: 20151013.3beta
Processor: AMD FX-4100 4-core 3.6gHz.
osu! version: 20151013.3beta
I get occasional "disconnects" (can't really call them disconnects since it's more like the icon just showing up and going away) with this error message:
Hope it doesn't matter that it's partly in Finnish
13.10.2015 18:37:29: BANCHO error: System.Net.WebException: Yhteyden muodostaminen etäpalvelimeen ei onnistunut ---> System.Net.Sockets.SocketException: Yhteyttä ei voi muodostaa, koska kohdekone ei salli sitä 141.101.112.193:443
kohteessa System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
kohteessa System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- Sisäisen poikkeuksen pinon jäljityksen loppu ---
kohteessa #=qFpJ7mYu0N56bzruZYCDMHh$Kv3qOSbSA$p$IC1LJuTo=.#=qfEULBnkOLWOSnU05e8OpkuVLhivWZEoIpbN8Kc0qL6g=()
kohteessa #=qAEYSVWenCExXoEZ1XzBV0EaVoDcGEWyOJoSH_BVkokE=.#=qczLKDFy7BTTfFmVQLSWiAA==(Boolean #=qov5S2_WdVpUesSjxtMRdsw==)
kohteessa #=qAEYSVWenCExXoEZ1XzBV0EaVoDcGEWyOJoSH_BVkokE=.#=qUrvekdHAx9e4odwNZFSVaw==()
kohteessa System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
kohteessa System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- Sisäisen poikkeuksen pinon jäljityksen loppu ---
kohteessa #=qFpJ7mYu0N56bzruZYCDMHh$Kv3qOSbSA$p$IC1LJuTo=.#=qfEULBnkOLWOSnU05e8OpkuVLhivWZEoIpbN8Kc0qL6g=()
kohteessa #=qAEYSVWenCExXoEZ1XzBV0EaVoDcGEWyOJoSH_BVkokE=.#=qczLKDFy7BTTfFmVQLSWiAA==(Boolean #=qov5S2_WdVpUesSjxtMRdsw==)
kohteessa #=qAEYSVWenCExXoEZ1XzBV0EaVoDcGEWyOJoSH_BVkokE=.#=qUrvekdHAx9e4odwNZFSVaw==()
Merged your thread to the CE thread, since you are saying it's in Beta and CE.Haganenno wrote:
I actually have a performance problem on Beta and Cutting Edge. The longer I play Osu, the higher my frametimes are, more fps drops and overall less FPS. And it's not like heating is the problem or anything, because it gets gradually worse after an hour or so, not in 10 minutes, when you could already say osu is already pushing computer far. Also, all I have to do is restart osu and everything is back to normal again, but then the performance problems kicks in faster.
Processor: AMD FX-4100 4-core 3.6gHz.
osu! version: 20151013.3beta
Could you check your CPU and memory usage on the task manager when you start getting a bad performance?