Sooo… how about that 3sec (sometimes more) delay just when changing zones? And sometimes even in the same zone (Burning steppes --> touching the stairs up to BRM). Since the servers hosted by russian kids in their basements has overthrown these in quality by x1000 i wonder how high the sub fee has to be until you fix this amazingly bad game?
Never experienced this - not once
The change from feralas to 1k Needles is the worst, takes so much time you just need to take your hands of the keyboard and see where you end up
Really - sounds like you have a hardware issue
1 Like
yes i guess my brand new hardware is the problem, and for everyone else i play with.
Yes - definitely sounds like a hardware issue
As I said - never experienced the issue you are describing
1 Like
That’s intended. Every zone is hosted on a different “server” that you need to connect to. Nostalrius had the same thing.
It’s 100% not a hardware issue. Try PvPing across areas like the pass between Badlands and Searing Gorge or the very entrance of a city like Orgrimmar and the jumps are atrocious. Everyone I’ve talked to about it in my realm have experienced it.
If you have been in such a situation and you haven’t noticed it it might be because perhaps in smaller realms they wouldn’t have to split load in the same way, or just you were not doing anything at the moment of said transitions. It gets particularly awful as melee.
I wouldn’t say “intended” but “a side-effect of current implementation”. If this is the best performance compromise they could come up with, it’s pretty disappointing.
Do you mean lag - which is a hardware issue
It’s not a user hardware issue because they can’t do anything to prevent it.
But please, spare me the pain of continuing with this conversation if you’re not going to say anything remotely useful. I’m still having migraine from the last one.
It’s not necessarily Blizz hardware either - it can be anywhere between your router and the Blizz servers
Throughout WOD and Legion Virgin UK clients has issues with lag caused by the Virgin DNS - cured by using Google’s instead
Very easy to blame the Client or Blizz Hardware - not very often the whole story
Edit- as an aside for those suffering lag in high population encounters check your FPS settings - changing to min 30 max 60fps can often cure a multitude of open world lag issues
Hplovecraft, it’s the server’s intended network design. It’s been like this since day 1, perhaps you just aren’t aware of your surroundings enough to notice it?
It has to do with what was mentioned earlier, how you go from one world server to another, because the world server got layers for each zone so you cross from one layer (kinda different from the layering™ tech that was basically a different form of sharding from retail), that was for one zone, you then transition into the layer for the next zone, and this carries with it a tiny but noticeable interruption of information flow.
You can see it when running from durotar to the inside of orgrimmar, some will be running on the spot and then rubberband to where they actually are if you run from one zone to the next at the same time as they do.
1 Like
I don’t disagree with you - but I simply don’t see any noticeable lag
So I still would suggest hardware is the issue
I had awful problems in Legion with load screens - I input WorldPreloadNonCritical 0 and the issue evaporated
Same with world boss fights - set min/ max FPS and the lag disappeared
So I’m not suggesting the Blizz world engine is ideal - artificial lag is a bummer
But I think some folk are suffering by having equipment set up for a modern game rather than an emulation off a 15 year old game
I sense as well that at least one response was alluding to huge WPvP events on area borders
Try reducing your draw distance, graphic quality and FPS- see if it makes a difference
Edit- as an afterthought - it is not unlikely that the player you see run in the spot and then ‘rubberband’ sees himself running normally across the ‘border’ of the servers
You see the information your client renders in front of you - which is not necessarily the same as another players client will show them
And it is hardware and hardware settings which has the greater impact upon that effect
You’re basically throwing spaghetti on the wall with your suggestions, when it isn’t even related.
Sorry, but this one is actually legitimately connected to the servers themselves. The rubberband effect isn’t connected to any hardware thing at all when it’s consistently happening under the same circumstances such as changing zones with others nearby. That’s the server itself.
PS:
The game is set up on the Legion engine, there’s no legacy issues of hardwares not “matching” it.
1 Like
Set up two machines next to each other logged to different accounts and then run through an area you feel affected by the lag
See what each player would see
I suspect each will have a different rendering in front of them
You seem to be heavily misunderstanding the way rendering works and how it can present symptoms of problems.
The rubberband effect is a symptom exclusive to network effects. While it can happen if a person on the “client side” so to speak, is suffering from packet loss, which can be due to a network card or a wire or the router and so on as well of course.
But when everything else is working fine, as well as the diagnostic tool I’ve got on the side is showing everything as fine (pingplotter), as well as other people seeing the same symptoms under the exact same conditions; then that’s a server thing.
2 Likes
No - run out of undercity on your mount and up to the Zep platform - sometimes you will stay mounted half way up the stairs and sometimes you will dismount immediately
That’s a delay in your position being correctly interpreted by your hardware - if somebody is riding next to you sometimes you’ll dismount straight away and they will ride up the steps - again - that’s a delay within your hardware - not Blizz
Uh no, that’s a network effect. Not related to the hardware per se other than possibly being related to that network equipment stuff I referred to in the previous post.
And with possibly, I don’t mean it can be that way in an absolute. I mean it can coincide as a symptom for issues with such things, but it’s regularly a network effect due to the server’s way of dealing with information in a psuedo-real time.
There are lots of priority settings to specific kinds of information in regards to the way this works.
A friend of mine tried to explain the concept to me - and I probably try to over simplify
You are running a gps for every NPC, mob and player at all times - you machine is receiving their position and any actions they are performing in ‘real time’ and rendering it in front of you
Any list or delayed data will display as a glitch and when you are rendering at max texture and draw distance in a ‘busy area’ this will create mid-matches between where you Machine and Blizz think something is and where your GPU has drawn it
I run a fast 6 core processor with very modest on board graphics because I have not connected my Apple eGPU ( have not worked out how to mount it on the wall behind the TV) - I don’t see the issues you are describing
The built in latency - spell batching - is there to try and eliminate mis-matches between locations and actions between machines
I think many issues we see reported are not caused by the Blizz servers but but the users local hardware and network settings
I understand that you disagree - and I don’t play on an overpopulated PvP server - but I believe their is an issue with the Blizz engine talking to modern gaming machines in its current build