New driver version 200 and CSW firmware 53 - UPDATE

edited July 2014 in Blog
-UPDATE-  Please connect your Fanatec devices and power on before you install the driver.


Time to upgrade your wheel. The new DRIVER brings a lot of new features and the new firmware for the ClubSport Wheel does not only support the new Universal Hub but also brings several improvements in the force feedback.

Driver v200 (for all Fanatec wheels):
  • Now shows the
    firmware version of our wheels (CSW, CSRE, CSR, GT3V2, GT2, PWTS) in the
    “update” tab of your device.
  • The driver can carry a
    new firmware for the CSW directly and the updater for the CSW is included as
    well. It will start automatically if you set the CSW into bootloader mode.
  • Automatic detection if the your CSW has an older firmware installed than the one which is
    included in the driver.
  • New firmware for CSW
    (V53) included!
  • The driver also
    contains both firmwares for the CS USB Adapter and asks you which mode you want
    to use (handbrake or shifter)


  • In the update tab you
    can start the FW updater to change the firmware from handbrake to shifter and
    “vice versa”
  • Handbrake bar for CSP
    added (if handbrake is connected directly to the CSP)


New functions of firmware 053 for CSW (ClubSport Wheel Base):

  • Improved wheel centering after boot up
  • "Center bump issue" has been improved significantly. More improvements will have other negative side effects so this is the optimum.
  • New rims added
  • DPR, SPR and FOR max. settings are now set to 150 (%) to avoid overclocking

Download Driver v200 with CSW Firmware 053

32 Bit

64 Bit

Tagged:
«134

Comments

  • edited July 2014
    Link fixed.
  • edited July 2014
    The download link is broken and the link to the firmware is not available on the CSW downloads page yet.

    Edit: Ah just found the firmware update exe

    To all those who need help here's what to do:

    [EDIT by MOD: This instruction was leading to some problems. Therefore it is better not to follow it]

    2. Open zip and run msi file
    3. Install driver
    4. Go to the installation directory (default C:\Program Files (x86)\Fanatec\Fanatec Wheel)
    5. Open FwClubSportBaseUpdater
    6. Follow on screen intructions
    7. Enjoy the new driver and firmware 

    Edit: I have just had to manually set the center after installing the new firmware but now it is saved and center is correct at every start up. 

    To set the center: 
    1. While on press the tuning button 
    2. Centre the wheel 
    3. Press the 2 joystick buttons simultaneously 
    4. Exit tuning menu and restart CSW
  • So this driver also works for the CSR wheel?

    "Improved wheel centering after boot up"

    I hope this will be fixed also for the CSR wheel, i use FW756...
  • edited July 2014
    Completely forgot about the manual lol
  • edited July 2014

    Maybe pressing the center-knob of the "Playstation-Button" on top of the Hub together with pressing the "Funky-Wheel-Knob" causes the same Effect - but I can´t verify this - Hubs are still in delivery...

    The Link at the Download-Page (which works, btw.) offers a couple of Driver 200 with the Firmware 053. The Link above (which is broken) seems to offer a couple of Driver 200 with Firmware 057. Typo or infact two different choices?

  • Read the manual!
  • Are the new drivers fixing the button bindings on the CSR wheel that have been screwed up since the first CSRE/CSW wheel drivers?
  • Sorry for the confusion. Just fixed the broken link.
  • I've just updated, the firmware installed fine but the driver hasn't installed. I click on CSW properties and it's the generic Windows calibration, No one has mentioned it so am I doing something wrong, though I can't see how?
  • Richard - I've got the same problem.  Everything seemed to install OK and I've updated the firmware OK but no Fanatec driver control panel.  Using the 64bit version.
  • Fixed my problem by re-installing driver with the wheel switched on, I had it off the first time.
  • Since I have installed the new driver/firmware my clubsport shifter doesn't work properly anymore; it keeps mixing up 1st & 3rd gear... I did re-calibrate it correctly and several times, it just selects the wrong gear every third or fourth time, any suggestions?

    In the panel it shows 5th and 7th in the same spot (7th), but 5th gear works fine in-game...

    I'm driving iRacing on Win7 64bit with CSW Pedals and wheel.
  • Since I have installed the new driver/firmware my clubsport shifter doesn't work properly anymore; it keeps mixing up 1st & 3rd gear... I did re-calibrate it correctly and several times, it just selects the wrong gear every third or fourth time, any suggestions?

    In the panel it shows 5th and 7th in the same spot (7th), but 5th gear works fine in-game...

    I'm driving iRacing on Win7 64bit with CSW Pedals and wheel.

    The back where you plug your shifter into the club sport wheelbase try switching from the second shift plug to the first shift plug and recalibrated and it should work.
  • Looks like nice work, Thomas. Any word on bringing the "center bump" and other improvements in driving feel to the CSR Elite in one last firmware update?
  • Fixed my problem by re-installing driver with the wheel switched on, I had it off the first time.
    Thanks Stephen, I'll give that a try.
  • Edit: Ah just found the firmware update exe

    To all those who need help here's what to do:
    2. Open zip and run msi file
    3. Install driver
    4. Go to the installation directory (default C:\Program Files (x86)\Fanatec\Fanatec Wheel)
    5. Open FwClubSportBaseUpdater
    6. Follow on screen intructions
    7. Enjoy the new driver and firmware 

    Hi Stephen,

    thank you for your message. It is unnecessary to perform the update like this. Please just install the driver and it will tell you everything that is necessary to update the firmware. You will not have to search for the updater or anything like that.

    All the best,
    Armin
  • edited July 2014


    Hi, nach dem update habe ich kein FFB mehr "iRacing"

    Hat sich erledigt! Treiber und Firmware neu instlliert.
  • edited July 2014
    DPR, SPR and FOR max. settings are now set to 150 (%) to avoid overclocking

    Omg Thomas, what the hell is this ? Are you kidding ? This is clearly changing the specs of the wheel, which is not acceptable...

    You told us the ffb motors failures were due to a motors design flaw, and that there will be no more dead motors because this flaw was fixed, so why limiting FOR now, if not because the motors still die ? And how can even your customers not wonder if the engine flaw even existed now we see you have to take further measures to prevent motors failures ?

    How can you call this "overclocking" when this is a feature you designed ? The fact it was your designed feature means the ffb motors were meant to be robust enough to handle it without failing, which obviously seems not the case.

    Using FOR above 150 is NOT overclocking, it is using the wheel as it was designed and you have customers who bought those specs. Calling it overclocking now is trying to persuade people this was not normal use, which is false.

    It is nowhere mentionned FOR would be an overclocking feature, neither that it would be unsupported or subject to be limited at Fanatec discretion. This is what the video manual says: "FOR: is the ffb signals are too weak they can be amplified by 4 times by using a value higher than 100%". You can change the video now, because this is not true anymore as you just changed the specs and have limited a x4 amplification to a x1.5 amplification, more than 2x less than what the wheel was sold for...

    Overclocking means raising the power beyond the initial specs, which FOR won't do, and you know this. Even at FOR 400% you will still have the exact same peak force (FF 100). What limiting FOR will do on the other hand is limiting the average stress on the motors (and this is where Fanatec will save RMA costs).

    As racing game designers (esp. in sim world) design their ffb signal according to the (small) available force range (dynamic range) to allow brief peak ffb effects without saturation, limiting the FOR setting as you just have done is an indirect way to limit the ffb strengh (and I refer to something equivalent to lowering FF here).

    Because when a developper keeps room to be able to have brief peaks, this means 90% of the time the ffb effects will be weak (= as if running with a very low FF setting). And this is what the FOR setting was meant to adress. It was your feature allowing to make such a ffb to be stronger, as if the developper did not keep this room for unsaturated brief peaks, and you advertised the wheelbase with this !

    Using that feature was not making you using the wheel out of the specs. A given game ffb signal used with FOR 400 was possible to do the exactly same by the game developper if this was his design choice. So whatever we feed an amplified ffb signal (using FOR) or the exact same signal coming from a default game ffb, the wheel motors have to be designed to handle it.

    Limiting the FOR feature through a firmware update is just an aknowledgment from Fanatec this is not the case, IOW an acknowledgment the motors are not robust enough to deliver the ffb strength the wheelbase was designed for, and this not even talking about the FOR amplification feature, as a game could send the same ffb signal as an amplified one.

    So yes, I'm upset by this change, and by the fact nobody here yet seems worried by this limitation of the specs. Would you guys accept the 260 horsepower turbo car you just bought was limited to 170 the 1st time you go to the garage, because the manufacturer decided to limit the turbo to almost nothing because using the turbo at its full designed potential is now "considered overclocking" ?
  • edited July 2014
    The bug with the mouse settings not being applied after a system reboot with the wheel on is still present. It has been there in all released drivers since it has mouse emulation.

    I've sent Armin an e-mail about that when I first found it (when it was introduced in May last year, in one of the alpha versions) and also to Fanatec Support (in December) but never got a reply, so I don't know if that is a known situation.
  • @ António

    Thank you for your message. Please submit a support request with your problem description and documentation of the issue and mention that it should be forwarded to me. I did not get your previous message and I will take a look into it asap.

    Thank you very much!
  • @ Armin

    Does it have to be through support request or do you want me to e-mail you directly like I did when testing the drivers? It might be faster.

    I will start writing the text and then I can send it one way or the other.

    Regards
  • Since I have installed the new driver/firmware my clubsport shifter doesn't work properly anymore; it keeps mixing up 1st & 3rd gear... I did re-calibrate it correctly and several times, it just selects the wrong gear every third or fourth time, any suggestions?

    In the panel it shows 5th and 7th in the same spot (7th), but 5th gear works fine in-game...

    I'm driving iRacing on Win7 64bit with CSW Pedals and wheel.

    The back where you plug your shifter into the club sport wheelbase try switching from the second shift plug to the first shift plug and recalibrated and it should work.
    Thanks Tony! The shifter had always been in the first input before the update. I calibrated the shifter both ways yesterday, didn't work. But when I gave up yesterday night I left it in input #2. So today I re-calibrated it in input #1 again and now it seems to work, I drove 20 minutes without missing a gear! :-) I hope it stays that way. Maybe yet another restart of my computer repaired some issue, I don't know exactly why it seems to work now.

    Best Wishes and thanks!

    Fabian
  • edited July 2014
    DPR, SPR and FOR max. settings are now set to 150 (%) to avoid overclocking

    Omg Thomas, what the hell is this ? Are you kidding ? This is clearly changing the specs of the wheel, which is not acceptable...

    You told us the ffb motors failures were due to a motors design flaw, and that there will be no more dead motors because this flaw was fixed, so why limiting FOR now, if not because the motors still die ? 



    There seems to be something totally wrong with you. Generally
    maximum settings are 100 and this is how it was in the beginning and how it should be because of people like you. It was changed in later firmware update to overclock it over a hundred to give you something extra, because some games give weaker signals. So they still let you overclock it 1,5 times if you think game signals are too weak and this is something other manufacturers don't do as far as I know. (so, you should be thankful they offer more than others in that department). It was about time to lower this value, because some people, probably like you, think that if it is possible to turn up the force values 4 times than generally meant to be the maximum, it is OK to run so all the time. Of course it cooks up your motors faster.

    I don't see anywhere on CSW or Rims page, where it says that you can turn those settings up four times over the maximum. So, they are not changing any specs that were promised. They can change their firmware any way they want.

    Cars also let you change gears almost any way you want, but that doesn't mean that it is totally OK to change from sixth to first while driving like 250+ km/h or drive all they long with first gear revs in the limiter.
  • Hello all, does this update apply to using a PS3 ?
  • edited July 2014
    @John Lomax

    Obviously it was an overclocking function to make it work 4x higher than the normal usage, that's why it could be set up to 400(%). That is not a normal usage.

    With every game I tried, the motors were clipping well before the 400 if the game's FFB was set correctly, some even before the 200, so using it always at that settings didn't deliver any FFB other than a simple clipped force that countered turning the wheel.

    And FYI, there should have been something wrong with the motors or whatever before, as my first motors burned with me always being 100 or below and only after a month. It was one from the first batch. Now, it has been almost 2 years without any problem and the wheel is still running as good as new, even with extensive hours of usage and most of the time with the BMW rim.
  • edited July 2014
    Hello all, does this update apply to using a PS3 ?
    You don't need the drivers to use it with the PS3, but you will need the firmware update to use the new universal hub and will most certainly change the FFB feel you have with the PS3
  • > Marek Laul >  because some people, probably like you, think that if it is possible to turn up the force values 4 times than generally meant to be the maximum, it is OK to run so all the time. Of course it cooks up your motors faster. I don't see anywhere on CSW or Rims page, where it says that you can turn those settings up four times over the maximum. So, they are not changing any specs that were promised. They can change their firmware any way they want.

    Don't try to give lessons if you don't know what you are talking about. As said multiple times in my 1st post FOR setting DO NOT allow you to turn up the ffb 4 times the maximum. Even with FOR 400 your maximum force will still be 100.

    What it does do it to make a 5% signal become a 20% signal (if set to max, and I never used beyond 250ish, AND with FF NOT AT 100).

    FOR setting acts like as a signal compressor and that's why it is extremely useful to be able to use higher values like up to 400 (not to say that it also does not affect SPR/DPR, contrary to FF).

    And as said, the 400 value IS PROMOTED on the product page (as said, in the video). This was a feature used to promote the base. Given even using it at 400 won't make you go above the nominal force (FF100), if the decision is made to limit it to 150 this means the motors are not robust enough to handle what is advertised. Plain simple.

    The comparison with other wheel allowing no signal compression at all is silly. I don't care other products. I haven't bought those, I have bought a CSW and this one has an online manual promoting a 400% signal compression.
  • edited July 2014
    @John Lomax

    Obviously it was an overclocking function to make it work 4x higher than the normal usage, that's why it could be set up to 400(%). That is not a normal usage.
    Same as Marek, read my posts again, learn about how this feature and your wheel works, because it is wrong to say it would make your base work 4x high than normal.

    Even "normal usage" means nothing. What is normal usage, a game with a ffb averaging @15% of your wheel nominal power 95% of the time ? Or another averaging @60% of nominal wheelbase power 95% of the time ?

    The latter is still within specs (older games have strong ffb. My microsoft ffb wheel handled them for more than 15 years). So why a 400% amp on the 1st one would change anything ? It doesn't. Same result in both case.

    If there was a problem with the 400% signal compression making the average ffb power being too much for the cheap mabuchi, then:

    1°) it would have pointed a design flaw and would have to be acknowledged as is, instead of trying to hide/twist the reality by talking about "overclocking" for a built-in feature. I'd have been more inclined to forgive if I was told "ok, we are sorry but we have been too optimistic with this feature and must limit it because our motors can't handle that much stress".

    2°) A better compromise should have been offered, to limit the impact of the required restriction to prevent from failures. For exemple, limiting FF when using too high FOR. Something like 200+ FOR limits FF to 90. 300+ FOR limits FF to 80. That would be way better I guess, because we'd still have the full 400% compression feature. 
  • edited July 2014
    1°) it would have pointed a design flaw and would have to be acknowledged as is, instead of trying to hide/twist the reality by talking about "overclocking" for a built-in feature. I'd have been more inclined to forgive if I was told "ok, we are sorry but we have been too optimistic with this feature and must limit it because our motors can't handle that much stress".
    I don't see a design flaw here, it needs to be limited, because people are using it wrong. Wheel is designed to work with everything at 100 and it should be capable of that that every day of the week. Overclocking was for weak signals, but of course it depends on the person. If you are a Schwarzenegger, you'd probably play every game at 400 and clearly it is not what it was designed for. It had to be reduced, because there are persons who think that if 400 is the maximum, they can use that all the time no matter whether signal actually was too weak to feel or not.

    What games are you playing anyway? I have never used it above 100, because I have not seen a need for it and I have had my CSW about two years now. What racing game is so bad that you'll have to amplify it 3-4 times?

    They should implement better quoting system here, because current sucks.
  • edited July 2014
    The FW just screwed up my wheel base. No I am not happy at this second The wheel no longer centers at boot up and the rotation seems to be screwed up as well.



  • I don't see a design flaw here, it needs to be limited, because people are using it wrong. Wheel is designed to work with everything at 100 and it should be capable of that that every day of the week. Overclocking was for weak signals, but of course it depends on the person. If you are a Schwarzenegger, you'd probably play every game at 400 and clearly it is not what it was designed for. It had to be reduced, because there are persons who think that if 400 is the maximum, they can use that all the time no matter whether signal actually was too weak to feel or not.

    What games are you playing anyway? I have never used it above 100, because I have not seen a need for it and I have had my CSW about two years now. What racing game is so bad that you'll have to amplify it 3-4 times?


    I totally disagree with your opinion. John Lomax is right. I'm also very annoyed about the new limit for the FOR-Setting

    I play most of the time ASSETTO CORSA (in my opinion the best and most realistic racing sim on the Planet) Depending on the driven car I have set the FOR to 100 up to 180 to get the most realistic feeling of driving. I can't raise the in-game-FF-seetting because I then get clipping. By raising the FOR-Seeting on the wheel I can avoid clipping and get a realistic driving feeling.

    When the FOR-Setting is now limited to 150 this is an unacceptable limitation. I never used FOR-Seetings above 250. But the new limit of 150 is by far to low. 

    I don't now if I boughtCSW if I would have been informed about this limitation. As John Lomax said the product is promoted with the possibilty to amplfiy the FOR up to 400. That is now no more true. I'm really annoyed because that was as for now an product feature is now called "overclocking" already for FOR-Settings more than 150.

    two questions:
    1.) Is there a possibilty to install the new driver without the new firmware?

    2.) Have anyone who installed the new firmware already experiences with the following feature: "Center bump issue" has been improved significantly




  • Very good job with these changes, before it was perfect in Assetto Corsa, now it is a dream to use the CSW with this game. Continue like that, your work is perfect.
  • The FW just screwed up my wheel base. No I am not happy at this second The wheel no longer centers at boot up and the rotation seems to be screwed up as well.
    Did you re-calibrate the centre as you were told?
  • 1.) Is there a possibilty to install the new driver without the new firmware?

     If you don't care about the changes in new firmware and don't have this universal hub, I don't see a problem in using older firmware with new driver.

  •  



    Yes I recalibrated the wheel so yes the FW is fine in that respects however now the v200 driver does not recognize my CS usb adapter and when I go to update it I get a message that the device is not in boot loader mode. How are we suppose to set the USB adapter into boot loader mode. However while going through this whole ordeal I reverted back to v144 FW37 and the USB adapter on the device page listed it as Shifter Mode. So could it be I could roll back v200 to v144 and have my shifter work and my Uni hub with the new FW

  • edited July 2014


    I don't see a design flaw here, it needs to be limited, because people are using it wrong. Wheel is designed to work with everything at 100 and it should be capable of that that every day of the week. Overclocking was for weak signals, but of course it depends on the person. If you are a Schwarzenegger, you'd probably play every game at 400 and clearly it is not what it was designed for. It had to be reduced, because there are persons who think that if 400 is the maximum, they can use that all the time no matter whether signal actually was too weak to feel or not.

    What games are you playing anyway? I have never used it above 100, because I have not seen a need for it and I have had my CSW about two years now. What racing game is so bad that you'll have to amplify it 3-4 times?

    They should implement better quoting system here, because current sucks.
    Who then could say what is the right way to use it and what is the wrong one, where is the limit where you can state you'd be going too far and are exposed to motors failure. Where is the warning in the manual. Where is it said or written the goal of the feature is to raise only weak signal, and how the user can determine when a signal
    can be considered weak or not.

    If you think a little you quickly see this is a non-sense as inapplicable. There is no way to give the user a way to determine when he'd be going too far. And with little sense nobody would imagine a company letting in a dangerous feature because "they'd rely on the average user to have a wise use of it". So anyone can only assume that if the feature is there and set to 400 max, the wheel was designed to handle it.

    To me it's clear the new limitation is there to limit RMA, and on top of this I could say for a wheel that is promoted to have a "large fan, providing ample cooling"  (see product page), and despite this "ample cooling" still even has a power-limiting system to reduce power when overheating, and STILL this is not enough to prevent motors death when using a built-in feature...

    BTW I was beta tester for this wheelbase and FOR never was limited to 100. I clearly remember using it on my 1st tries with pCars for the review (IIRC it was 250 during beta testing).

    As for Marc Wendling, this feature is also one of the top feature for me and it played a lot in my decision to buy this wheel. So no, no , no, seing it being reduced to almost nothing (+50% instead of +300%, this is HUGE downgrade) is not acceptable to me.

    And seeing how Fanatec is trying to dodge their responsabilities on this by trying to imply this was an unsupported feature by now calling this "overclocking", when it was clearly used as a selling feature for advertising the wheel, makes me even less likely to accept this. Shall Courts had to tell who is wrong there, I have no doubt they would say the product is "not as advertised anymore".

    About games, as Marc I'm currently focusing on Assetto corsa, and I have similar feedback than his. I remember I've used a bit above 200 FOR on some cars because as he says AC FFB has to be lowered to prevent clipping.

    This means this is nowhere near using the FOR feature to get an ultra-strong ffb, but just something I consider "normal strength" where "normal" mean "decent" but still within the specs for this wheel. The goal is to use lower ffb for the ingame setting to avoid clipping then bring back the signal strength to an decent value using the FOR signal amplification. And has he says, 150 is way too low.

  • edited July 2014
    And seeing how Fanatec is trying to dodge their responsabilities on this by trying to imply this was an unsupported feature by now calling this "overclocking", when it was clearly used as a selling feature for advertising the wheel, makes me even less likely to accept this. Shall Courts had to tell who is wrong there, I have no doubt they would say the product is "not as advertised anymore".
    Interesting that you see a manual as a selling advertisment. People usually see what features are given on a homepage, not go look for a manual and see what is shown there.
    Notebook sellers should stop selling notebooks with different configurations then, because if you buy a laptop without 3G module, but it is in the manual, then this is a false advertisment in your view, even though on a page it is sold, there's no talk about 3G.
  • And seeing how Fanatec is trying to dodge their responsabilities on this by trying to imply this was an unsupported feature by now calling this "overclocking", when it was clearly used as a selling feature for advertising the wheel, makes me even less likely to accept this. Shall Courts had to tell who is wrong there, I have no doubt they would say the product is "not as advertised anymore".
    Interesting that you see a manual as a selling advertisment. People usually see what features are given on a homepage, not go look for a manual and see what is shown there.
    Notebook sellers should stop selling notebooks with different configurations then, because if you buy a laptop without 3G module, but it is in the manual, then this is a false advertisment in your view, even though on a page it is sold, there's no talk about 3G.
    I'm one of the people who look in the manual before buying a product, at least when - as in case of the CSW - the "manual" is a video and also an advertisement. Product features can also be told in a manual, as it is here. 

    I don't know where your problem is. I und John Lomax have expessed that the FOR-Amplifing is very important for us and we bought the product with the former description that the force can be amplified signifcantly (up to 400 %). With the new firmware this is no longer the case.

    If you don't use this feature or it is not of interest for you, why do you blame other people - who have another opinion - that they drive always with 400 % FOR-Seeting. As you see, your assumption was wrong.

    I'm also a fan of the CSW. But is it undisputabale that the new limitation changes the product features in a significant point and way (from 400 % to 150%). This is far too much. The limit should be raised  at 250 %.
  • I don't know where your problem is. I und John Lomax have expessed that the FOR-Amplifing is very important for us and we bought the product with the former description that the force can be amplified signifcantly (up to 400 %). With the new firmware this is no longer the case.
    Well, here's a tip for Fanatec for the future. With next products, show only picture and tell absolutely nothing about it, so noone could get upset, because absolutely nothing was advertised or put disclaimers absolutely everywhere that features are subject to change without notice.
  • John,
    Marc,

    let me give you some examples:

    Last week with the latest system update, my ANdroid phone lost the capability to view flash on websites.
    Can I now go to HTC and claim my money back?

    If you buy a new car you can expect that the brakes last for many thounsand kilometers. If you go on a race track and heat them up too much you can burn them within an afternoon.
    The car makers fault?

    We could have just made the overall FF weaker and keep the 400 setting as we never advertised how strong the wheel is.
    Would you be happy now?

    The FOR settong can be overclocked but this feature was not meant to be a permanent setting and it is a potential threat for the reliability of the wheel. Many customers are already out of the warranty period and we also protect those customers.

    The overclocking of the force settings is an artificial amplification and should only be used to amplify very weak signals to a reasonable level so that you can enjoy a game with weak force effects as much as a perfectly tuned game like Assetto Corsa at 100%.



  • edited July 2014
    Yeah Thomas, you should demand your money back from HTC and also demand millions as reprisal, because your whole world collapsed, because you know very well you bought this phone for this reason only :))
  • > Marek Laul  Interesting that you see a manual as a selling advertisment.
    Lol have you looked at this video ? It is as an adv as a quick manual.
    It's even hosted on youtube and is the 3th result returned when searching for "fanatec csw".
    https://www.youtube.com/watch?v=cMP-CDJVock

    Or maybe you prefer the CSW introduction video at E3 promoting the FOR setting that let you increase the ffb signal from the game:
    https://www.youtube.com/watch?v=SgnxlWXs_CY

    After seeing this feature promoted you will want to know more about it if you are interested by it, and will check for reliable public informations on it. We are talking about a 800€ wheel here (and that's entry price. Base + gt rim + csr pedals).

    > Marc Wendling > The limit should be raised  at 250 %.
    Agree with you on the figure you propose.

  • The overclocking of the force settings is an artificial amplification and should only be used to amplify very weak signals to a reasonable level so that you can enjoy a game with weak force effects as much as a perfectly tuned game like Assetto Corsa at 100%.



    @John Lomak
    Like Thomas said, the FOR setting is an amplification of the FFB, it has nothing to do with FF setting which just limits the FFB from the game to a plateau. So yes, I know how my product works!
    And, "normal usage", as one would expect from the context, is understood as 100% of force... It might not have been the right expression to use, but that is another matter 
  • edited July 2014

    Okay I was able to load the FW53 and driver 200 CS usb device not detected in v200 driver Roll back Driver to v144 CS usb device is detected. With Wheel booted with a FW53 Dr v144 combo GTR2 crashes, GTL Crashes, Assetto Corsa Loads but no FFB and that is as far as I have gotten. I turn the wheel off GTR2 loads up no problem so it would seem FW53 has compatibility issues with games and Driver 200 is no good as well. I have no choice but to fully roll back and hope my universal hubs work with a FW37 Dr v144 combo. 

     

    I am also not too happy with having to pay $5.00 to arrange that my first hub be delivered in between 5-8pm due to the fact your US webshop is requiring direct signature delivery requirements. I may have to do the same exact thing when my 2nd one is delivered on Saturday or Monday as well.

  • edited July 2014
    > Thomas Jackermeier > John, Marc, let me give you some examples: Last week with the latest system update, my ANdroid phone lost the capability to view flash on websites. Can I now go to HTC and claim my money back?

    If HTC advertised this phone on its capability to read flash then a court will be your side because of false advertising. Even if not in a "true" advertisement, if the court estimates it can be assimilated to an adv, like publicly released informations any potential customer have fair chance to base his decision on to decide to buy or not, then the court could state you intentionnaly tried to abuse the customers by spreading false informations or nature of mislead him.

    > Thomas Jackermeier If you buy a new car you can expect that the brakes last for many thounsand kilometers. If you go on a race track and heat them up too much you can burn them within an afternoon. The car makers fault?

    Come on Thomas, you cannot compare using a road car every customer will understand is not made for racing on track (and court will certainly state the same), with a feature designed to make a 4x signal amplification (and only signal, max power output remains unaffected) that the company would hope the customers will understand by themsleves (not a single warning from Fanatec) that it's not meant to be used at designed full potential.

    And we are not even talking about using it to its full designed potential, but at least a decent one, one that would correspond to the use meant for this feature and not make it almost inexistant.


    250 seems a fair value to me too
    . 150 is removing a feature that you promoted the wheelbase with.


    See, when I tested the wheelbase I first expected a lot at the first glance at it, based on the quality feel when looking at it and touching it.

    Then it did not took long to realize the ffb fading due to the heating protection system, pointing at the fact that the motors were not as strong as I'd have expected regarding the overall built quality.

    That was a first little disappointment (among some others, in particular significant wheel play due to the QR system, or unadjustable shifter paddles throw due a design flaw). But, weighting the pros & cons, it was not perfect but still a good value for money.

    Then after a few monthes I read on forums people have ffb motors dying. I'm not very pleased to see this but mine is still working. Until the day mine die too. So you change them at your charge, nothing to say about that, but now after that I wonder how long the new ones will last, and what will happen if they die again when I'm out of warranty.

    You spreaded the info you found a design flaw on those engines and that it was now fixed, but that's just an info we have no way to verify, so I cannot say I'm confident again my 800€ wheel will last (my 2 microsoft wheels are still working, the older being 15 or 20 years old now).

    And now there is this update where you significantly reduced a feature that is susceptible to stress the motors (but you promoted the wheelbase on).

    So how to still be happy and confident when various events that happened during my 1st year of use (ffb fading, other users' dead motors (sometimes twice), my own motors death, your fw limitation) just pointed toward the motors as really being not robust enough for that wheelbase.

    I really wish you decided to offer a motors upgrade kit for the most enthusiasts CSW customers, that you would offer at decent price for early adopters like you did earlier with the GT3RS upgrade kit to v2. Better motors ? Or a watercooling kit for the mabushi ones ?


    > Thomas Jackermeier should only be used to amplify very weak signals to a reasonable level so that you can enjoy a game with weak force effects as much as a perfectly tuned game like Assetto Corsa at 100%.

    How your customers are meant to determine was is "reasonnable level" ? I felt I was using reasonnable level when using FOR with assetto. Not stronger ffb than what I could have with other games without using FOR. Still my motors died.

    About AC, it is a really good sim. But I won't go as far as saying it'd be "perfectly tuned". Not yet at least, but I don't think the ffb will significantly change by the time we reach the final product. I feel it will continue to be as now, which means best ffb is obtained by using 150 to 250 FOR, depending on car (with lowered ingame ffb setting, like 20-60 depending on car).

    edit: I've just checked my current AC setting is 20 for ingame ffb gain and 180 for CSW FOR. And this is for competitive racing, I may go a bit higher if I'm more toward playing for fun, or with some specific cars.
  • I've just updated, the firmware installed fine but the driver hasn't
    installed. I click on CSW properties and it's the generic Windows
    calibration, No one has mentioned it so am I doing something wrong,
    though I can't see how?
  • edit: I've just checked my current AC setting is 20 for ingame ffb gain and 180 for CSW FOR. And this is for competitive racing, I may go a bit higher if I'm more toward playing for fun, or with some specific cars.
    You have very interesting settings. Totally different what most probably uses. Even AC team suggests similar what probably most use and they should know the best,
Sign In or Register to comment.