Unknown Scope Sens

[KN!F3]

I finally got the stupid scope problem that says scope range .001...1000 blah blah
unknown alias lookup: scopesensescale

Does anyone know how to fix this without resetting binds?

[Thorite]

look here http://forum.cubers.net/thread-65.html

[KN!F3]

I tried all but resetting my binds which I don't want to do. None of those worked. :\

[Thorite]

make a copy of saved.cfg then reset your binds and paste the saved binds that you kept into the new .cfg

[KN!F3]

blah I just reset all settings and am currently trying to repair my voice com binds. Thanks for your help anyways.

Peace, KN!F3

[DrauL]

I reset my binds and its still stuffed.

[Matasar]

Manually enter your scopesens in the same option as you set your sense.

[DrauL]

How do i set it?

[MathiasB]

Type

[SELECT ALL] Code:

/alias scopesens 0.5

[Carnifex]

What MathiasB said.
0.5 is default.

[Kirin]

[SELECT ALL] Code:

//Sniper Zoom Script made by Franz "Kirin" Al.
alias zoom [
    if (= $arg1 1) [
        push oldsens $sensitivity
        sensitivity (*f $oldsens (divf $scopefov $fov))
        setscope  1
    ] [
        setscope 0
        sensitivity $oldsens
        pop oldsens
    ]
]
alias altaction_4 [ zoom 1; onrelease [ zoom 0 ] ] // Sniper
bind "MOUSE2" [ if $editing [ showmenu editing ] [ altaction ] ]

this script fixes every possible problem you might have had with zooming
also it automatically calculates the sniper scoping sensitivity
for example if you use a sensitivity of 3 at fov 120
you'll probably like a sensitivity of 1.5 at fov 60
the script does this automatically

just put it at the end of autoexec.cfg which can be found in AC/config/

(also in AC 1.1 this problem is inexistent, it wont happen again)

[ech0]

http://forum.cubers.net/thread-65.html

[Bexlab]

very nice script Kirin..

[Bukz]

...blah I just reset all settings and am currently trying to repair my voice com binds...

[offtopic]

Protip: instead of binding keys and changing voicecoms in-game or with menus, I recommend keeping all your settings in the autoexec.cfg - this way, if you ever need to reset binds/settings or delete saved.cfg - you won't lose all your precious settings. :)

[/offtopic]

[V-Man]

Or even multiple .cfg files, for easier handling.
That way, if you want to exclude a particular script, you merely comment out one line of "exec", thus:

[SELECT ALL] Code:

exec config\dynamic.cfg
becomes
//exec config\dynamic.cfg

and the script is excluded from gameplay until you un-comment it back in!

[DrauL]

[SELECT ALL] Code:

//Sniper Zoom Script made by Franz "Kirin" Al.
alias zoom [
    if (= $arg1 1) [
        push oldsens $sensitivity
        sensitivity (*f $oldsens (divf $scopefov $fov))
        setscope  1
    ] [
        setscope 0
        sensitivity $oldsens
        pop oldsens
    ]
]
alias altaction_4 [ zoom 1; onrelease [ zoom 0 ] ] // Sniper
bind "MOUSE2" [ if $editing [ showmenu editing ] [ altaction ] ]

this script fixes every possible problem you might have had with zooming
also it automatically calculates the sniper scoping sensitivity
for example if you use a sensitivity of 3 at fov 120
you'll probably like a sensitivity of 1.5 at fov 60
the script does this automatically

just put it at the end of autoexec.cfg which can be found in AC/config/

(also in AC 1.1 this problem is inexistent, it wont happen again)

Will try that when i get ho0me Kirin. :D
Sounds good mate.

[#M|A#Wolf]

I did it and it fked up my scope. The zoom was way too much and it was just a pain since I couldn't change it. I could change the sensitivity and fov of the scope in the menu but it wouldn't change. Then as usual with every scope script, once I took it out of my autoexec it would still be there so I had to reset binds.

[Kirin]

if you read my script i didnt change scopefov so the problem you may have had come from some old script you used... mine didnt enforce scopefov...

[R4zor]

Apparently this can be easily fixed by going into settings > input.

[16:03] <DES|Inline> you fail
[16:03] <DES|Inline> i went to my settings
[16:03] <DES|Inline> and it had .0001 sens for my normal
[16:03] <R4zor> wtf
[16:03] <R4zor> LOL
[16:04] <DES|Inline> and $scopesens or some shit for my scope
[16:04] <R4zor> hahaha
[16:04] <R4zor> soo what did you do
[16:04] <DES|Inline> changed it back to 6 and .5
[16:04] <R4zor> yes thats obviously why you couldnt look around
[16:04] <DES|Inline> lol
[16:04] <R4zor> .. or you could, but VERY SLOWLY AHSUASHA
[16:04] <DES|Inline> well i could
[16:04] <R4zor> and is it fixed?
[16:04] <DES|Inline> yes
[16:04] <R4zor> jaj

[#M|A#Wolf]

R4zor: did that, didn't work.

[Inline]

Wolf you went to Settings > Input and then put a number in the scope sens? That's all I had to do to fix it.

[#M|A#Wolf]

I did that but it wouldn't change. I had to do the /resetbinds command. It always happens to me that when I put a script in the autoexec about something that affects a gun, removing it in the autoexec isn't enough.

[Gibstick]

For the future if anything ever messes up you will still have to look inside saved.cfg for the bad alias/script/setting.

[Huntsman]

Yeah every time I play 1.1 then go onto normal ac I hve to change my scope sens

[V-Man]

This is why I play 1.1 in its own little folder, all self-contained. Then it doesn't eff around with 1.0.4 settings.