By Anonymous on Tuesday, July 19, 2005 - 08:57 am:

could be a memory issue. the profiler is known to be a mem hog.

i've run into weird things with the signed driver too. the wheel itself never fails to work but the degree of rotation becomes unaccuate. i use a 310 degree in pretty much ever game so i nuke the profiler as it's not needed (and a RAM hog). when it's working correctly i can set the CP driver setting to 310 and i get the 'soft stops'. works great. but sometimes (seems random) the wheel while require me to readjust the CP settings to like 640 or up to 700 to get the same (actual) 310 rotation. the soft stops are the actual 640 or 700 rotation but the wheel responds to the 310 or so in the illustration in the CP app. wierd huh?

By FerryFast on Monday, May 2, 2005 - 01:59 pm:

Hi there,

I seem to have a problem with the 4.60 signed profiler. I want to set the amount of rotation of the DFP. For example in richards burns rally I use 540 degree, in GTR I use 480 and in LFS I use currently 900. When I use the profiler to set the degree automatic I get bad responses of the wheel , when compared to the wheel on the screen it seems to turn with little shocks. When I shut down the profiler its gone !

By Mark Alan on Wednesday, April 27, 2005 - 03:51 pm:

Maybe a little late for this post, but... .

I still have the Momo Racing (Blk), but connected a set of pedals from my old $25 MS Sidewinder NonFF:). I wont say anything bad about the Momo pedals, but the old work great(why better pots too). Oh, had to join the Logi Sub-D connector to the phone-jack type used by MS. ID's and cross-referenced the wires an sodered phone jack pigtail to the Momo serial.

During the journey here's what I learned (simplified) see link below:

The system has to make 65535 counts per 55ms prior to sending the signal to port 558. 201 also used. ("0" and "1" onoff) That happens to coincide with the 0-65535 usable ports where 0-1023 is controlled by IANA. 1024-49151 registered ports and 49152 through 65535 dynamic open I guess. Papyrus/Sierra Server Port, coincidently are 32766, 32767 and 32768 -read the readme.txt for server in game folder. hummm

Seems, to get to the higher resolution, the post from another member is correct - has to be just a multiple or more signals per rotation. Take the 16384 value: its 1/2 of 32767 or 32768 and X4 is 65535. See our real center for the Black model I think is 511.5, why I do not know exactly, but using DXTweak2, you can correct values to even up range and ensure break and throttle do not interfere and from another suggestion not take the pedals to the stops hard. I adjusted so the upper range divided by 2 equals 127 not 128 and (1, 511 1023 for wheel 2, 127, 257 for both accel and break)

Still working on but what troubles me is interrupts to the ports during the "breaks" according to the link below, are vunerabilities. And, when interrupted, I feel is when you loose the calibration - Serial Ports I guess are always on and through the unused pin 8 and MIDI 12 is it you have a possible doorway.

This not substantiated but useful information.

http://www.epanorama.net/documents/joystick/pc_joystick.html


Mark

By IronFly on Friday, April 15, 2005 - 02:43 am:

i found 2 bugs in this new 4.60 beta release.

1) at random time the pedals stops to work completly , you need to recalibrate to make it ok.
2)sometimes the wheel, at boot time (win XP SP2 home), doesn't run auto calibration and the 2 green led stay off.

with older 4.60 beta all run perfectly.

By richardcostello on Wednesday, April 13, 2005 - 03:53 pm:

beta is beta, if you cant stand the heat dont jump in the fire (ball) :)

By tom on Tuesday, April 12, 2005 - 09:47 pm:

Fireball, I sent you an e-mail yesterday with some details.

As for software not doing what it's supposed to, that's exactly the statement on the top of the page with the betas:

---

Quote:

Warning:
This is beta software. It might do what you want, it might not. Don't bother customer support with problems, rather, let us know.

---

By Fireball on Tuesday, April 12, 2005 - 08:23 pm:

Just so long as you understand that I don't appreciate you getting your "bug report" at the expense of my windows installation because that's what it cost, Tom! I believe this is a whole different matter than, "It might do what you want, it might not." Now my video card is refusing to accept any kind of driver without texture corruption present. I've just reformatted my system two weeks ago and am now forced to do it all over again! At the very least one would think that any new driver version you guys would come out with would have the same level of compatibility as the previous one. I'm very fortunate that I'm a person who is equipped to deal with these types of problems, HUGE inconvenience notwithstanding!!!!!!!!!

By tom on Monday, April 11, 2005 - 02:46 pm:

Thanks for the bug report. It is indeed a bug and I can reproduce it. I'll keep you updated...

By Fireball on Monday, April 11, 2005 - 05:48 am:

Tom,
Yes, I did indeed have the 4.60 beta installed on my system before I installed the new driver and I was running it without incident other than the fact that it was a huge pain to install correctly. I was able to tell from the error report that was created after I had my issue that the problem was between the video card driver and the wingman driver but I didn't try to boot without the wheel attached so I don't know whether or not it booted correctly without the wheel plugged in. I've learned not to unplug it because it always causes problems when I do. My system specs:
Windows XP Home
Intel P4 1.80 GHz
768 MB RAM
ATI Radeon 9600 SE 128MB

By tom on Sunday, April 10, 2005 - 07:27 pm:

Sorry to hear about your problems. A few questions:

- what is the history? Did you have the beta 4.60 driver installed before? Or an older driver version? Did you experience any problems then?

- how did you find there was a conflict between video and wheel driver?

- when you were in the state of bluescreening, did it boot correctly without the wheel attached?

- what OS version are you running?

We run a variety of tests in a variety of hardware environments (including ATI display adapters) and haven't seen anything like what you describe before...

As for your question, the 64 bit version refuses to install on the 32 bit OS, and vice versa.

By Fireball on Sunday, April 10, 2005 - 06:40 pm:

Tom,
I'd just like to tell you that this new 4.60 driver package is absolute JUNK! I'm lucky to even have a computer working where I can get online after installing that wretched thing. I've worked on my machine now for seven hours since you guys' driver package trashed it and I'm still hoping I won't have to reformat. All I had hoped was for the new driver to power my driving force pro without having to recalibrate my wheel after EVERY reboot. I also thought this driver package would be more reliable. I mean, you guys are touting windows logo certification and drivers don't get that designation without being thoroughly tested, right? My advice to anyone thinking about installing this driver package is: DON'T DO IT!!!!!!!!!
When I initially installed it and rebooted, after my machine checked the BIOS the wheel calibrated itself. Then I got a blue screen flash, the computer checked the BIOS again and the wheel calibrated again. Once my system had loaded up, I got a "your system has recovered from a serious error" message. I rebooted and the same thing happened so I uninstalled the driver package and reinstalled it again. The same thing happened all over again.
This time, after the error message appeared, I got on line and sent it to Microsoft. Now, I'm no geek like you guys and don't know a whole lot about what all this technical mumbo-jumbo means, but any idiot could see from the error report that the problem was caused by a conflict between the wingman drivers and the display drivers on my system!
I have an ATI 9600SE. I didn't have the latest version of the Omega drivers on my system, I had the one before it. I uninstalled the Omega and left the wingman software on. When I booted back up, no problem. I scanned windows and tried reinstalling the Omega. When I booted back up, same problem so I uninstalled the Omega and downloaded the newer version thinking that might solve my problem. NOPE! Same problem with the newer version. I figured the third time was the charm so I tried installing the ATI Catalyst Version 5.3 as a last result. How could I go wrong? I figured any problem the wingman junk had with the Omegas it surely wouldn't have with the official ATI driver.
Wrong again! It didn't like the ATI driver package either and I got the same message-"serious error."
Anyway, I took the wingman software off and I won't be putting it back on. The software is apparently defective. Do you think you guys might have gotten the links labeled wrong on the 32-bit and 64-bit versions? Something is messed up bad!!! If the links aren't mislabeled, these drivers are obviously poorly written and something needs to be done before another person has to go through what I've had to.
Fireball

By mike on Sunday, April 10, 2005 - 12:47 am:

Hi Tom,
Thanks for the excellent driver. I have 2 questions:
- I have been using your beta 4.60 (my system is Win XP SP1) and it never had to reinstall it because it's unsigned (and it never complained except the 1st very time). So should I remove this early beta and reinstall this signed version?

- Once in a while, I lost the brake pedal in the middle of a racing game and when I exited, I ran dxtweak and the brake pedal was intermittent. Is this a problem with driver or hardware? (Mine is a 3-week old brand new DFP)

Thank you.

-mike-

By Tom (Tom) on Friday, April 8, 2005 - 09:38 am:

Updated 4.60 release (with signed drivers!) is available here: http://www.wingmanteam.com/latest_software/beta_main.htm

(both 32 and 64 bit versions for those of you who run 64 bit machines)

By richardcostello on Monday, April 4, 2005 - 03:07 pm:

Thanks tom, sorted it now. It was in F1C, there is a game setup deadzone, used DFP alone before so it was device 1, now using old pedals and DFP so DFP = device 2 and I hadn't switched deadzone off for device 2!

Now all I need to do is butcher my old WMFF so the DFP has cable FF ;)

Thanks again

By tom on Monday, April 4, 2005 - 12:10 pm:

There's no deadzone that the driver puts in, unless you create a Profile that sets a non-zero deadzone. Where do you observe the deadzone? In the control panel or PosWDM, or in the game?

By richardcostello on Monday, April 4, 2005 - 09:14 am:

Thanks tom, got the wheel recognised correctly now and all cool EXCEPT I still have a big deadzone which I can't get rid of, any ideas? I didn't have this problem prior to installing 4.6? Cheers

By Anonymous on Sunday, April 3, 2005 - 05:19 pm:

Read this in this same thread, or wait until there's a signed driver for it.

By dino340 on Sunday, April 3, 2005 - 04:49 pm:

i have a gt4 steering wheel for ps2 and i want to put it on the coputer i have windows me and im just wondering what driver to download

By Anonymous on Wednesday, March 30, 2005 - 02:22 pm:

BTw on my momo force i had to uninstall all logitech HID devices (and all logitech devices except mouse) in device manager to get the pedals working in non-combined mode with the 4.60.
I had 4.50 installed before, and uninstalling/reinstalling made no difference.
Just a tip for those who get the same problem.

Floruro

By Fireball on Saturday, March 26, 2005 - 06:44 am:

Hey Tom,

I know you're the software guy so shoot me for asking, but I was wondering if you could tell me how to clean my DFP pedals so I can keep them working nicely and not void my warranty?

Thanks.
Fireball

http://soundsofsims.8.forumer.com/

By tom on Thursday, March 24, 2005 - 06:15 pm:

With the wheel plugged in, re-run the detection wizard (as described http://www.wingmanteam.com/discus/messages/4/3227.html#POST14548). After that, the wheel should go away and come back as Driving Force Pro.

Next time you unplug/replug or reboot, chances are good that it will revert back (and appear to stick) with DF. In that case, go to Device Manager, look for the "HID-compliant game controller" under the HID entries and do an Update Driver, "don't automatically select", "I will choose from list", and then select the Driving Force entry and confirm the warning about unsigned drivers.

After that ordeal, the wheel should go away and come back as DFPro and stay this way.

By richardcostello on Thursday, March 24, 2005 - 04:52 pm:

Thanks for 4.6 tom, my install dosn't pick up the DFP just DF i.e. 1024 resolution and I cant seem to get rid of what feels like a 5 degree deadzone! Tried everything with DXTweak2, any ideas?

By tom on Wednesday, March 23, 2005 - 01:26 am:

I'm a software guy so shoot me for wrong information :) The DFP wheel does have a ball bearing on the shaft, so it's closer in feel to the original MOMO rather than the MOMO Racing, at least as far as slop is concerned.

4.60 doesn't increase resolution for any device but DFP.

Pre-4.60, DFP was dealt with in "legacy mode" that makes it have to report like a regular DF wheel - and this includes having to emulate the regular resolution, 10 bit, of the regular DF (and incidentally also the old MOMO wheel). Once the 4.60 release is installed, it's kicked into its "unlocked" mode which is the full resolution that isn't bound by the compatibility to regular DF anymore. In this mode, you get 14 bit resolution on the wheel axis for DFP.

By Anonymous on Wednesday, March 23, 2005 - 12:01 am:

I have the Momo Force, great wheel with the 3 inch and 1 inch precision bearings on the main stering shaft! No slop in 4+ years

What type of bearing (or bushing) on the DFP wheel axis (not pedals)?


Also will this new v4.6 driver increase the Momo Force wheel resolution?

thanks :)

By tom on Monday, March 21, 2005 - 11:08 am:

As for the "unsigned driver" causing problems in online racing due to hacking checks: no, this is not a problem. "Unsigned" just means that the operating system is suspicious of installing these drivers. The application doesn't care exactly how the input comes into it, whether through standard or vendor-specific, signed or unsigned drivers.

Not sure what to say about your problem with DXTweak2...

By AL on Saturday, March 19, 2005 - 10:41 am:

HI, I recently installed this software, very pleased Thank you. But since it is not signed by microsoft, will this cause any problems? I race in a NR2003 league, if they run cheat dectecting software, will they think I am cheating because of unsigned programs? They might become suspicious this next race at atlanta when my tires out last everyone else's ;)

I also was wondering how to use dxtweak2 to achieve a super precise brake pedal? I usually just lower the sensitivity until the car performs the way I want on the track. What I am looking for is to be able to use only a very small amount of brake in the corner and do this smoothly. Oh and I do need to be able to stop the car for pitting too. Any suggestions for settings to try? I am new to dxtweak2, I did read the readme and now my brain hurts. HELP.

By tom on Friday, March 18, 2005 - 09:55 pm:

That sounds more reasonable ;)

By Mike on Friday, March 18, 2005 - 08:46 pm:

Hi Tom,
My bad! I have been looking at the wrong line in dxtweak2 all this time! This is what I got from dxtweak2:

throttle : 0-255
brake : 0-255
Wheel : 0-16383

So I'm all set.
Thank you, Tom, for an awesome driver! I appreciate it very much.
-Mike-

By Mike on Friday, March 18, 2005 - 03:21 pm:

Thank you, Tom. I appreciate your help.
I'm going to try it when I get home. Will keep you posted.
-Mike-

By tom on Friday, March 18, 2005 - 03:08 pm:

Try pulling the Saitek stick, just for kicks. You might also want to try with PosWDM (on the gadgets page) with "Calibration mode" enabled. That should give you the same 14 bit range.

I am at a loss as to how to explain 8 bit ranges...

By Mike on Friday, March 18, 2005 - 01:22 pm:

Hi Tom,
Thank you so much. It's because of your driver that I bought the DFP :-)

The 4.6 driver was installed properly as in the Control Panel->Game controller I was able to set the steering lock and it shown the picture of DFP and the wheel was also correctly identified as "Logitech Driving Force Pro". I have only 1 wheel installed (and a Saitek stick on #2). When in dxtweak2, I selected "steering" and moved the wheel from lock to lock and the "raw" data column shown 0 to 255. Is there anything else you couldn't thing off? (I had a Logitech Formula Force before I installed the DFP and before installing the DFP, I used "add/remove program" to remove the old Logitech driver (4.30) of my Formula Force GP, disconnect the GP, then run 4.60 installion and when I prompted me, I plugged in the DFP and finished the installation. I'm running Windows XP SP1).
-Mike-

By tom on Friday, March 18, 2005 - 01:14 pm:

---

Quote:

- reading some of the posts here, the DFP is supposed to output 14-bit resolution? I download dxtweak2 here and when I moved the wheel from lock to lock, dxtweak2 shown the raw data was frmo 0 to 255. What am I missing? Why didn't I see the higher resolution of the wheel?

---

---

Quote:

- Also, for ex, when I set my wheel to 540 degree, I did feel it stopped at 540. However, if I moved it a little more, it just kept movingto beyond 540 degree. Is this normal?

---

By Anonymous on Friday, March 18, 2005 - 01:04 pm:

Hi all,
After reading about the excellent 4.6 driver, I bought a Driving Force Pro and received it yesterday and I just absolutely love it. I have no problem installing and using the wheel. However, I have a question:

- reading some of the posts here, the DFP is supposed to output 14-bit resolution? I download dxtweak2 here and when I moved the wheel from lock to lock, dxtweak2 shown the raw data was frmo 0 to 255. What am I missing? Why didn't I see the higher resolution of the wheel?

- Also, for ex, when I set my wheel to 540 degree, I did feel it stopped at 540. However, if I moved it a little more, it just kept movingto beyond 540 degree. Is this normal?
Thank you very much in advance.
-Mike-

By Farts on Thursday, March 17, 2005 - 05:29 pm:

I have both the DFP and MS wheel in seperate USB ports at the same time, and use the pedals from the MS, and steering from the DFP. Reason.. the DFP pedals lose cal or just get super sensitive during racing for no reason whatsoever. I'll assume that same trouble will go away with signed drivers, but not fun when racing for points in an Online League :( I wired in the MS pedals RJ11 to the DB9 of the DFP, but the MS wont calibrate its full travel thru the DFP. No biggie cause it works great with both wheels plugged in.
Any fix for the plastic Rev.1 pots? Im not calling a toll line to ask for a replacement of a bad part. Seems to me, they should set up a way to easily get a replacement, just like automotive recalls. Have been reading this forum since buying the DFP around a week ago, lots of info here, whole lot more than the Corporate Logi site.

By HJZ on Thursday, March 17, 2005 - 11:41 am:

will these work fine even when using the dfp in combination with other pedals (connected to pc gameport)?

By Madness on Wednesday, March 16, 2005 - 11:31 pm:

ok i found in LFS i had to put the center reduction in lfs to 0.44 and Profiler on 900 deg just to make my wheel and game wheel look same deg of turning anyone know how to help me the old drivers where alot better and new drives i have to use the LFS center reduction stuff

By dontsimon on Saturday, February 26, 2005 - 05:29 am:

Ignore my stupid post. Just had a dig around inside the Logitech software and found specific settings I hadn't seen before.

DOH!

By dontsimon on Saturday, February 26, 2005 - 05:25 am:

Thanks :)

I see how the wheel auto calibrates, so do the pedals calibrate the first time you push them each time you use them at the start of each session?

Also, I did use dxtweak, not only for steering raios which now isn't necessary, but also for deadzones at each end of the brake travel. If there's even 1% of the brake sitting on it can slow you down. Not all games have deadzone settings. Does the auto calibration deal with this? I'd be happy to dump Dxtweak for good.

Oh, thanks once aain for the new drivers, you've made an okay wheel excellent.

:)

By tom on Friday, February 25, 2005 - 08:59 pm:

No, you can't because it's fully autocalibrated.

If you really feel the need to do so, you could always modify the calibration data with DXTweak2. Not recommended, but if you can't resist, hey, up to you ;)

By dontsimon on Friday, February 25, 2005 - 07:53 pm:

Can I no longer calibrate the wheel /pedals?

The option seems to have gone in the wheel control panel.

By Anonymous on Friday, February 25, 2005 - 07:01 am:

RESEASE FOR WINDOWS 2003 SERVER

4.40 WORK OK in W2003S
4.60 DONT WORK

I NEED DFPro PLEASEEEE!
thanks ;)

By Anonymous on Thursday, February 24, 2005 - 12:19 pm:

this drivers works on Windows 2003 Server Standar ?

in my windows 2003 dont work... = Driving Force USB

By dontsimon on Wednesday, February 23, 2005 - 07:21 pm:

Cool. Thanks :)

By tom on Wednesday, February 23, 2005 - 06:27 pm:

The resolution went from 10 bit (1024 counts) to 14 bit (16384 counts), as you noticed correctly.

The actual optical resolution depends on a few factors, but is above 9000 distinct counts. In order to actually be able to get 9000 counts, you need to switch to 900 degree mode and move the wheel reeeally slowly. Then, you should get single or double increments, depending where you are in the scaling. I have actually tested this by keeping track of distinct values while moving the wheel back and forth (automated) and have come up with numbers around 9600, if I remember right (it's been a while and was pre-production hardware at that point).

Even with 9000, you will get 10 counts per degree of motion in 900 degree mode. That's *a lot*, more than anything else I know.

By dontsimon on Wednesday, February 23, 2005 - 05:05 pm:

People are talking of an increase in resolution. Could this, and the exact figure, please be confirmed?

I noticed the number has changed from 0-1023 to 0-16383, but the numbers do not move one count at a time - often between 2-5 counts per step approx.

I checked this with Dxtweak.

Great drivers though, thanks team :)

By Anonymous on Wednesday, February 23, 2005 - 11:35 am:

OHHH, Don't work me... :(
Its Being recognosized how Logitech driving force USB not DRIVING FORCE PRO
in spanish please ;)

By Fireball on Tuesday, February 22, 2005 - 10:07 am:

I'm using this wheel in NR2003 and am using the full 900 degrees rotation. I just got the beta drivers installed this morning and turned a few laps. WOW! Kudos to you guys. This just might be the best wheel on the market! I'll turn a few more around TalladegaBR and get back to you on how it acts. I can't wait to play GT4! I'm going to pick it up this afternoon.

Fireball

By IronFly on Tuesday, February 22, 2005 - 05:29 am:

In nascar 2003 i use 360° thats i little bit more then the real steer but i feel like the rotation is 1:1 with the virtual steer.

just one thing TOM: is possible to put an option to disable the autocalibration of pedals?
We, Frex owners, have some problems with it, it's boring to do everytime we boot and maybe sometimes we are not so precise to push all the brake pedal.

Thanks.

PS: DFP beta drivers are incredible!!

By Anonymous on Monday, February 21, 2005 - 08:37 pm:

Anyone using this wheel in N2003? If so what are you running it at? Are you using the full 900 deg or you trimming it down a bit? Also what about the settings in XP and the profiler? Thanks!

By tom on Monday, February 21, 2005 - 08:25 pm:

Do you have the Bus Enumerator working? Does the separate pedals work in the control panel? (easiest test: press both and see whether the marks go to max (separate) or cancel each other out and stay at 0 (combined)).

As for the slider, you can (when selected) adjust it with your mouse wheel. Typing in a number would be possible, too. We'll take that as a suggestion ;)

By AxelRod on Monday, February 21, 2005 - 03:48 pm:

Great job on the new drivers Tom(Tom)!!! ;) The increased resolution is awesome!! Ive been waiting for these drivers since september!! The only thing i'd suggest is the ability to type in values (instead of trying to hit a mark with the slider).

I had one problem with LFS where the axis showed that i was using combined pedals (only one slider moves when either pedal pressed) So i exited, checked the settings in the Wprofiler, and they were set correctly (report combined checked off) went back into LFS and all was working correctly. Any suggestions?

By fcuttin on Monday, February 21, 2005 - 05:28 am:

In LFS the virtual steering wheel has a rotation of 720° (2 complete turns): so with your real wheel you would have the same for perfect results (you must rise the "maximum steer" setting up your car, anyway).

By Anonymous on Monday, February 21, 2005 - 01:16 am:

Hey winman guys. These drivers work perfect for me, the wheel is soooooo much better now, very happy i bought it. Keep up the good work!

By Arthur on Sunday, February 20, 2005 - 04:54 pm:

Thank you Aidan for your help. I am now able to use both pedals together! :)

By tom on Sunday, February 20, 2005 - 03:08 pm:

4.60 announcment: http://www.wingmanteam.com/discus/messages/4/3227.html?#POST14489 (sort of hidden away, I know...)

By Anonymous on Sunday, February 20, 2005 - 02:17 pm:

where can i get the beta profiler v460.319 chrs in advance

By exude on Sunday, February 20, 2005 - 01:59 pm:

Thanks for posting these new drivers Tom! Even for a beta they are working very well (except that I cant get keystroke/commands to work, but I couldnt with the older drivers either).
I love the artifical lock when limiting the degrees of rotation and the force feedback in general is definitely better.

By aidan on Sunday, February 20, 2005 - 01:49 pm:

If anyone is interested in versions of the beta other than english, or a 64-bit version (for anyone using WinXP 64-bit beta) please let us know. thanks.

By Anonymous on Sunday, February 20, 2005 - 01:47 pm:

If anyone is interested in versions of the beta other than english please let us know. thanks.

By Ubul on Sunday, February 20, 2005 - 01:26 pm:

I recommend using 540 degrees in Live for Speed, but with the new drivers I'm starting to get used to the whole 900 degrees. In game it is recommended to set center reduction to 0, in car setup steering lock to 45° and force feedback strength to 25%. Wingman profile should be default with separate pedals and 540°.

By disq on Sunday, February 20, 2005 - 01:24 pm:

ok incognito from rsc forums hooked me up, setting the wheel to 60% ffb and using 100%-0%-0%-disabled settings worked great. (in LFS)

By disq on Sunday, February 20, 2005 - 12:50 pm:

enabling centering spring and setting it to 0% seems to disable all forces now (except the soft-lock) so i had to set it to 5%.

also, ffb is a lot stronger. so, any recommended settings for live for speed?

By aidan on Sunday, February 20, 2005 - 12:08 pm:

anonymous, the wheel supports both split and combined pedals reporting. Take a look here for more details on these various modes
http://www.wingmanteam.com/files/documents/webfaqs/wmhelp/Product_Specific_Information/Combined_and_Separate_Pedals.htm

By aidan on Sunday, February 20, 2005 - 12:06 pm:

The drivers in the beta are unsigned. As you know unsigned drivers are somewhat of a problem in Windows, because Windows perfers to automatically install signed drivers.

For DFPro the process is somewhat more complicated. Without going in to boring details the wheel basically can operate as an old DF, or a DFPro...so that adds some complexity to the installation of unsigned drivers. Those issues should disappear after the drivers are signed.

You can avoid un-install,re-install by just manually running the 2nd part of the installation.

The "first part" of the gaming installation installtion basically copies the drivers to your systems. It is the "second" part that actually updates the drivers associated with devices. This can be run as standalone step as follows

- run cmd.exe
- cd "C:\Program Files\Common Files\Logitech\WMDrivers"
- rundll32.exe wmwizard.dll,WMWizardMain

By Anonymous on Sunday, February 20, 2005 - 10:12 am:

Is it hardware limitation that you can only use either gas or brake at the same time, but not both?

I just got my DFP yesterday and downloaded the new driver as well(Thanks Tom!), and while going through the setup and test..etc I noticed my input for gas or brake will only register if the other one is not being used at the same time.

I looked at the connection between the pedals and the steering wheel and remembered vaguely this was a limitation factor on the com port back in the DOS days, I didn't know this is still a factor?

Can anyone else confirm/deny this behavior?

I wouldn't even bother with this question couple of months ago except recently I've had good experience with modulating gas while braking to adjust the weight transfer in my real car on the track. That technique is also being used quite heavily in karting I believe.

Anyway, I'd appreciate if anyone else notices this as well.

Thanks.

By Ubul on Sunday, February 20, 2005 - 09:52 am:

Some of us on the LiveforSpeed forums have problems when the wheel is disconnected from the PC and reconnected again after a time, so Windows wants to install the wheel's drivers every time. This results in not being able to get extra functions like separate axis pedals or more than 180 degrees, unless the whole Wingman Software is reinstalled with the wheels drivers.
Any ideas how to tell Windows not to reinstall its own drivers every time I connect the wheel?

In the options of Wingman Software, when I modify the degrees setting with the good drivers, if the right side LED is off, pressing OK to the settings switches the wheel to clever mode. When windows finds and installs the driver by itself, this does not happen.

By disq on Sunday, February 20, 2005 - 08:22 am:

wow. finally. thanks a lot.

By taitai on Saturday, February 19, 2005 - 10:37 pm:

Damn! I can't set my range in radians. UPDATE UPDAAAAATE!

By tom on Saturday, February 19, 2005 - 10:59 am:

The link works, and I know of no other location (perhaps we should start a torrent? :). It's just that hordes of folks try to download it right now, and the server is choking a bit with that load. Just wait a bit and try again ;)

By buedi on Saturday, February 19, 2005 - 07:22 am:

Can someone post another Link to the Drivers? The original one seems to be messed up, because it leads to a 4.5kb File :-(

By Anonymous on Saturday, February 19, 2005 - 06:26 am:

Thanks Wingman Team for the new drivers, the new features are nice and the wheel now feels more presice when i'm playing GPL :)

However, the wheel still feel's the need to autocalibrate itself which is a bloody pain when you're trying to race close to somebody and you end up taking them off because of it:((

Would it be possible to post a patch to either disable autocalibrating as a per game feature or fix the problem once and for all.

Keep up the good work and i'm looking forward to the next release :)

By Anonymous on Saturday, February 19, 2005 - 04:50 am:

nice!

cheers

pez

By Tom (Tom) on Friday, February 18, 2005 - 06:57 pm:

---

Quote:

...everything.

---

By Bryan on Friday, February 18, 2005 - 06:51 pm:

"you can race your car on a tightrope made out of human hair now :)"

After having a go in my favorite motosport game (RBR) I can confirm this is true :D

Everything about the control, FFB, and feel is better...everything.

I don't know what to say...tom...I love you man (in a friendly way) :)

Now to go drive until my arms fall off.

By tom on Friday, February 18, 2005 - 06:44 pm:

Yes, you get the full resolution (and other things, like separate shifter and paddles, and proper forces) unlocked. This will give you a reported 16384 values on the wheel axis from lock to lock, with a realistic actual distinct value count of 9000 to 10000 (I forget the exact number).

Even if it's 9000, that means you get 10 counts per degree of rotation in 900 degree mode, and a ridiculous 45 counts per degree in 200 degree mode. This makes it a good bit more precise than anything we (or anyone else that I would be aware of) has done so far. In other words, you can race your car on a tightrope made out of human hair now :)

By Anonymous on Friday, February 18, 2005 - 06:38 pm:

Thank you Wingman Team! great great great! im so excited, cant wait till i can get home and try them. So these drivers make use of the full resolution now dont they?

By Tom (Tom) on Friday, February 18, 2005 - 06:15 pm:

And another note:

Q: "I'm having trouble getting Driving Force Pro working right. It shows up in the control panel, but forces don't work and adjusting the range has no effect"

A: There are many possibilities for this behavior. The most likely one right now is that the drivers are not signed, and the way DFP works is not very suitable to unsigned drivers. How to get it working nonetheless:

- install normally. If the above symptom occurs, follow the next steps.
- run the driver wizard again. See this FAQ entry for details

By Tom (Tom) on Friday, February 18, 2005 - 06:10 pm:

Apart from support for DFPro, there are a few other changes. One of them could come in handy if you use Profiler and use a lot of "keystrokes" (either single-key commands, or "hotkeys" such as "Shift-R"). There's a new concept called "Keystroke" which is like a "Command", but easier to deal with (less steps involved in creating, labelling and using them).

The main people interested in this feature would be folks who play first-person shooters with gamepads. However, others might find it useful as well.

There's not too much driver changes, a few minor things here and there but nothing that I would say is really useful or necessary for people with other wheels.

By Bryan on Friday, February 18, 2005 - 05:45 pm:

Thanks Tom! a dream has come true :D

By Anonymous on Friday, February 18, 2005 - 05:33 pm:

Does anyone know if theres anything is these 4.6 drivers that will benefit non-DFP users?

eg: MOMO Force

By marcocale on Friday, February 18, 2005 - 04:59 pm:

Great Job!!!! :)))

Only some problem detecting the pedals when I start the computer.
I'm forced to move the steering wheels, then accelerator and brake (in this order) for the full travel and the pedals are immediately detected.
If I try to move the pedals first, I cannot detect them.
The accelerator seems to be more problematic than the brake.
OK,
It's a beta so no problem! :))))

By Anonymous on Friday, February 18, 2005 - 01:20 pm:

Thanks Tom and the WingmanTeam.

It looks sweet so far. I haven't had time to test it in my games yet, but install was a breeze..

Many many thanks Tom for listening to our whiining ;-)

2re

By Anonymous on Friday, February 18, 2005 - 11:35 am:

Beautiful, I just got my DFP today. Lucky me that new drivers would be released.

By Vadi on Friday, February 18, 2005 - 11:20 am:

Great!

Works for me! :D

By IronFly on Friday, February 18, 2005 - 11:20 am:

AWESOME!!!!
Now the steering is much better and also the FF.
Thanks to all at WINGMAN TEAM!!!!

By Anonymous on Friday, February 18, 2005 - 10:12 am:

It Detects my Driving force pro as being the old Driving force....

By Anonymous on Friday, February 18, 2005 - 08:54 am:

Hi,


i can´t get it work under XP.After half o installation he says can´t find logo!"logo test not...! for Windows.

Anyone had the same Problem?

I´m from Germany,so can´t find the right words at the moment!


cheers

By Gabkicks on Friday, February 18, 2005 - 07:27 am:

For some reason, the degree scale does not show up in the global settings. It thinks my DFP is the old driving force. Also, how do you guys have your Force feedback set up for LFS with these new drivers?

By Frankalexandre on Friday, February 18, 2005 - 07:11 am:

Nice drivers guys! Force-feedback much better in GPL. The wheel rotation feature is great.

By Rich_A on Friday, February 18, 2005 - 04:55 am:

Thanks Tom:)

Hehehe can't wait to try them. I've been using 4.2 which were better FFB wise than 4.4 but now with totally customizable steering lock I am slightly extatic to say the least:D By far the best wheel on the market..

By Smokey on Friday, February 18, 2005 - 02:26 am:

Well Tom, they work alot better. I tryed it out with Live for Speed, and there is just something about it that makes it feel so much better. Props on this, man. I hear it makes GTR's force feedback even better too. I guess it picks up even more things it didn't use to. I'll try it later and see what it's like.

By Tom (Tom) on Friday, February 18, 2005 - 12:18 am:

That's right, I wrote it so if it doesn't work blame me ;)

As stated in my message below, it's beta, we don't have all the various languages yet, there might be some gotchas as it's not fully qualified yet (besides the DFPro there's also other changes, such as a really nice and simple way do do "keystrokes" (aka simple macros) with Profiler now, which is more flexible and easier to deal with than it used to be before.

If you find things that are wrong, it'd be nice to hear from you (I guess "suggestions@wingmanteam.com" would be a good place to drop feedback). We appreciate your comments.

By Anonymous on Thursday, February 17, 2005 - 11:26 pm:

Tom is part of the Wingman team. He didn't find them, he made them ;)

By Florian on Thursday, February 17, 2005 - 11:24 pm:

He didn't find it, I guess he did programm it ;)

By Smokey on Thursday, February 17, 2005 - 11:16 pm:

OMG thank you. Where exactly did you find these at? Logitech has no drivers at all on their site for the DFP.

By Jack57 on Thursday, February 17, 2005 - 10:08 pm:

First impressions are very favorable :))

I've only tried Richard Burns Rally so far, but Force Feedback feels much better - particulalrly in regard to suspension loading and traction.

Love the wheel rotation setting - so now we can dispense with DXTweak (at least for that purpose).

Thanx for your continued interest Tom :)

By Jack57 on Thursday, February 17, 2005 - 09:32 pm:

/me faints [thud]

By Tom (Tom) on Thursday, February 17, 2005 - 05:59 pm:

Splat, there it is.

Next stop, official release notes sometime somewhere on the beta.

So much for now:
- not signed
- beta, might mangle your system
- unsupported
- might not work right or have unexpected behavior

Have at it :)

By Jack57 on Thursday, February 17, 2005 - 12:57 pm:

Here I am, waiting at the station with ticket in hand :))

By Anonymous on Thursday, February 17, 2005 - 11:55 am:

Let us do the beta testing.. Hand it over please.

By Anonymous on Thursday, February 17, 2005 - 04:03 am:

Please!!!!

Thanks.