82 replies to this topic

[ShinVector]

Morgana, on 08 April 2015 - 05:37 PM, said:

Curious as to what is in the game, that is now causing Ping issues. As others have stated, I have been able to play 2-3 matches without issue, and from there the ping starts to climb. I typically run a 50+/- ping, and after a few drops, can watch it climb upwards to 500+/-, until I finally get the Network Error has Occurred Error and am dropped out of match.

I have run the Repair Tool with no issue, with all things resolved, get into game, play 2-3 matches, and still have the same issue. Am able to do anything else on the computer, with the exception of MWO. Repair Tool is not fixing the issue.

You know Repair Tool does not solve your local network issues right ?
Simple scenario would be your playing MWO... But at the same time someone in your decides to download the lastest episode of Star Trucks S2E12.... Be it your download or upload bandwidth gets saturated...
Your MWO client says 'Your internet sucks... I can't communicate with the game servers at all !! ggclose.. Rage quits the connection..'

Edited by ShinVector, 08 April 2015 - 06:00 PM.

[Morgana]

Then it would do so watching videos, twitch streams and playing other online games. It is not happening during any of those things. I do not have a shared connection, and no one else in the home is using the internet. I did however, just remember that peeps had issues with VoiP, so I may try a few Pug drops with it disabled and see if that makes any different. It didn't bother before. And this issue did not arise until I downloaded the patch. It started with the very first drop after patching, and has occurred everytime I try to play.

As for your issue, I've only run the Repair Tool three times in three years, and I too, had to repair every pak. file.

Edited by Morgana, 08 April 2015 - 06:39 PM.

[ShinVector]

Morgana, on 08 April 2015 - 06:37 PM, said:

Then it would do so watching videos, twitch streams and playing other online games. It is not happening during any of those things. I do not have a shared connection, and no one else in the home is using the internet. I did however, just remember that peeps had issues with VoiP, so I may try a few Pug drops with it disabled and see if that makes any different. It didn't bother before. And this issue did not arise until I downloaded the patch. It started with the very first drop after patching, and has occurred everytime I try to play.

As for your issue, I've only run the Repair Tool three times in three years, and I too, had to repair every pak. file.

This kinda off topic.

But you might want to use WinMTR to monitor your connection:
http://winmtr.net/download-winmtr/
The info it provides will be useful if determine where the lag is coming from when you troubleshooting with your ISP.
You can just keep performing a traceroute to www.mwomercs.com.

[Modo44]

Krist Smith, on 08 April 2015 - 01:39 PM, said:

Thanks for the pointer. For the upcoming patch, I'll be adding a confirmation dialog window when you click the option to set the temp directory. This dialog will indicate your current selection and ask if you would like to change it. I hope that makes things clearer.

A simple dialog like that will do exactly what is needed. Thank you.

Krist Smith, on 08 April 2015 - 01:39 PM, said:

As for "rummaging around" on your SSD, [snip]In terms of file operations the patcher essentially does the same thing.

I understand that. My point is, you want to move all temp directories away from the SSD, and the patcher as is makes it seem like you have to do it manually every time. Anyway, with the added dialog it will all be good.

[Morgana]

ShinVector, on 08 April 2015 - 07:03 PM, said:

This kinda off topic.

But you might want to use WinMTR to monitor your connection:
http://winmtr.net/download-winmtr/
The info it provides will be useful if determine where the lag is coming from when you troubleshooting with your ISP.
You can just keep performing a traceroute to www.mwomercs.com.

Thanks so very much Shin, this definitely helped. My CMD prompt tracert wouldn't tell me where the problem was, but this did.

Devs, please look into nwk-1-6k.nj.us , as this is where I'm experiencing 90% - 100% packet loss.

Sorry I this hijacked the thread, was not my intention, was merely looking for a resolve. Move post where deemed necessary.

Edit: Looking throughout the forums, I have found similar threads showing issue with the same server for the past several months. Is it possible to re-route traffic to another server as this one is clearly NOT reliable?

Edited by Morgana, 09 April 2015 - 05:13 AM.

[ShinVector]

Morgana, on 09 April 2015 - 04:46 AM, said:

Thanks so very much Shin, this definitely helped. My CMD prompt tracert wouldn't tell me where the problem was, but this did.

Devs, please look into nwk-1-6k.nj.us , as this is where I'm experiencing 90% - 100% packet loss.

Sorry I this hijacked the thread, was not my intention, was merely looking for a resolve. Move post where deemed necessary.

Edit: Looking throughout the forums, I have found similar threads showing issue with the same server for the past several months. Is it possible to re-route traffic to another server as this one is clearly NOT reliable?

As mentioned best people to help on you this issue is your ISP.
They will have to let you whether it it is normal or not normal and the problem is on their end.
Usually if its a major issue.. They would have gotten many report on the problem already.

If they start blaming the issue one MWO network then you can start asking MWO support or make a post on patch feedback on the issue.

[Morgana]

Sorry I'm confused, what does the 10th hop of 14 to MWO servers have to do with my ISP? And this IS the Patch Feedback forum is it not? I don't live in the state that the server in question is located in, so no, I won't be bothering my ISP with this. The issue resides with a completely different company.

[ShinVector]

You should create your own thread about you issue.
This thread is about repair tool.

Basically troubleshooting start with your ISP. They should help you verify first.

[Morgana]

Did you ever consider that by some chance, the issues with the Repair Tool, may be that some of us are loosing packets while downloading the Patch, or even during the Repair Tool process, that would cause it to give those inconsistent results that others have reported, and explain the slow download speeds. Unless you are a Networking Technician that has all the answers, I would appreciate if you could stop being condescending.

But just to bolster your ego, I did called my ISP and they verified that the issue was not with me OR with them. The problem is with the server not receiving the packets as I stated in my original post.

Have a good sir, and I look forward to a Devs response, as they DO know what they are talking about.

[Krist Smith]

Morgana, on 09 April 2015 - 09:53 AM, said:

Did you ever consider that by some chance, the issues with the Repair Tool, may be that some of us are loosing packets while downloading the Patch, or even during the Repair Tool process, that would cause it to give those inconsistent results that others have reported, and explain the slow download speeds. Unless you are a Networking Technician that has all the answers, I would appreciate if you could stop being condescending.

But just to bolster your ego, I did called my ISP and they verified that the issue was not with me OR with them. The problem is with the server not receiving the packets as I stated in my original post.

Have a good sir, and I look forward to a Devs response, as they DO know what they are talking about.

Well, this isn't really the proper thread for this discussion. You may be right about connectivity issues also being related to repair tool download speeds, this thread is actually intended to discuss the recent update to the repair tool and direct consequences.

However, since you do have some valid points and questions, I've brought this to the attention of a team member who actually knows this stuff much better than I do. He said that he will pop in to help out (and most likely split out that discussion into a new thread).

I hope this will help clear things up.

[Morgana]

Thank you kindly Krist

[sabujo]

I've started the Repair Tool by 2:00pm and now, almost 11:00pm here, it still goes on Objects.pak. And man, it states that at this speed it will take more than 7 hours just to get this .pak.

[Insects]

Will this upgraded version detect old version files?
Previous repair tool versions did not detect if an old version of the file (ie patcher didn't complete and didn't upgrade that file) was there if its checksums were valid.

Could this upgrade to the pak format have been done with a tool to add whatever has been changed in the format rather than full download?

[Jon Cunningham]

Morgana, on 09 April 2015 - 11:38 AM, said:

Thank you kindly Krist

Could you send me a PM with a traceroute to mwomercs.com and the results of ping mwomercs.com ?

Slightly easier to continue that there.

[Morgana]

PM sent, along with a trace from a player that resides in Germany, as he seems to be having the same issue.

Hope it helps, and thanks for looking into this.

[ShinVector]

Morgana, on 09 April 2015 - 09:53 AM, said:

Did you ever consider that by some chance, the issues with the Repair Tool, may be that some of us are loosing packets while downloading the Patch, or even during the Repair Tool process, that would cause it to give those inconsistent results that others have reported, and explain the slow download speeds. Unless you are a Networking Technician that has all the answers, I would appreciate if you could stop being condescending.

But just to bolster your ego, I did called my ISP and they verified that the issue was not with me OR with them. The problem is with the server not receiving the packets as I stated in my original post.

Have a good sir, and I look forward to a Devs response, as they DO know what they are talking about.

sabujo, on 09 April 2015 - 01:46 PM, said:

I've started the Repair Tool by 2:00pm and now, almost 11:00pm here, it still goes on Objects.pak. And man, it states that at this speed it will take more than 7 hours just to get this .pak.

Yep... That's 1.4GB thing... PGI better start wondering about that full install suggestion I mentioned.
I have a very fast internet connection but being capped at 10Mbits... It took 2-3hours after being forced to re-download all the .pak files.

Alternatively a huge one time patch that users can pre-download to reduce the inconvenience.

[river908]

Since Monday April 6 I havent been able to login at all. It will not even reach the login section.
Just the initial MWO picture then it freezes. Whats wrong? How can I fix this.

[Krist Smith]

ShinVector, on 09 April 2015 - 04:52 PM, said:

Yep... That's 1.4GB thing... PGI better start wondering about that full install suggestion I mentioned.
I have a very fast internet connection but being capped at 10Mbits... It took 2-3hours after being forced to re-download all the .pak files.

Alternatively a huge one time patch that users can pre-download to reduce the inconvenience.

A single patch (that isn't a complete uninstall/reinstall) just isn't an option. The underlying mechanic of the patcher is changing with an upcoming patch, and it will require every pak file to have a very specific source structure. The reason that most file structures won't be the same (as proven by the number of files you're each downloading via the Repair Tool) is because the current patcher method is to extract the pak file contents, patch the individual files therein, and then re-zip it again. The method made the file structure not only slightly different, but unique on each computer that ran the patch (although I will admit there's an incredibly small chance that two people patched at exactly the same time with exactly the same rig with exactly the same programs that were running in exaclty the same state with billions of other factors exactly the same, resulting in files that had exactly the same compression and timestamps. I can dream... ).

We really wanted to find an option that wouldn't put such a strain on the downloads, but overall this really was the best choice. As I've said before, we're really trying to get a tighter control on problems like pak file corruption, not to mention get the patcher more stable and faster overall, and this is how we do that. The way to achieve it is to ensure absolute consitency on the pak level, not on the contents. The original concern was that every patch size would go through the roof, but to solve this we've made changes to the pak files themselves. In the end, this one-time bout with downloads comes as the price for keeping the patch sizes the same while gaining all the other wins (faster patch, faster scan).

And, most importantly, I have to say that's a well-placed (and awesome) GIF. Bravo. Although I also would have accepted

river908, on 09 April 2015 - 09:26 PM, said:

Since Monday April 6 I havent been able to login at all. It will not even reach the login section.
Just the initial MWO picture then it freezes. Whats wrong? How can I fix this.

Please check this thread:
http://mwomercs.com/...mwo-wont-start/

If there's no info in that thread to help you, (or you have more questions) please just let me know there, and I'll do what I can to help out.

[river908]

Krist Smith, on 09 April 2015 - 10:43 PM, said:

A single patch (that isn't a complete uninstall/reinstall) just isn't an option. The underlying mechanic of the patcher is changing with an upcoming patch, and it will require every pak file to have a very specific source structure. The reason that most file structures won't be the same (as proven by the number of files you're each downloading via the Repair Tool) is because the current patcher method is to extract the pak file contents, patch the individual files therein, and then re-zip it again. The method made the file structure not only slightly different, but unique on each computer that ran the patch (although I will admit there's an incredibly small chance that two people patched at exactly the same time with exactly the same rig with exactly the same programs that were running in exaclty the same state with billions of other factors exactly the same, resulting in files that had exactly the same compression and timestamps. I can dream... ).

We really wanted to find an option that wouldn't put such a strain on the downloads, but overall this really was the best choice. As I've said before, we're really trying to get a tighter control on problems like pak file corruption, not to mention get the patcher more stable and faster overall, and this is how we do that. The way to achieve it is to ensure absolute consitency on the pak level, not on the contents. The original concern was that every patch size would go through the roof, but to solve this we've made changes to the pak files themselves. In the end, this one-time bout with downloads comes as the price for keeping the patch sizes the same while gaining all the other wins (faster patch, faster scan).

And, most importantly, I have to say that's a well-placed (and awesome) GIF. Bravo. Although I also would have accepted





Please check this thread:
http://mwomercs.com/...mwo-wont-start/

If there's no info in that thread to help you, (or you have more questions) please just let me know there, and I'll do what I can to help out.

Followed the link...worked like magic. thanks.

[Damian Frost]

Thanks for the heads up, I just run the repair tool and saw all the files and then come here to see if there was an explanation for all the mismatched files. Stared having a fatal error message with crash come up during game and decided to run repair tool. It's almost like having to uninstall and reinstall when trying to fix it with this many mismatched files.