Main page

Ok..... Will you add in a option to disable the snap targeting. It is just awful. It will snap to what ever is closer to you. even if it is a friendly tank.. That causes a problem because you can have your cross hairs on a enemy tank and right as you pull the trigger a friendly passes under your gun not in the line of fire and your gun site snaps to him and bam team damage. Also it snaps to stupid stuff like houses and trees like i really want to shoot a house or tree. The aiming should be just that aiming you point at what you want to shoot at and the gun hairs go their also...it is so bad that I missed a tank point blank with arty because I could not site in at just over the top of a hill without my gun wanting to snap to the hill itself.
So please fix this and give us a option to disable it. I don't care if it is in patch 10.8 or 100.5 just fix it.

Thank you

In Sniper mode
Edited by shadowolfs, May 09 2012 - 15:23.

Uh... it's not snapping at all. It's showing where your shell will ACTUALLY hit.

If you hit a teammate because of that, he was in your real line of fire. Check with sniper mode if that happens.

And please, arty brutally sucks at hitting tanks that are on the opposite side of the hill, so it's not "OMG STUPID SNAP TARGETING", it's the arty gun mechanics.

Yeah, really not sure what you are referencing here.  There is no "snap targeting," just the computer adjusting for objects in your line of sight.

Snap targetting? Do you mean target lock (rmb)? If so it will only target enemy tanks and not buildings or friendlies. If you are locked on a target and there is a house or friendly between you and the target it may appear that you are targetting the and if you fire and hit a friendly then it is your fault.

You can remap it to an unused key or be more careful.

That's not snapping at all, it's targeting showing where you'll hit, with that angle and direction. Use "Shift" to check sniper mode, and u'll understand.

 Heh, on May 09 2012 - 15:06, said:

Not when they are coming over the hill 5 meters infront of you. and you just want to target just over the ledge so that when they crest the hill you can fire...and not in siper view.......

And this is in Sniper mode....sorry for not clarifing in org post.........
Edited by shadowolfs, May 09 2012 - 15:24.

 POKEDSMOT, on May 09 2012 - 15:15, said:

No not RMB...

 shadowolfs, on May 09 2012 - 15:20, said:

....some people will just never get it..

 ctlbulldg06, on May 09 2012 - 15:23, said:

Like you? So your saying that a arty cant target the crest of the hill just over the top? in standard view? I guess their gun is differnet than a tanks gun that doesnt allow them to do this? clear line of site stright line.

Occasionally the cross hairs snap around when moving the turret and gun such as when backin up over a crest of a hill or ledge and seems to throw the aim way off to where you have to move it back to where you were origionally aiming.

Is this what you mean by snap targeting ?

 Dinnger, on May 09 2012 - 20:29, said:

Kinda....it happens when sitting still also...the gun will snap to a tree for example when you site is close to it but above it. then you move it a touch more and it jumps to your site hair. so that leaves a gap between the trees edge and the point where it jumps off. normaly about 1/8 - 1/4 on my screen.21"...

I hope this helps the understanding...its something you might have to see to understand and hard to explain....

Agree with OP. It's annoying, whatever you call it. The gun jumps all over the place in arcade mode.

 JamDawg, on Sep 30 2012 - 19:45, said:

It just has to do with your POV... they fixed the main issue in 8.0, making it so you can't aim at the underside of bridges etc.

It's a three-dimensional marker. If the ray ends at an obstacle, the marker will end at that position, drawing the accuracy circle around that vectorial point. It's actually good that way because it lets you see that the shot won't go where you think it should. On narrow passages, use sniper mode.

Also, it is natively rendered with 3D coordinates (because nVidia does not have to correct it when 3D Vision is enabled).
Edited by Ettanin, Oct 01 2012 - 12:25.