load times are horrible
10
Patch Notes - 1.4.159.0 - 17-Apr-2018
Started by InnerSphereNews, Apr 13 2018 04:32 PM
431 replies to this topic
#322
-
-
- Ace Of Spades
- 31 posts
Member
Posted 17 April 2018 - 10:28 PM
D V Devnull, on 16 April 2018 - 03:38 AM, said:
- End of 32-Bit Support
Here's another one that upsets me, albeit I can count myself lucky to still be able to have enough computer (64-Bit CPU, 64-Bit OS, and 16 GB RAM) to play. PGI has, without any Proper Large-Scale Announcement that provided enough time in advance, dropped a whole chunk of their player base. Anyone still on an Old 32-Bit CPU or 32-Bit OS has just been told they're Effectively Banned until such time as they go buy New Hardware. Worse, I've seen what trying to use the 64-Bit Client on anything less than 16 GB Total System RAM causes, and that problem is Random Crashes. (For reference, I actually had to use 32-Bit MWO on a 64-Bit System until I upgraded from 8 GB RAM to 16 GB RAM.) I guess the Minimum System Requirements just increased hard for MWO, and that's going to narrow the crowd of who can play... Not good at all, and makes me wish that PGI had better announced their intentions earlier on. This kind of abandoning is going to likely net them a lot of bad reviews on the Internet.
So, first of all, you can't play this game with a 32-Bit CPU.
Second, those kind of crashes you experience strongly indicate a faulty RAM Module, you should do a Memtest86 to find the error. In my experience, every second to third sold RAM Module, especially when clocked beyond the minimum for the respective Standard (e.g. DDR3-1333 or DDR4-2133), is faulty.
This doesn't occur with 32-Bit, because it doesn't have the capacity to adress the Memory that is faulty, bc 4 GB RAM - VRAM = Max RAM.
Third: It's 10 bucks, like literally 10 bucks to buy a 64-bit Windows. You are going to profit from that, because running 32-Bit Applications on a 64-Bit OS will decrease the performance in many cases.
#323
-
-
- Shredder
- 1,907 posts
Member
- LocationFracking the third toaster.
Posted 17 April 2018 - 10:38 PM
I must say (and i only say this very rarely when PGI actually get something right) I'm impressed with the new mechlab.
As for loading times now getting noticeably longer on first load to splash screen not so much. Also looks like its going to crash more, at least it reloaded the match faster after rejoining.
Had a look into solaris and had no idea what to do, just about figured out how to chose one of my own mechs. Clickathon!
As for loading times now getting noticeably longer on first load to splash screen not so much. Also looks like its going to crash more, at least it reloaded the match faster after rejoining.
Had a look into solaris and had no idea what to do, just about figured out how to chose one of my own mechs. Clickathon!
#324
-
-
- Bad Company
- 102 posts
Member
- Locationozz
Posted 17 April 2018 - 11:02 PM
Mikayshen, on 17 April 2018 - 06:37 PM, said:
Things that need to be addressed:
1. Load in times after a match back to the mech bay, I don't know about other people but I went from (what feels to be) 30ish seconds after clicking 'end match' to a full 1 minute 14 seconds (yes, I used a stopwatch). This is unacceptable and makes me not want to play until it's addressed and rectified.
2. An option to turn off the cache progress popup. There's a progress bar, I don't need a popup.
3. An option to turn off the new mech bay and return to the old one. It's only really needed for camo patterning and decal selection. If the new mech bay is the primary reason for load times then an option to turn off the new system seems like a good thing, with the option to turn it on when entering the camo section.
1. Load in times after a match back to the mech bay, I don't know about other people but I went from (what feels to be) 30ish seconds after clicking 'end match' to a full 1 minute 14 seconds (yes, I used a stopwatch). This is unacceptable and makes me not want to play until it's addressed and rectified.
2. An option to turn off the cache progress popup. There's a progress bar, I don't need a popup.
3. An option to turn off the new mech bay and return to the old one. It's only really needed for camo patterning and decal selection. If the new mech bay is the primary reason for load times then an option to turn off the new system seems like a good thing, with the option to turn it on when entering the camo section.
Mikayshen, on 17 April 2018 - 06:37 PM, said:
Things that need to be addressed:
1. Load in times after a match back to the mech bay, I don't know about other people but I went from (what feels to be) 30ish seconds after clicking 'end match' to a full 1 minute 14 seconds (yes, I used a stopwatch). This is unacceptable and makes me not want to play until it's addressed and rectified.
2. An option to turn off the cache progress popup. There's a progress bar, I don't need a popup.
3. An option to turn off the new mech bay and return to the old one. It's only really needed for camo patterning and decal selection. If the new mech bay is the primary reason for load times then an option to turn off the new system seems like a good thing, with the option to turn it on when entering the camo section.
1. Load in times after a match back to the mech bay, I don't know about other people but I went from (what feels to be) 30ish seconds after clicking 'end match' to a full 1 minute 14 seconds (yes, I used a stopwatch). This is unacceptable and makes me not want to play until it's addressed and rectified.
2. An option to turn off the cache progress popup. There's a progress bar, I don't need a popup.
3. An option to turn off the new mech bay and return to the old one. It's only really needed for camo patterning and decal selection. If the new mech bay is the primary reason for load times then an option to turn off the new system seems like a good thing, with the option to turn it on when entering the camo section.
Mikayshen, on 17 April 2018 - 06:37 PM, said:
Things that need to be addressed:
1. Load in times after a match back to the mech bay, I don't know about other people but I went from (what feels to be) 30ish seconds after clicking 'end match' to a full 1 minute 14 seconds (yes, I used a stopwatch). This is unacceptable and makes me not want to play until it's addressed and rectified.
2. An option to turn off the cache progress popup. There's a progress bar, I don't need a popup.
3. An option to turn off the new mech bay and return to the old one. It's only really needed for camo patterning and decal selection. If the new mech bay is the primary reason for load times then an option to turn off the new system seems like a good thing, with the option to turn it on when entering the camo section.
1. Load in times after a match back to the mech bay, I don't know about other people but I went from (what feels to be) 30ish seconds after clicking 'end match' to a full 1 minute 14 seconds (yes, I used a stopwatch). This is unacceptable and makes me not want to play until it's addressed and rectified.
2. An option to turn off the cache progress popup. There's a progress bar, I don't need a popup.
3. An option to turn off the new mech bay and return to the old one. It's only really needed for camo patterning and decal selection. If the new mech bay is the primary reason for load times then an option to turn off the new system seems like a good thing, with the option to turn it on when entering the camo section.
Mikayshen, on 17 April 2018 - 06:37 PM, said:
Things that need to be addressed:
1. Load in times after a match back to the mech bay, I don't know about other people but I went from (what feels to be) 30ish seconds after clicking 'end match' to a full 1 minute 14 seconds (yes, I used a stopwatch). This is unacceptable and makes me not want to play until it's addressed and rectified.
2. An option to turn off the cache progress popup. There's a progress bar, I don't need a popup.
3. An option to turn off the new mech bay and return to the old one. It's only really needed for camo patterning and decal selection. If the new mech bay is the primary reason for load times then an option to turn off the new system seems like a good thing, with the option to turn it on when entering the camo section.
1. Load in times after a match back to the mech bay, I don't know about other people but I went from (what feels to be) 30ish seconds after clicking 'end match' to a full 1 minute 14 seconds (yes, I used a stopwatch). This is unacceptable and makes me not want to play until it's addressed and rectified.
2. An option to turn off the cache progress popup. There's a progress bar, I don't need a popup.
3. An option to turn off the new mech bay and return to the old one. It's only really needed for camo patterning and decal selection. If the new mech bay is the primary reason for load times then an option to turn off the new system seems like a good thing, with the option to turn it on when entering the camo section.
Mikayshen, on 17 April 2018 - 06:37 PM, said:
Things that need to be addressed:
1. Load in times after a match back to the mech bay, I don't know about other people but I went from (what feels to be) 30ish seconds after clicking 'end match' to a full 1 minute 14 seconds (yes, I used a stopwatch). This is unacceptable and makes me not want to play until it's addressed and rectified.
2. An option to turn off the cache progress popup. There's a progress bar, I don't need a popup.
3. An option to turn off the new mech bay and return to the old one. It's only really needed for camo patterning and decal selection. If the new mech bay is the primary reason for load times then an option to turn off the new system seems like a good thing, with the option to turn it on when entering the camo section.
1. Load in times after a match back to the mech bay, I don't know about other people but I went from (what feels to be) 30ish seconds after clicking 'end match' to a full 1 minute 14 seconds (yes, I used a stopwatch). This is unacceptable and makes me not want to play until it's addressed and rectified.
2. An option to turn off the cache progress popup. There's a progress bar, I don't need a popup.
3. An option to turn off the new mech bay and return to the old one. It's only really needed for camo patterning and decal selection. If the new mech bay is the primary reason for load times then an option to turn off the new system seems like a good thing, with the option to turn it on when entering the camo section.
#325
-
-
- Shredder
- 1,907 posts
Member
- LocationFracking the third toaster.
Posted 17 April 2018 - 11:12 PM
InnerSphereNews, on 13 April 2018 - 04:32 PM, said:
Top Matches to Spectate
A list of the top 5 most competitive matches will be available for others to spectate (based on Elo ranking). These 5 top matches will consist of players with high Elo ranking with the smallest Elo gap between the competitors. The number of remaining spectator slots available will be displayed in this area and access is given on a first come first serve basis. At the start of every season, spectator viewing of matches will not populate until players start breaking into the high Elo ranks. When matches start to appear, players will know that these matches will be with the high competition players.
Wait!
ELO! Can we bin this PSR **** in the rest of the game and go back to ELO then!!!???
#326
-
-
- Urban Commando
- 1,202 posts
Member
- LocationSelling baguettes in K-Town
Posted 18 April 2018 - 12:27 AM
I can play as stock Winged Urbanmech, can't complain about the new mode. ¯\_(ツ)_/¯
#327
-
-
- 4,305 posts
Member
Posted 18 April 2018 - 12:52 AM
Ed Steele, on 17 April 2018 - 05:27 PM, said:
I would like to get the stuff from my Caches though.
Go to "MechLab Home > Inventory (Left-Hand Side) > Supply Caches (Left-Hand Side)" and enjoy... You should find them there, from what the Patch Notes showed.
Naitrael, on 17 April 2018 - 10:28 PM, said:
<<<snip>>>
So, first of all, you can't play this game with a 32-Bit CPU.
Second, those kind of crashes you experience strongly indicate a faulty RAM Module, you should do a Memtest86 to find the error. In my experience, every second to third sold RAM Module, especially when clocked beyond the minimum for the respective Standard (e.g. DDR3-1333 or DDR4-2133), is faulty.
This doesn't occur with 32-Bit, because it doesn't have the capacity to adress the Memory that is faulty, bc 4 GB RAM - VRAM = Max RAM.
Third: It's 10 bucks, like literally 10 bucks to buy a 64-bit Windows. You are going to profit from that, because running 32-Bit Applications on a 64-Bit OS will decrease the performance in many cases.
So, first of all, you can't play this game with a 32-Bit CPU.
Second, those kind of crashes you experience strongly indicate a faulty RAM Module, you should do a Memtest86 to find the error. In my experience, every second to third sold RAM Module, especially when clocked beyond the minimum for the respective Standard (e.g. DDR3-1333 or DDR4-2133), is faulty.
This doesn't occur with 32-Bit, because it doesn't have the capacity to adress the Memory that is faulty, bc 4 GB RAM - VRAM = Max RAM.
Third: It's 10 bucks, like literally 10 bucks to buy a 64-bit Windows. You are going to profit from that, because running 32-Bit Applications on a 64-Bit OS will decrease the performance in many cases.
Well, someone who took my post as if I had been knocked offline... Nice misread... What are you smoking?
Anywho, some return thoughts for you...
1.) Only since this Latest Patch... Before, 32-Bit CPUs could still play, providing they were fast enough... I think PGI still did a bad thing, as I'm sure I'm going to find people who were playing actively, and are on my Friend List, to be Not Online for a while. Means my Online Mech Battles are going to be a little less enjoyable.
2.) Actually, I was running out of RAM on 8 GB with the 64-Bit MWO Client. That's what caused the crashes, as between the OS/MWO/GPU, they were trying to eat up more than a value of 8 GB RAM. The RAM was not faulty by any means. Having been able to do an Upgrade to 16 GB RAM fixed this, so the 64-Bit Client is no longer choking due to the OS and GPU trying to eat up RAM around it. Just so happens my NVidia GPU keeps needing System RAM thanks to MWO's being rather texture-heavy.
3.) Already running 64-Bit Windows 7 here, so I'm still able to play MWO myself. However, people have to have a 64-Bit CPU, or that level of Windows won't run. Oh, and by the way, IT COSTS A [BEEP]-TRAIN MORE THAN $10 USD IN THE USA TO PURCHASE MICRO$OFT WINDOWS!!! Any friends I had who were limited to 32-Bit MWO due to their CPU just got Effectively Banned out from under me. People being Removed from the game (or again, Effectively Banned) due to lack of Hardware is a foul thing for a company to do, even PGI. Now I have to wait until they're able to get better hardware before they even have the ability to come back online.
...and now I'll walk off... with a hope that you get the picture a bit better now.
~Mr. D. V. "It wasn't for me I was voicing this, but for those I won't be seeing for a while." Devnull
#328
-
-
- The Mercenary
- 4,737 posts
Member
- LocationPoland
Posted 18 April 2018 - 12:55 AM
Naitrael, on 17 April 2018 - 10:28 PM, said:
Third: It's 10 bucks, like literally 10 bucks to buy a 64-bit Windows. You are going to profit from that, because running 32-Bit Applications on a 64-Bit OS will decrease the performance in many cases.
10 bucks that most players don't need to pay in the first place.
If you have Windows Vista or newer, you don't need to buy a new license.
Your existing license is valid for the 64-bit version.
You just need to get a 64-bit setup disc for the same SKU (Home/Premium/Pro etc) and install that version using your current product key,
#329
-
-
- Shredder
- 132 posts
Member
- LocationLiverpool
Posted 18 April 2018 - 01:15 AM
Played 3 quick play matches. 2nd one got dumped back to the login screen after about 4 minutes of play (Never had this before). Takes longer than two minutes to reload and get back into game now which is awful and I lost my rewards!
Third game never actually made it into game and ended up killing client and reloading and rejoining game and lost my rewards.
Never had issues for a long long time with connection or being dropped until this patch.
Hope its an easy fix.
Cheers
Codestar
Third game never actually made it into game and ended up killing client and reloading and rejoining game and lost my rewards.
Never had issues for a long long time with connection or being dropped until this patch.
Hope its an easy fix.
Cheers
Codestar
#330
-
-
- The Scythe
- 329 posts
Member
Posted 18 April 2018 - 01:55 AM
Come on now, 32-bit hardware is 10+ years old. We really need to get rid of old ballast. A say $300 refurb computer (or perhaps even cheaper) will do 64-bit and improve overall performance.
People, really, CHECK YOUR HARDWARE FOR 64-bit CAPABILITY. Very often computers were installed with 32-bit OSs just because the techs were too lazy to get new OS images or somesuch.
Also, if you own Vista and newer, you can upgrade to 64-bit FOR FREE (if your hardware supports that). If you have Win 7 and newer, you can even go up to Win 10, which is still out there for free as an upgrade.
And to DV - no, MWO does not use up 8G of RAM. The only time I ran into issues was when loading into a FP match when I had a browser with 10+ tabs open in the background. Closing it brought the system back to reasonable memory usage. If your machine is using more than that it may be worth checking what else is running and what is the resource usage for background apps/services.
People, really, CHECK YOUR HARDWARE FOR 64-bit CAPABILITY. Very often computers were installed with 32-bit OSs just because the techs were too lazy to get new OS images or somesuch.
Also, if you own Vista and newer, you can upgrade to 64-bit FOR FREE (if your hardware supports that). If you have Win 7 and newer, you can even go up to Win 10, which is still out there for free as an upgrade.
And to DV - no, MWO does not use up 8G of RAM. The only time I ran into issues was when loading into a FP match when I had a browser with 10+ tabs open in the background. Closing it brought the system back to reasonable memory usage. If your machine is using more than that it may be worth checking what else is running and what is the resource usage for background apps/services.
#331
-
-
- The Wrath
- 21 posts
Member
- LocationKazakhstan, Almaty city
Posted 18 April 2018 - 01:59 AM
Myrrddin, on 17 April 2018 - 04:36 PM, said:
My launcher is stuck patching - patch 1 of 2....
Tried, running the repair tool, and manually downloading the patch and making a cache folder.
Any ideas?
Tried, running the repair tool, and manually downloading the patch and making a cache folder.
Any ideas?
Have the same problem. Patching proccess stucks on "patch 1 of 2". Any solution without downloading a whole game?
#332
-
-
- Ace Of Spades
- 31 posts
Member
Posted 18 April 2018 - 02:00 AM
D V Devnull, on 18 April 2018 - 12:52 AM, said:
Well, someone who took my post as if I had been knocked offline... Nice misread... What are you smoking?
Anywho, some return thoughts for you...
1.) Only since this Latest Patch... Before, 32-Bit CPUs could still play, providing they were fast enough... I think PGI still did a bad thing, as I'm sure I'm going to find people who were playing actively, and are on my Friend List, to be Not Online for a while. Means my Online Mech Battles are going to be a little less enjoyable.
2.) Actually, I was running out of RAM on 8 GB with the 64-Bit MWO Client. That's what caused the crashes, as between the OS/MWO/GPU, they were trying to eat up more than a value of 8 GB RAM. The RAM was not faulty by any means. Having been able to do an Upgrade to 16 GB RAM fixed this, so the 64-Bit Client is no longer choking due to the OS and GPU trying to eat up RAM around it. Just so happens my NVidia GPU keeps needing System RAM thanks to MWO's being rather texture-heavy.
3.) Already running 64-Bit Windows 7 here, so I'm still able to play MWO myself. However, people have to have a 64-Bit CPU, or that level of Windows won't run. Oh, and by the way, IT COSTS A [BEEP]-TRAIN MORE THAN $10 USD IN THE USA TO PURCHASE MICRO$OFT WINDOWS!!! Any friends I had who were limited to 32-Bit MWO due to their CPU just got Effectively Banned out from under me. People being Removed from the game (or again, Effectively Banned) due to lack of Hardware is a foul thing for a company to do, even PGI. Now I have to wait until they're able to get better hardware before they even have the ability to come back online.
I don't know what you read between my lines, I just can't let sciolism stand like that, so I provided a counter argument.
1. No, you couldn't before the patch. There haven't been 32-Bit CPUs around since the Pentium 4 or Athlon XP, with which you cannot play this game.
2. The Game only fills up that large amount of RAM, if there is a memory leak, which would either have to occur in everyone's game experience or it is system-specific due to faulty memory banks. Under normal circumstances, MWO acquires between 2 and 3 GB of RAM and, depending on the Texture Quality (Low, Medium, High) => (2048, 2560, 4096) MB of VRAM.
Your VRAM load filling up to the maximum does not automatically mean it's completely required, it means that the Garbage Collection System leaves Data in the RAM to reduce GPU Load.
If your Graphics Card lacks the sufficient amount of VRAM, you have to reduce the Texture Quality. General rule of thumb.
3. And no, it doesn't, you can even get Win 7 from ebay for 3 bucks
Also, thanks to Horseman for mentioning that you don't have to buy a new OS for getting 64-Bit.
I hope you realize that you didn't actually have any picture of this subject matter and that you could have just googled this and be the wiser.
#333
-
- Ace Of Spades
- 4 posts
Rookie
Posted 18 April 2018 - 03:39 AM
Got some bolt-ons from supply cathes, but cant put them on my mech or find them anywhere as owned (they are tusks for atlas). What am i doing wrong?
Edited by Comrade1, 18 April 2018 - 03:41 AM.
#334
-
-
- The Pharaoh
- 806 posts
Member
- LocationGermany
Posted 18 April 2018 - 03:55 AM
HandsomeJBW, on 18 April 2018 - 01:59 AM, said:
Have the same problem. Patching proccess stucks on "patch 1 of 2". Any solution without downloading a whole game?
Jep waiting. If it is stuck, be patient for some minutes and it will continue.
#335
-
-
- The God
- 1,441 posts
Member
Posted 18 April 2018 - 04:07 AM
Ed Steele, on 17 April 2018 - 06:52 PM, said:
I think it has been like that since they did the most recent visual pass on the Atlas.
Yeah, that was this patch. I was playing with my Founder's Atlas most of Monday, and it did NOT look like this... I really hate it, I want my awesome skull back.... Was one of the best looking mechs until this...
#336
-
-
- Legendary Founder
- 1,494 posts
Member
- LocationAm Grill
Posted 18 April 2018 - 06:23 AM
Jaspbo1, on 17 April 2018 - 03:07 PM, said:
Also, the Firestarter looks hilarious.
Indeed! As i said. It's horrible ...
The position of the MG's should be back in the hip area. These shooting breasts are just embarrassing.
#337
Posted 18 April 2018 - 06:43 AM
HandsomeJBW, on 18 April 2018 - 01:59 AM, said:
Have the same problem. Patching proccess stucks on "patch 1 of 2". Any solution without downloading a whole game?
I had the same issue. I finally updated the MWO Portal and was able to download the patch with no problem. So if you haven't upgraded the portal try that.
#338
-
- Ace Of Spades
- 4 posts
Rookie
Posted 18 April 2018 - 06:59 AM
q
Edited by Comrade1, 18 April 2018 - 07:01 AM.
#339
-
-
- The Wrath
- 21 posts
Member
- LocationKazakhstan, Almaty city
Posted 18 April 2018 - 07:17 AM
Bishop Six, on 18 April 2018 - 03:55 AM, said:
Jep waiting. If it is stuck, be patient for some minutes and it will continue.
Well, waited for an hour... Patching progress still doesn't move. Restarting portal also not helps
UPDATE: Reinstalled portal and patching was succesful!
Edited by HandsomeJBW, 18 April 2018 - 07:53 AM.
#340
-
-
- Shredder
- 3,685 posts
Member
- LocationDusting off my Mechs.
Posted 18 April 2018 - 07:57 AM
D V Devnull, on 18 April 2018 - 12:52 AM, said:
Go to "MechLab Home > Inventory (Left-Hand Side) > Supply Caches (Left-Hand Side)" and enjoy... You should find them there, from what the Patch Notes showed.
Yes, thank you, I already knew that. I was mainly trying to find my bolt-ons, before I found out that they are Mech / Variant specific and there is no way to view them unless you are blessed to somehow guess which Mech / Variant they are for (if you did not see that info when the cache was opened).
5 user(s) are reading this topic
0 members, 5 guests, 0 anonymous users
