Yes that can cause problems, always best to use the driver which is meant to be used with the firmware.
Thanks. Turns out this bug annoys me more than I'd like to admit- so I was relatively happy with v352. Would you recommend rolling back to that? Or a different FW?
If you want tro downgrade, then NOT 352 - that one can cause vlue screens and therefore was replaced with 356.
Will do. Thanks for the quick response!
I have dd2 wheel, ver356 and i downloaded 1.23 fanalab,
I have windows 10 (64) and i have no telemetry available and unable to get fanalab to connect to any games,
I do have simhub, and that seems to work fine, i have tried a output udp from simhub to fanalab and still no luck,i have tried reinstalling etc,
Any reason or fix would be greatly appreciated
FYI: I did downgrade to 356 but continued to have new problems that I didn't have with 352... including many wheel "crashes", including one where it spun around like crazy. Most of the cases were just freezes of some form that I could only recover from by pulling the power to the DD1.
Anyway, against your recommendation I downgraded all the way back down to 352... and my BME LEDs were bright again. In all cases, with every driver update, I updated all of the firmware to match the driver release. So, respectfully, I think you're incorrect on this assertion (quoted above). For 352 (669/8/2) the LEDs on my BME is *absolutely* brighter compared to 356, 361, or 365 (and their matching firmware). I never got a BSOD with 352, so I think I'll stick with this for now.
FWIW, I'm really looking forward to whenever (if ever?) Fanalab lets us adjust the brightness manually. Having this intense brightness in the BME is actually quite useful for detecting ABS and TC. I'm actually hoping I can eventually make my Formula V2 just as bright.
Like everyone though, I'm really looking forward to this driver situation settling down. I know you guys are trying (on top of a global pandemic), but the state of this software is pretty disappointing for hardware this expensive. It's a clear area where Fanatec needs to invest more (and heavily).
As I have written, and as you have quoted, the BME Leds were significantly made less bright with Firmware 9 and you are using Firmware 8 according to your post, so yes of course they are brighter, as I always said..... Update the BME firmware to v9 or the newest one v11 included in driver 365 and your leds will be darker how they are supposed to be (same brightness as Formula v2).
Apologies- the way you phrased that made me think that the LED brightness WASN’T changed between the firmware updates. Anyway, like I said this brightness level is quite useful, so I hope we’ll be able to adjust it back to this level in the future.
I just discovered the BME Software Package v1.2, and it includes a v1.24 version of Fanalab. As a BME user should I be using this 1.24 version of Fanalab, or 1.23?
I am totally lost on what the latest drivers, firmware, BME and Fanalab is and how to install them.
Should I do thw whole install with older drivers as described here in the PBME thread?
Or can I go ahead with newer drivers and follow the same procedure?
Use the latest driver 365 and Fanalab 1.24
Is there a way to get Fanalab working?
I have searched this forum for a solution,but could not find anything working.
I have tried different versions Fanalab and different drivers but only see startup screen and then nothing.
I use Windows 10,fresh installation.
I see a lot of complaints about this issue,but no solution so far.
Hope anybody can help me out,
I think the strategy of primary announcement and distribution of software, firmware, and drivers via the support forum format is simply untenable. A simple, accessible webpage with a compatibility matrix is really necessary here, at a *minimum*. Depending on the products, the user needs to (at most) juggle Fanalab, the driver, the WB firmware, WB Motor Firmware, Wheel Firmware, and Hub firmware. That's 6 (!!!) pieces of software/firmware that a user can ultimately mix and match as they please. And on top of that it's all being managed via the forums. This is a recipe for disaster.
I think Fanatec deserves our patience, but at the same time I sincerely hope that this is only temporary and isn't the long-term plan. The entire software/firmware strategy needs a complete overhaul. This isn't working.
I agree, I am for sure no IT specialist,so a bit more clarity on the software side is welcome.
When I do a firmware update (after a full read on the topic) I say a bunch of Hail Mary's and press flash..
I'm having a problem of compatibility between Fanalab and Rfactor 2 Dedicated Server. Whenever I try to launch the dedicated server from the launcher it crashes. Removing the fanalab plugin from Rfactor 2 solve the problem. How can I run the Dedicated Server using Fanalab?
Will Fanalab be updated to include AMS2 when the sim is officially at version 1.0 ? Thanks
@ Maurice Böschen , I just swapped out my clubsport V3 pedals for Heusinkveld Ultimates. Am I still able to use Fanalab for iRacing along with my Porsche Podium Wheel?
It seemed to work ok just plugging in and playing and selecting my normal profile, although it said "pedal mismatch"
Am I able to delete the pedals from my profile and just use the profile in Fanalab for the Porsche Podium Wheel and F1 Wheel with DD1?
Well, this is really, really annoying. Just installed Fanatec Drivers, 356 and 365, and Fanalab 1.24 on an old 2006 laptop. Originally Windows Media Creation and upgraded to Windows 7 5ish years ago. Very little drive and programme maintenance at all.
Fanalab runs perfectly!!
The only error in the FLControl.log is that Steam app cannot be found - as I didn't install it!!
So come on Fanatec, please get the Windows 10 problems sorted and/or advise on what the issue is??
Why did you install 2 different driver versions? Only one driver is needed. With 2 drivers there it can cause problems. Always uninstall the old driver, reboot and then install the new driver.
I installed 2 drivers separately to try them, uninstalling the other, so there was only one at a time. Rebooting after every install/uninstall.
I've now installed on a small 2015 Lenovo with W10 Home 1909 and 365/1.24 again runs perfectly. So on 2 32bit PCs it all works.
So, I've just removed all Fanatec software, restarted and started again with 365 and 1.24. Fanalab doesn't run.
The FLcontrol.log indicates, well to me as a non computer guy, an issue with ITM:
05/28/2020 05:48:55.794 | ERROR | PCUtilRegistry::GetRegistryValueCurrentUser [int] | Subkey: SOFTWARE\Endor\PodiumSuiteName: ITM | System.NullReferenceException: Object reference not set to an instance of an object.
The full file is attached.
Who has written this software??
From the error message it seems like your Windows Registry is missing a value. Did you do this step?
"Open the "Enable_ITM.reg" file in the "FanaLab_v1-24_beta" folder and accept the messages with yes."
(From the 'Instructions.xtx' in the .zip with Fanalab 1.24)
Thanks. No I hadn't run that - but I didn't on the other 2 PCs where FL works just fine. Perhaps a 64 bit thing?? Thought the instruction was for the BEM.
Anyway, ran it, rebooted, and FL splash, crash. FLControl has a new error, ITM has gone:
05/28/2020 06:42:02.067 | ERROR | WindowMain::PrivateUnhandledExceptionHandler | Message: Unable to load DLL 'dll\GameTelemetryExtractor.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E) From: Void GteDllGameLaunchDetectStart(System.String, Int32, CallbackGameDetectorStringParam) HResult -2146233052
So now hunting for that dll, but some progress. Thanks again.
Found GameTelemetryExtractor.dll in the Program(x86)/Fanatec/Fanlab folder. Which is where I guess it should be??
Well, the telemetry error has now gone. I copied the telemetry dll to both SySWOW and System 32.
I now get new errors:
05/28/2020 10:05:31.152 | ERROR | PCUtilRegistry::GetRegistryValueCurrentUser [int] | Subkey: SOFTWARE\Endor\PodiumSuite\Led\ThreeDigitName: iRPM | System.NullReferenceException: Object reference not set to an instance of an object.
at PodiumControl.PCUtilRegistry.GetRegistryValueCurrentUser(String Subkey, String Name, Int32& Value)
05/28/2020 10:05:31.616 | ERROR | PCUtilRegistry::GetRegistryValueCurrentUser [int] | Subkey: SOFTWARE\Endor\PodiumSuite\Led\ThreeDigitName: Fuel_I | System.NullReferenceException: Object reference not set to an instance of an object.
05/28/2020 10:05:33.659 | ERROR | PCUtilRegistry::GetRegistryValueCurrentUser [int] | Subkey: SOFTWARE\Endor\PodiumSuite\Led\ThreeDigitName: Gear | System.NullReferenceException: Object reference not set to an instance of an object.
So, a hunt through the registry and compare with a running PC.
Think Fanatec should pay me for more than beta testing - or how about free carriage - Deutsche Post will do - on a set of Button caps??
After a day faffing about installing and uninstalling drivers/software/repair software in various combinations plus trying to do a repair install of W10 1909, which was refused as W10 2004 is now available. But not available for my PC - Microsoft Surface Laptop 3. So what the hell is Microsoft up to if they release 2004 and their own machines can't repair/update?? If anyone from Redmond reads this, grateful for some help on that one.
However, I seem to have 2 error messages:
With DD1 etc switched on:
+------------- FanaLAB START-------------+
| FanaLab V1.24 BETA 19/12/2019 |
05/28/2020 14:57:22.744 | ERROR | PCUtilRegistry::GetRegistryValueCurrentUser [int] | Subkey: SOFTWARE\Endor\PodiumSuite\DeviceName: RimFormulaV2 | System.NullReferenceException: Object reference not set to an instance of an object.
05/28/2020 14:57:23.407 | ERROR | WindowMain::PrivateUnhandledExceptionHandler | Message: Unable to load DLL 'dll\GameTelemetryExtractor.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E) From: Void GteDllGameLaunchDetectStart(System.String, Int32, CallbackGameDetectorStringParam) HResult -2146233052
So GameTelemetry and V2 error.
Then with DD1 switched off, just the GameTelemtry:
05/28/2020 14:58:25.492 | ERROR | WindowMain::PrivateUnhandledExceptionHandler | Message: Unable to load DLL 'dll\GameTelemetryExtractor.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E) From: Void GteDllGameLaunchDetectStart(System.String, Int32, CallbackGameDetectorStringParam) HResult -2146233052
GameTelemtry is in the dll folder, just as on other PCs and V2 is fine on other PCs.
Good morning, maybe this was posted before but I feel very confused (or in wrong place).
I acquired the wheel base (CSL Elite 1.1) and Formula V2 wheel. I installed the 1v23 (Fanalab) and the V365 drivers. I'm an rFactor 2 user and I'm very interested in the telemetry data Fanalab can give.
I managed to get everything installed, but in game the telemetry LED's seem to not work. I installed the plugin and says installed correctly.
(Check the links I don't want the post to be huge.
After that I launched rF2 and activated the plugin.
So I decide to go on track and test everything and then the telemetry leds just don't work. Maybe I have to able other settings on rF2?
This is how the page looks like when I run rF2: https://i.gyazo.com/46abdbe773594d780b6cd6025c12bc81.png
This is how it looks like when I quit the game: https://i.gyazo.com/323949c79630b2f2b8db9af670fda31f.png
If you can help me to solve this I will be very thankful for it!
For CSL bases, I think you have to use v347 (https://forum.fanatec.com/discussion/1058/fanatec-beta-driver-v347-for-csl-csw-all-wheels/p1) and Fanalab v1.12 for the moment (https://forum.fanatec.com/discussion/1056/fanalab-1-12-available-post-feedback-here/p1)
I all I am having trouble with this version so i am running
PC Driver 352
WB FW 669
SW FW 28
The issue I am having is when i turn on Iracing my fanalab is not responding correctly, however if i turn off my wheel and turn it back on it works.. but i have to do this each time which is very frustrating if truth be told. the program worked fine but i had 30 days off and came back and was doing this, so i am assuming it throwing a wobbly on me because i went walkies :D is anyone a having this issue? has anyone solved it and is this known to fanalab/Fanatec software?
I've tried both v1.23 and 1.24, same issues others have reported where the program acts like its starting but doesn't appear.
I've noticed though, that even though there is no icon in the task bar, it is showing as running in Task Manager... When I select the option to "switch to" my graphics cards go haywire and then my computer restarts. I think there is way too much going on with fanalab with the GPU.
I am running; i9 9900K, RTX 2070 Super, 16gigs of memory. Fanatec drivers 365 (fresh installed twice). Peripherals are; DD2 w/formula V2 and advanced paddle module and v3 clubsport pedals.
I've since uninstalled fanalab all together until the next release.
Have you tried repairing the driver? It’s possible that a Windows Update was performed and running the repair should help.