Skip to content
ConfigHub.gg

faveN vs blameF

9 differences across 13 published values.

Crosshair

faveN · 1280×960 stretched

blameF · 1280×960 stretched

Settings

Settings for faveN and blameF
RankVRS #25VRS #25
DPI400400
Sensitivity2.12
eDPI840800
Resolution1280x960 stretched1280x960 stretched
Crosshair
CSGO-ySVJd-Fb5Fz-A2sJA-eJLXS-KWLoD
CSGO-OComx-ewftc-UrLZC-JDPjx-Pd74E
Viewmodelviewmodel_fov 68; viewmodel_offset_x 2.500000; viewmodel_offset_y 0; viewmodel_offset_z -2; viewmodel_presetpos 4—

Gear

Gear for faveN and blameF
Mouse
Logitech G Pro WirelessAmazon
Zowie EC2Amazon
Keyboard
Corsair Gaming K70 RGB TKLAmazon
Corsair K70Amazon
Monitor
Zowie XL2546Amazon
Zowie XL2540Amazon
Headset
HyperX Cloud II WirelessAmazon
HyperX Cloud IIAmazon
Mousepad
SteelSeries QcK HeavyAmazon
Logitech G640Amazon

Profile

Profile for faveN and blameF
TeamBIGBIG
RoleRiflerLurk, IGL

9 differences across 13 published values.

As an Amazon Associate, ConfigHub.gg earns from qualifying purchases.

faveN vs blameF head-to-head setup breakdown

On the competitive ladder in Counter-Strike 2, faveN (BIG) is VRS #25 worldwide, while blameF (BIG) is VRS #25 worldwide.

Comparing effective sensitivity in Counter-Strike 2, faveN plays at 840 eDPI (49.5 cm/360°) while blameF runs 800 eDPI (52.0 cm/360°). That makes faveN's setup 5% faster than blameF's, requiring less horizontal desk sweep for entry flicks while blameF's lower eDPI trades turn speed for wider micro-adjustment margin.

For display output, faveN uses 1280×960 stretched whereas blameF uses 1280×960 stretched. On the hardware side, faveN competes with the Logitech G Pro Wireless and blameF uses the Zowie EC2.