Jump to content

Bash

Premium Members
  • Posts

    11
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Bash's Achievements

  1. Brilliant! Thanks for the quick response @DPI Wizard!
  2. I notice that Apex (at some point) added an 8th scalar to their cfg. I also see that the calculator generates eight scalar values. However, the calculator generates two scalar_0 values and no scalar_7 value. Are we meant to use the two scalar_0 values as scalar_0 and _1 in the settings.cfg? Or should we be deciding between the _0 values depending on whether we prioritize smgs/pistols or rifles? And if the latter, what should we be using for scalar_7 (it was set to default 1.0 when I checked recently). It's also odd that the in-game menu only includes the original 7 multipliers, there is no 8th value. It only exists in the cfg file. Should this mystery 8th scalar (scalar_7) be ignored? I simply want to ensure that I'm entering the correct values for the appropriate scalars in settings.cfg. Cheers!
  3. Cheers @fortunate reee! I've been toying with different values and 75% feels really comfortable atm. Much better than anything I accomplished with the viewspeed conversion.
  4. Couldn't agree more, and to be honest, that's how I've always moved between games. I used to play around 35cm but I've been creeping upward in recent years. Sitting at 39.33 these days (oddly specific, I know). I've honestly never felt the need to tweak for specific ADS but something about the Apex default doesn't sit right with me. Thanks again for all the information, I'll definitely read more into it. May even try 56.25%. So much to know, seems like a deep rabbit hole.
  5. Brilliant! I think I understand now. Since 0% is the default in Apex, I have to input a different % in order for the calculator to generate a value other than 1.0 for the scalars. I figured it was something simple and obvious that I was missing. Thank you for your patience, I really do appreciate it! (I've used my fov of 1.26836 at 75%, I'll be sure to try 100% as well) Curious, is there a reason you opted for horizontal distance as opposed to vertical distance for the conversion? Just preference?
  6. And this is exactly why I started this thread tbh. Everyone states that distance is the most optimal method, yet my problem seems tied to viewspeed. You mention that all scopes showing 1.0 is normal for Apex and that the perceived speed is something one has to get used to. I think that's my issue. I don't want to get used to it. I really dislike how slow the higher magnification feels compared to my hipfire (specific to Apex). EDIT: Regardless, I really do appreciate you trying to help. I'm not trying to frustrate you on purpose.
  7. I don't have a secondary game to compare to, nor am I trying to match the feel to a game I've played in the past. I suppose I want the Apex scopes to closer emulate my Apex hipfire sens, but obviously I cannot simply translate the 360cm to a 10x scope or the sensitivity would be off the charts. My hipfire and iron sights feel great in Apex, I don't want or need to adjust this. My issue is with the different levels of ADS magnification. I can track and snap from hipfire with no issue, but any level of magnification screws with my muscle memory (I assume due to the way it handles fov). Maybe what I'm trying to accomplish isn't feasible or doable? That's the answer I'm looking for. Thanks again for your help.
  8. Here are my results using viewspeed to normalize my scalars for each specific magnification: It feels pretty good. I guess I'm just looking for confirmation: Is this placebo? Or is this the "best" method to accomplish what I'm trying to do?
  9. Oh nice, I didn't realize that's what the "all" aim option was for. Thanks for that. Hmm. So do most people not use the ADS scalars in Apex? I'm not coming from a different game (though my 360cm hipfire is generally the same in most shooters), I'm simply trying to normalize the different ADS magnifications with regard to my muscle memory, specific to Apex. Leaving the scalars at 1.0, the higher magnification scopes feel extremely slow to move but I'd rather not adjust the scalar multiplier by feel (which is how I did it prior to finding this website). I'm starting to realize that the viewspeed conversion may be the "optimal" solution after all. Seems like my issue is less about monitor distance, more about viewspeed at higher magnifications.
  10. Thanks for the response. I'll post some images to better explain my issue. In the first pic, I've used distance vert 0%, but the scalar calculation (highlighted) remains at 1.0000 no matter which aim I select. The second pic shows the same values but using viewspeed vert, wherein the calculation gives me a usable value to put into the config for each ADS scalar. I assume I've either missed a step, I'm not inputting something correctly, or viewspeed is the best way to accomplish what I'm trying to do. Just want to confirm either way. Thanks again!
  11. Hello! I've tried my best to sort this out myself, reading through the instructions and the resources, I've attempted to search the forums, but I could still use a nudge in the right direction. I realize that no method is without it's flaws, but what is the "optimal" way to calculate the ADS magnification scalar values for Apex Legends, for each separate sight and optic? I start with my hipfire 360 sensitivity and attempt to convert it to monitor distance vertical for 1x ADS (for instance) and the scalar result is always 1.0000. All other sights and scopes result in the same. The only way I can generate a usable value for the config is to use viewspeed. Is this how I should be making the conversion, or is there a better option? Viewspeed results are decent but I feel like I may be missing something. All of my fov, sens, and other values have been lifted from their respective Apex config file. Any help would be appreciated, thanks!
×
×
  • Create New...