3 minutes ago, IMIachine said:

Is there any conclusive ADS Modifier that is most accurately mated to hip fire sens? I've heard that 0.9 is supposed to be. I don't know enough of how this stuff works to tell. But is ADS modifier 1 supposed to be the closest out the box? I'm at least looking for the best match for hand cannon hip to ADS. I run 400 dpi with 10 sens currently. 34cm 360.

1 is MDH 100%, while MDH 0% is close to 0.8.

vor 2 Stunden schrieb DPI Wizard:

1 is MDH 100%, while MDH 0% is close to 0.8.

I think on handcannons, 0.9 is closer to MDH 0%.  (1.4 zoom)

Impulserifles with like 1.8 zoom, 0.8 feels closer.

 

3 hours ago, IMIachine said:

Is there any conclusive ADS Modifier that is most accurately mated to hip fire sens? I've heard that 0.9 is supposed to be. I don't know enough of how this stuff works to tell. But is ADS modifier 1 supposed to be the closest out the box? I'm at least looking for the best match for hand cannon hip to ADS. I run 400 dpi with 10 sens currently. 34cm 360.

 

 

If you set the multiplier to 1, the game uses MDH 100%.  The other values don't represent any specific MDH percentage, so every scope uses a different one.

C:\Users\.....\AppData\Roaming\Bungie\DestinyPC\prefs\cvars.xml file has an option "fov_adjustment_offset" value="96". I was wondering if changing the value to "100" had any effect on fov discrepancy.

2 hours ago, FlynnB2 said:

C:\Users\.....\AppData\Roaming\Bungie\DestinyPC\prefs\cvars.xml file has an option "fov_adjustment_offset" value="96". I was wondering if changing the value to "100" had any effect on fov discrepancy.

Good find. The actual fov is ~96% of the configured value, so it sounds reasonable. Don't know why they would deliberately offset it though.

On 06/10/2019 at 12:32, Drimzi said:

Good find. The actual fov is ~96% of the configured value, so it sounds reasonable. Don't know why they would deliberately offset it though.

if it is only offset by 4% because of this single file  changing the number and setting that file to 100% and locking it would be interesting (edit) my file does not seem to have that line would be more than interested i having the fov numbers verified 

Edited October 7, 20196 yr by fortunate reee

I feel like it would also be worthwhile to test going 100% and higher. If we're able to push the FOV without any detrimental effects I'd be ecstatic. 

would be nice if @DPI Wizard could verify with the steam launch 

Edited October 9, 20196 yr by fortunate reee

Mine is set to 103 (105 in-game):

cvar name="fov_adjustment_offset" value="103"

Should be 100.8 if it was reflecting that 94% change

Guys please forgive me for being a total noob, but i'm assuming MDH stands for Monitor Distance Horizontal???    Also i'm not sure in practical terms what the difference between 100% would feel like from 0% etc. I guess in a nutshell, I was hoping to see which felt more seamless since on CSGO I use a lot of work shop training maps but on hipfire @ 34cm 360. I've only ever based sensivity on 360 which is why i'm having a hard time keeping up with what yall are saying. Is there an ADS modifier that is supposed to have the most similar feel to hipfire? I may be off the rocker on this. To me 0.9 feels excellent across a multitude of weapons, but in essence sometimes it feels a hair slow for hand cannons. I'm between 0.9 and 1 and having a hard time deciding which would be more beneficial as far as muscle memory and the fact that i use CSGO to train my aim.

On 10/6/2019 at 10:16 AM, FlynnB2 said:

C:\Users\.....\AppData\Roaming\Bungie\DestinyPC\prefs\cvars.xml file has an option "fov_adjustment_offset" value="96". I was wondering if changing the value to "100" had any effect on fov discrepancy.

Strange, I don't have this option in the file. I tried adding it manually, but it didn't do anything. Could someone upload their file?

You can have these (with 103 FOV  -I didn't change anything-):

 

cvars.xmlcvars.old

13 minutes ago, ProuDBeasT said:

You can have these (with 103 FOV  -I didn't change anything-):

My FOV didn't change with that file (had it set to 89, was still 89 after I replaced the file). If you try deleting the fov line, does it re-appear? I suspect it might be an old config line no longer in use.

23 minutes ago, DPI Wizard said:

If you try deleting the fov line, does it re-appear?

I entered the game, then checked if the FOV line was back in file and it wasn't.

25 minutes ago, DPI Wizard said:

I suspect it might be an old config line no longer in use.

It looks like it. The file was created back in the beta (2017).

2 hours ago, DPI Wizard said:

My FOV didn't change with that file (had it set to 89, was still 89 after I replaced the file). If you try deleting the fov line, does it re-appear? I suspect it might be an old config line no longer in use.

would that mean that  the fov given in  the calc might not reflect the current values ? 

Just now, fortunate reee said:

would that mean that  the fov given in  the calc might not reflect the current values ? 

No, the actual FOV in the calculator is correct.

18 minutes ago, DPI Wizard said:

No, the actual FOV in the calculator is correct.

https://www.polygon.com/2015/3/5/8158001/destiny-animation-motion-sickness just found this article this might explain some of the given fov if this is actually the reason for the weird fovv id rather have more fov 

Edited October 10, 20196 yr by fortunate reee

2 hours ago, fortunate reee said:

https://www.polygon.com/2015/3/5/8158001/destiny-animation-motion-sickness just found this article this might explain some of the given fov if this is actually the reason for the weird fovv id rather have more fov 

It's good that devs care about motion sickness etc, but that's easily fixed by just having a camera bob option and adjustable FOV. Reducing the FOV by 4% makes no sense, I think it's just a bad implementation. Probably something like in Apex, where a multiplier and the FOV doesn't add up.

From what i'm gathering 1.0 ADS modifier and 100% MDH just feels better with the flicking type shots taken with hand cannons. the 0.9 is MUCH better for rifling and everything else and tends to add consistency to various weapon use just all around... but I do end up feeling a lack in my flick shot accuracy with hand cannon duels etc... I really wish there was a way to run 0.9 with the long weapons and keep the 1.0 with lower zoom weapons like hand cannons and shot guns.

 

Am 10.10.2019 um 19:27 schrieb DPI Wizard:

It's good that devs care about motion sickness etc, but that's easily fixed by just having a camera bob option and adjustable FOV. Reducing the FOV by 4% makes no sense, I think it's just a bad implementation. Probably something like in Apex, where a multiplier and the FOV doesn't add up.

If, you are in third person (in the tower or equipping a sword for example) in Destiny, the configurated FOV is 100% true. Its just bugged, maybe because it was designed for consoles in first place.

Edited October 25, 20196 yr by WesleyPipes

For who confused like me what is ıron sights and red dots in game check this site

http://destinyscopes.com/

Hey @DPI Wizard is there any way that I could provide proof of this?

1 hour ago, ProuDBeasT said:

Hey @DPI Wizard is there any way that I could provide proof of this?

they got this exact feed back years ago ,id be more than amused if they'd now actually care

8 hours ago, ProuDBeasT said:

Hey @DPI Wizard is there any way that I could provide proof of this?

It's easy to test if you use scripts.

Set the sensitivity to 1 which will give you a 360 distance of 54545.45 counts. Set FOV to 80 and line up something vertical at the edge of the monitor.

Now move with scripts what should line up the crosshair with this vertical line, which is 54545.45/360*80/2=6060.6 counts.

This will however put you here, which as you can see clearly overshoots.

If you instead move 95.9% of the distance (6060.6*0.959=5812 counts) you will end up smack in the middle of the line:

Which means that the FOV is actually (5812*2)/54545.45*360=~76.72 and not 80

Calculator is bugged? actual fov is higher than the inserted fov now for some reason