Jump to content

The Reason I Will Stop Playing Mwo


26 replies to this topic

#21 627

    Member

  • PipPipPipPipPipPipPipPipPip
  • Wrath
  • Wrath
  • 4,571 posts

Posted 31 May 2015 - 03:04 PM

have you tried to change your dns to google? it is 8.8.8.8 - for some reasons mwo seems to work better with it.

#22 GeistHrafn

    Member

  • PipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 450 posts
  • LocationMB, Canada

Posted 31 May 2015 - 03:10 PM

View PostThunder Child, on 31 May 2015 - 02:12 PM, said:

I've tried 32, and 64. DX9 and DX11. Repaired. Reinstalled. Scanned for Viruses and Malware. Recited the Grimorum Arcanorum backwards under a full moon while holding down Ctrl Alt Delete in a vat of fresh goats milk....

Well there's your problem! It's a vat of fresh goats blood! ;)

(Disclaimer: I shouldn't need to say this, but please don't actually sacrifice a goat!)

#23 Speedy Plysitkos

    Member

  • PipPipPipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 3,460 posts
  • LocationMech Junkyard

Posted 31 May 2015 - 03:30 PM

View PostElizander, on 31 May 2015 - 06:44 AM, said:

Try 32-bit. My 64-bit client is crap.


this.

#24 Nightmare1

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 7,636 posts
  • Twitch: Link
  • LocationPeeking over your shoulder while eating your cookies.

Posted 31 May 2015 - 06:40 PM

The only thing consistent about this game are the pathetic nature of Pugs and the inconsistency of the connection.

#25 Anjian

    Member

  • PipPipPipPipPipPipPipPipPip
  • FP Veteran - Beta 2
  • FP Veteran - Beta 2
  • 3,735 posts

Posted 31 May 2015 - 07:28 PM

This is likely due to connection issues, as I have experienced the same things.

Despite that, I have seen games that, despite connection issues, won't disconnect and return you to the desktop. They have made client stability a science. I have played games that are closed betas and they don't disconnect me like MWO does.

#26 HellJumper

    Member

  • PipPipPipPipPipPipPipPip
  • 1,226 posts
  • LocationIslamabad, pakistan

Posted 31 May 2015 - 09:46 PM

View Post627, on 31 May 2015 - 03:04 PM, said:

have you tried to change your dns to google? it is 8.8.8.8 - for some reasons mwo seems to work better with it.



i will do that and the 32 bit thing when i get hom..

i am glad i am not the only person.
at one point i can understand that its bceause i am connecting from Pakistan so distance might play. on the other hand i was playing Armored warfare over the weekend (EU server).. played for about 6 hours (spilt between 2 days).. not a single DC or crash so i am more than confident its not my internet.. :(

#27 NeoCodex

    Member

  • PipPipPipPipPipPipPip
  • The Predator
  • The Predator
  • 799 posts

Posted 31 May 2015 - 10:03 PM

HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows NT > CurrentVersion > Multimedia > SystemProfile > NetworkThrottlingIndex

Replace the Value Data with "ffffffff"

I had the same issue. This fixed it for me.

Long version:

Windows implements a network throttling mechanism to restrict the processing of non-multimedia network traffic to 10 packets per millisecond (a bit over 100 Mbits/second). The idea behind such throttling is that processing of network packets can be a resource-intensive task, and it may need to be throttled to give prioritized CPU access to multimedia programs. In some cases, such as Gigabit networks and some online games, for example, it is beneficial to turn off such throttling all together for achieving maximum throughput.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile]
"NetworkThrottlingIndex"=dword:ffffffff (DWORD, default: 10, recommended: 10 for media sharing, ffffffff for gaming and max throughput, valid range: 1 through 70 decimal or ffffffff to completely disable throttling)

Disable Nagle's Algorithm

This tweak works with all versions of Windows from Windows XP to Windows 8.1/10/2012 server. This is the same as listed in our general tweaking articles per OS.

Nagle's algorithm is designed to allow several small packets to be combined together into a single, larger packet for more efficient transmissions. While this improves throughput efficiency and reduces TCP/IP header overhead, it also briefly delays transmission of small packets. Disabling "nagling" can help reduce latency/ping in some games. Keep in mind that disabling Nagle's algorithm may also have some negative effect on file transfers. Nagle's algorithm is enabled in Windows by default. To implement this tweak and disable Nagle's algorithm, modify the following registry keys.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{NIC-id}
There will be multiple NIC interfaces listed there, for example: {1660430C-B14A-4AC2-8F83-B653E83E8297}. Find the correct one with your IP address listed. Under this {NIC-id} key, create a new DWORD value:
"TcpAckFrequency"=1 (DWORD value, not present by default interpreted as 2, 1=disable nagling, specifies number of outstanding ACKs before ignoring delayed ACK timer). For gaming performance, recommended is 1 (disable). For pure throughput and data streaming, you can experiment with small values over 2. Wifi performance may see a slight improvement with disabled TcpAckFrequency as well.

In the same location, add a new DWORD value:
TCPNoDelay=1 (DWORD, not present by default, 0 to enable Nagle's algorithm, 1 to disable)

To configure the ACK interval timeout (only has effect if nagling is enabled), find the following key:
TcpDelAckTicks=0 (DWORD value, not present by default interpreted as 2, 0=disable nagling, 1-6=100-600 ms). Note you can also set this to 1 to reduce the nagle effect from the default of 200ms without disabling it.

For Server Operating Systems that have Microsoft Message Queuing (MSMQ) installed, or if you have the MSMQ registry hive present, also add TCPNoDelay to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters
TCPNoDelay=1 (DWORD, not present by default, 0 to enable Nagle's algorithm, 1 to disable)

Note: Reportedly, disabling Nagle's algorithm can reduce the latency in many MMOs like Diablo III and WoW (World of Warcraft) by almost half! Yes, it works with Windows 7 and Windows 8.

System Responsiveness Gaming Tweak

Exists in all versions of Windows from Vista to 8.1/10/2012 Server.

Multimedia applications use the "Multimedia Class Scheduler" service (MMCSS) to ensure prioritized access to CPU resources, without denying CPU resources to lower-priority background applications. This reserves 20% of CPU by default for background processes, your multimedia streaming and some games can only utilize up to 80% of the CPU. This setting, in combination with the "NetworkThrottlingIndex" can help some games and video streaming. We recommend reducing the reserved CPU for background processes from the default of 20%.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile]
"SystemResponsiveness"=dword:00000000 (default: 20, recommended: decimal 10 for general applications, 0 for pure gaming/streaming)


More Gaming Tweaks

This section includes gaming-specific tweaks not listed in our general tweaking articles (and not implemented by the TCP Optimizer).

In the same Registry hive as the above two tweaks, you can also change the priority of Games, compared to other types of traffic. Below is a list of the settings and default/recommended values:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\Games]
"Scheduling Category"="High" (default: "Medium", recommended: "High")
"SFIO Priority"="High" (default: "Normal", recommended: "High")
"Background Only"="False" (default: "False", recommended: "False")
"Priority"=dword:00000001 (default: 2, recommended: 1)
"Clock Rate"=dword:00002710 (default: 2710, recommended: 2710)
"GPU Priority"=dword:00000001 (default: 2, recommended: 1)
"Affinity"=dword:00000000 (default: 0, recommended: 0)

P.S.: changing to google 8.8.8.8 DNS made things worse for me, particulary for the web browsing, so I advise against changing your DNS. In most cases, you should keep using your default ISP ones, unless you have a really horrible ISP those are ussualy the most reliable.

Edited by NeoCodex, 31 May 2015 - 10:14 PM.






11 user(s) are reading this topic

0 members, 11 guests, 0 anonymous users