My csgo sensitivity is 1.91 pls help me convert to fortnite

My sensitivity is a 2.2. what is my sensitivity targeting in game ?

Just now, Zackrone7 said:

My sensitivity at csgo  is a 2.2. what is my sensitivity targeting in game (Fortnite)

 

 

Just now, Zackrone7 said:

 

 

Today a new update dropped on fortnite and I have the feeling that all the sens are changed again. Scoped ar and sniper are brand new for sure, but I think that the fov may be changed again

3 hours ago, big engine said:

Today a new update dropped on fortnite and I have the feeling that all the sens are changed again. Scoped ar and sniper are brand new for sure, but I think that the fov may be changed again

Yeah, a lot of people complained about the sensitivity changes on reddit.

Yeah I'm having issues with getting a comfortable sensitivity since the update. Not sure what it is exactly...

@DPI Wizard Will it be possible to re-add Targeting sensitivity (config, ingame) for Save the World ? as it's still using the same sensitivity as hipfire.

i think you forgot to add it back with Hipfire sensitivity when you separated PVP/PVE.

Thanks.

Edited October 26, 20178 yr by bebeto

42 minutes ago, DarkFaith said:

Yeah I'm having issues with getting a comfortable sensitivity since the update. Not sure what it is exactly...

I'll see what they changed a bit later today.

38 minutes ago, bebeto said:

@DPI Wizard Will it be possible to re-add Targeting sensitivity (config, ingame) for Save the World ? as it's still using the same sensitivity as hipfire.

i think you forgot to add it back with Hipfire sensitivity when you separated PVP/PVE.

Thanks.

Do you have the targeting option in Save the World now? I didn't have them last time I checked.

Just now, DPI Wizard said:

 

Do you have the targeting option in Save the World now? I didn't have them last time I checked.

No, it still use hipfire sensitivity. but before you separated BR/STW in the calculator, there was the option with 45 fov targeting sensitivity for save the world

Just now, bebeto said:

No, it still use hipfire sensitivity. but before you separated BR/STW in the calculator, there was the option with 45 fov targeting sensitivity for save the world

Aha, gotcha. I'll add it again. I removed it before I realized they split the sensitivity in the game modes.

4 hours ago, DPI Wizard said:

Aha, gotcha. I'll add it again. I removed it before I realized they split the sensitivity in the game modes.

Have you checked it? Epic made a reset on the sensitivity. Maybe that's the problem what everyone has and they just have to set it back.

 

EDIT: Now I'm feeling it too, something is off here, not sure what. But both scoped weapons are broken now.

Edited October 26, 20178 yr by Mixthat

Updated it now!

36 minutes ago, DPI Wizard said:

Updated it now!

I can't get some number for targeting. Get Calculated sensitivity too high no matter what I enter.

 

Also, are you sure about the sniper and scoped sensitivity? The results I get are the same as before but they reworked something.

Edited October 26, 20178 yr by Mixthat

10 hours ago, Mixthat said:

I can't get some number for targeting. Get Calculated sensitivity too high no matter what I enter.

Also, are you sure about the sniper and scoped sensitivity? The results I get are the same as before but they reworked something.

Fixed the targeting now. Sniper and scope should be the same as before, because they are relative to the hipfire sensitivity. But I'll do some more tests to verify.

3 hours ago, DPI Wizard said:

should be the same as before, because they are relative to the hipfire sensitivity. But I'll do some more tests to verify.

Sniper feels way too slow

4 hours ago, DPI Wizard said:

Fixed the targeting now. Sniper and scope should be the same as before, because they are relative to the hipfire sensitivity. But I'll do some more tests to verify.

When you have time,  please don't forget to put back targeting sens for STW.

Thanks

1 hour ago, bebeto said:

When you have time,  please don't forget to put back targeting sens for STW.

Thanks

Done!

2 hours ago, big engine said:

Sniper feels way too slow

Updated scopes, they make a but more sense now.

 

Hello, I am new here, I would like you to help me with a question, to this day this method is safe to use? I read by reddit that you can be banned for modifying the config.ini due to the battle eye implemented, someone who currently uses it and can give me an opinion, I would really appreciate it.

[/script/engine.localplayer]
AspectRatioAxisConstraint=AspectRatio_Mai

6 hours ago, MiracleShoot said:

 

Hello, I am new here, I would like you to help me with a question, to this day this method is safe to use? I read by reddit that you can be banned for modifying the config.ini due to the battle eye implemented, someone who currently uses it and can give me an opinion, I would really appreciate it.

[/script/engine.localplayer]
AspectRatioAxisConstraint=AspectRatio_Mai

That line doesn't work anymore

I'm trying to get my scoped senses in fortnite the same as the 1:1 on screen speed, like with the awp in csgo with "zoom_sensitivity_ratio_mouse 0.818933027098955175"(that number might be out of date I haven't played csgo in a while). Does anyone know how to do this in fortnite ? thanks for any help.

Edited November 5, 20178 yr by PixelDeath

9 minutes ago, PixelDeath said:

I'm trying to get my scoped senses in fortnite the same as the 1:1 on screen speed, like with the awp in csgo with "zoom_sensitivity_ratio_mouse 0.818933027098955175"(that number might be out of date I haven't played csgo in a while). Does anyone know how to do this in fortnite ? thanks for any help.

Convert using Monitor Distance 0%, that's the same as 1:1 and that number.

Anyone having trouble changing sensitivity in the config file? Every time I change it, even if I put it on read-only, after I hit ready, it automatically changes back to default (0.28) sensitivity.

As a CS player, until they fixed everything I'd advice you do the calc with your CS sens (in my case 1.88 400 dpi raw on) to fortnite (360 & ingame) and stick with that number it gives you for Ingame, they change the setting file a lot lately, and putting them read only seems to screw things over. For me it's 0.07 and I just slide it as Close to 0.07 before it swaps to 0.08 I can (because doing the calc with cs 1.90 instead of my 1.88 it will give me 0.08) and yes, it does feel like the small increments ingame, matter. I always open note++ (%LOCALAPPDATA%\FortniteGame\Saved\Config\WindowsClient) and make sure  bDisableMouseAcceleration=True and bShowGrass=False is as I write them here, save it, Then open then game. Put scoped and targeting to 95% ingame and you're About as close as you'll get. I do and have been paid to play CS and this is what I've chosed to live with, till they fix their sliders n shitt  it feels Almost as my cs scene and since the game is so fast paced, it doesn't seem to effect my muscle memory in CS.

Hope it helps everyone. and do feel free to ask/debunk me, because this annoys the hell out of me too that I just can't get a 1:1 calc and be done with it... but this is the best solution, as a "semi/pro" player I've come up with and I can hit my shots in both games, so. Try it. 

happy fraggin'!

 

And the recent changes to the Engine file fucked some of fps tweak settings too, for my rig; these are the best:

as a CSGO (semi/pro) I care more about seing people than a blurry pretty background. This seem to give me the most fps while still having a good looking game

 

(i7 6700k non oc'd atm, gtx 1070)

Edited November 12, 20178 yr by Traxilla

Currently there is no way to change the config file because it resets once you press the "ready" button. No idea why it's like this. There is no consistency now, the aim feels totally weird and not snappy at all. Is it worth playing this game if it's gonna mess up your muscle memory? I don't think so... Is there any way to raise the sensitivity so that u get that responsive feeling?

They updated the scoped sensitivity with the last patch. It needs to be adjusted again.

 

EDIT: Probably false alarm. tried it myself and it seems it's only for console.

Edited November 16, 20178 yr by Mixthat