Sorry I wasn't there I would have been but my graphics card is dead. I will attend future events once I am able.
FragBU test. Friday, June 4th, 2010
- Thread starter JohnDoe641
- Start date
-
Two Factor Authentication is now available on BeyondUnreal Forums. To configure it, visit your Profile and look for the "Two Step Verification" option on the left side. We can send codes via email (may be slower) or you can set up any TOTP Authenticator app on your phone (Authy, Google Authenticator, etc) to deliver codes. It is highly recommended that you configure this to keep your account safe.
me too
but i dont care if its off i can play with a 124 ping too
can some 1 tell me what is wrong with ping compensation
but i dont care if its off i can play with a 124 ping too
can some 1 tell me what is wrong with ping compensation
When games have lag, you're going to get inaccuracies between what individual players can see, because they cannot be kept in synch with the split-second differences between what they all can see and are doing.
There are two ways of addressing this problem:
1) To keep the game fair, you can assume that the server is always correct. When you take a shot, it is sent to the server, and it works out if you hit the target or not. If the server has the target in a different position to you - then even if you 'hit' the enemy on your screen, it is still registered as a miss - UT3 does this. You can also get noticable delay when shooting in UT3, as it doesn't fire the trace until you get the feedback, which makes it even more unresponsive.
2) To keep the game fair, you could alternatively assume that what the player sees is correct. In this case the trace is calculated on that player's machine and the server is told if a target is hit or not. The problem with this is, that if another player sees themselves in a different position (such as behind cover or around a corner), then they can still be hit due to the original player's machine saying that they have been. This is what ping compensation does.
There are two ways of addressing this problem:
1) To keep the game fair, you can assume that the server is always correct. When you take a shot, it is sent to the server, and it works out if you hit the target or not. If the server has the target in a different position to you - then even if you 'hit' the enemy on your screen, it is still registered as a miss - UT3 does this. You can also get noticable delay when shooting in UT3, as it doesn't fire the trace until you get the feedback, which makes it even more unresponsive.
2) To keep the game fair, you could alternatively assume that what the player sees is correct. In this case the trace is calculated on that player's machine and the server is told if a target is hit or not. The problem with this is, that if another player sees themselves in a different position (such as behind cover or around a corner), then they can still be hit due to the original player's machine saying that they have been. This is what ping compensation does.
It should be noted that the compensation in UTComp and some other modern games uses a combination of those two systems to try to even out what players see with what the server is seeing under lag conditions. The problem is that reconciling these two systems requires making some assumptions that are kind of annoying to witness in UT3, but to be fair I have not tries UTComp for UT3 extensively. This is just how it worked in UT2004.
What if you don't have bloom or any of that other new stuff activated? Will running the Blossom mutator mess with the INI files?
Exactly, if you have it off, you have it off entirely. And if you have it on, you get all the postprocessing and slight bloom where it's needed.