Another question, when using custom profile, i dont get the feel of vibation from the engine as i do when using default, is there something that I can do to get that to work as well ?
Yes its the stand still i mean when race starts :) I removed the # in the textfile ( ffb_custom_settings) and pasted it in the ams 2 folder. Did I do something wrong ?
Can someone help me with for the Rev Led settings for the iRacing Mazda MX5?
I tried the iRacing controlled setting in options, but theshifting lights don't seem to match quite right... I am using the Fanalab v1.69.1 with my GT DD Pro base and for the MX5 I use my WRC wheel.
When you use FanaLab you have to disable the native iRacing LED option in the in game settings as explained in the instructions shown to you when clicking the two green buttons in the game profile Tab in Fanalab to Enable Telemetry and Enable Fanalab support.
Then you need to try to find the accurate RPM value for the RevStripe by yourself.
That's what I was saying I did, but thought someone may have already figured out optimal RPM values, Im trying my best but I don't know what I'm doing. lol
In all iRacing online sessions CDALP is not working due to an issue with the car ID telemetry reader.
Still unknown if this ia a (fixable) FanaLab or a iRacing game issue, dev is on holiday so no fix expected anytime soon for this, not before at least next week.
For now you will need to do the "old" way like the last 3 years by manually loading profiles when driving iRacing in an online session until the issue got investigated.
THANKS for this hint! You are right, they indeed changed the names for these cars quietly and secretly with the latest game update...
But even worse is that they also changed the CAR IDs together with the car names... Therefore CDALP no longer works for these cars now so we indeed need to provide a new CarsList now. So here you go:
Installation instructions:
In your Documents folder you will find a folder called "Fanatec". In this folder is another folder called "Update".
Simply extract the attached CarsList_AMS2.zip and copy/paste the included new xml file into that "Update" folder with FanaLab being closed. On the next start of FanaLab it will update the cars list.
This new list of course will also be directly implemented in the next FanaLab releases going forward.
Together with the new CarsList I also updated my personal FanaLab Profiles where I have now renamed the respective car profiles and changed the car bindings to the new renamed cars of the CarsList so it also includes a new ProfileCarsList now.
When you use my profiles for AMS2 then only use this combination now as the old combo no longer works for these two cars.
When you dont change the picture manually via the grey arrow on the main page: yes. ;)
A V2.5x is internally 100% the same as a V2 and neither the Driver nor the Lab can differentiate which of the 8 variants of this wheel is attached, therefore by default the regular V2 is shown and its up to the user to select the "real" image. This does not change anything in functionality, its just for the correct look on the main page.
Its recommended to only use with 448 which is quite stable, there are no big issues reported for it and it might be the next official driver soon without changes.
My apologies if this has already been covered but im struggling to find a solution. I have the Clubsport v2.5 wheelbase, the motor is currently stuck on V0 after doing this update. I have gone back to 447 but im still stuck on V0.
This thread is related to FanaLab and FanaLab can not update your Base or your Motor.
A V0 shown on the motor usually means the motor is dead though. You can try to manually flash the motor Firmware again but I somehow doubt that this can help...
Thats frustrating as all was workimng fine before trying 448. I have tried flashing it but no change. I can still use the wheel, i dont know what effect its having but i can still drive.
Thank you anyway Maurice, sorry its in the wromg thread, im not used to forums.
Which window? You can resize FanaLab to fit your needs. The images now scales better since 1.69 with the from the user selected window size, that's it. No other change made.
What's your Monitor resolution and Windows Scaling?
The Minimum size of FanaLab was not reduced at all, when you manually resize it to your desired size there should be zero difference between 1.69 and older versions.
There is the potential to have it split out files for anything really given that the Fanalab PWS files are just XML, either way not sure if this is useful or if people want me to upload a converted zip in future.
Comments
Another question, when using custom profile, i dont get the feel of vibation from the engine as i do when using default, is there something that I can do to get that to work as well ?
The custom ffb file included in my profile pack does feature engine vibration in standstill, but only in standstill.
Make sure you remove the # from the file name to get it properly activated ;)
Yes its the stand still i mean when race starts :) I removed the # in the textfile ( ffb_custom_settings) and pasted it in the ams 2 folder. Did I do something wrong ?
I honestly dont know. Working fine for me.
Can someone help me with for the Rev Led settings for the iRacing Mazda MX5?
I tried the iRacing controlled setting in options, but theshifting lights don't seem to match quite right... I am using the Fanalab v1.69.1 with my GT DD Pro base and for the MX5 I use my WRC wheel.
Thanks in advance!
Frank
When you use FanaLab you have to disable the native iRacing LED option in the in game settings as explained in the instructions shown to you when clicking the two green buttons in the game profile Tab in Fanalab to Enable Telemetry and Enable Fanalab support.
Then you need to try to find the accurate RPM value for the RevStripe by yourself.
Now its working, must have put the file in the wrong folder earlier. Thanks for great and quick support.
That's what I was saying I did, but thought someone may have already figured out optimal RPM values, Im trying my best but I don't know what I'm doing. lol
I think I have it sorted out now.
Any profile for WRC Generations? Thanks you very mucho for your work
Nope, sry
profiles do not load in hosted sessions. it's normal?
In all iRacing online sessions CDALP is not working due to an issue with the car ID telemetry reader.
Still unknown if this ia a (fixable) FanaLab or a iRacing game issue, dev is on holiday so no fix expected anytime soon for this, not before at least next week.
For now you will need to do the "old" way like the last 3 years by manually loading profiles when driving iRacing in an online session until the issue got investigated.
@Maurice Böschen
In the latest Fanalab AMS2 Cars list and your latest AMS2 profiles there are a couple incorrect car names:
should now read:
I think Reiza changed their names in this latest update.
Kind regards
THANKS for this hint! You are right, they indeed changed the names for these cars quietly and secretly with the latest game update...
But even worse is that they also changed the CAR IDs together with the car names... Therefore CDALP no longer works for these cars now so we indeed need to provide a new CarsList now. So here you go:
Installation instructions:
In your Documents folder you will find a folder called "Fanatec". In this folder is another folder called "Update".
Simply extract the attached CarsList_AMS2.zip and copy/paste the included new xml file into that "Update" folder with FanaLab being closed. On the next start of FanaLab it will update the cars list.
This new list of course will also be directly implemented in the next FanaLab releases going forward.
Together with the new CarsList I also updated my personal FanaLab Profiles where I have now renamed the respective car profiles and changed the car bindings to the new renamed cars of the CarsList so it also includes a new ProfileCarsList now.
When you use my profiles for AMS2 then only use this combination now as the old combo no longer works for these two cars.
Lets hope Reiza does not secretly changes car IDs again in the future and this was just a one-time-only thing...
Already done manually when I noticed the change, thanks! 😀
Let's hope... 🤞
[Edit] I also double checked the rest of the car names while I was at it 😁 [/EDIT]
Is it correct that the Fantec Formula Wheel v2.5x is only recognised as Formula Wheel v2 in FanaLab?
When you dont change the picture manually via the grey arrow on the main page: yes. ;)
A V2.5x is internally 100% the same as a V2 and neither the Driver nor the Lab can differentiate which of the 8 variants of this wheel is attached, therefore by default the regular V2 is shown and its up to the user to select the "real" image. This does not change anything in functionality, its just for the correct look on the main page.
Does this work on driver 447?
Is 448 stable enough or does it have issues?
Its recommended to only use with 448 which is quite stable, there are no big issues reported for it and it might be the next official driver soon without changes.
Thank you for this information 😁
Hello
My apologies if this has already been covered but im struggling to find a solution. I have the Clubsport v2.5 wheelbase, the motor is currently stuck on V0 after doing this update. I have gone back to 447 but im still stuck on V0.
Any help would be hugely appreciated.
Many thanks
You post in the wrong thread.
This thread is related to FanaLab and FanaLab can not update your Base or your Motor.
A V0 shown on the motor usually means the motor is dead though. You can try to manually flash the motor Firmware again but I somehow doubt that this can help...
Hi Maurice
Thats frustrating as all was workimng fine before trying 448. I have tried flashing it but no change. I can still use the wheel, i dont know what effect its having but i can still drive.
Thank you anyway Maurice, sorry its in the wromg thread, im not used to forums.
Good Morning,
I just updated to Fanalab 1.69.1 and now the window is huge and I can’t view half of the buttons / menus.
Has anyone had this issue with resolution of the window?
Thanks for your time.
Jeremy
Which window? You can resize FanaLab to fit your needs. The images now scales better since 1.69 with the from the user selected window size, that's it. No other change made.
This is what it looks like so the windows to load profile are cut off:
What's your Monitor resolution and Windows Scaling?
The Minimum size of FanaLab was not reduced at all, when you manually resize it to your desired size there should be zero difference between 1.69 and older versions.
Appreciate the feedback
Im on a 50 inch tv so my scaling has always been 300% with no issues on past versions of fanalab but for some reason this one is different.
going to 250 scaling resolves it thanks again for your feedback Maurice.
Hey Maurice, I've really appreciated the profiles for Fanalab. Given that I've got a DD1 and I'm also incredibly lazy I built a quick and dirty Python script to allow the files to work on the DD1: fanalab_profile_changer/fanatec-config-transformer.py at main · jevansdotio/fanalab_profile_changer (github.com)
There is the potential to have it split out files for anything really given that the Fanalab PWS files are just XML, either way not sure if this is useful or if people want me to upload a converted zip in future.
Thanks again!