I am having problems with the key assignment. It shows my VKB, X52 and Crosswinds, but it is operating weird. I looked in my WOFFKeys.xca and my Thrustmaster T16000m(see pic) is still showing in there. This is WOFF PE. Windows 10 64bit. I set the VKB up the first time I went in and everything worked like normal and all assigned buttons worked fine in sim. The problem is when I go back in to make key changes. 1. The editor is real slow to respond, like 20 seconds. 2. It only responds to commands, after having clicked in editor, I have to push the VKB trigger to get anything to happen 3. it is just not operating the way it usually does.
Should I delete the highlighted section in the pic, eliminating the Thrusmaster T16000? I no longer use it. Any help is appreciated.
Blade, I don't have much idea on the slowness - maybe something like a button is on and on "auto repeat" -it should show in the WOFFKeys program window if something is being pressed. If you have software for the controllers check if anything in there is set to do something like repeat a button.
Also make sure you do not run the WOFFKeys more than once at the same time.
Yes you can delete that section but also delete the </Device> line just below the bit you marked as that is part of that section too. Best to backup the file first. Make sure it saves as .xca not .txt
Also it may be worth checking the null zone on each of the controllers and expand it a little - could be something is twitchy.
Yes in the button column, long skinny up the middle column, is showing up constantly for all buttons. I will have to check it out. I bet it is one of the ministicks that is causing the problem. Thanks Pol.
OK the column should show buttons normally, and show their current state (usually "up"). If it says "down" or flickering up/down whatever then that may be it.
Deleting the T16000m has fixed most everything, but i have buttons programed to my X52 Throttle which are correct in the WOFFkeys file but do not function in game for some reason? They did function right after i programed them, but in the next mission they ceased working?
Not much idea on that one, strange how it would work then not. Maybe configure a couple of buttons again to test and save and retry. Perhaps the file is corrupt.
Is there a limit to how many buttons can be programmed or how many hat buttons can be programmed? It is a hat on my throttle that is having the problem. If I send the WOFFkeys file could you have a look at it please? Thanks for your help so far Sir.
Not sure what you mean by hat buttons, usually hat is just POV and you can't change that normally (maybe with controller software).
I have a Ravcore Javelin which is basically a VBK and I can program more than 8 buttons- I have about 10 plus the POV on there assigned. I think for more than 16 you may need software (although on mine there's a switch to toggle more buttons so it replaces previous ones). Maybe just try to get a few working first (not on hat though).
My Saitek x52 Pro has a Hat on the throttle that can be used as 4 buttons. My Vkb has 5 hats on the grip, 1 is like a mouse(game controller type), 1 controls the POV and 3 Hats that can be used as 5 buttons each. It seems to be working correctly now, but I think I am losing 3 of the 4 button assignments on the throttle Hat when I exit WOFF PE completely. When I restart I have to reassign those 3 buttons. Weird I know??? Can you please just give a quick look at my WOFFkeys file. I do not see anything that looks suspicious, but you would know better than I would. Thanks in advance Sir.
One more thing please. Is there a way for me to reduce the size of the sun in WOFF PE. It is just huge for some reason in the Winter months and I would like to have a go at it if I can. Is it possible through the suneffect.xml or is that dictated in the shaders? Thanks again Pol.
You may need software for some things to work, especially some POVs used as something else. I can't see much in the .xca except 15,16,17,18.19 buttons are not assigned, and 22 is in there twice although one is not assigned.
Maybe it's not being saved, when you assign in WOFF function bindings prog, make sure you save it, then go look at the .xca in C:\Users\<YOUR LOGON>\AppData\Roaming\OBD_Games\OBDWW1 Over Flanders Fields make sure it's changed? PE won't change that itself.
Otherwise something is changing on the system when you reboot to the hardware assignments somehow.
I flew last night and all of my button assignments were working correctly. It seems I have to make my VKB assignments first and then my X52 assignments last and then save them and then WOFF PE will hold the assignments. Thanks again for your help Pol.
Pol what does P4Use="y" refer to in the WOFFkeys file. My VKB stick has 128 buttons available(I am not trying to use128 buttons, probably less than 20 on the stick) and I think this is causing problems with WOFF PE. Some of the assignments still come and go, and I am trying to understand the logic in the WOFFkeys file. My saved profiles don't seem to save all of the modded key assignments, i.e in game setting Shift+E bound to a key never works on either stick. Anyway I am trying to figure it out. Is there anyway that you will add 128button support like TFS just did for CLOD? How many controllers and how many buttons per controller does WOFF PE, WOFF BH&HII and WOTR support?
Game is now unplayable as mutliple axis' are assigned control surfaces and I cannot change them off of a device because it freezes. For me it is my virpil CM3 throttle and VKB gunfighter 3 MCGpro.
Maybe configure the VBK with only it plugged in, save, (maybe backup the WOFFKeys.xca at that point in your C:\Users\<YOUR LOGON NAME>\AppData\Roaming\OBD_Games\OBDWW1 Over Flanders Fields folder), then plug the other in and configure that, save. I believe it's a 32 limit you can use.
In the device software you have to delete anything over 32 buttons. I did this on both the Virpil throttle and VKB stick and the lag issues and keybinding headaches went away. I saved a new profile for each just for woff. The device cannot have more than 32 buttons.