@hoboadam_psn said in Here's what's happening with the servers.:

I've taken quite a few tries at explaining the issue in various threads, so I'm going to make one myself, and offer to SDS to help. They have my contact information.

Stress balancing is broken on the server node for the menu interfacing.

There's send and receive functions embedded everywhere in every menu that sends data after a function is performed, IE, conquest victory, moment completions etc. When you complete the task, data is sent from your console to a server and logged. For a user to see it at a splash screen post event, a call script reaches out to the data repository and shows your progress.

Whenever you are getting the unhandled server exception, it's like timing out on a ping. The game will then attempt a refresh, thus your little button icon in the bottom right of your screen.

Sometimes you get partial and get bounced back to the main screen of the menu you are in, and sometimes booted completely out to the main game menus.

Whenever you try to log back in to where you were, you are inadvertently creating additional traffic because the data from your console hasn't been reconciled with the data server. This reconciliation actually has happened, which is why you aren't losing progress 95% of the time.

Take these errors and multiply them by the number of users on at any given time, the people banging buttons trying to get back in, and data cached with nowhere to display it because you're already out of that menu. SDS dumps the returned data when you are logged back in and at another menu, but it has to record the failed attempts.

It's an exponential function problem that needs to be debugged because the call time of the functions can't possibly get returns why? Because Xbox game pass created too many users and user requests throughout the game.

Solutions?

1- Change some of the menus. Require us to only go to one spot to get anywhere. Right now for example, I can enter moments from inning programs and moment menus. How do I know this is an issue? When you access a moment from the Inning screen, you get taken all the way out afterwards. If you were in the moments menu, you get taken back out to the moment menu. It's all in the coding.

Dedicate more nodes, bandwidth for menu navigation calls. The game plays awesome. Whenever you're actually doing anything, it's smooth as silk. All the troubles are menus. XP, parallels, etc. Data is routing, being stored and ultimately being credited properly.

3- Turn off the web site marketplace untill you eliminate the console errors. It will hurt and stink, but you need a cleaner production environment to test your fixes.

Ultimately, SDS is going to have to reboot servers everyday because these issues must be fixed in a production environment. They need to trim down the production environment in order to resolve though.

Gotta walk before you can run.

I'd bet a good bottle of 1986 Chateau Rothschild that I'm on point with my diagnosis and potential fixes. I've fixed this type of code before for Morgan Stanley and know what I'm talking about.

Thank you for your time.

Exactly what a self aware AI would want us to believe before it launches the nukes! Fear the singularity! :P. For real though you sound like a pretty knowledgeable programmer! Maybe they’ll listen but I’d imagine if they have good programmers there they know this but maybe not!?

Community Forum

CrunkLogic_XBL