There's a certain configuration for the projectile detection, something in the ini files called "NavMeshDetection" or something one another. Basically, the number is so low that your magic spells or arrows that are shot eventually don't detect or hit anything (becoming collision-free) after a certain distance. That distance is quite low and makes sniping absolutely worthless. So, newer hardware. IS THIS FIXED?! If not, will the CREATION KIT be able to fix this for consoles?! Why is this overlooked.... it's the "next gen" version for Talos' sake. This makes or breaks the purchase for Battlefield 1 instead, in advance.

Hello?

CK can fix the gravity for arrows and bolt so that they can travel straight without dropping down on floor 2 metres ahead but i doubt ini files can be changed on consoles to make them travel further.

Edit : i think those ini tweaks are for better accuracy so gravity affects distance they travel.

Edit 2 : I messed up things i guess

[Actor]
fVisibleNavmeshMoveDist=12288.0000 This Tweak is responsible for distance

[Combat]
fMagnetismStrafeHeadingMult=0.0 These are for accuracy
fMagnetismLookingMult=0.0
f1PArrowTiltUpAngle=0.7
f3PArrowTiltUpAngle=0.7

The NavMeshMoveDist is what extends the range, the TiltUpAngle (for both arrows and bolts) is for aiming. By default the arrows are fired higher than the crosshair, so that after a certain distance they hit what the cross hair is pointing at. Those change it so that the arrow are fired at the crosshair always, like in Oblivion.
And i'd bet that neither will be changed from the original.

*Take notes for making an archer class in Skyrim SE, conclusion to avoid disappointment: shoot bows at shotgun range, best option.*

Battlefront 1 show a lot of bugs on the beta when it comes to hit detection, so don't think your changing to a more "refine experience". When a bow in Skyrim fail you, just don′t look cool. But in Battlefront 1 when a gun fail you, you will die.

I always do that is why I love Xbows in Dawnguard

Problem from ancient times, fixed in ancient times. PC and xbox are good, ps4, unfortunately, can't have it fixed as it's an ini fix rather than CK one.

BETHESDA BETTER START EXPLAINING THEMSELVES ABOUT THIS ONE THING I THINK IS IMPORTANT OR I'LL...I'LL....

uhh....

I don't know, what will I do?

You can fix it by tinkering the ini but even if you do, the AI pathfidning won't be able to reach your sniping position. In the end the fix is something like exploiting the engine weakness to give you an advantage.

Strange.

All of my characters used bows, and I sniped from rather long distances. I had to aim a few feet over the head of the target, and usually ended up hitting center of mass, like the chest. Still killed them, so I don't know about useless or worthless.

It usually only applies to extremely long range shots. I've tested it on a bear before.


But I wouldn't worry, OP. The unofficial patch fixes it, and I'm sure that will be coming to SE eventually. It was one of the first important mods I noticed when FO4's mods came out on Xbox.

I guess that's why I didn't notice. Let's just say I was far beyond any distance a real shot could have been taken, but still managed to kill the target. It was completely not noticeable for me.

I usually turn the crosshairs off so I've never been bothered by this issue. Archery is so much more fun without a crosshair anyway. I also play with mods that change the arrows gravity stats so they are more realistic and can't fly forever.

Alright, I see a few people not understanding, that's okay.

And yes, this is the exact tweak.

Actor]
fVisibleNavmeshMoveDist=12288.0000

I changed mine to the proper multiple, somewhere in the 16,000. Seemed to work a lot better. This stuff is important, otherwise everything is unrealistic with arrows practically giving up no matter how far you shoot them.

Wait, the unofficial patch made it to consoles? And as for the fix for Skyrim, what specifically is the tweak? Does it change that particular ini file? If I can get the fix for consoles, I'd be happy.

{edit} and I've tested this a thousand times on Vanilla. I've seen my arrows hit the enemies without doing anything, and I'm not as far away as I could be as well. I've toggled the console and went exactly where my arrows are, hitting enemies but not making detecting anything. Collision = off.

AI don't snipe anyways :b besides, it's not so much an exploit as it is fixing the game.

Again, if you shoot your target, let's say a giant, from farther away than what it was indented, he won't be able to reach YOUR sniping position and engage you in combat. He will stop searching almost immediately or he will stand there without able to understand from what place you are shooting him. This isn't because the giant is a little light on his head but because the path finding can't generate a clear path after a certain distance.

This.

Not that at all. The target is not that far away. I can't clarify it more than that. It wasn't there in Oblivion. The distance needs to be a little more than what it is naturally. Even the unofficial patch fixes this. So it should be standard in the remaster.

I can't say I've had this happen to me? How far out are you shooting from? Cause I've made some pretty long range kills that have me grinning like a fool.

I find the default range fine

What are you trying to do....shoot things from miles away?

In real life arrows have a limited range and lose killing momentum way before they hit the ground

If you want the equivalent of a sniper rifle in Skyrim best to stick with Battlefield

And yet the arrows still come in contact with something. You must be playing with a patch that fixes this issue already.

Camelworks just confirmed that the limit for projectiles is completely removed. GODS BE PRAISED.

Just saw this today, confirmed here: https://youtu.be/GXOjkr4ewcA?t=11m38s

Your question has been answered op, may your spirit finally rest

Thank you for your words

I was quite surprised and pleased about this

Looks like you got your wish