Question / Help Studio randomly disconnects, Classic and demo XSplit do not have this problem

T

TerryKun00

New Member
I get the generic "
Received FD_CLOSE xxxx ms since last send
Aborting due to FD_CLOSE error 10053" message in my log, have tried no new network, new network and new network with low latency, all with the same random disconnects.
I know there is this right here https://obsproject.com/forum/threads/dropped-frames-disconnecting-lag-read-this-first.8870/ but Classic and the demo XSplit keep connected.
It seems other people are having this problem as well and going back to Classic/XSplit/Gameshow they no longer have the issue
https://twitter.com/MissGigglesss_/status/929092902986199041
https://twitter.com/Evo2587/status/945254490764185600
https://www.reddit.com/r/Twitch/comments/750rw3/obs_studio_random_disconnects_this_week_from/
https://obsproject.com/forum/threads/periodic-disconnection.78211/
https://obsproject.com/forum/thread...ing-data-to-twitch-for-so-many-seconds.71971/
https://twitter.com/ANerdNamedNova/status/936032678939447296
Maybe Studio hates certain isps in which maybe using your own variation of XSplit's networking code or figuring out why Classic works fine and Studio doesn't would help.
 
Studio uses the exact same network code as Classic when the "new networking code" option is enabled.
 
Sadly we have to wait til a big name streamer have the same issues all of us are having in order for them to actually want to fix this issue. For now do like me and stick with Classic since it actually works. Yes I have tried the new networking code and low latency options, they do not work unlike in Classic so while the coding maybe the same something is wrong with Studios itself where it stop receiving internet data despite internet connections working flawlessly otherwise.
 
You must log in or register to reply here.
Back
Top