i not sure how this spin is possible because it should be limited from firmware self, i quess they not have limitation build in, soo if something goes wrong then you may lose you hands
or there is somesort bug at firmware, that in some cases if something goes wrong with software it drives firmware self totally nut
Managed to fix it after a few repairs, install kept hanging complaining some other software was interfering with the installation although i didnt had anything else related running, after a few restarts and repairs all became ok in this regard. Only used AC,ACC and rF2 and had no issues with FFB unlike some other people. Something might be off too with their initial instalation.
If you have to correct something, you have worked sloppy beforehand and this does not testify to quality ... If you deliver reasonable work, you don't have to repair mistakes and that testifies to quality and stability ...
Wow thank you for the hotfix. I thought the issue was the new F1 23 patch because it was only happening in F1 23 and not ACC, R3E or RF2. I was getting ready to write them a harsh comment on it. You saved Codemasters from hearing it lol
Dude lol, no ones perfect. They released a quick hotfix thanks to us being understanding and providing them with the quick and proper feedback, get a grip lol
This fix would not have been necessary at all if you had worked properly ... unfortunately it is not the first time and that is the bad thing about it ...
welcome to the world of software development..... its going to happen. the fact that they worked on in and fixed it immediately is a big thing! There will always be bugs, and as the firmware gets bigger, more is going to be missed and more bugs will be introduced - mainly because not every scenario will be tested. It sucks, but thats just how it is these days
Tested F1 and DR2.0, both now working properly with alt-tab. Thanks for the quick fix!
Also fully agree about the undeserved backlash. As the first person to report this issue with v453, I commend the team for jumping on a hotfix faster than expected. Oversights happen, it sucks but effort was made to correct very quickly upon discovery. There are certainly times where pitchforks can be at the ready, but this one isn't it.
Well then, congratulations on this attitude ... just good that the software developers of other companies do not think and work more carefully before they let go of their products ...
You think its the actual developers that get a say in when something is released? Its the higher up management that say when something gets released - and more often than not are TOLD to release something, knowing that there are bugs that will be fixed later.
Sometimes there are massive show stoppers - which no one outside of the dev team thought about/considered. It happens due to siloing/deadlines or just some other reason.
Its not an attitude - its how it works. Maybe get a job in software development, and you give it a try?
What you describe is called "bad management", nothing else ... there is nothing to talk about ... I don't work for a company that forces me to cheer me on something faulty and the customer in the end only has trouble ...
Let Ma be good, I prefer to give my workforce someone who appreciates my work and wants to have peaceful customers and not just the customer's money ...
you are mixing up workers and management. Workers probably want to do the best job they can. Being forced to do something, even when the workers object to it - thats what happens in a lot of companies - because money.
Just to be clear, i dont condone this behavior. Its the way it works. Codemasters, EA, Microsoft - any company that produces hardware/software that CAN update at a later date - all go through the same thing.
Im glad you work for a noble company that will not face the wrath of angry customers due to something being delayed.
Its not just software development - it happens all over. Im guessing youve never rushed a report/presentation? or did you just tell management that you need to push the meeting back because you were not ready.
Searching the logs I found that there was a conflict with other USB devices. I disconnected all of them and only left the whel base, so when I tried again, I updated without problems.
I am a software developer. I spent my entire day prepping for a release and fixing bugs. I have a deployment to do in 2 hours.
I got my DD1 yesterday and only had time to test for 30 minutes. I was excited to give it a whirl again today but noticed the new driver prompt so I tried to install.
Errored out twice. I am not in the mood to debug :')
Anyone else having issues with this firmware update? Can't get it applied on any wheel (ie. McLaren GT3 V2, Formula V2.5X, etc). It immediately stops with error saying to power off and the cycle just keeps repeating itself. Windows is 100% up to date and nothing seems to get it to work, including multiple restarts.
Can you please use the "Collect Logs" feature of the driver and upload it here so the Dev can investigate why the update dies not work for you as in his testing the steering wheel updates are working fine on his CSW V2.5...
Also did you only tried the automatic update via the green update button or did you also tried a manual update? If not done already, manual update would be worth a try as well.
Now i heard from several people that the 454 driver update crashes during the update, is that just bad luck or is there a problem with the driver i don´t want to update if it´s faulty
Comments
Do i have to rollback Fanalab version when downgrading driver to 451?
i not sure how this spin is possible because it should be limited from firmware self, i quess they not have limitation build in, soo if something goes wrong then you may lose you hands
or there is somesort bug at firmware, that in some cases if something goes wrong with software it drives firmware self totally nut
Yes, newest Lab only works with driver 453 or newer.
Dude, we'll be on driver 628 by the time devices get delivered.
Any time frame on next version or quick fix? Few days or soon?
It's in internal testing and we will take our time to test it properly before we release it.
But should be later today.
Wonderful. Quick fixes should be released more often like this.
Managed to fix it after a few repairs, install kept hanging complaining some other software was interfering with the installation although i didnt had anything else related running, after a few restarts and repairs all became ok in this regard. Only used AC,ACC and rF2 and had no issues with FFB unlike some other people. Something might be off too with their initial instalation.
Driver 454 available
Fixing the alt+tab issues with some games causing loss of FFB and/or freezing the game.
Thanks for everyone raising this quickly and sorry for the hassle it might have created.
Great that was fast! I’ll test now.
If you have to correct something, you have worked sloppy beforehand and this does not testify to quality ... If you deliver reasonable work, you don't have to repair mistakes and that testifies to quality and stability ...
Wow thank you for the hotfix. I thought the issue was the new F1 23 patch because it was only happening in F1 23 and not ACC, R3E or RF2. I was getting ready to write them a harsh comment on it. You saved Codemasters from hearing it lol
Does anyone know why I can't update WQR to version 7?
Lol
Dude lol, no ones perfect. They released a quick hotfix thanks to us being understanding and providing them with the quick and proper feedback, get a grip lol
This fix would not have been necessary at all if you had worked properly ... unfortunately it is not the first time and that is the bad thing about it ...
welcome to the world of software development..... its going to happen. the fact that they worked on in and fixed it immediately is a big thing! There will always be bugs, and as the firmware gets bigger, more is going to be missed and more bugs will be introduced - mainly because not every scenario will be tested. It sucks, but thats just how it is these days
well, if this would be that easy then why the hell Microsoft releases the bug fixes all the time
Tested F1 and DR2.0, both now working properly with alt-tab. Thanks for the quick fix!
Also fully agree about the undeserved backlash. As the first person to report this issue with v453, I commend the team for jumping on a hotfix faster than expected. Oversights happen, it sucks but effort was made to correct very quickly upon discovery. There are certainly times where pitchforks can be at the ready, but this one isn't it.
Well then, congratulations on this attitude ... just good that the software developers of other companies do not think and work more carefully before they let go of their products ...
You think its the actual developers that get a say in when something is released? Its the higher up management that say when something gets released - and more often than not are TOLD to release something, knowing that there are bugs that will be fixed later.
Sometimes there are massive show stoppers - which no one outside of the dev team thought about/considered. It happens due to siloing/deadlines or just some other reason.
Its not an attitude - its how it works. Maybe get a job in software development, and you give it a try?
Also, why I can't update the WQR firmware on my CSL DD?
What you describe is called "bad management", nothing else ... there is nothing to talk about ... I don't work for a company that forces me to cheer me on something faulty and the customer in the end only has trouble ...
Let Ma be good, I prefer to give my workforce someone who appreciates my work and wants to have peaceful customers and not just the customer's money ...
you are mixing up workers and management. Workers probably want to do the best job they can. Being forced to do something, even when the workers object to it - thats what happens in a lot of companies - because money.
Just to be clear, i dont condone this behavior. Its the way it works. Codemasters, EA, Microsoft - any company that produces hardware/software that CAN update at a later date - all go through the same thing.
Im glad you work for a noble company that will not face the wrath of angry customers due to something being delayed.
Its not just software development - it happens all over. Im guessing youve never rushed a report/presentation? or did you just tell management that you need to push the meeting back because you were not ready.
anyway, very off topic. sorry
Searching the logs I found that there was a conflict with other USB devices. I disconnected all of them and only left the whel base, so when I tried again, I updated without problems.
I hope it is helpful
I am a software developer. I spent my entire day prepping for a release and fixing bugs. I have a deployment to do in 2 hours.
I got my DD1 yesterday and only had time to test for 30 minutes. I was excited to give it a whirl again today but noticed the new driver prompt so I tried to install.
Errored out twice. I am not in the mood to debug :')
Anyone else having issues with this firmware update? Can't get it applied on any wheel (ie. McLaren GT3 V2, Formula V2.5X, etc). It immediately stops with error saying to power off and the cycle just keeps repeating itself. Windows is 100% up to date and nothing seems to get it to work, including multiple restarts.
Dude you're just miserable and never happy lol. I'll pray for you.
Can you please use the "Collect Logs" feature of the driver and upload it here so the Dev can investigate why the update dies not work for you as in his testing the steering wheel updates are working fine on his CSW V2.5...
Also did you only tried the automatic update via the green update button or did you also tried a manual update? If not done already, manual update would be worth a try as well.
Now i heard from several people that the 454 driver update crashes during the update, is that just bad luck or is there a problem with the driver i don´t want to update if it´s faulty
Regards JMP