Is it too much to ask on XBOX ONE to not have game menus lag? For Pete’s sake it’s getting real old. I’m tired of accidentally clicking the wrong things and messing stuff up. Why is it so hard to get smooth menus in 2017?
> 2535425339399643;1:
> Is it too much to ask on XBOX ONE to not have game menus lag? For Pete’s sake it’s getting real old. I’m tired of accidentally clicking the wrong things and messing stuff up. Why is it so hard to get smooth menus in 2017?
I know what you mean. I’m searching thrn go through reqs or anything, then it lags, I press B, thrn B, then I’m in menu
> 2533274836333284;2:
> > 2535425339399643;1:
> > Is it too much to ask on XBOX ONE to not have game menus lag? For Pete’s sake it’s getting real old. I’m tired of accidentally clicking the wrong things and messing stuff up. Why is it so hard to get smooth menus in 2017?
>
> I know what you mean. I’m searching thrn go through reqs or anything, then it lags, I press B, thrn B, then I’m in menu
And I always sell the wrong reqs cause it takes so long to follow what you press. ugh
Yeah this is probably the most annoying thing with H5 and Xbox one in general.
> 2535425339399643;1:
> Is it too much to ask on XBOX ONE to not have game menus lag? For Pete’s sake it’s getting real old. I’m tired of accidentally clicking the wrong things and messing stuff up. Why is it so hard to get smooth menus in 2017?
I almost bought the $100 req pack bundle by accident. I had to delete my cards off my xbox to make sure it doesn’t actually happen
I agree, it can get irritating. This is why Warzone needs something like saved loadouts for each req level. Maybe they could even be automatically equipped once you reach the necessary req level?
> 2533274904158628;6:
> I agree, it can get irritating. This is why Warzone needs something like saved loadouts for each req level. Maybe they could even be automatically equipped once you reach the necessary req level?
Maybe not automatically equip you with a gear loadout right as you hit a certain rank; maybe an individual category with a Req station for loadouts themselves could work though.
I send game invites when i try to look at service records lol
> 2533274805919869;8:
> I send game invites when i try to look at service records lol
I hate when that happens especially when they actually join your lobby. One time I booted someone when I did that and sent him a mistake message and he got very salty, lol.
> 2727626560040591;9:
> > 2533274805919869;8:
> > I send game invites when i try to look at service records lol
>
> I hate when that happens especially when they actually join your lobby. One time I booted someone when I did that and sent him a mistake message and he got very salty, lol.
When they join your like uhhh sorry
The whole game has a lot of waiting. sigh…
Yeah! They really need to do better with the req things. I HATE having to select each weapon every time, and i always end up hitting the wrong one and having to do it all over again because of the lag. Some might not want the automatic loadouts, so have AN OPTION for it. JUST GIVE US THE OPTION AND EVERYONE IS HAPPY for all of these disputes
> 2533274834066497;11:
> The whole game has a lot of waiting. sigh…
honestly though
> 2535425339399643;12:
> Some might not want the automatic loadouts, so have AN OPTION for it. JUST GIVE US THE OPTION AND EVERYONE IS HAPPY for all of these disputes
That’s kind of what I was thinking
It’s not that bad. If there is lag, it’s about a second. If you’re lagging more than that, you might want to reset your Internet.
> 2533274848704527;15:
> It’s not that bad. If there is lag, it’s about a second. If you’re lagging more than that, you might want to reset your Internet.
IT’S A MENU.
.
IT’S 2017.
There should be exactly 0 lag.
Reset internet?
UI navigation should never operate on the same level as client/server communication.
Wrong way:
- Click button
- Freeze UI
- Send request to server
- Wait for response
- Repeat steps 3 & 4 for all other inputs given by user while waiting for server response
- Process everything all at once
Right way:
- Click button
- Load appropriate menu
- Process server requests in the background
(Using some sort of visual “loading” indication for any individual UI elements that actually require server information) - Repeat steps 1-3 as user continues to enter inputs
- Upon server response, check current navigation state to ensure the received data is still relevant/currently open.
If it is, populate that particular UI element. If not, cancel the server request if additional data was expected.
Note: Obviously the above is all lamen’s terms, but even the more expanded explanation is pretty basic undergrad stuff, there’s no excuse for the terrible implementation of menus on the xbox one & Halo 5.
“It’s not that bad” isn’t an argument for something that shouldn’t exist at all.
The way Microsoft has implemented menus is like going to the most expensive mechanic in town for a basic oil change, and having them pour it into your gas tank.
“It’s only a little bit of blue smoke coming out your exhaust.” No big deal, right? Just turn it off & on again.
Yeah, you’re right… the temporary blue exhaust, purely in isolation to any other factor, isn’t really that big of a deal on its own… but that’s NOT the point, now is it?
Edit:
Speaking of problems that shouldn’t exist… Man, it’s been years: someone fix auto formatting on this forum already. Hoooly. I shouldn’t have to keep editing my posts to add in non-bolded periods at the end of any line that uses bold, come on.
> 2535425339399643;3:
> > 2533274836333284;2:
> > > 2535425339399643;1:
> > > Is it too much to ask on XBOX ONE to not have game menus lag? For Pete’s sake it’s getting real old. I’m tired of accidentally clicking the wrong things and messing stuff up. Why is it so hard to get smooth menus in 2017?
> >
> > I know what you mean. I’m searching thrn go through reqs or anything, then it lags, I press B, thrn B, then I’m in menu
>
> And I always sell the wrong reqs cause it takes so long to follow what you press. ugh
Yep it’s so brutal how many big she these things have and still have to this day
> 2535425339399643;12:
> Yeah! They really need to do better with the req things. I HATE having to select each weapon every time, and i always end up hitting the wrong one and having to do it all over again because of the lag. Some might not want the automatic loadouts, so have AN OPTION for it. JUST GIVE US THE OPTION AND EVERYONE IS HAPPY for all of these disputes
THis has been asked for since the start guess no one is listening
> 2533274834881503;16:
> > 2533274848704527;15:
> > It’s not that bad. If there is lag, it’s about a second. If you’re lagging more than that, you might want to reset your Internet.
>
> IT’S A MENU.
> .
> IT’S 2017.
>
> There should be exactly 0 lag.
>
> Reset internet?
> UI navigation should never operate on the same level as client/server communication.
>
> Wrong way:
> 1. Click button
> 2. Freeze UI
> 3. Send request to server
> 4. Wait for response
> 5. Repeat steps 3 & 4 for all other inputs given by user while waiting for server response
> 6. Process everything all at once
>
> Right way:
> 1. Click button
> 2. Load appropriate menu
> 3. Process server requests in the background
> (Using some sort of visual “loading” indication for any individual UI elements that actually require server information)
> 4. Repeat steps 1-3 as user continues to enter inputs
> 5. Upon server response, check current navigation state to ensure the received data is still relevant/currently open.
> If it is, populate that particular UI element. If not, cancel the server request if additional data was expected.
>
> Note: Obviously the above is all lamen’s terms, but even the more expanded explanation is pretty basic undergrad stuff, there’s no excuse for the terrible implementation of menus on the xbox one & Halo 5.
>
> “It’s not that bad” isn’t an argument for something that shouldn’t exist at all.
> The way Microsoft has implemented menus is like going to the most expensive mechanic in town for a basic oil change, and having them pour it into your gas tank.
> “It’s only a little bit of blue smoke coming out your exhaust.” No big deal, right? Just turn it off & on again.
> Yeah, you’re right… the temporary blue exhaust, purely in isolation to any other factor, isn’t really that big of a deal on its own… but that’s NOT the point, now is it?
>
> Edit:
> Speaking of problems that shouldn’t exist… Man, it’s been years: someone fix auto formatting on this forum already. Hoooly. I shouldn’t have to keep editing my posts to add in non-bolded periods at the end of any line that uses bold, come on.
It’s not that simple, though. While yes, it is just a UI, don’t forget that mostly everything on Xbox One is a server/client connection. This isn’t Xbox 360.
If you want to pull a service record, for example, the service record still needs to be retrieved from a particular server/place. Its not like everything is saved locally…
There’s more than one way of doing things than just YOUR way. Both “right” and “wrong” way you explained are pretty much identical. You still have to wait on things, just at different point in time within the UI.
> 2533274848704527;19:
> > 2533274834881503;16:
> > > 2533274848704527;15:
> > >
>
> It’s not that simple, though. While yes, it is just a UI, don’t forget that mostly everything on Xbox One is a server/client connection. This isn’t Xbox 360.
>
> If you want to pull a service record, for example, the service record still needs to be retrieved from a particular server/place. Its not like everything is saved locally…
That’s literally what I just explained.
> 2533274848704527;19:
> > 2533274834881503;16:
> > > 2533274848704527;15:
> > > There’s more than one way of doing things than just YOUR way.
It’s not “my way,” it’s what is referred to as “standard practice.”
It’s literally what they teach in the very most basic level of UI design.
This is the kind of fundamental design mistake that will get you flunked from an introductory course.
Again, that’s why I used the example of a mechanic pouring the oil into your gas tank: it should never happen for even the noobiest of interns, let alone a billion-dollar corporation like Microsoft. It shouldn’t even be in the discussion.
> 2533274848704527;19:
> > 2533274834881503;16:
> > > 2533274848704527;15:
> > > Both “right” and “wrong” way you explained are pretty much identical.
There’s no such thing as “pretty much” when it comes to code.
It’s either the same or it isn’t. Code works purely objectively, exactly as you tell it.
This is very important because the tiniest of changes make an enormous difference, that’s how it works.
It’s like chemistry: Water, H2O, is safe to drink. Hydrogen Peroxide, H2O2, will kill you.
You wouldn’t say they are “pretty much” identical purely based on the structure, you also have to consider how they function in real-world scenarios.
In regards to the end function, environmental reactions, common usage, etc. they are not at all similar. Same as the 2 examples I posted.
Sure you can say they are “structurally similar,” but as an overall whole, they are not.
> 2533274848704527;19:
> > 2533274834881503;16:
> > > 2533274848704527;15:
> > > You still have to wait on things, just at different point in time within the UI.
That’s exactly the point of all of this.
At no point has this ever been a discussion about avoiding waiting, that’s obviously inevitable.
This is about not freezing the UI upon user input.
The user should always get some sort of immediate feedback to indicate that their input has been accepted, to avoid accidental redundant inputs.
The “waiting” part should be completely separate from the navigation.
Imagine if anytime you clicked on a youtube video, your entire computer would just freeze up until the entire video has loaded, and then only unfreeze afterwards.
There’s no way to cancel the request, there’s no way to know if the first command was accepted, or if you didn’t fully click, or if the computer is just freezing due to something unrelated.
Again, this is all basic design principles. All of this is completely avoidable.