I can't replicate this. Try the following and see if you can make it happen:
1. start osu!
2. join multiplayer game (or start one)
3. have someone spectate you
4. does it happen?

Torrent full power
Playing multi, nothing happened when p3n spec'd.

Played on multi, 3 people spectating me, can't confirm.

Same problem for me, confirming.

Roxas wrote:

Same problem for me, confirming.

Following my steps? Does it also happen if you use the test build? If it does, can you check for a "network.txt" file in your osu! folder when it happens?

peppy wrote:

I can't replicate this. Try the following and see if you can make it happen:
1. start osu!
2. join multiplayer game (or start one)
3. have someone spectate you
4. does it happen?

It doesn't have to be in multiplayer. Just happened to me a minute ago, though it took me a little longer to get dc'd.

peppy wrote:

Roxas wrote:

Same problem for me, confirming.

Following my steps? Does it also happen if you use the test build? If it does, can you check for a "network.txt" file in your osu! folder when it happens?

Yes I can replicate.
Did on test build too.

Yes, I can find a network.txt too. This is the content:

Edit: I got disconnected when I finished the map.

So the only time it happens is on finishing? Do you get to the ranking screen? Is this only in a multiplayer game, or without one too?

Well it happened in a head to head match, when I play tag coop mode it doesn't happen.
I try in solo too (always in test build).

Can't replicate this in solo (test build). But in those days I got disconnected when I was in solo and with spectators (not test build).

Btw yes, I get the ranking screen.

Edit: Okay, really strange thing... After I finished a beatmap I couldn't submit the score even if my connection was working, and plus, my friends was seeing me offline, but I didn't have a disconnect here.

Noone ever spectates me. I haven't experienced this yet. I'll be playing multi soon if anyone wants to troll me.


Edit: i just had a weird experience. The game got stuck on submitting scores. I couldn't ready up and when I left the game my player was still part of the game. I had to restart osu! to reenter the game I was in.

https://osu.ppy.sh/ss/954387

Umm peppy i can't even access test build. Everything that has to do with bancho gives me a massive lag spike that maxes out my CPU.

This is what's in the network text

#qd.#ne: HTTP/1.1 403 Token Failure
at #qd.#je.#qA(Int32 , StringCollection , String[] )
at #qd.#je.#hA(String , String[] , Stream , Stream )
at #qd.#je.#yA(String , String , String[] , Stream , Stream )
at #Xn.#Wn.#ur(Boolean )
at #Xn.#Wn.#It()

That network.txt is outdated/unrelated to your issue, for what it's worth.

I figured it might be. Well until bancho stops locking up the test build, I can't help with this issue.

Test build should be working again, anyways.

Please re-test this with the new public release. May or may not be fixed.

Marcin spectated me on latest public for two maps and it didn't happen. the first map Marcin spectated me on the old public version, it disconnected me. It may be fixed or it just may not happen as frequently as it used to. It's probably fixed though.

I had some dude spectate me today, but I was fine.

But just now I was trying to spectate Yoshi_green again, but he kept d/cing without any seeming cause, always a different point in the song

it's quite possible they haven't updated to the latest version yet.

I'm pretty sure I had the most recent version when Hula was spectating me; I update whenever it prompts me to do so on the main menu, and I log in at least once a day

Well let us know if it happens again.

Bancho has been having some weird timeouts since I started multiplayer. I don't think it's related to people spectating. Leaving the game seems to time me out sometimes.

Bancho has been having some weird timeouts since I started multiplayer. I don't think it's related to people spectating. Leaving the gameroom seems to time me out sometimes.

this is still happening for me..
my network.txt

Confirm that you're on the 0829 public build or the test build. I had to manually update the public build.

And check the date on network.txt. It isn't relevant unless it is dated at the point you encountered the issue.

was on 0830.5test but can't confirm the date since it has been overwrited again one hour later (due to my connection problems). Maybe adding the date inside the file would be helpful..

Okay, I tried it now since it happened to me yesterday and its still happening. And not just in multiplayer. I played in solo.

Still need to really find a replicable case for this. Very hard to figure out otherwise.

Happens to me whenever I get a spectator, regardless of if I'm in multiplayer or singleplayer

Just have been playing multiplayer with marathon song, being spec'd by TVO, and

#qd.#ne: HTTP/1.1 403 Token Failure
   w #qd.#je.#qA(Int32 , StringCollection , String[] )
   w #qd.#je.#hA(String , String[] , Stream , Stream )
   w #qd.#je.#yA(String , String , String[] , Stream , Stream )
   w #Xn.#Wn.#ur(Boolean )
   w #Xn.#Wn.#It()

Yeah, pretty much disconnected. It happens at the end of song.
Edit: Now again disconnect, in the middle. We've been guessing with TVO it has something to do with spectator going AFK. Needs further testings.

I believe it is happening because the spectator is going AFK while spectating. Before I hit the boss key and it seemed to disconnect the player at the end of the match. The next run I was active the whole time and he didn't disconnect. the third time I decided to let myself go AFK and the disconnect was immediate.

Edit: Not getting consistent results. I still have a few theories.

TheVileOne wrote:

I believe it is happening because the spectator is going AFK while spectating. Before I hit the boss key and it seemed to disconnect the player at the end of the match. The next run I was active the whole time and he didn't disconnect. the third time I decided to let myself go AFK and the disconnect was immediate.

Edit: Not getting consistent results. I still have a few theories.

I can guarantee it's not tied to the spectator going afk. With Yoshi_green it happens sometimes instantly, or we can get 1 minute into Airman, and I'm not going afk, occasionally I get buffering... and then he d/cs, other times it continues playing as if he was cookiezi on my pc at least.

My current theory is that it's related to #spectator opening either on the player's end or the spectator's end. I haven't found any conclusive proof yet.

Edit: I think this is the issue, but I can't replicate it at all. It seems to happen more commonly when I have to download the map to watch and generally once it happens to someone, it doesn't want to happen a second time. I've been spectating this player for awhile and it hasn't happened since the first DC.

Edit: I can't get this to happen anymore.

Hi,
It happens to me too.
When I play (in multi or not) and if someone is spectating me, i'm disconnected and then, my score can't be submited.

Happened again, this time in solo. (osu!.exe)

Roxas wrote:

Happened again, this time in solo. (osu!.exe)

Same here. Still happening also after latest updates. (When the spectator click Start Spectating and I can see the name in the spectator list I get disconnected after 20-30 seconds)

I've made more changes to the test build earlier tonight, so please test further. Also please state that you are using the test build (and the version number) when you reply after this post.

I'll be using test build version 0902. I'm not sure whether the spectated and the spectator need to be updated to the test build version. I'll try to get someone to crash me, but it's really hard to tell whether it is fixed unless people flatout stop experiencing it. It happens like once every 10-20 spectated plays.

just the host (player) needs to be updated.

I find that this problem only occurs for a only a few people out of everybody. Most of the people on my Friends list can spectate and be spectated without any disconnection problems, but when it comes to me, I disconnect anywhere within 15 to 100 seconds into gameplay.

I had a few people spectate me today, and the problem still persists on my end. I spectated a few of my friends with no problem, though.

As I said above, use the test build and make sure to specify the version where you experience failures. I have made many fixes in the recent test releases.

Oh sorry, I didn't read that.

I can't download the test build :/
When I run the updater, this is what shows:



I didn't download the test build, and yet the option is not there for me. It's not a picture of the newest version, but I'm running the newest version at the moment for sure.

Also, I found something like this in my osu! folder...



so I'm figuring that might be related. I don't know how it got there though 'cause I never touched the test build

^Delete the test build and redownload it. You may want to redownload osume as well.

I spectate Marcin and he played various songs and it didn't disconnect him once. I encountered all sorts of other spectator bugs though. we were both using the latest test build.

I just spectated Ono and he disconnected several times. he is using the public build. That means that this issue is either fixed on the test build, or it tends to happen more often for certain people than others. If Ono gets on test build I can see if it still disconnects for him.

I know what is going on! Onosakihito updated to the test build to see if it would still disconnect him when I spectated him. It seemed fine at first, but weird things started to happen when I tried to use Fraps. My computer would disconnect me from spectator mode when I activated Fraps. He reported that this was disconnecting him from the channels he had joined, but it wasn't disconnecting him entirely from Bancho.

After I stopped doing that to him, he started playing a couple maps that I didn't have. I think downloading maps was a trigger for me disconnecting from him. If I disconnected, then he would disconnect shortly after. This leaves the trigger for this bug to be one of two possibilities. Bancho is sending a packet that causes connections issues to both spectator and players and the spectator gets the packet first or it is a direct result of the spectator disconnecting that is causing the player to disconnect.

This bug is pretty serious as I could interrupt the bancho connection to Ono just by activating my Fraps.

Replication steps

1. Spectate someone (I think some people are more likely to disconnect than others. It would explain why spectating Marcin wasn't causing disconnects.)
2. By some means forcefully cause yourself to disconnect from spectator mode. I used Fraps to kill the connection.
3. The spectated player will either disconnect from Bancho entirely or lose connection to the chat tabs he has open.

Note: downloading maps via osuDirect seems to be enough of a strain on the connection to disconnect me from spectator mode. Bancho is probably creating a fit trying to reconnect me that it puts strain on their connection somehow. I'm not sure how it works.

Side effects of this bug:

The player doesn't need to be in multiplayer.

The disconnect that I triggered via Fraps never disconnected Ono completely from Bancho unlike the events that triggered randomly within the game.

Because Ono doesn't lose connection with bancho, I think that Bancho still thinks that I am spectating Ono serverside even though clientside it no longer says I am spectating him. If my memory serves me right, this would explain peculiar events where it would throw me back to the osu menu, but still retain spectating status if the player suddenly changed statuses. This issue will not allow me to respectate the player until he changes the map or i manually unspectate the player via some means. The game will not try to rewatch the player until spectator is toggled or under certain circumstances the player changes status.

Bancho's status for the player seems to freeze clientside when you disconnect in this way. It could have been a coincedence though.

Disconnecting from spectator mode does not send an issue report to network.txt.


Ono gave me this image.

TheVileOne wrote:

^Delete the test build and redownload it. You may want to redownload osume as well.

Done and done. Unistalled and re-installed the whole thing too. The option to download test build is still not appearing :/

Go to extras and select test build :p?

Marcin wrote:

Go to extras and select test build :p?

Checked the Extras tab before; wasn't there ._.

Checked again; still not there
(unless I'm missing something (which I think I am))

It's there, and you have a bug with UI, /me looks at peppy

EDIT: As work around:
1. Go to your osu! installation folder
2. Open osu!.cfg
3. Add Line "u_UpdaterTestBuild = 1" or update to "1" if it already exists"
4. Run osume.exe

peppy wrote:

I've made more changes to the test build earlier tonight, so please test further. Also please state that you are using the test build (and the version number) when you reply after this post.

It's working running b20130903.5test - Test Build, but I can't load any map I download from site or direct. (Yes I did F5 and nothing happen)

@TheVileOne please PM me in-game next time you are online. Let's try and replicate this.

I would like to take some time to see if my replication steps are consistent. Apparently I was only taking screenshots with Fraps, so i'm not sure why it would interfere with bancho. The first time I take a screenshot with fraps, it crashes the game with a graphics card corruption error, but it works correctly upon restart. It might be the issue, but it could be a coincidence.

I was spectating various people today and hitting the screenshot key on fraps and it wasn't sending me to the osu! menu like it was that day. I may need a particular load on my internet connection or a maxxed CPU to trigger a disconnect from spectator mode. I might not be able to replicate the disconnect for one reason or another.

I'm pretty certain the spectator disconnects before the player does though. It would be nice if someone could verify this.


Edit: I think the general consensus is that this bug is resolved. We could possibly tag this thread and bring it back up if anyone still experiences this issue. although the fix should be pushed public to stop it happening for everyone.

I believe this is fixed, as I haven't heard of anyone with this issue since the last build.