326 replies to this topic

[InnerSphereNews]

STATUS UPDATE AND KNOWN ISSUES

OG POst Nov 22nd

1st UPDATE Nov 25tH

2nd update Dec 1st

2ND UPDATE DEC 1ST:

Hey everyone, I just wanted to provide another update as we head into the weekend. I appreciate everyone voicing their thoughts on the forum and understand the frustrations that can grow from an unreliable gameplay experience. I know communication and transparency can go a long way to ease those tensions, so with that in mind, here is the latest update.

We have spent the last few days testing both the current build and the "Great Bolt-On ID Cull" build, and we are happy to report that we are optimistic about moving forward with this change next week. I will explain why we are waiting until next week, but first, here is some interesting information about this change.

Currently, MWO has 22,288 items in the database. These item IDs encompass Mechs, Engines, Weapons, Equipment, Patterns, Colors, Decals, Titles, Badges, Cockpit Items, and Bolt-ons.

Here are the stats for the current live item ID Database:

• Total Items: 22,288
• Total Bolt-on Items: 12,381

Of the 22,288 item IDs, 12,381 are bolt-on IDs. That is around 55.5% of the items in the database.

This is why bolt-ons have been targeted as the best possible optimization.

Here are the stats for the new optimized Bolt-on ID Database:

• Total Items: 10,431
• Total Bolt-on Items: 529

Bolt-ons now make up 5% of the items in the database.

What I find interesting is the majority of the Bolt-ons were added in the original release of the bolt-on system in April 2018. The patch that released the bolt-on Faction Flags was probably the second-largest addition of bolt-ons. Here we are 5.6 years after the addition of bolt-ons, and we appear to have hit a theoretical item cap of 22,288 items in the database (using the current system).

Another interesting stat is we only added a total of 706 new Item IDs to the Database this entire year. Again, these 706 item IDs encompass EVERYTHING we added this year: Mechs, Weapons, Patterns, Colors, Decals, Titles, Badges, Cockpit Items, and Bolt-ons.

So with this optimization, we have given ourselves lots of room to continue to add content to the game for the foreseeable future!

So let's get back to the fix. We are waiting until next week for the fix for a few reasons.

1. We want to continue to test both the Current and New Build to make sure the patch is safe to deploy.
2. The change is significant as it will affect many areas of the Database, not just the Item IDs. Player Inventory, Player Loadouts, Player Purchase Trail, and more all have to transition and align with the new Item IDs so the systems that rely on them can continue to function properly (Events rewards systems, Customer support tools, etc.). This requires testing those systems as well.
3. We prefer to patch early in the week to have support available to address individual player issues before the weekend.

We haven't got a date and time locked in yet, but we will let you know as soon as we do.

CURRENT EVENTS:

We have both the Free Mech Event and The Longbow Challenge event running right now. Both events will receive an extension once the patch is live. I am currently thinking of adding a 10-day extension to both.

UPCOMING EVENTS:

The compensation event and all the Holiday events will not be posted or started until the patch is live, and we can confirm on the live environment that everything is back to normal.

UPCOMING PATCH:

The December Patch is still on track for December 13th; we will let you know if this changes.

Keep sharing your thoughts on the forums (I am reading all the posts), and we are truly grateful for your passion for MechWarrior Online.

I can't wait for this fix to be out so we can look toward the future and all the great stuff coming next year to MechWarrior Online: Legends, MechWarrior 5: Mercenaries, and MechWarrior 5: Clans.

Again we want to thank you for your patience and understanding,

The MechWarrior Online Team

P.S. It has occurred to me that we will need to update players on how bolt-ons will behave post-patch - that information will come with the Patch notes for the bolt-on changes next week.

1ST UPDATE NOV 25TH:

We understand that the ongoing situation is less than ideal, and we want to assure you that we are actively addressing the issues. We have allocated the necessary resources to resolve these issues promptly and are committed to providing a confirmed fix at the earliest opportunity. Given the complexity of the problems, we are approaching the resolution methodically.

Here's a brief overview of the current plan:

Server Disconnect Issue:

We suspect that the disconnect problem stems from an excess of items in the game. The server loads the database of items that players can potentially equip, cross-referencing it with player loadouts. Due to the growing number of items, servers are timing out during attempts to load both the database items and player loadouts.

Our current best solution involves consolidating bolt-ons. Each bolt-on currently has a unique ID for each Mech it works with, resulting in tens of thousands of IDs. We have reduced this to fewer than 1000 IDs, allowing players to equip certain bolt-ons across multiple mechs for a more flexible system. Testing for this fix is currently underway.

Testing the Fix:

One challenge we face is replicating the issue during testing. The original problem did not surface in our pre-release testing on the staging environment. Our QA team is actively working to reproduce the issue reliably with the old version to confirm the fix in the new version. This process is ongoing but progressing slowly due to build times and deployment processes.

Deploying the Fix:

Before deploying the fix, player items need reconfiguration to align with the new bolt-on systems. A database script is being created and tested to ensure the integrity of player items. We are working efficiently on the potential fix, and if possible, we will implement a hotfix. If needed, we may consider a slight delay in the December patch to ensure a thorough resolution.

Side Note:

The Centurion crash has been confirmed fixed, though integration into the bolt-on fix is uncertain. Our priority remains addressing server disconnects. If the Centurion Fix cannot be integrated, it will be included in the December patch.

Closing:

We want to emphasize that we are diligently working to resolve all critical issues, prioritizing your ability to enjoy the game. Your experience is as important to us as it is to you. We have exciting plans for December, but none of it matters if the game isn't functioning reliably.

Compensation:

Once the fix is deployed, we plan to host an event with compensation as a gesture of appreciation. We look forward to celebrating together.

Thank you for your continued patience and understanding.

ORIGINAL POST:

Greetings MechWarriors,

Matt Newman here wanted to give you a status update on MechWarrior Online post-Nov Patch.

We have a few known issues occurring intermittently.

Errors preventing players from connecting to games which results in an error message

• We originally thought this was an issue with EU servers only.
• We are continuing to investigate this issue and will update you when we have a solution.
• This issue is having a knock-on effect of locking Mechs in match until the match terminates

Mechs not visible post-match

• on occasion, players' mechs will not be visible in their account post-match
• They are not lost and will reappear upon re-logging into the client

Intermittent Crashes

• We have identified an issue with Centurion variants that were causing crashes and the fix is confirmed
• The Variants Casuing the issues are CN9-AH(L), CN9-A(NCIX), CN9-D(P)
• The Onyx is safe to use :)

Bolt-on and Decal Sale

• The bolt-on and Decal sale was causing long connect times due to downloading the Sale stats
• This happens anytime we put a large set of items on sale
• We disabled the Bolt on and decal Sale Earlier last week
• We are working to optimize the Bolt-on system to make sales possible in the future.

Other Issues:

• If you are aware of other issues please contact: support@mwomercs.com

As we work towards fixes we are also completing the work on the December Patch which is scheduled to release on Dec 13th.

Depending on where we are in the patch cycle and the continuing severity of the Issues we may not be able to Hot Fix before Dec 13th as Hot Fixes tend to block Patch progress on multiple fronts. Our #1 goal is to resolve the issues and deliver the Dec patch content.

One last update is we will be continuing our tradition of an event-filled holiday Season this year so keep a look out for upcoming announcements for:

• Advent Event Daily Challenges
• The Holiday Bonus Mech Event
• The Holiday Christmas Card Email
• New Years XPerience
• In-Game Sales and MWO Sales on Steam and MWO Store
• MW5 Sales on Various Storefronts

See you on the Battlefield,

The MechWarrior Online Team

[FartSniffer87]

aight bet

[Iliyena]

"Mechs not visible post-match

• on occasion, players' mechs will not be visible in their account post-match
  
• They are not lost and will reappear upon re-logging into the client"

This bug have been a part of the game forever right, happened to me sometimes, it can be almost every mech, just all the Clans or all but the Mediums and such. But as said it can be fixed by restarting/relogin. </p>

[Void Angel]

Huh. I've never seen it before; likely the increase is linked to whatever's causing the servers to be borked.

[Tarzan of Barsoom]

Are players bounced from matches with that error message getting penalized PSR wise as if abandoning or losing a game with a zero match score?

[BlueDevilspawn]

Tarzan of Barsoom, on 28 November 2023 - 03:33 PM, said:

Are players bounced from matches with that error message getting penalized PSR wise as if abandoning or losing a game with a zero match score?

From what I've seen on streams, it doesn't appear to be the case as the entire lobby is bounced. Doesn't seem to create a PSR drop, but that's just anecdotal/visual.

Thanks for the update PGI, good luck with the fixes.

[rascje]

Two matches in a row crashed... with two mechs blocked in game... and it's no more possible reconnect...
...
...
Very nice!!!

[ghost1e]

really unfortunate that this is right before the worlds grand final

[rascje]

Really?..
Other two games in a row crashed.
Both NA and EU servers have the same problem...
No more comment

[Oozie Man]

Tarzan of Barsoom, on 28 November 2023 - 03:33 PM, said:

Are players bounced from matches with that error message getting penalized PSR wise as if abandoning or losing a game with a zero match score?

This issue is still going on, just happened to me and locked my mech inside.

[Sierra3]

Just kicked out of three match attempts... no server... mechs cannot be used as they are locked.

Kicked out of 4th attempt, at Initiating Drop screen. NA Server.

Edited by Sierra3, 28 November 2023 - 05:40 PM.

[Eiji Sixfinger]

Spent the last two hours getting to match selection, but never lobby, then kick and locking mechs. Currently unplayable for me.

[shockdiode]

Eiji Sixfinger, on 28 November 2023 - 05:34 PM, said:

Spent the last two hours getting to match selection, but never lobby, then kick and locking mechs. Currently unplayable for me.

Experienced the same thing just now.

"Depending on where we are in the patch cycle and the continuing severity of the Issues we may not be able to Hot Fix before Dec 13th"

Alrighty then... see you in a few weeks I guess.

Edited by shockdiode, 28 November 2023 - 06:06 PM.

[killkimno]

pgi, Longbow 12-R(S) Screen shakes too much when using jump jet
This problem is the same as when Atlas K3 first came out.

[PeacockBassSVT]

Game appears to crash at the end of each match regardless of mech used. Haven't had any issues until late so assuming its this. Otherwise having a fun time when able to play.

[TheCaptainJZ]

I'm guessing you guys are getting bounced if anyone in the match is using one of the affected mechs. The only way I think they could filter those out is with the Event Queue Match Maker?

Appreciate the update, Matt.

Edited by TheCaptainJZ, 28 November 2023 - 06:57 PM.

[Tarzan of Barsoom]

Any plans to do anything for premium time that was wasted during this blackout period of not being able to play?

[PraetorGix]

Tarzan of Barsoom, on 28 November 2023 - 03:33 PM, said:

Are players bounced from matches with that error message getting penalized PSR wise as if abandoning or losing a game with a zero match score?

I sure hope not, I'm struggling as it is to stay in tier 3 and today has been a trainwreck of being kicked off of one match after another...

[T B Kind]

Thank you for the update. GL

[Tarl Cabot]

TheCaptainJZ, on 28 November 2023 - 06:54 PM, said:

I'm guessing you guys are getting bounced if anyone in the match is using one of the affected mechs. The only way I think they could filter those out is with the Event Queue Match Maker?

Appreciate the update, Matt.

Being bounced back to mechbay No Server indicates the players have not unchecked the EU server. Afaik, PGI would need to patch to remove that option without a player doing anything.

The temporary disappearing mechs, from personal experience and testing, occurs after a failed drop when the game attempts to send me to the EU server then kicked back to the mechbay. The tons of empty mech bays shows its face when logged out of the game then back in while the EU mech is still locked in for the 15min timer. And of the 3 "tests" did not resolve itself until that EU mech was freed up then relogging out/back into the game.

And for those who, for one reason or another, still cannot change the servers within the game, please review the following to make a change to one game file.

Scroll down to the folder C:\Users\Windows log in name\Saved Games\MechWarrior Online\Profiles then the folder with your pilot's name.

Locate and open up attributes.xml with notepad. Cntrl F (Find bar) then search for Region. Change the number to match which server(s) you want to be selected then save. Make sure you are logged completely out of the game before editing.

<Attr name="RegionSelection" value="1"/> NA only This one
<Attr name="RegionSelection" value="2"/> EU only
<Attr name="RegionSelection" value="3"/> NA-EU only
<Attr name="RegionSelection" value="4"/> OC only
<Attr name="RegionSelection" value="5"/> NA-OC only Or this one!!
<Attr name="RegionSelection" value="6"/> EO-OC only
<Attr name="RegionSelection" value="7"/> NA-EU-OC (all 3 default)

Edit - Just seeing others who are now getting the No Server on the NA only. Oh well

Edited by Tarl Cabot, 28 November 2023 - 07:48 PM.