a more consistent algorithm that takes in the base fov and also the mouse sens at 90 with zoomsens 0 is a bit less than the base sens like 0.96 of it or something and I haven't heard any issues with it unless it seems to link with the sens bug.
but I use zsens 0 with my script so and I still experience the sens bug crap and also I didn't feel any difference beside the different sens values when I used zsens 1 before
or it could just be some guy trying to do thin shaft with with fov 130 and zfov 90 script and the feeling the mouse a shit ton slower than it was :E
also it seems fox uses zoomsen 1
and its apparent when he stopped using his old script because there was no +alias at the time because the sensitivity conversions per-weapon were rounded values from the zoomsens 1 algorithm
I'm glad I'm shit at maths otherwise I'd waste my time to verify if 1 is really better than 0 and probably switch to it even though it wouldn't make any difference :D
well that all depends on you base fov so if you use 90 as a base fov with your lg and you set fov 90 and zfov 90 then your sens will be the same while using fov 50 with zfov 90 for lg your sens would be tons higher
Ok, the lightbulb finally blinked : I remember those sens/accel stuff instead of +zoom aliases in fox's old cfg and back then I couldn't understand why he didn't scale the accel, it just feels so weird..
well it feels that way for me since I use zsens 0 but I think a new player would prefer it unscaled as it would probably be a bit more natural and I recall a post by CZM on it posting the way to scale it back and what not.
extract hidusbf.zip to some folder you never wanna see again
run dseo13b, enable test mode
restart
right click on hidusb.inf
run dseo13b, sign a system file
type in location of that hidusb folder eg: C:\Users\Bellend\DRIVER and then the location of the one proper for your OS,
for x64 use \DRIVER\AMD64\HIDUSBF.SYS, for x86 use \DRIVER\NXT86\HIDUSBF.SYS
restart
run setup.exe from hidusbf folder
select filter on device
select desired rate
click install service
close window
restart
run remove watermark for your desired OS
restart
i got win7 sp1 64 bit.
I was trying to use gid above (same as yours) , but only get usb port stop working (device managers fix it again), but no 500 hz :(
odd, i'm on the same os (7 ulti sp1 x64) and it works wonderfully.
you have to do these in this exact order, otherwise the usb stops functioning. also: restart means a full system reboot, just in case you were not doing that. also make sure you're running everything as admin.
e: right clicking on the inf, click install service
e2: you HAVE to stay in test mode, just in case you didnt know. going out of test mode causes the usb to lock up.
I have this text file. (worked on 2 win7 x64 pc's several times)
1. Download Driver Signature Enforcement Overrider from this link.
2. Download HIDUSBF
3. Run Driver Signature Enforcement Overrider and choose Enable Test Mode.
4. Extract HIDUSBF to some folder, right click on HIDUSBF.inf and choose Install.
5. Run Setup.exe from HIDUSBF’s folder, check the Filter on Device box and select
your desired sample rate.
6. Run Driver Signature Enforcement Overrider again, choose Sign a System file and insert
full path to the installed HIDUSBF.sys file (For example:
C:\Windows\System32\Drivers\HIDUSBF.sys).
7. Restart your computer and enjoy.
C:\Windows\system32\drivers\hidusbf.sys (<- just for quick copy&paste.)
Is there really any need to go into settings with it?
- Plug in
- 500hz
- Favorite sensitivity/fov/resolution
- Frag
Personally I used a 3.0 for a bit but now 1.1:
500 hz 6/11
90 fov
800x600
2.9 sens with no accel.
Works fine for me. Depending on the server and my connection I hit normally about 40% LG, fairly decent rails, movement and rockets are usually fine... Just set it 500/1000 hz, 6/11 and use whatever sens you use