sc0zz

Perfect, Thank you.

Ok that makes sense. Thanks. It looks like the 3rd person view of the ridden doesn't change the sensitivity anyway. They just throw a mini ridden model into the first person perspective XD - thanks again. Merry Christmas

Hi, thanks for that. Are you sure it's correct? I ask because when using the horizontal option I now get a sensitivity that's almost 7+ what it was before - when really that shouldn't change. Basically they now have two options in the menu - one slider for hfov and another slider for vfov - you can choose which calculation you want. So, I would have thought that the horizontal calculation would remain the same and in fact that is my experience in game. A bit confusing. It wouldn't matter except this affects the newly added ridden 3rd person sens too =/ - appreciate the fast work though. Top man

Hi again. Will there be an update to the calculator, now that they've add vfov options to the menu? Also, the ridden play in third person - any plans to add that view to the calculator? Not urgent by any means - just asking, in case I forget.

One thing I've found useful for UE4 games is https://www.saveeditonline.com/ You can upload .sav files and edit them, then download the edited copy and replace. It doesn't work with everything but I just tried the B4B file with the sensitivities ( C:\Users\userid\AppData\Local\Back4Blood\Steam\Saved\SaveGames\PlayerSettingsGame) .. and it did work. Worth a shot if you're a perfectionist and your 360 sens is above 10 because of a low dpi.

Thank you my man. So I'm good to go. Just choose "all" set my fov and job done. Great stuff thanks. Keep up the sterling work

Thanks. I am aware that the fov changes the sensitivity in UE4 games. I come across it a lot but you have specifically put Monitor Distance Horizontal, where as I use vertical for ads etc (no reason for that, I think I was told to once) - but it appears that ads and scope sens doesn't change if I change the second field to monitor distance horizontal, so I just wondered why it was specified. Did you just mean that the game uses horizontal FOV? Also can you clarify that only two decimal places can be entered if your sens is 10+? I assume that if somehow you could get 100+ (40 dpi? :P) it would be 1 decimal then.

Affected by: FOV: (Monitor Distance Horizontal 100%) what exactly does that mean for me when converting a sensitivity say from BF3 when using these settings? Must I change my ads and scope fields or can I leave them? Also, I am able to put three decimals if a sens is say 1.045 ... but not if it's say 18.567 - I would have to round up the latter to two decimals.

Hi. I'd like to add to this, that if you create a .cfg file (I did it by copying one of the existing ones) and rename it autoexec, then pop it in the game directory, you can get your preferred fov on launch without messing around in console each time. You can also alter viewmodel fov - this helped me get a less screen stealing ADS. Example autoexec contents: sv_cheats "1" fov "90" viewmodel_fov "54" the above are the default values - mess around to suit your preference. P.S. there's also a small mod that lets you hold aim instead of toggle. You'll find it by googling.

Mad Max https://www.gog.com/game/mad_max Genre: Action - Adventure - Survival Works on: Windows (7, 8, 10) Release date: September 1, 2015 Company: Avalanche Studios / Warner Bros. Interactive Entertainment Size: 32.5 GB Links: Forum discussion Rating: PEGI Rating: 18+ (Bad Language, Violence)

Yea. I don't really aim scoped in anyway. I aim then scope in so it's only really mattering for adjustments, plus I rarely use anything higher than reflex/red dot scale. I get the feeling it's not really going to change anything for me since it was probably the same for me before the change? Anyway, great, we got there in the end Sorry for being such a dunce. Both I and my muscle memory thank you, for your usual prompt and informative help. Stay safe.

OK so, converting from BF3 hip fire, same aspect and uses VFOV, really all I have to do is plug in my hip fire sens, choose all and change everything to either 50 or 0.02 (depending on muliti vs sens dropdown) and that's that?

I meant as the reason these games use MDV was because they all use VFOV now. Anyway, I am converting from another games hip fire but I always use 360 distance for hip fire and always use the same fov. So do I need to change to MDV in the origin sens game too? Still confused here tbh.

Why? Because VFOV? Anyway, so if I just set all ADSMouseMultiplierUnit to 0.020003, leave MouseSensitivityMultiplierUnit as it is, I should be good with MDV at 0%? Otherwise, I don't understand how if I'm guessing a monitor distance %, how is that going to be consistent?

Yea, I haven't changed anything yet. That pic is how it looked after the patch. Ah, I see - ADSMouseSensitivityXx - so I can't just choose all then? I have to do each individually? I don't really know what I'm supposed to put for Monitor Distance - and mine is Horizontal not Vertical - should it be vertical - I didn't bother with scopes before, just reflex but now they've fixed this I'd like to mix it up a bit, if I can achieve consistency.

Hi, just getting around to updating my settings for this. So, it seems like MouseSensitivityMultiplierUnit stays the same as I had it before but I'm a bit confused by the rest. If I choose sensitivity from the drop down it tells me to just change all the scopes to 50 - I mean is that right? What about xfactor aiming? If I change it to multiplier it tells me to change ADSMouseMultiplierUnit to 0.02. Multiplier seems to have less discrepency to the sensitivity I'm basing it on, so I'd rather use that. Am I right in thinking then, that actually, I don't need to do anything here in this pic?;

Yea but in the calc - if you leave it at game settings, the discrepancy is a bit much - 2.6% - and the sens would be 1.9 for me - and that's where it says Mouse Horizontal Sensitivity 40. If I set it to console, the discrepancy is 0% and sens is 1.85 for me but that's where it shows the (0.022) yaw/pitch settings instead of Horizontal/Vertical (40). So 40 is same as 0.022 then? and it's simply that the sens can only do two decimal places in console?

Hi, so is m_yaw 0.022 the same as Mouse Horizontal Sensitivity 40? I'm not sure whether I'm supposed to change that 40 to something else in game. If I enter m_yaw 0.022 and m_pitch 0.022 into the console along with my sensitivity, only my sensitivity changes. The Mouse Horizontal Sensitivity and Mouse Vertical Sensitivity stay at the default 40.

Thanks for the reply. So would 260 step up to 300? Because 260 definitely feels faster than 250 - set in ghub. I settled for 250 - feels pretty good. You didn't answer my question about the horizontal or the scaling but that's OK, it doesn't really matter now since I can't imagine any other scenario where it would matter for me aside from this one.

I have a question about desktop speed. I recently decided I'd had enough of having too fast a cursor in Diablo ii. Now, this runs in 800x600, 4:3, black bars at sides, scaled up to fill the screen. I use 400 dpi normally at 1920 x 1080. Converting this using monitor distance horizontal outputs 170 dpi as what I should set it to, but using monitor distance vertical outputs 220 dpi. The latter feels closer to being right, with the former feeling too slow. Now it could just be that I need to adjust, but does the conversion for horizontal match moving between the black bars (800) to moving across 1920? and is this why using vertical feels truer? Since it's filling the screen, moving top to bottom - 600 at 220 dpi should feel the same as moving top to bottom 1080 400 dpi, right? Which it kind of does, but not quite - but 225 dpi feels much faster. Also, does scaling 800x600 to fill the screen afffect the calc? Sorry if any of this is like common sense Edit: Actually I think it might be that I prefer the equivalent of 450dpi for 2D at that aspect and res - which is 250 dpi - feels fast but not too fast. I think I was doing the calc correctly and it's just a comfort thing for that particular game. Weigh in if you want though - might be something I didn't factor in.

Hi. Are these settings the same for Death of the Outsider? It uses the Void engine. Update: Using my mere mortal cfg. file skills and puny human senses I have determined the answer to this question to be yes. The calculations for Dishonored 2 feel the same for Death of the Outsider. This is no surprise really, since upon launching it I could immediately tell it was a glorified expansion for DH2. My apologies if you were actually looking into this.

Would conversions for this game also work with Unreal Gold? - since that doesn't seem to be included in the list of supported games. I think it's the same engine but it might be a different multiplier or soemthing?

Hi just fyi, the same mouse sens console command works in Hard Reset Redux too, however the FOV command in redux is just r_fov instead of r_gameplay_fov regards

Hi. Consider adding Revulsion? https://store.steampowered.com/app/719180/Revulsion/ At your leisure - it was only just released today I think.

Brill. Thanks. Keep up the good work. This is literally the only site I've ever subbed to. So unique but so needed. Cheers.