| |
Any updates about the XP version of DXtweak... it's been awhile...
| |
After I posted my last reply about Deadzone in win XP, I came upon this topic. Is the LWTWEAK utility for windows XP available yet ?
| |
Thanks for the reply Aidan... I'll check back for a beta then :)
| |
Stanc, we have some beta version of the LWTWEAK utility available now ... but we still have some things to figure out before posting a beta.
Also remember if a game is applying a deadzone then any such tweak utility would not help.
If the changes were easy (or even documented by MS) then DXTWEAK for WinXP would already exist :-)
There is no workaround that we know of with changing system file versions.
When will it be ready ? Hard to say because Roland is working on it only a little "part time" amongst a number of other things.
| |
I came across this in RAS... can someone provide more detailed info if I can change something here to kill deadzone?
Open regedit and click yourself to the following key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\MediaResources\joystick\
Find the value "JoystickUserValues" and edit the six last DWORDs to adjust
the deadzone. There is a link below to a GIF to show you the values to edit
for each axis (specified as a percentage). Only X & Y is handled by the
system driver, and the deadzone is valid for all controllers connected to
the computer. Remember that the data is in hex format, so after 09 you have
to type 0A, 0B etc...
| |
Could you advise on a time frame for the release of the XP version of DXtweak? Like say, by the end of the year? Or Q2??? Using that seems to have helped quite a lot of Win9x folks kill deadzone and linearity problems, so I'm hopeful it'd work for me too. Besides, I'm sure you'd want to get this popular tool working for XP soon..
I'm under the impression that it worked well for Win2K, not under DX8.1 for XP? Or is there any other way of getting DXtweak to work? By using an earlier dinput.dll or something?
Thanks again
| |
Stanc, can you please pass this feedback on to EA ? We'll do the same at this end.
I'm glad to you figured out to use POSWDM. It is a great way to do an independant check of functionality outside of a game.
We are working on a DXTWEAK replacement for WinXP. However, even such a utility should be impacted by any game decision to impose a deadzone.
| |
Just some other observations:
After checking with POSWDM.exe, I can confirm that there is almost no deadzone as viewed by windows/directx... It's just in-game that the deadzone kicks in.. and it's for both pedals as well... despite deadzone being set to 0 in-game AND in the *.PLR file
BTW, can anyone can DXTweak to work with WinXP??? Then I could try this fix :
http://dynamic2.gamespy.com/~hg/forums/showthread.php?s=&threadid=25808&highlight=solution
| |
I've observed a huge throttle deadzone in my LWFF after installing the latest 4.11c profiler for WinXP. It wasn't there with version 4.11!
It calibrates fine in the profiler itself, but once I'm in F1-2001 (already patched), I find the throttle only comes on when my pedal is halfway down... acting like a switch. If a fix for this isn't available (since ClrCalib, DXtweak etc don't work under XP?), can someone PLEASE tell me where I can D/L a previous build of 4.11 or even 4.10 from??? (Why oh why couldn't a different file name be used for 4.11c...)
Thanks for any help you may be able to provide