Mine opens up at Profile 2. I change to profile 1. Close it, use the wheel, shut down. Then next time i restart, it opens up on Profile 2 again, even though the last one I used was Profile 1.
When you say "Profile 2", do you mean "Index 2"? If you have saved a profile and marked it as the default profile then Fanalab will automatically change to the setup index of that default profile.
I dont use Fanalab. This is in the Drivers. Where you click tuning menu on the left. Then Advanced Mode. Then you have 5 profiles which they call: Set 1, Set 2, etc. Each one is different tuning presets that you can save for different games, etc. Each time i restart the power to my DD2 wheel base, it starts up with "SET 2" checked off, I switch it back to "SET 1" in the tuning menu.... Then after I'm done, I shut down the power, when i go back to turn the DD2 back on, it once again starts up with SET 2 checked off. It forgets which tuning profile I was using the last time and constantly goes back to starting in "SET 2"
I see now, sorry about that.
Have you tried setting it in the wheel itself, rather than in the software? Just a thought. Prob won't make any difference.
I have figured out why!
It will never remember the last used tuning profile if you turn off the wheel using the E-stop button instead of the power button underneath it!
All figured out.
Hi Folks. In all Driver Versions later than 4.02 CSP V3 manual mode won't work. It can be enabled but disables itself after closing the control panel (CSW V2)
https://www.youtube.com/watch?v=XF_F1UMdaSs worked for me
instead of me just bitching... is there a debug mode I can put my DD2 into to help troubleshoot?
I can then collect the data gathered when I plug my GT2 wheel in and turn it 90deg to enable high torque mode... as screen just blinks and stays at low torque mode... surely there is some data there that can be collected and be sent over to you since you are unable to replicate issue.
I can turn each of these wheels/bases 90deg to enable high torque mode fine...
Hi, I have exactly the same problem as Malcolm and others. It started to do it after updating to 411, after updating to 415 it's still the same. Please fix it quickly. Thank you. Podium DD1 + Porsche 911 Gt3 R.
When you upgrade to a new driver on DD2 should you do a new motor calibration?
no. only after a motor firmware update a new motor calibration would be needed, if you like the result of the current motor calibration method.
Any hint on how we could reproduce it would be immensely helpful. For example if its only happening in a specific mode or if it makes a difference how things are booted up or if USB is connected or not and other things that might be able to be different.
Not sure why we should be ashamed by something weird happening for some people. If this would be happening for everyone and we missed to detect it then I would understand your point, but with the current situation I don't understand your point. In case you are bothered by the issue, use the previous firmware where it worked fine.
Remco is only helping out part time as far as I know, you can contact Dominic Brennan:
we could reproduce the issue and will take care of it
We've tried to reproduce this issue with the same hardware you have and driver 415. We've tried with turning base off/on, restarting PC,re-plugging USB and re-opening the driver but in all cases the seq Shifter was always still mapped to the shifter paddles. Is there maybe more to it which we need to do to re-create the issue?
I also love the trophy trucks of iR and would also hope the sessions would be less empty.
By the way as another maybe more comfortable workaround you could map the SEQ shifter for the trucks with the individual mapping and check the box for saving the options per car.
While the base is plugged in and running, use the repair function of the driver installer.
Does the base boot up and work fine besides the issue you mention?
Does going back to the driver which it worked with before help?
Maybe, lets give it a try. Normally the driver logs shouldn't catch what might be going wrong here because the issue is not caused by the driver but by the firmware. As people said its also happening when not connecting to the PC so without influence of the driver.
Which wheel base, which firmware, when did the issue started happening or what did you do before it started to happen?
Is the base in the correct PC mode? Maybe its in Xbox or PlayStation mode.
In case its in the correct mode, did you already try running the repair function of the driver installer while the base was plugged in and running?
Which error message, can you share a screenshot?
Any error message or is the updater not opening?
E-stop is for emergency, it will shut off the base immediately without saving things.
please provide info on how to do this rollback and I'll be gone
sigh try to downgrade and I'm back here again
ok used the FwClubSportBaseUpdater.zip that was previously supplied and reverted back... all now working again.
Thanks Marcel, will do so.