Jump to content

fortunate reee

Premium Members
 View Profile  See their activity

  • Posts

    1,177

  • Joined

  • Last visited

  • Days Won

    39

 Content Type 

Everything posted by fortunate reee

  1. fortunate reee
    what dpi wizard meant to tell you was that siege has different multiplier for different scopes which makes it impossible to have the same feel for all scopes on one ads value ( so deciding which scope yo would want to start converting with , i like the 1x scopes (since those include iron sights/ pistols and all the 1x scopes ) ^ this is why the siege calculator gives you different ads numbers depending on the scopes you want to use \ sticking to one scope would make conversion possible /easier all of this is pretty well explained over here https://r6fix.ubi.com/test-server/TTS-20721-Scope_sensitivity_needs_to_be_adjusted_per_scope__requires_separate_sliders_for_1x__ACOG__and_Kali_s_two_scope_magnifications_ ^worth giving it an upvote while you are at it
  2. fortunate reee
    this was the exact point that got me confused ^ how do you get that value ? a change in fov shouldn't have anything to do with the resolution unless you change the aspect ratio ( the fov cant magically get bigger than it's limit ,unless you modify game files ) using another fov type in the calculator might end up spiting out other values but those shouldn't be applicable in most games with a hard coded fov limit 105 fov ingame caps at exactly 100.8 anything above that will likely just mess up your calc numbers that is what got me confused in the first place . ---------------------------------------------------------------- figured it out you are doing what we are doing just that you mentioned game b as a and a as b your default fov is 105.5263 hor/73.00858 vert @ 1440p and you are just using focal length to match the hard capped destiny just like me yikes thought i had just missed a point might have just misunderstood your explanation initially for a second you made me hope that there was a way to increase fov that i just hadn't found yet after years of searching
  3. fortunate reee
    destiny is a difficult example since its very inaccurate by default(at least its scopes can be) it doesn't go over 105 in game as far as i am concerned so why are we setting it to 110 ? ^ if you aren't doing that on purpose stick to auto fov at your desired 103 with one fov type and let the site handle the conversion (to make sure that it actually caps where the game caps ) the reason that doesn't work perfectly in destiny might as well be that the game is inaccurate you are also setting a completely different fov type is there a reason for that besides of demonstrating the pixel ratio ? think out goals overlap slightly but not exactly
  4. fortunate reee
    https://www.mouse-sensitivity.com/?share=e6fae65788ed7c45430044784171bad6 should look something like this most things are well explained here
  5. fortunate reee
    works like a charm so far thx for the quick implementation
  6. fortunate reee
    if you use the all conversion you will get the same thing just that your hip fire and otehr scopes will be the same too
  7. fortunate reee
    there is no ideal way of matching 4;3 stretched with 16;9 you will only be able to match one axis somewhat well there are up to date instructions that can elaborate 0% and alll the other things with this you are only matching this one zoom level with the other games zoom level selected use all options when available
  8. fortunate reee
    shouldn't be afraid of voicing your ideas in regards to aim im pretty sure that most of the active users here are more than interested in optimizing their setup / alternatives crowd sourcing ideas is the fastest way to achieve progress after all out of interest does your setup look like this then ? https://www.mouse-sensitivity.com/?share=c4e4d2bcac8450a57fb351583346e199 or do you manually convert desktop to hipfire with 110 then on another instance match hipfire with focal length 0% to not get the scopes affected by windows 100+ 0% in theory the scopes should have the same number unless they get affected by 100% btw i just noticed that the value i keep going back to when it comes to hipfire 41/43 cm/360 is pretty close to 100/110% mdh on 400dpi ironic
  9. fortunate reee
    did you just trial and error all options until you hit %110 mdh ?
  10. fortunate reee
    highly suggest using auto fov when intending to keep the same fov saves you so much effort down the road
  11. fortunate reee
    im just creating the custom res to then use in the game with black bars works like a charm
  12. fortunate reee
    ngl even after re downloading the whole file /opening it in open office i am now able to open it and i still dont get it i hardly play cs these days and i stay away from stretched/ 4;3 because i actually prefer matching with blackbars/focal length when needed \ so i might not be the target audience
  13. fortunate reee
    you set fov 1 ( alpha/ game you want to convert from) you set fov 2 ( beta / you wish to convert to) you set then custom res you get as a result as game 2s resolution in the calculator and the focal length isn't as far off when you cant natively match the fov thus the pixels/count stay closer to the original and you can maintain teh sens https://www.mouse-sensitivity.com/?share=bb5648614fd29bb64f99e0c47a7597a2 this would be the focal length matched destiny (100.8 fov beta matched from 73.74vdeg/106.26 alpha )as an example for 73.74 vdeg this would end up with those numbers or something close for destiny and 103 fov games like overwatch and valorant it is just a bit of a hastle to redo the geogebra thing every time i wish to change the base fov so an implementation would be very beneficial my initial thought was to create a stretched /black bars option "focal " that would take fov alpha match it to Beta in a similar fashion to the geogebra thing and then automatically insert the matched res in the game b resolution allowing for simplified use with the calculator im unsure how doable this would be from a math / implementation stand point but i must say whatever we can get would likely be a step up from what we have to do now
  14. fortunate reee
    rookie numbers
  15. fortunate reee
    This feels too high (110 cod fov to 110 apex fov) -then tweak it and actively try to fit your ideal across all games that was my whole point do it through the auto fov function for actual results and make sure you are using the config file for apex ^this is crucial for uniform hipfire / movement those are the "correct" values you were getting i explained this above you were matching two different fovs tho which made the whole thing scale different thus the different numbers
  16. fortunate reee
    legit cant open the thing without having it corrupt on me let me know if you understand it
  17. fortunate reee
    the first part is factually incorrect and the second part is exactly why i mentioned using a middle ground is because that is the only way you can achieve a level of uniformity or much rather consistency in your aim/ movement exactly the same 110 fov using auto fov and it feel identical (i prefer 0% matching but that one is up to you and your preference , 133.333 will never be completely uniform across games due to different scope fov sizes ) at the end of the day its up to you just sharing what is considered to be the go to in most cases
  18. fortunate reee
    you have not matched your fov to be the same across the 2 games , i mentioned that for this exact reason you are telling game b to perform scopes scaling at 133.333 as if it was game a at 133.3333 the other thing you are comparing it to would be telling game a to use 133.333 ads scaling matched to its own fov i didn't mention this for no reason pick 1 fov and stick to it across all games especially if you want to match 360 distance and something other than 0% ads its up to you which number you end up using find a decent middle ground (it is the better long term solution to staying consistent ) https://www.mouse-sensitivity.com/?share=e697f5fac4bb44d4fe1c6fa23655d8f0 <--- use this and raise/ lower your fov
  19. fortunate reee
    the file corrupts if i download it dunno interested tho
  20. fortunate reee
    that is exactly why i do 360+ 0% from game a to game b i like slow scopes too im not used to sniper scopes since i hardly used them in the past its mostly preference that windows thing is weird i felt the same
  21. fortunate reee
    i can relate to that very well , i still prefer game to game 360 + 0% ads ( ) at slow sens which kills my sniping but really does feel well for short zoom games aren't necessarily making it easier when it comes to their bad implementations when it comes to ads options ( cod / bf being the only exception to that )
  22. fortunate reee
    ^ nvm would have been the same result +/-
  23. fortunate reee
    that is intentional with focal length scaling ( 0% ) the more zoom the slower it gets gets you the ideal level of precision
  24. fortunate reee
    hey @DPI Wizard aimlab received an update yesterday that focused on the inputs/ 360 distance / focal length would appreciate an update to the calculator just to make ure its still working as intended another thing that i am interested in would be this concept and its potential viability
  25. fortunate reee
    relative is the go to ,since legacy is only for old timers not usefull for 99% of players in the end of the day scope scaling is preference after all happy to help
×
×
  • Create New...