I've spoken to Wolfman before about this or similar issue and he did confirm what everyone else has said. But it's quite good when you can't tell easily, eh?! Mission accomplished.

I didn't simply restate my opinion as you say. I offered evidence refuting other people's opinions.

Go ahead and laugh too, i don't really care.

Until a DEV actually says that it is indeed hitscan, I'm of the opinion it is not. I have stated my reasoning for this opinion.

Everyone on here ridiculing me for my opinion, which I have offered strong evidence to support, has shown absolutely no evidence whatsoever that it is hitscan. You are simply assuming that it is because other games (not all games) use hitscan.

So yea, go ahead and laugh it up.

I've seen a long-range Scrambler Rifle projectile heading towards me and dodged to the side, watching the projectile.

It disappeared when it reached the point my head HAD been when it was fired, with the same graphical effect as you get when a Scrambler shot hits.

I lost more than half my Scout suit's shields.

Pretty sure it's hitscan. Will laugh if a dev posts here, because they WILL confirm the weapons are hitscan. I'm pretty sure the AR being hitscan was mentioned in an early devblog, but it's been a LOOONG time since I looked at anything that far back.

several people have givin you evidence PROVING its an animation.

people have posted countless links and tryed to reason with you.

you havnt actually refuted any arguments...

your just saying NUH-UNH but with more words.

Visually representing the firing effect of a hitscan weapon can be difficult - since the weapon hits its target instantaneously, any bullet or projectile that comes from the weapon is merely a 'ghost', and where it lands may not necessarily represent its actual hit. In particular, a projectile bullet effect will always lag behind the effect of its hit, a problem which can be compounded by internet latency in online multiplayer gaming.

The hitscan method also precludes ballistics, as it cannot simulate any kind of movement other than a straight line, such as a parabolic arc or atmospheric resistance (including wind direction).

With advances in processing and internet bandwidth, it has become more practical to simulate the ballistic nature of real-world firearms in real-time games by using a more realistic "projectile" model, spawning bullets as actual game objects with mass and velocity and continuously simulating them until they reach their target.

What evidence? Show me the evidence that it is simply animation.

If you are referring to the wikipedia, this came from the same page:


People have stated their opinion that it is animation.

I stated my opinion that it is more than animation, and offered evidence to support my claim.

You're just saying NUH-UNH but with less words.

Link?

IRC and I haven't kept logs, you'd have to ask Nova Knife or Heinz D. to dig up logs.

Another thing about the Laser, it fires in pulses. I used it for many months so got got intimate (:P) with it. If you swiped a person fast enough you could avoid damaging them as one of the pulses wasn't aimed at them even if they crossed the beam.

What evidence? Show me the evidence that it is simply animation.

If you are referring to the wikipedia, this came from the same page:


People have stated their opinion that it is animation.

I stated my opinion that it is more than animation, and offered evidence to support my claim.

You're just saying NUH-UNH but with less words.

So then, it isn't hitscan?

Because, if it was hitscan, as soon as you held the trigger, if someone was in your sights, you would deal damage, right?

Just like if the AR was hitscan, no matter how fast you swipe your reticule over your target, you would do damage, right?

Correct me if I'm wrong, but this doesn't happen in DUST, does it?
.

So then, it isn't hitscan?

Because, if it was hitscan, as soon as you held the trigger, if someone was in your sights, you would deal damage, right?

Just like if the AR was hitscan, no matter how fast you swipe your reticule over your target, you would do damage, right?

Correct me if I'm wrong, but this doesn't happen in DUST, does it?

So then, our guns actually fire projectiles, right? These projectiles have actual travel time. That is very apparent if you are shot from an AR, for example, outside of its effective range.

Granted, these weapons don't have complete ballistic model, as pointed out by the gentleman above, but they also aren't hitscan weapons.

yoru not taking into account rate of fire.

for what your thinking to be true weapons would all have to have a damage over time damage profile.

instead it just has a timer built into the hitscan to keep track of the rate of fire for the weapon and apply damage at the apropriate invervals

That is not hitscan. As I stated before, when you get shot from Long Range with an AR, you can feel each bullet hitting and dropping your HP as individual bullets, not a stead stream of damage.

Hitscan = steady consistent non intermittent HP drain.

This is not how DUST works.

As for your previous post, just because all bullets do not have an animation, does not make it Hitscan.

All of my steps do not make a sound, does that mean I'm not taking those steps?

The ScR does not do damage before it's beam reaches you. If that is what you see, you are delusional.

In DUST, sniper rifle's bullet travel time is a factor.


It seams that DUST uses a partial ballistics model.

Hitscan = steady consistent non intermittent HP drain.

So you don't know what hitscan means.

Glad you finally confirmed it. I was a little confused about how exactly you were defining the term until you posted this.

You're incorrectly applying a specific possible damage model as a requirement for hitscan, rather than actually understanding what a hit detection model entails.

Whether hitscan is being used to trace a single line in a single instant and mark a target for a binary "yes/no" damage application, or used for a constant stream of damage, the method of determining the "hit" condition that mkes it hitscan.

If there's a slow-moving stream of energy that creates an arc when you turn, and anything within the energy stream takes constant damage, that's NOT hitscan.

If the game simulates bullets by tracing straight lines out from the weapon and applying damage any time one of those lines intersects with an enemy hitbox (or a friendly one if FF is on), that's hitscan. It doesn't trace a line and keep that line in place, or shake it around a bit and apply a tiny amount of damage every time. It traces a line that doesn't stay in place, then traces another line for the next bullet, and each time one of those lines touches a valid hitbox, it applies damage to the target.

well said.

i think this clears up some of the confusion as to what hitscan is and why were looking atyou a little funny.

were simply using different definitions for hitscan, ours being backed by actual referances.

Everything I have stated, was backed either by my own experiences or by references.

If you cannot think of any other way to discuss this other than the condescending tone you have taken, then leave my thread. As much as you would love to think otherwise you don't know everything. Most of what you have said is completely baseless, unless you want to count other people's posts as your "references"

doesn't trace a line and keep that line in place, or shake it around a bit and apply a tiny amount of damage every time. It traces a line that doesn't stay in place, then traces another line for the next bullet, and each time one of those lines touches a valid hitbox, it applies damage to the target.

This is a bit more in depth definition of hitscan than any I have been able to find.

Basically what you are saying here, is that when you fire your weapon, multiple hitscan lines are produced. (one for each "bullet"?) Does each one of these hitscan lines have a beginning and end? How long are the hitscan lines?

Why is it that, when I get shot by an AR at range, the damage does not occure immediately? From everything I have read about hitscan, that is how it works. The damage is simultaneous with the pull of the trigger.

Do you see the questions this raises?

EZMode reference courtesy of Wikipedia:

http://en.wikipedia.org/wiki/Hitscan

It was posted earlier in the thread, but you should probably go back and actually read it.

The page also cites a variety of examples that are described by actual game developers as hitscan.

Care to provide a reference that contradicts that (correct) definition?

if an object is detected in the path of the projectile, a hit is registered. Since the effect is immediate, the projectiles effectively travel at infinite speed and have a linear or otherwise simple trajectory GÇö a practical approximation of a bullet's speed and accuracy over short distances

What are you trying to tell me? That I can dodge bullets?

This is a bit more in depth definition of hitscan than any I have been able to find.

Basically what you are saying here, is that when you fire your weapon, multiple hitscan lines are produced. (one for each "bullet"?) Does each one of these hitscan lines have a beginning and end? How long are the hitscan lines?

Why is it that, when I get shot by an AR at range, the damage does not occure immediately? From everything I have read about hitscan, that is how it works. The damage is simultaneous with the pull of the trigger.

Do you see the questions this raises?

its one hitscan line that wobbles. thats what hes saying

and its a single line that exsists for as long as you hold the trigger.

each "bullet" you fire just changes teh state of the line from no damage, to damage

think of it like a flashlight, for as long as you press the ON button it shines a blue light, and at a rate of 1000RPM it changes its color from blue to red.

as long as two conditions are met damage is done

theres a target in the beam, and the beam is in its red state.


as for what your experiancing with the "no damage immediatly thing" its probable that the condition "target in beam" is not being met :P

aka hes shooting but hasnt trained on you yet.

What are you trying to tell me? That I can dodge bullets?

Basically what you are saying here, is that when you fire your weapon, multiple hitscan lines are produced. (one for each "bullet"?)

Does each one of these hitscan lines have a beginning and end? How long are the hitscan lines?

Why is it that, when I get shot by an AR at range, the damage does not occure immediately? From everything I have read about hitscan, that is how it works. The damage is simultaneous with the pull of the trigger.

(emphasis added)

From the Wikipedia page, which I did actually read. So this is saying that hitscan is pretty much simultaneous with trigger pull. Well, damage output in DUST is not simultaneous with trigger pull.

(emphasis added)

From the Wikipedia page, which I did actually read. So this is saying that hitscan is pretty much simultaneous with trigger pull. Well, damage output in DUST is not simultaneous with trigger pull.