but me and a Friend, can't create custom Games for some reason, like we fill out all the info about the game etc. and when we hit add game nothing pops up in the game list. I managed to get my 3 games imported from FanaLab after installing this new App to my second drive but a friend of mine can't get it to work.
I notice that the CPU load (i5-3470) from the FanatecService (32bit) service is between 15-20%, which is relatively high and even causes unpleasant FPS drops in some games.
The Fanatec App itself lags when displaying the brake or throttle movement of Clubsport V3 pedals connected via USB, either on the Home screen or in the Pedals section. Moving either of these axis causes lag within the app, the input displaying bars become choppy. This scenario is also accompanied by high CPU load of the Fanatec App process, as observed in the Windows Task Manager. The clutch axis movement however always displays smoothly and doesn't cause any issue.
Had issues adding new Custom Games also, created them for me, but wouldn't run the games when double clicked, checked the config file where the settings are stored and found the "steamlaunch ID=" line in the config file had multiple repetitions:
Copied the config file from my previous Fanalab setup to the new Fanatec App equivalent directory as listed in previous post in this forum at bottom of page 2.
When adding a custom game, the app requires the Steam ID field to be filled. I point the app to the game .exe, but when the game (good old Richard Burns Rally) has no Steam ID, I am still forced to add a Steam ID. So I had to work around by putting in a random number.
Sorry been away for the weekend but yes those are the steps and can see that MadDog replied and confirmed as well.
Will give MadDog's fix a go in the interim :)
Only other issues that I have had is that sometimes when loading the app my Elite V2's are detected as CSL pedals and are unresponsive, reload the app or restart the base fixes.
Quick update regards saving profiles to cars, think the app is just being weird as thought I had found a potential fix which was the unedited post but went to assign a profile to a car in iRacing it was already assigned which must be from when I originally posted. It feels more like the app did not refresh the saves.
I have edited the profiles I import slightly as well, to match the base, software pedals version etc. to what you get as default in the new app rather than Fanalab.
Is there an option in the Fanatec.App to toggle the Fanalab like features on and off at will, so you can run the new Fanatec Drivers and APP but with standalone Fanalab 2.01.xx package instead for (RPM LED Support).
How quickly would driver updates / corrections be in coming (rough estimates) ?
I ask, because of the following (Don't want to have to be installing different driver packages all the time):
1) I would prefer to run the standard Fanatec drivers (v464) + Fanalab 2.01.xx (Full RPM LED Support) in daily use.
2) I would also be interested in running the complete FanatecApp for testing purposes in general.
3) I would also be interested in running the FanatecApp with the Fanalab like features disabled and use the standalone Fanalab 2.01.xx instead.
4) If running FanatecApp fully, I am not sure I would be able to use the FanaLED program for my older racing games as Fanalab side of things would block it from running, well I assume it would as the standalone version of Fanalab 2.01.xx does, but the standalone can be shutdown.
Sorry for my late reply. Steep 1 is wrong: Pedals are directly connected to my PC through USB; except for this, everything you wrote explains my issues.
I hadn't opened Fanatec Control Panel for about a month, last time it was open I was on 464 Drivers and everything fine. DD2 + Formula V2.5X + Clubsport Pedals.
Launched it today, FCPanel states it cannot communicate with wheel and needs to reinstall the driver for the wheel. (base and pedals still show up fine) The wheel worked fine, playable, just FCPanel giving this problem. Prior to this always recognized as a v2.5X and never had an issue.
After attempting all basic plug it in and out / reboot troubleshooting, still the same. So I proceed with the prompt to repair and it reinstalls the same 464 driver package.
Now FCPanel recognizes the wheel but it shows up as a "Clubsport Steering Wheel Formula V2".
So, figured I’d try this new beta and see if it recognizes differently here..and still recognizes as a V2 on firmware 47.
All functionality and tests seem fine but just curious if this is a concern with the wheel..
Overall the app looks good and is functioning well. Well done!
Feature Request:
Can you please consider adding a toggle to enable/disable wheel LEDs regardless of game telemetry? I have a Rev strip attached to my wheelbase and a Clubsport RS wheel, since I prefer the rev strips over the LED on the CS RS wheel I would like to disable the LED on the wheel. Currently I have a black tape over the wheel LED which is pretty and keeps coming off every once in awhile.
That's normal. A Formula V2.5 X is basically a V2 just with Magnetic Shifters instead of spring Shifters. Everything else is the same, so same electronics and therefore same Firmware so the Software simply can not differentiate them and always shows it as V2.
That's a bug, it should only be shown for when using the Fanatec USB Adapter but for some reason is also shown on USB Pedals without using Adapter. This will be fixed.
Ah ok, some elements were made bigger because a complaint we saw often in FanaLab was that things are too tiny and especially the UI was too buzzy showing too much at once. I understand that this has the downside of seeing e.g. less profiles at once.
One thing I want to mention is that in the future users likely will have much less profiles because of the LED profiles for each car being included in the software already and no need to import those from Maurice anymore (Feature is included but needs fixing). So maybe its not that bad for the profile list in the future? Or do you also have other examples.
We'll discuss this topic internally and see for more feedback. We likely won't change this soon but maybe in the future if more people agree that its needed.
The old driver will be removed automatically when you try to install the Fanatec App. FanaLab won't be removed automatically, you can keep it installed and turned off while using the Fanatec App or uninstall it as well.
Noted, maybe the separation line between the car names could be removed and the gaps in between them a bit smaller. Also the box around the profile names could be made a bit smaller to find a compromise and not making it look too crowded right away. As said in the previous comment I think users will have way less profiles to look at in the future because of the automatic LED preset feature.
It's a big difference between 1440p and 1080p and I agree that especially on 1080p you don't see many profiles at once while 1440p doesn't seem to bad. Here two example screenshots.
Looking at this it could also make sense if the list of the cars uses more of the available screen space.
True the Game Launch doesn't work correctly and it also starts with the fact that the function to create a new game is incorrect. Steam ID is a must field which it should not be, we are working on an improvement.
Thanks, can you give me a summary on how to reproduce this step by step because for us mapping the profile to a car and then the profile being automatically loaded worked. We had this as an issue in an earlier version some weeks ago but for us this was resolved.
I am torn also on this one also, being of poor eyesight myself, I appreciate the larger pictures and Icons of the menu in 1080p screenshot as Fanalab is a bit tiny with its icons and writing, however it was still quite usable.
The look of the 1440p second bottom picture is much more appealing to me as it looks like a good compromise between the old and the new, large enough and practical.
Either way, as you said I probably will not be doing to many Car Profiles in the future, but as I do most of my work directly within the CarLists_????.xml, ProfileCarList_????.xml files with a word processor and the RPM LEDs in actual Fanalab system.
Change in menu system will not affect me to much, just have to learn to adapt.
I produced all the Car RPM LEDS for:
Assetto Corsa (Full CDALP supported)
Project Cars 1 (Best Guess on Car names and No CDALP support anyway)
Project Cars 2 (Best Guess on Car names and CDALP not supported properly anyway)
We'll have a look. The Formula V2 and V2 X are almost identical, also in their detection so maybe this piece of extra info for knowing the difference is either not communicated or handled correctly.
Everything else about the wheel still working fine like going into Xbox mode?
But if I'm not confusing anything here I think the Control Panel since a while shows the same Formula wheel picture for all variants only changing depending on the APM being attached or not.
EDIT: Ah I see Maurice is confirming this so all good I would say?
The current mobile app available on IOS and Android is only compatible to the Control Panel at the moment. We are working on an overhaul for the mobile app which then will be compatible to the new Fanatec App. This will come in summer.
Then I'll request for that feature to be added, would allow me to commit to running FanatecApp in pure mode for general testing and also playing my games with Fanalab for full LED support in the interim ;-)
Comments
But it was also already on fanalab right?
Hi,
overall the App looks amazing! Love it :)
but me and a Friend, can't create custom Games for some reason, like we fill out all the info about the game etc. and when we hit add game nothing pops up in the game list. I managed to get my 3 games imported from FanaLab after installing this new App to my second drive but a friend of mine can't get it to work.
is that known or are there any solutions?
I notice that the CPU load (i5-3470) from the FanatecService (32bit) service is between 15-20%, which is relatively high and even causes unpleasant FPS drops in some games.
The Fanatec App itself lags when displaying the brake or throttle movement of Clubsport V3 pedals connected via USB, either on the Home screen or in the Pedals section. Moving either of these axis causes lag within the app, the input displaying bars become choppy. This scenario is also accompanied by high CPU load of the Fanatec App process, as observed in the Windows Task Manager. The clutch axis movement however always displays smoothly and doesn't cause any issue.
Had issues adding new Custom Games also, created them for me, but wouldn't run the games when double clicked, checked the config file where the settings are stored and found the "steamlaunch ID=" line in the config file had multiple repetitions:
ie
<steamlaunch id="1293830">steam://rungameid/1293830</steamlaunch>steam://rungameid/1293830</steamlaunch>
or
<steamlaunch id="1293830">steam://rungameid/1293830</steamlaunch>"1293830">steam://rungameid/1293830</steamlaunch>
Check this config file to see if looks similar to the format below for each custom game you may have created:-
File: c:\Users\Public\Fanatec\OneFanatec\xml\CustomGameConfig.xml
Contents - Partial of my 10 or so custom games added to keep it brief:
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<Config>
<Game majorId="1000" minorId="1000" isSupported="true">
<title>Forza Horizon 4</title>
<img>C:\Program Files (x86)\Fanatec\FanaLab\Control\background\Forza Horizon 4 Ultimate Edition Wall.jpg</img>
<exe>ForzaHorizon4.exe</exe>
<steamlaunch id="1293830">steam://rungameid/1293830</steamlaunch>
<exelaunch></exelaunch>
</Game>
</Config>
My Solution to have it work:
Copied the config file from my previous Fanalab setup to the new Fanatec App equivalent directory as listed in previous post in this forum at bottom of page 2.
This reminds me of another, minor issue:
When adding a custom game, the app requires the Steam ID field to be filled. I point the app to the game .exe, but when the game (good old Richard Burns Rally) has no Steam ID, I am still forced to add a Steam ID. So I had to work around by putting in a random number.
Sorry been away for the weekend but yes those are the steps and can see that MadDog replied and confirmed as well.
Will give MadDog's fix a go in the interim :)
Only other issues that I have had is that sometimes when loading the app my Elite V2's are detected as CSL pedals and are unresponsive, reload the app or restart the base fixes.
Thanks, Bob,
Quick update regards saving profiles to cars, think the app is just being weird as thought I had found a potential fix which was the unedited post but went to assign a profile to a car in iRacing it was already assigned which must be from when I originally posted. It feels more like the app did not refresh the saves.
I have edited the profiles I import slightly as well, to match the base, software pedals version etc. to what you get as default in the new app rather than Fanalab.
Thanks, Bob.
@Marcel Pfister or anyone else in the know.
Is there an option in the Fanatec.App to toggle the Fanalab like features on and off at will, so you can run the new Fanatec Drivers and APP but with standalone Fanalab 2.01.xx package instead for (RPM LED Support).
How quickly would driver updates / corrections be in coming (rough estimates) ?
I ask, because of the following (Don't want to have to be installing different driver packages all the time):
1) I would prefer to run the standard Fanatec drivers (v464) + Fanalab 2.01.xx (Full RPM LED Support) in daily use.
2) I would also be interested in running the complete FanatecApp for testing purposes in general.
3) I would also be interested in running the FanatecApp with the Fanalab like features disabled and use the standalone Fanalab 2.01.xx instead.
4) If running FanatecApp fully, I am not sure I would be able to use the FanaLED program for my older racing games as Fanalab side of things would block it from running, well I assume it would as the standalone version of Fanalab 2.01.xx does, but the standalone can be shutdown.
Sorry for my late reply. Steep 1 is wrong: Pedals are directly connected to my PC through USB; except for this, everything you wrote explains my issues.
I hadn't opened Fanatec Control Panel for about a month, last time it was open I was on 464 Drivers and everything fine. DD2 + Formula V2.5X + Clubsport Pedals.
Launched it today, FCPanel states it cannot communicate with wheel and needs to reinstall the driver for the wheel. (base and pedals still show up fine) The wheel worked fine, playable, just FCPanel giving this problem. Prior to this always recognized as a v2.5X and never had an issue.
After attempting all basic plug it in and out / reboot troubleshooting, still the same. So I proceed with the prompt to repair and it reinstalls the same 464 driver package.
Now FCPanel recognizes the wheel but it shows up as a "Clubsport Steering Wheel Formula V2".
So, figured I’d try this new beta and see if it recognizes differently here..and still recognizes as a V2 on firmware 47.
All functionality and tests seem fine but just curious if this is a concern with the wheel..
Overall the app looks good and is functioning well. Well done!
Feature Request:
Can you please consider adding a toggle to enable/disable wheel LEDs regardless of game telemetry? I have a Rev strip attached to my wheelbase and a Clubsport RS wheel, since I prefer the rev strips over the LED on the CS RS wheel I would like to disable the LED on the wheel. Currently I have a black tape over the wheel LED which is pretty and keeps coming off every once in awhile.
That's normal. A Formula V2.5 X is basically a V2 just with Magnetic Shifters instead of spring Shifters. Everything else is the same, so same electronics and therefore same Firmware so the Software simply can not differentiate them and always shows it as V2.
That's a bug, it should only be shown for when using the Fanatec USB Adapter but for some reason is also shown on USB Pedals without using Adapter. This will be fixed.
We are working on a fix, thanks for the report.
Ah ok, some elements were made bigger because a complaint we saw often in FanaLab was that things are too tiny and especially the UI was too buzzy showing too much at once. I understand that this has the downside of seeing e.g. less profiles at once.
One thing I want to mention is that in the future users likely will have much less profiles because of the LED profiles for each car being included in the software already and no need to import those from Maurice anymore (Feature is included but needs fixing). So maybe its not that bad for the profile list in the future? Or do you also have other examples.
We'll discuss this topic internally and see for more feedback. We likely won't change this soon but maybe in the future if more people agree that its needed.
Hello, can the mobile app work with this new interface? I haven't found one, how can I activate it?
Yes the ClubSport v2.5 is supported.
The old driver will be removed automatically when you try to install the Fanatec App. FanaLab won't be removed automatically, you can keep it installed and turned off while using the Fanatec App or uninstall it as well.
Thanks, we'll have a closer look on the pedals issue.
Noted, maybe the separation line between the car names could be removed and the gaps in between them a bit smaller. Also the box around the profile names could be made a bit smaller to find a compromise and not making it look too crowded right away. As said in the previous comment I think users will have way less profiles to look at in the future because of the automatic LED preset feature.
It's a big difference between 1440p and 1080p and I agree that especially on 1080p you don't see many profiles at once while 1440p doesn't seem to bad. Here two example screenshots.
Looking at this it could also make sense if the list of the cars uses more of the available screen space.
True the Game Launch doesn't work correctly and it also starts with the fact that the function to create a new game is incorrect. Steam ID is a must field which it should not be, we are working on an improvement.
Correct, we are working on this.
Thanks for the update, I've asked our testing team to reproduce it and we'll create a task for it.
Thank you for the report, we could see the same now and are looking into this with high priority.
Thanks, can you give me a summary on how to reproduce this step by step because for us mapping the profile to a car and then the profile being automatically loaded worked. We had this as an issue in an earlier version some weeks ago but for us this was resolved.
It seems like the LED and display functions can't be turned off at the moment unfortunately.
Thanks for the clarification, then I'll update the created task to fix it.
GAME PROFILE MANAGEMENT:
I am torn also on this one also, being of poor eyesight myself, I appreciate the larger pictures and Icons of the menu in 1080p screenshot as Fanalab is a bit tiny with its icons and writing, however it was still quite usable.
The look of the 1440p second bottom picture is much more appealing to me as it looks like a good compromise between the old and the new, large enough and practical.
Either way, as you said I probably will not be doing to many Car Profiles in the future, but as I do most of my work directly within the CarLists_????.xml, ProfileCarList_????.xml files with a word processor and the RPM LEDs in actual Fanalab system.
Change in menu system will not affect me to much, just have to learn to adapt.
I produced all the Car RPM LEDS for:
Assetto Corsa (Full CDALP supported)
Project Cars 1 (Best Guess on Car names and No CDALP support anyway)
Project Cars 2 (Best Guess on Car names and CDALP not supported properly anyway)
Thanks for the feedback and screenshots.
We'll have a look. The Formula V2 and V2 X are almost identical, also in their detection so maybe this piece of extra info for knowing the difference is either not communicated or handled correctly.Everything else about the wheel still working fine like going into Xbox mode?
But if I'm not confusing anything here I think the Control Panel since a while shows the same Formula wheel picture for all variants only changing depending on the APM being attached or not.
EDIT: Ah I see Maurice is confirming this so all good I would say?
Thank you for the feedback, we will add an option to disable the LEDs.
The current mobile app available on IOS and Android is only compatible to the Control Panel at the moment. We are working on an overhaul for the mobile app which then will be compatible to the new Fanatec App. This will come in summer.
Then I'll request for that feature to be added, would allow me to commit to running FanatecApp in pure mode for general testing and also playing my games with Fanalab for full LED support in the interim ;-)