I know exactly what hitscan is.

With hitscan weapons, when 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

ie: you cross the path of the weapon, you get hit. My observation is that this is not how weapons in dust work, except of course the laser rifle.

OP dosent know what he's talking about

Then try to prove me wrong instead of just being a troll.

Laughing.

Link?

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 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.

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"

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?

Just so you know, we've already found the source of the problem, which was OP's misunderstanding of the term "hitscan", and he's not only admitted his mistake, but edited the OP and thread title to reflect his recognition of the mistake.

You're late.

Really now?

Do you have any evidence to support this?

I surely offered plenty evidence to support that they do. Even others who have posted in this thread seem to agree that they do. If you can support your statement, I would be more than happy to consider the evidence.

Actually, I am basing this off of how I receive damage from long range shots, not the animations.