FFXI/Ventrilo key overlap.

[Korremar]

Like a lot of other shells, our shell has a Vent server. I'd always used F12 for my PTT key, and never had any problem with it. Last night I finally got around to updating Windower from 3.3 to the most recent version, and now whenever I press F12 it targets a member of my alliance, which it never did before. F12's not set as a bind in Windower. I changed the PTT key for the night, but I'm used to F12's position; is there any way to have F12 -not- target an alliance member?

[Blabj]

I'm reasonably sure this is something added to the init.txt inside your windower folder/scripts.

However, another fix is to enable direct input on hotkey inside the ventrilo setup menu, or create a keybinding to enable transmit over ventrilo, I believe one of these two will gain complete control over the key and make it so it wont change your target in game.

[Mafai]

it is definately a default setting inside init.txt.

[Korremar]

I'm reasonably sure this is something added to the init.txt inside your windower folder/scripts.

I'd thought that at first as well, but I didn't see anything. I might just be retarded though, I'll post my init.txt.

Spoiler: show

//echo Init script loaded.

// *** THIRD PARTY APPLICATION SETTING ***
// This MUST be set to true to make use of applications that use WindowerHelper
// to send Keyboard Commands. If you do not use any applications that control your keyboard, then you
// do not need to set this to 1. If you do, you must set this to 1 to make use of those applications.

keyboard_allowmmf 0

//Set console variables
console_position 15 50
console_color 255 255 0 0
console_displayactivity 1
console_fadedelay 3500
console_chatopen 1
console_screendir screenshots

//Set game variables
game_forceambientlight 1
game_ambientlight 255 120 120 120
game_gamma 55
game_allowsetcursorpos 0
game_exittype 1
game_exitprompt 1
game_allowresize 0

//Set general variables
//showfps 1
// FPS Position - Use -75 1 to position it on the top right corner.
fps_position 5 5
//wait 5 seconds before auto loading plugins
wait 5

//Load plugins -- Remove the // from plugins you want to have autoloaded
// TParty : TP #'s beside party members names and HP% number on target
// Distance : Shows distance to current target
// ConsoleBG : Puts a background behind the console
// Recast : Shows Recast Timers for All Abilities and Spells
// LightLuggage : Auto stacks items entering inventory and has profile system for auto lot and pass
// Timestamp : Adds time stamps to all chat log messages
// Silence : Removes all 'Equipment Changed' messages from the chat log to reduce spam
// DrawDistance : Increases the drawing distance of the game farther than normal, creating an amazing scenery view of the game.
// Send //drawdistance set X once logged in where X is a number between 1-20 to increase. 1 = max game NORMALLY allows.
// Or press Alt+F10 to set to 5 and Ctrl+F10 to reset to 1
// SSOrganizer : Organizes all screenshots you take so you may easily find them.
// Logger : Logs all ingame chat to text files located inside of your Windower directory.
// StatusTimer : Displays timers on your buff icons on how long they will last.

load TParty
load Distance
load Recast
load LightLuggage
load TimeStamp
load DrawDistance
load SSOrganizer
load ConsoleBG
//load Logger
load StatusTimer
//load Silence
load Clock
load Infobar
load PlasticSurgeon



//Uncomment or add plugins you want to use


//Bind keys
//Bind syntax is "bind <key> <up> <command>
// ^ represents control- and ! is alt, eg !1 is alt-1
bind !f10 drawdistance set 5
bind ^f10 drawdistance set 1
bind f11 game_forceambientlight
bind sysrq screenshot png
bind ^v paste
echo Toggle Lighting = F11 (Bump mapping must be off to work properly)
echo DrawDistance Lv 5: Alt-F10
echo DrawDistance Lv 1: Ctrl-F10
echo Paste Clipboard = Ctrl-V

//Sets ConsoleBG Background Position
consolebg position 15 50

// *** ALLIANCE TARGET KEYS ***
// This lets you push Alt+F1-6 and Ctrl+F1-6 to to target Alliance members.
bind ^f1 input /ta <a10>
bind ^f2 input /ta <a11>
bind ^f3 input /ta <a12>
bind ^f4 input /ta <a13>
bind ^f5 input /ta <a14>
bind ^f6 input /ta <a15>
bind !f1 input /ta <a20>
bind !f2 input /ta <a21>
bind !f3 input /ta <a22>
bind !f4 input /ta <a23>
bind !f5 input /ta <a24>
bind !f6 input /ta <a25>

However, another fix is to enable direct input on hotkey inside the ventrilo setup menu, or create a keybinding to enable transmit over ventrilo, I believe one of these two will gain complete control over the key and make it so it wont change your target in game.

Thanks; I'll try that.

[Blabj]

Yeah it was the bottom I must have gotten myself confused with, I know they added something to do with alliance targetting in a recent windower version update, but wasn't sure exactly what!

[Korremar]

Seems I've already got the Direct Input to detect Hotkey checked. F12 targeting an alliance member ingame doesn't seem to be related to Windower apparently, as other people are saying F7-F12 target them. However it seems odd that I'd never once noticed it before I updated, since I've been in full alliances for Dyna/Sky plenty of times, which leads me to believe that for whatever reason it wasn't doing it before.

[Kohan]

F12, by default, does target the first member in one of your alliance parties. However, this is not a Windower bind, so anyone who stated they can do it without Windower is 100% correct. It's a native FFXI function that has been there since the beginning.

If Windower's F12 functionality is overriding the game's, it activates the FPS counter overlay in the upper left corner. Judging by your INIT file, this binding has been removed completely, which is why you're experiencing the targeting functionality instead.

Since you didn't experience any problems with this before, try re-binding to its old function within the INIT file. Under bindings, add:

bind f12 showfps

And see if it works with Vent again.

[Norellicus]

I'm more a fan of the pause/break key, myself, since it's never used for anything ever and also benefits from being distinctly positioned on just about any keyboard.

But then I also just use a headset with a quick-kill switch on it (sneezing and such), and leave vent in vox mode, so I haven't actually used PTT in a while.

[Kohan]

I'm more a fan of the pause/break key, myself, since it's never used for anything ever and also benefits from being distinctly positioned on just about any keyboard.

But then I also just use a headset with a quick-kill switch on it (sneezing and such), and leave vent in vox mode, so I haven't actually used PTT in a while.

I use NumLock, myself. My keyboard has a somewhat unconventional layout, so the Pause/Break key is in an awkward place. Because I use the WASD config, I don't use the NumPad within FFXI anyways. Thus, NumLock it is.

To me, F12 would be too far away from where my fingers ordinarily go, but whatever floats one's boat.

[Korremar]

You know, that might just be it. I removed the FPS bind last night right after I updated, because I have Infobar up there. That'll probably fix it.

Thanks a lot guys.