Okay!
Sorry for not getting around to this sooner. After reviewing the problems listed by forum members, and looking at the menus in-game, I used some troubleshooting and came up with some fixes, some script workarounds, and some useful information.
Click this link and unzip the config folders into your AC 1.1.0.0 config folder, replacing the old ones.
http://baconbukz.co.cc/up/uploads/AC_110..._fixes.zip
Now stop saying 1.1 is full of bugs and glitches and old people's teeth or whatever you've been saying.
____________________________FIXES____________________________
- Crosshairs menu typo fixed (thanks Gibstick)
- Voicecom: voicecomver alias and menuitem commented out (voicecom menu version should be edited in cfg file directly)... Sorry, Gibby... It is really nifty and I can almost get it to work, but saved.cfg is executed before the menu cfg files, and this makes it impossible for the menu files to read any saved aliases...
- Voicecom: Extra voicecom registersound indices accounted for in mute menu
- Misc menu: (applecake) Misc settings unknown command fixed (it was treating [ ] ("alias voicecomver [ ]") as a command).
- in-game menu: (Apollo{TyD}) playermodel being shown on unexpected menu hovers fixed.
- jamz, JGAN, and pwnage{TyD}: loading an empty map in single player has been fixed ("callvote 7" starts in packages directory by default now). ***flowtron is committing a fix to this. When you next update AssaultCube, you'll want this to go back to default.
- mykegregory and RandumKiwi: "bilinear 0" has been removed from menus_settings.cfg to avoid pixellation of textures.
______________________AUTOEXEC SOLUTIONS______________________
- Panda: put voicecomsounds 0 in autoexec.cfg -- it isn't one of the variables examined and passed on by writecfg. But yes, hearing your own voicecoms when this is 0 is a bug.
- Matasar: Until the devs change the default gamma (currently 100), you may want to put gamma 200 in your autoexec.
- Chill: put in your autoexec.cfg file.
- Matasar: No, weapon switching cannot happen unless a button is being pressed.
or however you used the other one. Now you have to click again to change weapons when your ammo is out. Just a tiny bit slower that way.
- |BC|Wolf: to have the minimap look like it did in 1.0.4, put in autoexec.cfg: This will also make it look that way:
- LeeZH: Clan tags using brackets will need to be placed in autoexec.cfg to work around the limited methods of saved.cfg's automated script writing. But you're right, the devs could fix this in the source code.
- IAF|@cid: Try putting your "showscores 1" bind in autoexec.cfg instead of typing it in the command prompt in-game.
__________________________INFO______________________________
- Coma: has your "option" button worked for other keybinds before? Does binding your scope command to another key work?
- Ducksong: in-game, type /findsens and use the number keys to figure out what sensitivity you prefer.
- Ducksong: Were you trying to open an official or otherwise "secure" map for coop editing? You shouldn't edit those anyway!
- |BC|Wolf: When using texreduce -1, the game checks to see how reduced the texture can become. Some textures can't compress in that special way and so are left alone. From texture.cpp:
- Lumpaz: From looking at the code, you'd think nades would go over shoulders. But trying it on bots, it bounces off the air above the shoulders. :/
- Mael: getdemo 1 review\blacklist; getdemo 2 fun\matches (you'll need to have the subfolders in demos\ made before using them in-game.)
- jAcKrOcK: I can't reproduce your bug (hearing a voicecom when using the knife). You said you use Mac?
- 1.0.4 vs. 1.1 config files sharing same directory: Just uninstall 1.0.4 and put all the important files aside.
- Buckoman: regarding the kick/ban menu:
- |BC|Wolf: I'll fix the documentation for scopefov (max is 60, not 50) in the 1.1 docs when I do those.
- Luc@s: blood and scorch seem to enable, but they don't show up on heightfields. GeneralDisarray might know the variables that govern this (probably polygonoffsetfactor and polygonoffsetunits -- but I can't find any useful values).
- saved.cfg is executed first, then autoexec.cfg is executed. The menu config files are executed before either of these.
Sorry for not getting around to this sooner. After reviewing the problems listed by forum members, and looking at the menus in-game, I used some troubleshooting and came up with some fixes, some script workarounds, and some useful information.
Click this link and unzip the config folders into your AC 1.1.0.0 config folder, replacing the old ones.
http://baconbukz.co.cc/up/uploads/AC_110..._fixes.zip
Now stop saying 1.1 is full of bugs and glitches and old people's teeth or whatever you've been saying.
____________________________FIXES____________________________
- Crosshairs menu typo fixed (thanks Gibstick)
- Voicecom: voicecomver alias and menuitem commented out (voicecom menu version should be edited in cfg file directly)... Sorry, Gibby... It is really nifty and I can almost get it to work, but saved.cfg is executed before the menu cfg files, and this makes it impossible for the menu files to read any saved aliases...
- Voicecom: Extra voicecom registersound indices accounted for in mute menu
- Misc menu: (applecake) Misc settings unknown command fixed (it was treating [ ] ("alias voicecomver [ ]") as a command).
- in-game menu: (Apollo{TyD}) playermodel being shown on unexpected menu hovers fixed.
- jamz, JGAN, and pwnage{TyD}: loading an empty map in single player has been fixed ("callvote 7" starts in packages directory by default now). ***flowtron is committing a fix to this. When you next update AssaultCube, you'll want this to go back to default.
- mykegregory and RandumKiwi: "bilinear 0" has been removed from menus_settings.cfg to avoid pixellation of textures.
______________________AUTOEXEC SOLUTIONS______________________
- Panda: put voicecomsounds 0 in autoexec.cfg -- it isn't one of the variables examined and passed on by writecfg. But yes, hearing your own voicecoms when this is 0 is a bug.
- Matasar: Until the devs change the default gamma (currently 100), you may want to put gamma 200 in your autoexec.
- Chill: put
[SELECT ALL] Code:
setfont v104
- Matasar: No, weapon switching cannot happen unless a button is being pressed.
[SELECT ALL] Code:
alias checkattack [if (= (magcontent (curweapon)) 0) [if (= (magreserve (curweapon)) 0) [shiftweapon -1] [reload]] [attack]]
bind "MOUSE1" [checkattack]
- |BC|Wolf: to have the minimap look like it did in 1.0.4, put in autoexec.cfg:
[SELECT ALL] Code:
showmapbackdrop 0
[SELECT ALL] Code:
showmapbackdroptransparency 100
- LeeZH: Clan tags using brackets will need to be placed in autoexec.cfg to work around the limited methods of saved.cfg's automated script writing.
[SELECT ALL] Code:
name "[aCKa]Ki113R"
- IAF|@cid: Try putting your "showscores 1" bind in autoexec.cfg instead of typing it in the command prompt in-game.
__________________________INFO______________________________
- Coma: has your "option" button worked for other keybinds before? Does binding your scope command to another key work?
- Ducksong: in-game, type /findsens and use the number keys to figure out what sensitivity you prefer.
- Ducksong: Were you trying to open an official or otherwise "secure" map for coop editing? You shouldn't edit those anyway!
- |BC|Wolf: When using texreduce -1, the game checks to see how reduced the texture can become. Some textures can't compress in that special way and so are left alone. From texture.cpp:
[SELECT ALL] Code:
if(canreduce && texreduce)
{
if(texreduce==-1)
{
w = 2;
h = 2;
} ...
- Lumpaz: From looking at the code, you'd think nades would go over shoulders. But trying it on bots, it bounces off the air above the shoulders. :/
- Mael: getdemo 1 review\blacklist; getdemo 2 fun\matches (you'll need to have the subfolders in demos\ made before using them in-game.)
- jAcKrOcK: I can't reproduce your bug (hearing a voicecom when using the knife). You said you use Mac?
- 1.0.4 vs. 1.1 config files sharing same directory: Just uninstall 1.0.4 and put all the important files aside.
- Buckoman: regarding the kick/ban menu:
the Devs Wrote:// only noobish vote abusers use this, if you really want it, just uncomment
- |BC|Wolf: I'll fix the documentation for scopefov (max is 60, not 50) in the 1.1 docs when I do those.
- Luc@s: blood and scorch seem to enable, but they don't show up on heightfields. GeneralDisarray might know the variables that govern this (probably polygonoffsetfactor and polygonoffsetunits -- but I can't find any useful values).
- saved.cfg is executed first, then autoexec.cfg is executed. The menu config files are executed before either of these.