Rifleman Archive

Okay... Could this be relate to Master scout and/or some ranger?
Is anybody seeing this that is NOT Master Scout orNOT Ranger?

Iam master marksman and very near master rifleman andI do NOT warp, andI have never been ranger nor master scout. Hasanyone else with rifleman/marksman but not master scout nor ranger warped?

Just thought I'd follow up.

I dropped Master Ranger down through Novice Scout last week. I haven't warped from going prone since then.

That makes me think it has something to do with terrain negotiation.

My current tree:

CH - 4/4/3/4

Rifleman - 2/0/0/2

Master Medic

Scout 4/0/4/0

Marksman - 4/0/0/0

Doc - 0/0/0/4

Just want to say don't confuse you warping with creature warping two different things.

Here's my theory on the warping problem. I'm fully convinced this is tied to the same sit and slide problem that I've seen since day 1. I think it just got amplified in recent patches.

Here's how I can warp just about every time.

1) Run up to spot. Stop for 10 seconds.

2) Run 40m in any direction, instantly sit/kneel/go prone.

3) within 1-30 seconds, you will warp back to where you were standing before.

Now if you do this again, but change 2 to read "Run 40m in any direction, stand for 5 seconds, then go prone/kneel/sit" you more then likely will not warp.

It seems that the server won't update you after you run and change position right away. Working as a medic/doc this happened all the time in the med center. Run to new patient and warp back to where you were sitting before. It's like the server goes.. Oh you didn't move let's up date the client.

I am Master Scout with Ranger 1 0 3 0 in addition to Rifleman 2 3 2 2. I do not recall when it started happening, but I suspect it was after getting Novice Ranger. So the Rifleman/Ranger connection is likely.

However, try this experiment if you are subject to this problem.

Find two things, a landmark such as a tree or rock and MOB or NPC you can target. Note: The landmark is only important to mark your starting point each time, and you do not need to attack the target; it is just there as an object you can target. The target and landmark should be a reasonable distance apart, 70 - 80m would be good.

First, move next to the landmark. Do not acquire a target lock on the NPC/Creature, but run towards it. At whatever distance you choose, stop and immediately go prone. I think that you will find that you will not warp.

Next, get up and go back to the sameLandmark.This time, acquire the target. Run to the same spot as before or to some other location in any direction. Immediately, go prone. If you warp, I can almost guarantee that you will be back next to that landmark where you acquired the target.

Finally, get up, again being sure you are near the landmark, break the target lock and reacquire a target (same or different one, it does not matter). Run to another spot. But this time, before going prone, break the target lock (just click on an empty area of the screen), then go prone. Once prone, you can reacquire your target. I can almost guarantee that you will not warp.

The direction you move does not matter. If you acquire the target then move away from the target and go prone, you will find yourself warped forward towards the target, again apparently back to or very nearthe point you acquired the target. I find this to be very consistent. If I do not have a target acquired when I go prone, I will not warp. If I have a target acquired and go prone, I will warp back to or very near where I acquired the target.

Thus, I agree it probably has something to do with the Rifleman/Ranger combination. It may alsohave to do with terrain negotiation as suggested. It is also likely related, as someone suggested elsewhere, to the bug where you can be standing perfectly still, but it tells you "You cannot do [whatever action] while running."That would make sense withtheobservation earlierthat you can wait 4 seconds or so before going prone to keep it from happening. The system probably has you in a running state for a few seconds after you stop running. By going prone in a running state, the system likely gets confused and thinks it needs to reposition you. However, I am also convinced, at least in my case, that it is intimately connected to having a target acquired. The only time I warp now is if I foget to drop the target lock before going prone, and when I warp it always seems to be at or near the point I acquired the target.

---

WayneInAustin wrote:
For those of you who it is happening to, Maybe we can find some common values:

---

I never, ever had a problem with warping while prone...

...until I went from a 2/1/2/1 Rifleman to a 2/2/2/2 Rifleman. I trained Rifle Special Abilities first, and trained Concealment shortly thereafter, so I'm not sure which of the two would have caused it. I think I was having the problem at 2/1/2/2, but I could be misremembering.

In any case, I am now warping while prone all the freakin' time.

Whoa. Should read the entire thread before responding.

I was a 4/0/4/0 scout for a very long time, and the warping while prone bug never happened happened.

But guess what skills I recently picked up, around the same time that I went from 2/1/2/1 Rifleman to 2/2/2/2 Rifleman?

(If you guessed "Master Scout" and "Novice Ranger," score yourself five bonus points.)

I have no Ranger skills and I'm not a Master Scout, so it's not tied solely to them. And I'm fully convinced that sit/slide bug is the same problem as the prone/warp bug.

Targeting is an interesting theory, I'll have to check it out, but running then immidiate prone/kneel/sit has almost always done it for me. I'll have to see if this is related to targeting too that would be good to find that out and could make some sense. The server starts targeting calculations and ignores your movment, then goes, wait you're supposed to be here, and moves you.. Kinda makes sense..

Have they fixed this?

I noticed I didn't warp once last night when i went prone.

Prone warping still occurs just like itdidin Beta. Keep in mind it doesn't seem to happen to everyone, so if you haven't seen this then don't think we're all retarded and don't know what we're talking about. It's a known and well-documented bug =)

"First, move next to the landmark. Do not acquire a target lock on the NPC/Creature, but run towards it. At whatever distance you choose, stop and immediately go prone. I think that you will find that you will not warp."

I did all kinds of testing a month or two ago on this. Yes, without a target you still warp. Notnecessarily always, but the vast majority of the time.

"Next, get up and go back to the sameLandmark.This time, acquire the target. Run to the same spot as before or to some other location in any direction. Immediately, go prone. If you warp, I can almost guarantee that you will be back next to that landmark where you acquired the target."

Interesting theory,and I think I see what you're getting at, but you also sometimes warp to somewhere halfway in between or maybe just a couple steps from where you started.

"Finally, get up, again being sure you are near the landmark, break the target lock and reacquire a target (same or different one, it does not matter). Run to another spot. But this time, before going prone, break the target lock (just click on an empty area of the screen), then go prone. Once prone, you can reacquire your target. I can almost guarantee that you will not warp."

UnlessI take a long time to do all that target switching,I still warp. In generalI needed to give myself 10 or 15 seconds before going prone to prevent warping regardless of targets.

I've never been a Novice Rifleman. When this first started happening to me I was at least at Exploration 4 (not sure if I was a Master Scout or Novice Ranger yet), andNovice Pistoleer.

My third holocron told me Rifleman, so I've been dealing with this issue lately.

I don't see why this has been a rifleman issue for so long.

I simply never warped when I was using my carbine or LLC and went prone as a Bounty Hunter.

This seems to be entirely a rifle issue.

yeap - it's a new bug. it started happening a few weeks ago (afterthe big patch? or some patch related to NPC stupidity, er AI pathfinding.) /bug seems to be broken as it doesn't do anything about these problems.

I've found :

1. moving into position and waiting like 15 seconds, then going prone. Don't always warp.

2. moving into position and kneeling and waiting 15 seconds, then going prone. Haven't warped yet.

3. moving into position, fire, go prone. Warp 100%. Problem is - often the smart NPC finds a path using non euclidean geometry and gets behind me at about 1m.

4. This isn't a bug - it is a feature for BH's... /attack;/prone;/stand;/eyeshot

Doremar,

Your tests would seem to indicate that it is not necessarily realted to targeting. In my experience, it is very consistent. If I target elsewhere and go prone, I warp. If go prone without a target, I do not warp. So if I have a target, and break the lock before going prone, go prone, and reacquire it, I almost never warp. The times it has happened in that scenario have been, from what I can tell, if I break the lock, go prone, andimmediately reacquire the target (in other words, do it such that there is virtually no time elapsed between the breaking of the target lock and the reacquiring of it).

I would be curious as to what kind of connection you are using. You mention a 10 to 15 second wait seems to keep it from happening. Others mentioning a time delay preventing itonly speak ofa 4 or 5 second wait being necessary. In the case of the targeting break, the time required to break the lock, go prone, and reacquire it may end up pushing that 4 second time frame; although, I usually do this very quickly. Although, I can guarantee that it does not take me 4 seconds to lose the target lock and go prone every time, but it could be that the total time to do that then reacquire the target could approach or exceed, in some cases, the 4 second time frame.

The reason I ask about the connection is that, whatever the cause, it is bound to be related to a client/server synchronization issue. If you have a slower connection than others, it would take longer for the client and server to synchronize and, therefore, it would make a resonable explanation as to why you have to wait longer than others. Although, I would find it hard to believe it would take three times as long (that is, thatthis exlpanation would fit, not that your observations are off).

If the targeting is not a factor as your observations would seem to indicate and the time issue is the key factor, I think that the observation someone else made that it may have to do with the fact that the system thinks you are still running, often, when you are standing still. The system may be having problems because it thinks you are still running, but it finds you are now prone according to the client, so it attempts to put you back at a location where it was sure you were at one point. This may be why the targeting seems to be related, because you stopped at that point or took an action other than running.

I am going to try an experiment tonight and do everything the same, except that just before going prone, I am going to hit the shift key and walk a few steps before going prone and see if this changes the behavior.

teh dsl

The original post has most of what I know about this issue.

I think we can safely say this isn't getting fixed though, regardless of the cause. Not this year anyway.

The fun part is that no matter what else I did, if I set up a /kneel /stand macro, wait for myself to show the graphic fully standing (no more than 5 seconds) THEN /prone, I never warped.