Jump to content

Fish Gaming

Premium Members
  • Posts

    36
  • Joined

  • Last visited

Posts posted by Fish Gaming

  1. DPI Wizard,

    Do you mind to add the new scopes from 0.14 once SPT's version comes out for you to use. I know there is a mod for 3.7.6 if you are wanting to sue that for the wilcox Boss and new Teng Scope.

  2. You can now change the FOV. They added with the primal update an additional FOV slider up to what looks like just 10 more so now you can be at 105. Needs an update to the FOV to make sure the calculations are still correct.

  3. 2 hours ago, Fish Gaming said:

    @fortunate reee @Yuril3 How long ago did they make this change in sensitivity?

    @DPI Wizard are we able to still calculate each of the sensitivities? Before you used the ADS to get the Global Sens and then use that to calculate all the other values but how do we do it now? Has this change made it where you cannot calculate the ads without and with zoom cannot both be placed in the config file?

     

  4. @fortunate reee @Yuril3 How long ago did they make this change in sensitivity?

    @DPI Wizard are we able to still calculate each of the sensitivities? Before you used the ADS to get the Global Sens and then use that to calculate all the other values but how do we do it now because all sens require a global sens that isn't being calculated?

  5. Hello,

    I just bought this game and just wanted to make sure since it was updated a while back if everything still works the same as before. I also wanted to make sure I'm going about this correctly. So it appears from the calculator that when you ads you don't change your FOV at all? And you have to put in the global sens to get the ADS and then use that Global Sens to set your hip fire? Just wanted to make sure that was correct.

    Thanks!

  6. Okay so after the Christmas update today I have my mouse at 400 DPI, I've lowered the polling rate down below 500 to keep the packet loss from interfering with the sensitivity, and I have my hip fire at 1.4 with 90 FOV. But now the sens isn't even close to 20.3 inches/360 turn. My mouse pad is only 18 inches wide and the 360 turn is complete before even finishing the mouse pad. I turned it up to 1.5 and it is much closer than before. I am starting to get worried because I like my sensitivity to be correct and every time I get on a different game it seems like something the developers have done is changing sensitivity and I'm initially under the assumption it's still correct. Just wanted to check with others on the forum to see if they too have experienced any difference in the hip fire after the update?

  7. Were the scopes gone through again? I cannot find really any snipers with two levels of zoom. Not saying they don't exist but I either don't see them or I can't access them. I want to get the correct sens and one of them feels tremendously fast while the other is okay. Don't know if that is just how the game feels or if the scope values are not completely correct.

  8. okay I just want to make sure I don't have this file. I went to my file explorer and typed %localappdata% and then under the Unreal Engine folder I see only numbered files such as 4.11, 4.12 ect. Is this what I am suppose to be seeing? How skewed of aiming will I get if this ini file is messing with the aim?

    Thanks for the help,

    Talmadge

  9. Hey I just wanted to check back in on this game to make sure nothing has changed. I took my base game and the calculator stated that if I used 950 DPI with 1.4 hip and 9.9 Eye of Reach I would get the 44 inch 360 turn. I used a ruler on my mouse pad and with the correct dpi change the scope 360 turn was way off. I can link the picture of my conversions to see if I did anything wrong. 

    Untitled.png

  10. Thank you so much for updating this and for also adding ADS!  I did find finally out that the \ button was the one to open the console up but how do you change that keybind and is there any list of working console commands?

    For the ADS sens how do you add that as separate and it not override hip fire sens?

    Lastly I have notice that after each match the sensitivity settings are reset. Is there any reason this keeps happening?

     

    THanks for the help guys!

     

     

  11. On 1/30/2019 at 11:57 PM, Drimzi said:

    This is an old thread full of misconceptions and bad ideas. 0% will always be the only way to convert the sensitivity. Anything else is generating a new sensitivity that preserves a characteristic of the old sensitivity.

     

    You got two viable options for consistency:

    • Convert 0% from a single source to everything. One universal sensitivity. Low fov and high fov games will have different mousing for navigation.
    • Maintain a constant hipfire cm/360° for consistent navigation and convert 0% to ads/scopes (anything that changes the fov) to maintain the same sensitivity relative to the hipfire. You end up having a different sensitivity for each game, but it is muscle memory associated per game.

    Drimzi,

    So I know I'm am WAY OVERDUE to this thread but I wanted to ask specifically on this post. I have read all your other posts and I understand your point. Just a couple questions on this. So I play a slow sensitivity for hip fire where I can be accurate in games such as CSGO for hip fire but when converting from the hip fire at 0% the ADS values, of course from being based on the hip fire, are tremendously  slow and I can't track targets at all. Up to now I have been using the same game (siege) using monitor distance match at horizontal auto % match. I have converted my hip fire with 360 distance, but for my ADS I have been using a sens that I've grown comfortable with from Siege. It  gives me 36.0472 inches at the acog's 49.46 FOV (original FOV 83). This Sens is what I convert from for all ADS also at auto % match on monitor distance horizontal. This way I have attempted to maintain the original point you had where the sensitivity is universal as much as possible but where I can also use it since it's too slow basing it off of hip fire. Do you see issues with this? I ask you because you understand the math portion clearly more than I do and I want to know where this method of converting could go wrong. Also extra piece of information that is needed is siege is at 83 Vdeg (115 Hdeg Res) but most all of my other games are at 102 Hdeg Res.

     

    There are two I play a lot that are 90 in TPP as well. Any advice on TPP from FPP? 

    Thanks for the advice, 

    Fish Gaming

  12. Just wanted to ask after reading the note on the game for the negative acceleration I'm getting mixed results online for how to fix this. You say to have a low report rate. Do you mean lowering the polling rate of the mouse? and if so how do you test it to make sure you lowered the polling rate enough? Some Sites have said to increase polling rate though to help with negative acceleration so I figured I would just ask you to know for sure.

  13. just one question at the moment on the aim trainer, why is there a separate value for the x and Y axis? I normally play 1:1 ratio on all of my games so the x and y axis are the same sensitivity. Does this aim trainer not work the same?

     

    Thanks for the help!

×
×
  • Create New...