FanaLab 2.01.58 Release Candidate (previously .57) - Post your Feedback here

12346

Comments

  • Appreciate the help but no luck as far as those files linked correctly, or so it appears...



  • What could cause this, "low torque mode" as well as not being able to auto load any profiles? Please let me know if there is anything I could gather to help diagnose


  • MadDog-ICMadDog-IC Member
    edited February 6


    All of your ProfileCarsList_xxxxxxx.xml files are only 1k in size (This is the wrong directory)

    (c:\Program Files (x86)\Fanatec\FanaLab\Control\xml), they are the defaults when Fanalab is first installed with no data for linking Telemetry CAR_ID to Car Profile files.


    The correct folder for all of you ProfileCarsList once correctly configured for games is stored in:

    (%UserProfile%\AppData\Local\Fanatec\FanaLab\xml). You need to check the file sizes match the ones in my pics.

    Their size should be 10k for Iracing and even larger for other games, you need to merge the correct files from Maurices fanalab profiles 2.01.58 into the XML folder of Fanalab structure as was shown on my original pics.

    If you don't have any configured already you just copy over the required ProfileCarsList_iRacing.xml and other ProfileCarLists, other wise you have to copy paste the data from one into the other.

  • MadDog-ICMadDog-IC Member
    edited February 6

    Low Torque mode usually caused by:

    1) Not pressing a button on the steering wheel when wheelbase is turned on and wheel is calibrated and centered and you are asked to press a button to enable HIGH Torque MODE.

    2) Torque Dongle Not being installed into the correct port on the back of the DD1 / DD2 Wheelbase.

    3) When Wheelbase is initialized and ready to use, you can press the power briefly to make it go into LOW Torque MODE.

    4) Lower Quality Plastic CSL Steering wheels with or without a plastic QR can dictate that only LOW Torque MODE can be used (Some wheels have a switch in them to do this).


    However in you examples of pics, it isn't actually in LOW Torque mode because it is reading 14 or 15nm which is 70% or 75% of the 20nm max in PEAK mode. So that in it self is odd having the warning showing, but not actually limiting the force to 8nm (Low Torque MODE).

    You can also check the OLED screen on the DD1 to see if your in LOW / HIGH Torque mode.

  • @Charles Hosea

    If you go to Fanalabs settings page -> Log Settings - enable all options, run games, etc and then post the Fanalab logs here, we might get some insights to what is going on.

    Fanalab Log is found here: c:\Users\Public\FanaLab Logs\FLControl.log

    Fanatec Driver Logs are found here: c:\Users\Public\Fanatec Logs\FWXXXXXXXX.Log

    or

    If you have archived all logs together then here: c:\Users\Public\Fanatec Logs\Compressed\FanatecDiag_xx-xx-2024_xx-xx-xx.zip


    Be sure to turn all of the LOG Settings back off after doing testing / creating logs as the amount of data it creates can be huge (in the Gigabytes) and can crash Fanalab altogether, with the symptoms of Fanalab seeming to disappear by its own (As you describe is your problem), however it is windows removing a troubled app than has stalled or not working correctly.

  • Thank you and the wheel base itself shows high tq and I am definitely feeling it in the FFB.

  • Thank you very much, I appreciate all the support. I will make sure these are correctly setup and report back.

  • For some months now, Fanalab has been crashing after about 10 minutes. I can always restart it, but in EA F1 23 it stops after almost exactly 10 minutes.

    I have already posted this several times, also with log files.

    Now I'll try it this way. Screenshot of the event log.

    I hope to get help soon:


    Yours sincerely

    Stefan


  • MadDog-ICMadDog-IC Member
    edited February 6

    Have you enabled any extra LOG Settings in Fanalab recently, this can cause Fanalab to crash after 10min with what looks like a ever increasing memory leak (Consumes up excessive memory and Cpu cycles until it crashes and is removed from memory by windows task manager), remedy is to disable ALL LOG Settings in Fanalab (might be only a specific one that causes it, but I couldn't be bothered trying to find it).

    Other symptom is that the log file will be come quite large very quickly when running your car game (Gigabytes of data instead of Megabytes in a short period of time).

    Fanalab Log is found here: c:\Users\Public\FanaLab Logs\FLControl.log

    You can see the behaviour happening using Window's Resource Manager and monitor the Fanalab.exe programs Memory and CPU Load whilst running a car game that uses telemetry for LED / RPM, etc, you will see it creep up approx 2mb of ram a second and CPU will have more and more cycles to process until Fanalab failure at 10 minutes.


    Also when your asked for log files, most important are the Fanalab logs, not so much the Windows Event logs, however they are helpful also.

  • A little question, i have the csl load cell brake connected at pc directly with usb. In the fanatec control panel i setting the sensibility on 65% but on fanalab every car have the brakforce on 50%. Wich is the value applicated on game? fanalab or the fanatec app?

  • Loading a car profile in Fanalab (Tuning Menu S1 to S5 settings) will always change what you have set in the Fanatec control panel settings (S1 to S5) .

    If you want the profiles to have BRF of 65% you will have to change each profile Tuning Menu setting to that for each car or just one profile for all cars and re-save the profiles.

  • Thank you very much for all of your help, so far so good with Fanalabs working properly. Fingers crossed all is well again, have a great weekend.

  • Many thanks for your help.

    I have removed ALL the checkmarks in the LOG, now it works again as usual.

    Regards

    Stefan

  • heyho! is there a new fanalab-version bei end of the next week (LMU Update)? :D im asking for a friend....

  • It seems the website cert has expired so the download for fanalab as well as the profiles doesn't work. Does anyone have a mirror or can share? Trying to get this set up before this weekend's iracing bathurst 12hour

  • Just as a follow up to my previous post, it seems the links are maybe just incorrect. If you remove the admin. prefix from the url, the downloads work fine.

  • Hello everyone,

    I have been driving with Clubsport Wheel Formula V2.5 and Wheel Base DD2 for years without any problems.

    The last months I had problems with the ITM data on the display of the DD2, error was probably the LOG file.

    After a few quiet days, the next error is now creeping in. In the race (F1 23) after different number of laps (between 5 and 35) the steering freezes for 1-2 seconds, as throttle/brake and steering angle, then it continues abruptly (sometimes without wings) and the display on the DD2 shows the original status (FANATEC ...).

    But all settings and button assignments on the controls work. What is bad is the stuttering and the fact that the display then no longer shows any information.

    If I pause the game, unplug the wheel briefly and plug it back in, everything goes back to normal until the next interruption.

    What can I do to solve the problem?

    Regards

    Stefan


    Translated with DeepL.com (free version)

  • Hi, there seems to be something wrong with the download links for both Fanalab and Maurice's profiles. Could someone upload the latest ones until the issue is fixed? Thanks

  • Everything is wrong. Everything is more broken every year. They aren't fixing shit anymore.

    Click the link and when it opens, remove "admin" from the link and it should work.

  • Janina RiebeJanina Riebe Member
    edited February 23

    The certificate for this CN has expired..


    temporary solution open link in incontito mode...then the download works or use the workaround from Tomaz Hocevar


  • Charles HoseaCharles Hosea Member
    edited February 24


    EDIT - Thank you @tomaz hocevar.

  • edited February 24

    Remove the admin. part from the link and it will work, the regular forum.fanatec.com certificate is still valid and the link still works because it is the same site. I guess admin/moderator version is on a separate domain.

  • edited February 24

    Hello there, I'm experiencing a small problem with Fanalab. Everytime I load in in iRacing the recommeded iRacing Profile applies. That's fine with me but what I don't like is that the brake pressure is set to 50%. I can change It in Fanalab but after I restart my PC it's reset to 50% again. I haven't found a solutions in the UI where I can turn it off. Does anyone have a solution for this?

  • edited February 25

    Set BRF accordingly and then save the profile, otherwise it will reload the previous value (which is in the profile) next time it loads the profile.

  • How do I save a profile? There is no button for that.

  • ElurztacElurztac Member
    edited February 26

    In the profile menu, where you have the list of all profile

    If you put a name in the bottom and click one save it will save the current setting you have in the setting tab.

    so you can :

    double click on default profile to enable it (iRacing icon showing up in fanalab)

    go to the tab where the BRF is, and put it like you like

    go back to the profil selection menu, put a name (mine is call BRF100) then save - and then right click on your new profile and « set as game default »

  • Hey guys, is FanaLab getting a new Version soon?

  • Yes, next week.

  • OH YES! Thanks!!!

  • Apologies in advance if this has been discussed before. I played LMU two nights ago, and today, I decided to play F1 24 again and noticed the car behaving strangely FFB-wise. I then checked Fanalab, and to my surprise, all of the profiles I had saved for years disappeared! I'm on driver Version 464, and Fanalab is 2.01.54. I have updated to 2.01.58, but it is still the same issue; only the recommended settings are visible.

    Is this where my profiles are supposed to be located?


    Any idea how to restore this? Is there any back-up location?

This discussion has been closed.