It reasonable to assume some form of lag compensation is happening. Pretty much standard in FPS these days.

I doubt however that it's willing to rewind upwards of 100ms or so due to entropy alone. You can only shift time around so much before it causes constant and massive desync for everyone involved. Funny things like dying from a hitscan bullet who's shooter died half a second ago would be possible. I've had this happen in crappier games, not in dust.

Actually EVE is a true TCP/IP game, and DUST utilizes UDP over TCP/IP so there is a big difference in how time stamps are handled in FPS.

I do not think that a simple orange/white orange switch is being used-I think they are using PC's with dual NICs and running a UDP flood on the transmit side.

It would look like a DDOS attack- a simple syn flood.

CCP your net code is too permissive in allowing people with bad ISP connections and your desire to have a global community-both are laudable and commendable, but you need to protect your baby (DUST514)

I love your game, I believe you are on the right track and I am supporting you financially-please feel free to look at my families DUST purchases. With this support in mind I must ask you to protect my investment in you and DUST 514.

You need to segment your regions first and then tighten up your net code. I know some of the "amazing" players will have to fix their internet situation and not be so "amazing" and the true hack/laggers will get filtered as well. I know this is a lot of work and expensive and we can manage for now, but you NEED to get it done, ready and tested before your PS4 migration.

The free riders are not helping the situation and they certainly are not here to support your baby as it grows up! They are trying to suffocate it in the crib.

My FPS friends, and I am 50yrs old so I have a lot, that have tried DUST will not play it because of the laggers, and when you combine the Proto/WASD stuff they wonder about your insight and ability to get this right.

My FPS experience started on "broken ring" IPX networks. ;-)

From my experience working at ubisoft on networked games this guy has nailed it right there !

How is it possible to lag switch on Dust?

well during some of the warping events i got rewound more than 50 meters and as a heavy that involves a sundial..
and to make clear the warping is not what i was alluding to but a point of ironic humor.

I don't think that people lag switch. It's too much trouble to go through for a video game IMO.

My FPS experience started on "broken ring" IPX networks. ;-)

If you capture the right thing off net card one going to net card two (ps3) decrypt packets find structure of delta optimized udp data, you can actually create or alter outgoing packets superseeding what the ps3 can send back, this could be controlled by software. Of course it helps alot to know how your own traffic is generated and optimized. So its highly unlikely to happen unless an insider does it, or somebody familiar with the network code of unreal engine 3 if they use that or any network engine. but you know, the blueray code was deemed unbreakable. The ps3 was broke up also, who knows what an intelligent felow with lots of time on their hands can achieve for personal fun. In the end software is always breakable, spoofable and inherently as secure as the people made it to be. Would you want to know more, try to get your hands on raknet lib, all these things are implemented. What is actually hard is to make sense of the information going from the server to the client because its optimized ajd make very little sense structure wise, but there is only that much same info going on while shooting and moving, two things that can be nailed down. All these info are pretty much common knowledge to game developpers.

I also second the comment on priority of packets here, its abnormal we get leveled down in ping so eastern players may play with the bigger player base, although the idea of cloud network is commendable...

What can this possibly achieve when the client has no authority over the game state? If your input is in any way conflicting with what the server allows or predicts then you just get yourself de- and then re-syncronised and that's it.

What am I missing here?

Something about tachyon emitters.

You are right if extra layers of protections are added server wise its futile. In reality very few server does that, you know cause the work involved doesnt warrant the benefit of doing it. In the ends its just a video game. I would be surprised the server actually record a series of frame and check if what is coming from its own client is secured, encryption of packets is the normal good to go basic protection against packet opening and peeping. Client side prediction is more popular on the other hand cause a client is not authoritative and will be overrided automaticaly by server packets.

Stop saying "lag switch" because a "lag switch" is already a thing and it's not this. At least not what intelligent people think is going on. Somebody come up with a new term because it's actually getting kind of annoying.




Ok, just so I'm clear about 'packets' and inferstructire jiggers and some of the other made up words you guys are throwing around:

Actually I don't understand any of it. I mean I understand what the words mean but I'm not seeing the big picture. So can anyone break it down for me? I've been in IT for years so go ahead and use big words but I still can't understand how exactly the cheater in one location is affecting what everyone else sees on their television or monitor without having access to either the server or the other players networks?

Because, correct me if I'm wrong here, isn't most of information for gameplay coming from the server? Such as when we used to get that desync where everyone else would keep moving in one direction but you were free to move around? If you shot your gun the animation would play but the ammo count would remain the same and you never had to reload. So it seems to me without input from the server you weren't actually shooting anything but the client was just going through the animation since that's stored locally and the actual shot in generated on the server.

So can please somebody tell just how in the hell they think this is all being accomplished?

Stop saying "lag switch" because a "lag switch" is already a thing and it's not this. At least not what intelligent people think is going on. Somebody come up with a new term because it's actually getting kind of annoying.



So can please somebody tell just how in the hell they think this is all being accomplished?