Jump to content

potato psoas

Premium Members
  • Content count

    430
  • Joined

  • Last visited

  • Days Won

    9

potato psoas last won the day on July 4

potato psoas had the most liked content!

About potato psoas

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    Australia

Recent Profile Visitors

1,200 profile views
  1. potato psoas

    Minecraft

    I think they did. Calculator GAME INFO will need updating. And for some reason the game seems a lot more laggy now. Usually I get like 500FPS but now I'm struggling to get 75FPS. What have they done...
  2. I know it sounds convincing, but there's really no proof. You'd have to explain the why and how it relates to sensitivity, otherwise all it is is just a hypothesis. I personally think the illusion of visual angle is enough of an explanation for how the brain perceives sensitivity for changes in zoom level. Just look back at my diagrams, with what I said about: - two differently sized monitors sharing the same visual angle - matching the in-game FOV to the same visual angle of your eyes In both situations it's obvious that you can use the same sensitivity settings because they take advantage of this illusion, yet you don't follow the line of logic all the way when they take advantage of the illusion. Why? I'm not saying I know everything either, I'm just making sure to stay objective. If there is any other objective explanation for a change in opinion then I'm always open to it. It's not a good idea to say "don't be so pedantic, the brain will adjust".
  3. potato psoas

    Every game feels different?

    Use monitor match 0%, not viewspeed. It does account for a change in perceived sensitivity. With 0% monitor match your sensitivity will feel precise at the crosshair, where it matters most - for tracking and precision. If there is a change in FOV, you will have to learn the particular FOV's muscle memory (though it wouldn't be any better if you used any other method), but at least the crosshair will feel in control, so you won't miss shots you know you should have more control over.
  4. Well that's true, but you've got to consider that people change monitor sizes (like, from 18" to 27") yet they will put them in exactly the same spot on their desk and use the exact same settings and wonder why their aim feels off. And even if you intuitively moved back for a cinema screen, you may not be at the exact distance where the visual angles for both the cinema and the monitor match. Your estimate could be wildly off. And with what I was saying before - you don't have to take sitting distance into account if you don't want to, if you think you can intuitively know how far to sit. I know it's a bit pretentious and it still has problems, because it's impossible to keep your head locked at the same exact distance all the time. However, I still think it's a valid and important part of calculating perceived sensitivity. This is also true, but there is of course a change in PPI when changing from a 18" 1080p monitor to a 27" 1080p monitor, which is what I mean. And it gets even more complicated if you have a change in sitting distance and a change in monitor size. These are situations where I think a calculator would really help.
  5. potato psoas

    Calculator Discussion

    Monitor Distance at 0%
  6. And I remembered another example... Let's assume we use the same monitor but change the sitting distance for different FOVs, like so: If we match the visual angle with the in-game FOV according to a change in sitting distance then we can also use the same sensitivity. This is essentially the 360 Distance conversion, except the monitor moves according to the FOV. It's important to know this when understanding how to convert sensitivity. If the monitor stays at the same sitting distance then a change in FOV means the visual angle has zoomed in. And when it is zoomed in we can no longer use the same 360 distance because the perceived sensitivity has changed. The very reason why we monitor match.
  7. potato psoas

    Dest way to convert 0% MM?

    I personally think it's easier to just have the hipfire converted and not even worry about the ads. Let the game figure it out, even if it uses a different conversion method. Don't worry about that miniscule disparity.
  8. So I was thinking about sitting distance and I have another example for why it is relevant and an important part of perceived sensitivity. So we can agree that the monitor size affects the sensitivity because for the same visual angle the monitors would show two different perceived FOVs. But this only applies if the sitting distance hasn't changed. However, let's imagine that we place the monitors at calculated sitting distances so that they share the same visual angle, like so: Since they share the same visual angle, even though they are differently sized, you can use exactly the same sensitivity settings for each. As you can see, sitting distance is definitely an important part of perceived sensitivity. Just as monitor size is.
  9. potato psoas

    FOV problem

    The calculator tells you the appropriate "Config FOV" and the line you have to edit. In this case, the config FOV is 90.
  10. potato psoas

    How do I get the EXACT same sens from Gmod to BF4?

    It works well with anything. It's the best way to convert sensitivity.
  11. potato psoas

    How do I get the EXACT same sens from Gmod to BF4?

    Well you can actually just set USA to 0 and it will convert as 0% monitor match. No need to adjust individual sensitivities. USA is pretty much just monitor matching.
  12. I did test it myself and it works fine. Of course, when you are closer the sensitivity feels slower and when you are further the sensitivity feels faster. Where you sit affects overall screen target size so it will feel like the sensitivity has changed but it really hasn't - it's just compensating for a change in visual angle. You can use it or not, but I think it should at least be a feature on the calculator.
  13. potato psoas

    Calculator Settings bug

    Thankyou
  14. Hey @DPI Wizard I was wondering if you could reprogram the calculator to incorporate Monitor Size into the equation. I've mentioned similar ideas before in these forum posts: But I was trying to wrap my head around it and I can definitely prove that your Monitor Size (and Sitting Distance) affect your sensitivity. It might seem ridiculous and a little pretentious to add Sitting Distance into the equation but I think it's really important as well. Of course, this only matters if you have to change to a different monitor or adjust your sitting distance. Let me first explain how the FOV changes depending on Monitor Size. Assume two different sized monitors share the same in-game FOV (90 FOV). If we overlayed the visual representations so that they shared the same sitting distance then we would find that the overlayed section produces two different FOVs when referring to the same visual angle, as shown below: But even though they share the same visual angle, if you compared the FOVs, the larger monitor would actually have a smaller converted FOV and the smaller monitor would actually have a larger converted FOV. So it really is important to have monitor size incorporated into the formula, even if you don't change your sitting distance. But if you do change your sitting distance... Let's use the same monitor but we want to adjust the sitting distance. What happens is that the visual angle changes and therefore the perceived sensitivity, as shown below: This concept is also very easy to test. If you move your eyes closer to the monitor, the sensitivity is perceived to be faster, but if you sit further from the monitor the sensitivity is perceived to be slower. The best way to convert this is to scale the monitor distance proportionately as if it shared the same visual angle even though sitting distance has changed. See below: The math for converting 2D edge-to-edge is simply as follows: New sensitivity = Old Sensitivity * (Previous Sitting Distance / Current Sitting Distance) I am going to figure out how to do 3D as well, but I should say it's not necessary - we can always use the 2D sensitivity as reference.
×