• Home
  • Index
  • Search
  • Download
  • Server Rules
  • House Roleplay Laws
  • Player Utilities
  • Player Help
  • Forum Utilities
  • Returning Player?
  • Toggle Sidebar
Interactive Nav-Map
Tutorials
New Wiki
ID reference
Restart reference
Players Online
Player Activity
Faction Activity
Player Base Status
Discord Help Channel
DarkStat
Server public configs
POB Administration
Missing Powerplant
Stuck in Connecticut
Account Banned
Lost Ship/Account
POB Restoration
Disconnected
Member List
Forum Stats
Show Team
View New Posts
View Today's Posts
Calendar
Help
Archive Mode




Hi there Guest,  
Existing user?   Sign in    Create account
Login
Username:
Password: Lost Password?
 
  Discovery Gaming Community Discovery Development Discovery Mod General Discussion
« Previous 1 … 102 103 104 105 106 … 546 Next »
How come you can't see SNACs hit you client side?

Server Time (24h)

Players Online

Active Events - Scoreboard

Latest activity

Pages (2): « Previous 1 2
How come you can't see SNACs hit you client side?
Offline Haste
10-02-2014, 07:42 PM,
#11
Lead Developer
Posts: 3,546
Threads: 107
Joined: May 2012
Staff roles:
Balance Dev

Damage is clientside. As in, what the 'firer' sees happening on his screen is what ends up being reality. They miss on their screen, no damage is done. They hit on their screen, damage is done.

This is why you can die to a lagging capital ship that fires a massive burst of fire in a random direction away from you but, on their screen, they just spent five seconds filling a drifting snub with secondaries. This is why a mini razor can fly straight past but at the same time burn a hole in your hull. This is why a SNAC that flies three ship sizes past you can still make you explode.

Fortunately, if someone misses you, yet you see a hit on your screen, you don't take damage either.

As aerelm pointed out, the margins in the case of snubs are rather small, so the odds of a single shot being properly 'synced' between two clients aren't too great.

It's somewhat important to note aerelm didn't mention position interpolation, something clients obviously do. You don't see ships hop from place to place as you receive packets telling you where they're supposed to be. The client 'guesses' what the likely path between two positions was. In case of significant lag where the client doesn't receive a packet for a longer-than-usual time, the guess might be very wrong, leading to a ship visibly 'spiking' around. However, a 100% accurate guess is almost impossible, so there's always a slight difference between 'guessed position' and 'actual position', leading to this weapon desync, for one.

[Image: cdSeFev.png]
Reply  
Pages (2): « Previous 1 2


  • View a Printable Version
  • Subscribe to this thread


Users browsing this thread:
1 Guest(s)



Powered By MyBB, © 2002-2025 MyBB Group. Theme © 2014 iAndrew & DiscoveryGC
  • Contact Us
  •  Lite mode
Linear Mode
Threaded Mode