Hi, I tried several times to upload my game to the binary in the Epic Games servers but every time it’s causing my wifi router to crash, Is there a way to make the uploading system not overload the router (I suspect that’s the problem)?
Hello. I recommend trying to use a wired connection or set the speed limit on the router to 80-95% … well, or change the router
PS I use a wired connection and have no problem with uploading to EGS
@GalMaron - Would you be able to elaborate a little bit on what you mean by your router is crashing? As in it actually goes through a reboot cycle, or that your internet connection slows down to an unusable state?
The uploading of builds can be demanding on your internet connection, particularly if your upload speed is substantially less than your download speed, as is the case in a lot of scenarios. But of course that shouldn’t translate to your router fully crashing when using BuildPatchTool. That would definitely be an unexpected and concerning outcome.
What @Station437 put forward might help given the general instabilities of Wi-Fi, but I can also appreciate that may not be possible in your scenario depending on how far you are away from your router.
Hi, thanks for replying and trying to help, so what’s happening is when I start the uploading process my router just stop providing internet entirely, it could happen at the start of the process or after that, the only way to make it work again is to call my internet provider. My computer is connected to a wifi extender and its usually providing fast and stable connection.
@GalMaron - Oh no, that is definitely not expected behavior! I would love to take a look at your BuildPatchTool logs to see if we could figure out what is happening at the time your router starts to have issues.
If you don’t mind, could you please do the following?
- Go to %localappdata%\BuildPatchTool\Saved\Logs and clear out the files that are in there so we can have a fresh start.
- Open up BuildPatchTool and start to upload the same binaries that you were uploading previously.
- Once you get to the point where your router crashes, you can close BuildPatchTool.
- Go back to %localappdata%\BuildPatchTool\Saved\Logs and grab the latest log file that was generated.
- This log file contains information that shouldn’t be shared publicly, so please make a private EOSHelp case with us as you’ve done previously, and reference this discussion in the subject so we can easily identify it. In that created private case, please attach your BuildPatchTool logs so we can take a look.
Thanks!
I tried once again to upload but the process got stuck for some reason (not due to the internet this time). I’ll try again and see what happens now.
Also I saw it uploaded more than 11000 files. is it normal? My game is only about 13gb.
It is normal for there to be a lot of files, but it’ll also greatly depend on the underlying game and how BPT processed your binary.
We’ll stand by for the logs!
I sent you the log file on a private case, send me a message if you need anything.
Received, thank you! Let’s go ahead and try throttling BuildPatchTool and see if that helps keep your connection more stable.
To note, please ensure that there are no instances of BuildPatchTool running while you’re making this change, as any running instance can cause the change to be undone.
First, navigate to C:\Users\<os-username>\AppData\Local\BuildPatchTool\Saved\Config\Windows\Engine.ini
Second, within that file add the following, then save the file:
[BuildPatchTool.ChunkWriter]
BatchSize=4
By default BatchSize is set to 16, but this will overwrite it to 4, which will reduce how many parallel uploads are happening at any given time. However, reducing this value will incidentally cause uploading to be slower.
Once you’ve done that, try the upload again and see if that helps with the instability. You’re also welcome to play around with this value, which can be anything from 1-16, to help find a balance of upload speed and instability.
That worked for me! Thank you!
1 Like
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.