Project Reality Forums

Well first of all i want to thank the DEVs & others for their hard work, i really love this mod, and was so addicted i played 0.6 average 15 hours a day... but

I have a question, what have you done to the sniper rifles? When using the M40A3 i cannot hit a single target, even ones standing still... im using bullet drop also like i was in 0.6 for 300m+ targets.. im trying to hit still targets at 200-300m and it doesnt even show bullet holes or sometimes even any dust on ground hits if i shoot the ground...

sinse 0.7 i feel like a noob... cuz in 0.6 i used to be so knowledgable of everything... hmmmm

any help ?

Average 15 hours a day!? Please get some sunshine, sunshine!

Anyway, with a new version, you`re bound to have to break old habits.

Sniper Rifles are completely screwed

Indeed mate, i'm not proud of the time i spend on the computer, but oh boy... it keeps me happy

edit: Also, for "old habits" ... hmmm... tbh i actually thought 0.6 was perfect, other than some extra things what could be added, and slight accuracy changes on assault rifles... and of course deletion of qspotting entirely, but this qspotting still remains? I can still spot things ... it shouts "enemy sniper" if i qspot him on the hill, just doesn't show the red target - thus meaning, you can still qspot invisible people?

Also, i thought sniper rifles in 0.6 was balanced, especially hard to hit with the extra latency pingers (120+)... you had to add that extra bullet time aka latency lag... but now i don't even hit still targets at 200m when they stand

I'm not bitching, i'm just confused and concerned seeking good information/updates i checked the 0.7 on "what is updated" but i see nothing in there to do with this...

Note: unless of course wind movement was added (flags please)

I didnt kill anyone over 300m from me with M14, jus saw some dust flying 5m from target. And of course i saw some sky when someone instaproned and got me headshoted.

Here's the issue. The deviation settings on the M40A3 and the M14 are fubar for some reason. We apologize about this and will attend to it in the 0.7 patch.