• Please make sure you are familiar with the forum rules. You can find them here: https://forums.tripwireinteractive.com/index.php?threads/forum-rules.2334636/
  • Weve updated the Tripwire Privacy Notice under our Policies to be clearer about our use of customer information to come in line with the EU General Data Protection Regulation (GDPR) rules that come into force today (25th May 2018). The following are highlights of our changes:


    We've incorporated the relevant concepts from the GDPR including joining the EU and Swiss Privacy Shield framework. We've added explanations for why and how Tripwire processes customer data and the types of data that we process, as well as information about your data protection rights.



    For more information about our privacy practices, please review the new Privacy Policy found here: https://tripwireinteractive.com/#/privacy-notice

Bring in lag compensation!

MrHello

FNG / Fresh Meat
Sep 2, 2011
537
122
0
I've seen many people talk about how it's neccessary to compensate for ping to the server.

This is disgusting, and entirely voids any realism the game has in bullet mechanics :\.

Can we band together and try to convince tripwire to include client hit detection!?

I'd prefer being able to hit off shots as they should be and have to deal with getting hit even when i'm behind cover after not being 1 second before, this is fine, as the other player still deserved that kill.

Why not even have a mixture, where on the client that has been hit, before it accepts that the shot is a hit, the server calculates if the hit player is still in a direct line to the original point of the shot. This would be an excellent mixture of both sides of hit detection.

Argh, please move this post to general discussion -_-
 

Mangley

FNG / Fresh Meat
Aug 7, 2011
244
105
0
Nah.avi

The netcode is fine, I can't believe out of all the problems and bugs and performance issues you want to change one thing that is absolutely fine and works precisely as intended.
 

WiFiDi

FNG / Fresh Meat
Oct 12, 2010
642
168
0
nope.avi :p

seriously it will just bring in more complaints because it will cause everyone to lag. :( and that it doesn't always work that well. :cool:
 

rta

FNG / Fresh Meat
Mar 16, 2006
98
16
0
earth
www.nodozetactical.com
lag compensation introduces an entire other set of problems. you'll have blood spatters everywhere with nobody actually being hit and people being pissed because of that as well.

Plus, i absolutely HATE being shot when i am clearly around a corner, out of sight because of where I was at the time of the shot.

there is a thread somewhere describing why TWI chose to do it this way and it makes sense. not sure where it is though sorry :eek:
 

Nenjin

Grizzled Veteran
Apr 30, 2009
3,879
480
83
Sub-Level 12
Negatory. Client-side lag compensation just benefits the person shooting. It makes the victim experience death when, to them, there should be no reason for it.

It's a lot fairer for everyone to miss because of the lag than for some to hit because of it.
 

cato12

FNG / Fresh Meat
Sep 16, 2011
29
0
0
lag compensation introduces an entire other set of problems. you'll have blood spatters everywhere with nobody actually being hit and people being pissed because of that as well.

Plus, i absolutely HATE being shot when i am clearly around a corner, out of sight because of where I was at the time of the shot.

there is a thread somewhere describing why TWI chose to do it this way and it makes sense. not sure where it is though sorry :eek:
ive read that thread as well and the dev make a great case for the way its set up in RO2.
 

Justd1e

FNG / Fresh Meat
Jan 23, 2011
55
81
0
Nah.avi

The netcode is fine, I can't believe out of all the problems and bugs and performance issues you want to change one thing that is absolutely fine and works precisely as intended.

HAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA
HAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA
HAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA
no.

slapping all of us an extra 100 ms for no reason is fine? are you drunk? That is EXACTLY the reson why I cant play.
 

panalfik

FNG / Fresh Meat
Sep 21, 2011
9
1
0
I totally agree with you OP. Lack of lag compensation is the biggest gameplay killer in the game right now.

I can deal with bugs, as I can deal with occasional crashes and fps drops.

But THIS is what makes me rage so much, because for some reason I almost never have pings below 100, even on servers in my country (while i have 30-40 in other games). The game is based on bolt rifle fights, where you mostly have the time to fire only one shot. With latencies like this it's almost impossible to hit a running target.

This kills firefights and all the realism TWI tried to bring in, because the lead you need to take varies from server to server. There's no way there will be any competitive gameplay unless lag compensation is brought in.

Just limit it to 150ms and maybe think about OP's idea, everything will be fine.
 
Last edited:

PsYcH0_Ch!cKeN

Grizzled Veteran
Nov 27, 2005
1,677
200
63
37
Brisbane, Australia
www.ragequit.com
slapping all of us an extra 100 ms for no reason is fine? are you drunk? That is EXACTLY the reson why I cant play.
Two things. Firstly, 100ms is not an unbearable ping, if you think it is then you've been very fortunate, perhaps even spoiled, in your gaming history. Some of us used to play RO as a mod on 230ms+ ping just fine. If you want to talk about games that slap 100ms onto your ping for no reason, perhaps you should be discussing the Battlefield series, which deliberately buffer every player's action for 100ms (and will almost certainly continue to do so in BF3).

Second, the increased pings are not the result of poor netcode or even of netcode at all. They're directly caused by server CPU load, itself caused by a problem in the game. It has nothing whatsoever to do with the netcode.

At the OP: Along with the other posters in this thread, I don't want to see lag compensation anywhere near this game. I loathe it wherever it's implemented and can't think of anything worse for RO2. Not to mention that it wouldn't actually help with the current server problems, it would actually make things worse.
 

jergul

FNG / Fresh Meat
Sep 19, 2009
522
10
0
I think all servers would do well dumping 8 players from their limit.

The community needs more dedicated servers with decent Mhz cpus (I understood that on the server side its best to lock down on a single core for now).
 

Xendance

FNG / Fresh Meat
Nov 21, 2005
4,484
572
0
31
Elitist Prick Club RS Branch
You people need to realize that some kind of lag compensation isn't a silver bullet to high latency in RO:HoS. More likely the extra calculations done in the prediction would just cause more lag and/or people warping everywhere since the client thinks "stuff A" and server tells "No, stuff B".
 

Justd1e

FNG / Fresh Meat
Jan 23, 2011
55
81
0
Two things. Firstly, 100ms is not an unbearable ping, if you think it is then you've been very fortunate, perhaps even spoiled, in your gaming history. Some of us used to play RO as a mod on 230ms+ ping just fine. If you want to talk about games that slap 100ms onto your ping for no reason, perhaps you should be discussing the Battlefield series, which deliberately buffer every player's action for 100ms (and will almost certainly continue to do so in BF3).

Second, the increased pings are not the result of poor netcode or even of netcode at all. They're directly caused by server CPU load, itself caused by a problem in the game. It has nothing whatsoever to do with the netcode.

At the OP: Along with the other posters in this thread, I don't want to see lag compensation anywhere near this game. I loathe it wherever it's implemented and can't think of anything worse for RO2. Not to mention that it wouldn't actually help with the current server problems, it would actually make things worse.


I wish it was 100..I wish...
100 is THE EXTRA that this game slaps over my usual 90 latency to the nearest servers, sometimes its even 120 more. And no, its not playable like that unless you mkb.
 

palco

FNG / Fresh Meat
Sep 17, 2011
123
72
0
Looks like all the games with unreal 3 engine seems to have this exceptional latency issue.
(I mean relatively slower bullet speed in +200ms ping, UE3 seems to have poor default ini setting causing this relatively severe lag, while some of EA's fpss had good ping optimization)

Unreal tournament 3 has relatively slow bullet speed in +200ms servers, america's army 3 also has this (though AA3 has poor graphic quality, source of this issue seems to be bad default setting of UE3./ It seems to take more resources than it looks= mostly with unnecessary amount of shadows or special effects )

For faster, more playable bullet speed with +200ms pinged servers, optimizing the game heavily really helped in my case.

I didn't completely disable the shadow or things like that but tweaked after 1,2.

1.
http://forums.tripwireinteractive.com/showthread.php?t=65000
2.
http://forums.steampowered.com/forums/showthread.php?t=2094647

3.
try to decrease texture MaxLOD size from 4096 to lesser values as 2048, 1024, 512, 256.

After tweaking with 1,2,3, I now can play in 250ms servers much easiler without severe bullet speed issues.
Hope you can have some luck.
 
Last edited:

FBX

FNG / Fresh Meat
Aug 17, 2006
238
42
0
err, lag compensation, when implemented correctly, has virtually no downside. I get killed in cover in this game because there is still lag from the server telling me I got shot to where I think I am now. Its very juvenile to think that because YOU think you're in cover, you should instantly be in a safe zone immune to what has already happened. If you die after entering cover it is because someone shot you when you were exposed, not because they are some how magically bending physics and somehow seeing you where you aren't and shooting at you where you aren't.

The reason there isn't any lag compensation is likely because the developers simply don't know how to implement it. They seem to be using actual projectiles with gravity which is a bit trickier to unlag than simple "straight bullet" physics. From what I can tell, they're trying to justify not having it because of X or Y but really any side-effect of lag compensation is because it just wasn't implemented right.

Personally, this game could stand to have some interpolation to it's movement. 3rd person locked / 1st person is nauseating because there isn't any smoothing that you would get with interpolation. Maybe if the game engine supports it, people who are spectating could get some interpolation.

Also, I know in the first RO, things like sway were server-side. So if you had a high ping, your sway would take longer to kick in. It is likely that trying to get the user experience to line up with the server without introducing client-side exploits would be difficult to do.
 
Last edited:
  • Like
Reactions: Mekhazzio and Reise

MrHello

FNG / Fresh Meat
Sep 2, 2011
537
122
0
For everyone saying they'd hate to be shot while just getting into cover, please check the idea I posted in my original post.


I still stand by lag compensation, and have implemented it in a top down shooter before, and it works VERY well.
 

Nenjin

Grizzled Veteran
Apr 30, 2009
3,879
480
83
Sub-Level 12
For everyone saying they'd hate to be shot while just getting into cover, please check the idea I posted in my original post.


I still stand by lag compensation, and have implemented it in a top down shooter before, and it works VERY well.
I think comparing hit detection and lag compensation in a 2d shooter is barely even in the same ballpark.