Bryjoe

Why would sitting farther away help with the FOV? No matter how far or close you are to the screen the 3D space that is shown is the same. Actually, when you are farther away a lower FOV should be more comfortable, hence why a lot of console games have low FOV (also better performance). I think matching based on a ratio like viewspeed works just fine. In fact, it has been a revelation in how I match sensitivities across multiple FOVS. Game to game, my aim feels the same, it is not challenging to jump right into a new shooter anymore.

So now we are talking about going back to the drawing board on Viewspeed? To me Viewspeed V2 made the most "sense" not in a mathematical way, but it was close to 75% monitor match which most people seem to like. Really, you can quickly get "used to" any Monitor Match after a few hours of playing. Games where the match is hardcoded like COD feel fine after awhile even if you're used to 75%. Maybe it's truly something like what was thought originally: there is no "right" ratio. 0% is better for aiming around the center of the screen, 50% is good for both, 75% is great for flicks while still retaining most of the accuracy of 0% and 100% is best for flicks.

So, this new solution is only for those that convert based on desktop sensitivity right? The current iteration of Viewspeed V2 is unchanged if you are converting from one game to another?

You never would. Hipfire for scoped feels atrocious. A lot of games have poor sensitivity options, but I haven't played a single one that doesn't lower your sensitivity when you scope. The best ones (Battlefield and CSGO) have a consistent ratio no matter what scope you are using. Many other you kind of have to pick your favorite scope and have an approximate ratio after, but if the aim isn't getting slower the higher zoomed your scope is the aim feels horrible.

It is debatable for hipfire sensitivity. CSGO and Overwatch have essentially the same FOV 103 vs 106, so no matter what you do, you will have the same aim for hipfire in those games. WIdowmaker and Ana's aims should be calculated based on Viewspeed V2 or a Monitor Distance number. I believe around 45 in-game is what is should be using Viewspeed V2 @1200 dpi. Take a game like battlefield, with a pretty low default FOV, matching 360 based on CSGO is guaranteed to feel a little fast for you. The FOV matters the most for aiming, it really does. The FOV determines how far you crosshair moves in the relative 3D space, it doesn't matter if you arm is moving the same distance in each game, the crosshair will move and behave differently at different FOVS, that's why 360 is inherently flawed. The easiest way to think about it is, take the AWP in CSGO, imagine using the same sensitivity for the scoped AWP as your hipfire 360, it will feel incredibly awful and fast. Now take that same concept and apply it to hipfire from game to game. It won't feel as bad as the AWP, but there still is a signficant difference to how aiming feels at different FOVS.

The current best way to use this calc in my opinion is to have one hipfire sensitivity that you love in your favorite game a specific distance in inches or centimeters. Pick a First-person game and a third person game. For me, this is CSGO and Pubg. You then convert this same sensitivity using Viewspeed V2, regardless of FOV. For the aimed scopes use viewspeed v2 that is based on the hipfire sensitivity you calculated from the original game. Even this is not always perfect, but that is more to do with developers not putting proper sensitivty settings in their games than the calcuator. Use Viewspeed V2 for everything.

I use my default 360 for pubg or 41.6CM/360. I then convert Viewspeed V2 for all games based on 41.6CM 360 for Pubg, it seems to work pretty well. In a game like The Witcher 3, which has approximately a 90 FOV it feels fast enough using viewspeed. It really depends largely on how the 3rd person FOV was calculated and how accurate it is. For instance, in a game like WoW, the calculator FOV is based on the first person view, but in reality, you are zoomed way far out in WoW, so who knows what the actual FOV of that zoomed out view is. I think the problem is that the FOV is more inaccurate on some 3rd person games than others, I have found through trial and error that pubg feels good at a similar sensitivity that I use in first person games, so I convert based on it and it works decently, but not great. Thankfully, there are very few competitive 3rd person games, so it doesn't matter all that much.

It is indeed perfect. The only limitation is some games don't have a good ratio matching system.

This might be the wrong thread, but I wanted to ask you. On a game like COD or Titanfall where you can only match the sensitivity to one "scoped" FOV, would it be better to match it to the higher FOV (pistols etc) or the sniper rifle FOV? Basically is it better to scale down or scale up, @DPI Wizard told me one time he thinks he would prefer scaling down, what do you think?

I am not really sure what the best way to match this game. Viewspeed matches an ADS value to what I assume is close to Monitor Distance 75% and then the rest of the scopes will scale at Monitor Distance 0%? I really wish their ADS was like CSGO where it's simply a ratio and the rest of the scopes would scale based off that.

You don't have to use the same FOV as Overwatch, Viewspeed V2's goal is to eliminate the need for that. However, for a perfect 1:1 ratio in hipfire, you must use the same FOV for it to be accurate. Accurate is probably the wrong word, for the 360 distance and the relative distance your cursor moves on the screen to feel and be the exact same you need to match FOV. Viewspeed feels the same regardless of FOV, at least when it comes to aiming. Where the argument comes is when you start talking about movement, as being able to control your character with the same 360 distance is valuable for that. (although, in my experience I don't really notice a serious difference in movement capablities) Matching the FOV to Overwatch means that your hipfire sensitivity won't only feel identical, it will be identical in every respect, which is why it's often the recommendation if you can stomach having the same FOV. When you are aiming down the sights or using scopes of any kind is when you are required to use something like Viewspeed, however. There are some games where it is very undesirable to change the FOV, or some games have it hard locked, this is where Viewspeed comes in as well. Games like Quake which play best at the default high FOV come to mind, or games that were designed with a low FOV in mind, like many console ports.

It 100% will, as most of your aiming in PUBG is ADS (Aim Down Sights) anyways. If you match based on Viewspeed V2, it will be the same as hipfire in CSGO, just slightly different as it is based on a ratio rather than how far you move your mouse. 3rd person hipfire won't be the same and may never feel the same.

So, stretched is a tricky situation. There is a way to convert it, but stretched makes one of the sensitivities inconsistent (I think it is horizontal). Someone like the Wizard or @Drimzi is going to have to help you.

This game has a locked ratio of Monitor Distance 0%. Therefore, you will not be able to get an accurate conversion from AWP. Just use Viewspeed V2 and base it off your CSGO hipfire. Ironsights will be a ratio you are familiar with from CSGO, but the higher powered scopes in COD will be matched based on Monitor Distance 0%. Snipers in COD will feel slower than the AWP and there is no way around it. It should feel perfectly fine for shots around the center of your screen, but it will take some adjustments to get your flicks down. You actually maybe be able to get an accurate conversion if you were to match CSGO's AWP to Monitor Distance 0%, but then you are defeating the purpose of converting your familiar AWP sens to COD.

So, Pubg is one of the only 3rd person games that doesn't feel absolutely sluggish using traditional conversions. Running the game at a modest 41cm 360 doesn't feel nearly as slow as it does in other 3rd person games. It also corresponds with settings most of the "pros" have settled on being 40-60 (in-game conversion) sensitivity. The viewspeed match with CSGO at that same 360 distance would make it ~55 cm/360, which surprisingly still feels pretty good if not a little slow. PubG seems like an ideal game to be your "Base" 3rd person game as the hipfire matches really well and feels good compared to other 3rd person games. It is surprising that so many find the conversion off in this game when it feels better than most 3rd person games.

Yeah, might be. I do find matching the "over the shoulder aim" to viewspeed the conversion feels fine, though. Maybe that is just placebo. I wish there was some way to find out even an approximate conversion. Quick and dirty is that third person hipfire movement feels much slower than first person hipfire movement given the same 360 distance, no conversion needed, that is just a fact that anyone can tell. Thankfully, the over the shoulder conversion works well enough and most 3rd persons you ADS the majority of the time you are shooting. It's just a matter of getting the movement to some semblance of the right ratio.

Third person hipfire just doesn't work well. The FOV changes too much. It feels fine when looking at a distant object, but when moving around match to 360 distance usually feels slow in 3rd person games. I have read that third person is effectively 3 times the FOV as First person. It's not based on anything technical and is probabaly woefully incorrect from a technical standpoint. The point is, third person doesn't feel good to me matching at 360. Since it always feel slow, maybe for calculation proposes it would be better to arbitrarily viewspeed match to a high FOV?

Hmm, well scoped in BF4 is based on a weird calculation if you don't use Universal Soldier Aiming. The different scopes all feel different, the more magnified they are the slower they are, but not necessarily by the same percentage (which is why USA was created). V2 should be faster, but you are right, it is slower in this case. It must be because you are using that conversion.

That is preference, and Viewspeed V2 gives a faster sens as well: In reality, I am not sure why you want to match it based on your scoped 1x in BF4, that is already so close to the hipfire in terms of FOV. It is up to you, if you use that setting to match every game you have with Viewspeed V2, they should all feel pretty close no matter what FOV you use. If you match FOV between games they will feel even better, but that is not always desirable.

Yeah that's right your hipfire is faster, not slower, and actually the FOV is not that much different because you have changed it to 74 VDeg which is pretty close to CSGO. 1x ADS is not that much different of a FOV compared to hipfire.

The BF4 ADS sensitivity is a really low FOV compared to CSGO hipfire, there is no way a straight conversion would be slower using Viewspeed V2. You are doing something wrong, can you screenshot it? If you use Universal Soldier Aiming, the calculation would be different as well.

In what games? What is your FOV in those games? It shouldn't. Viewspeed 1 is very close to Monitor Distance 70% and Viewspeed 2 is very close to Monitor distance 75%. 75% should be a faster sensitivity than 70%, actually, it is in all cases as far as I know. So, H1Z1 hipfire should be lower than CSGO if you are using the default FOV, not by much though. It is all about your FOV, your FOV determines your sensitivity, lower FOV, lower sens with Viewspeed. If you think about it like that, you can see why scoping sensitivity makes such a huge difference. All games have a ratio for scoped guns (if they didn't it would feel terrible) it is a ratio that is slower than your hipfire. Here is the process if you want to match sensitivities between games for best accuracy: 1. Match both games by hipfire using either viewspeed or 360 distance. If you use 360, I would recommend trying to match FOVs as well, this is a little trickier though, as games use different methods for FOV calculation and just inputting the same number for each is often wrong. You have to match the type of FOV calculation too. This is why, for beginners, it might just be best to use Viewspeed V2 for hipfire as well. 2. Now, with Viewspeed V2 selected, simply click the drop-down menu on the right to match each scope. CSGO, like many games, only has the option to match one of the scopes. I would recommend you match it to the AWP and match it to the scoped setting for H1Z1. It gets really confusing if you try and match scopes and hipfires across games. It is best to just convert the hipfire for one game and then use Viewspeed V2 for each game individually. You can then use Viewspeed V2 for all scopes in every game and be confident your scope is always scaled based on the same sensitivity. Some games don't even have the option to adjust scope sensitivities, in those cases you sensitivity while scoped will NOT be consistent, but at least it still will be a ratio of your hipfire. The beauty of Viewspeed is it takes all the confusing nature out of it, it is the same ratio for every game no matter what you FOV is, scoped or unscoped. Your distance 360 changes based on the FOV, but that is always based on the same consistent ratio. Like for me, my "home" game is CSGO. It is a great one because it has a very safe FOV. I use 41.6CM/360 hipfire to convert the aim in every single game that I own. Using Viewspeed V2 I don't even have to match the FOV is I don't want too (although that is objectively the best option for a perfect match). Pick a "home" game use that one sensitivity for every game.

They really are extremely similar. I don't know anything about the technical aspects of each, but Viewspeed V2 is superior as it works better at the extreme ends of FOV. Viewspeed 2 is a faster conversion, but not by much. Use Viewspeed 2 unless for some reason you like the lower sensitivity the the original viewspeed offers. Viewspeed 2 should feel identical to CSGO default AWP sens in most situations. You sensitivity increases and decreases based on your FOV, so if you are unscoped you will move faster, if you are scoped you will move slower, it sound counterintuitive but it really is the best way to do things. If you like consistent movement, you can use 360 distance, but I recommend matching FOV if you want to use 360 distance. Actually, if you match FOV, Viewspeed is meaningless in hipfire.

It is better to match your R6 FOV to 70.53 if you want to use the 360. 360/Hipfire: Viewspeed V2 conversion for ironsights if Widomaker is converted from viewspeed v2:

Would there not be an issue because his Ana sens is not calculated using Viewspeed? Or would it calculate it correctly to be a faster sensitivity?