No Logitech PRO RACING WHEEL support?
Hello, I don't see the Logitech PRO RACING WHEEL anywhere in the list of compatible wheels. This wheel was compatible with F1 2022. Will there be no official support for this wheel in the game? In ...
Forum Discussion
@ScarDuck14 I don't have any issues with our new CM personally. I have issues with the job he's being told to make us do.
Let's just take the volumetric fog issue as an example. It was something I noticed the first time I sat in the car. Immediately. It was not an obscure issue, which means that if EA does any in-house testing at all, it would have been noticed.
With just that information, you can either conclude that they don't test, or that they didn't care.
Two and a half months later, a patch comes out claiming to fix the issue. Customers immediately notice that it isn't fixed. Presumably now we get to wait at least another 2-3 weeks for that to maybe be allegedly fixed again.
What's the conclusion now? Unless one believes that they simply lied in the patch notes, the only conclusion still remaining is that they again didn't test it (or at minimum, they have a glaring problem with their QC pipeline).
As I said in the other thread, I used the quick reply function. It automatically tags people. I don't have a problem with Groguet. I have a problem with paying customers being used as the (apparently) first and only method of testing the product we paid for.
Whomever is instructing Groguet to ask those questions of us, instead of having a better workflow that includes internal (or external) paid testing, needs to know that it isn't our job to test their work and that it is not acceptable.
I'll say it a final time to be clear: I do not hold Groguet responsible for this nonsense.
Let's just take the volumetric fog issue as an example. It was something I noticed the first time I sat in the car. Immediately. It was not an obscure issue, which means that if EA does any in-house testing at all, it would have been noticed.
With just that information, you can either conclude that they don't test, or that they didn't care.
Two and a half months later, a patch comes out claiming to fix the issue. Customers immediately notice that it isn't fixed. Presumably now we get to wait at least another 2-3 weeks for that to maybe be allegedly fixed again.
What's the conclusion now? Unless one believes that they simply lied in the patch notes, the only conclusion still remaining is that they again didn't test it (or at minimum, they have a glaring problem with their QC pipeline).
As I said in the other thread, I used the quick reply function. It automatically tags people. I don't have a problem with Groguet. I have a problem with paying customers being used as the (apparently) first and only method of testing the product we paid for.
Whomever is instructing Groguet to ask those questions of us, instead of having a better workflow that includes internal (or external) paid testing, needs to know that it isn't our job to test their work and that it is not acceptable.
I'll say it a final time to be clear: I do not hold Groguet responsible for this nonsense.
@TrekariI don’t think Groguet has been told to ask us. I’m going to take a punt as he hasn’t told me one way or other. But he’s asking us. Because we are quicker and more thorough at testing the game:, More information he can give to Codemasters should mean they can’t say theres no issue and also aid them in finding what’s wrong and hopefully fixing it quicker without it leading to more bugs.
End of the day just because coders code this game doesn’t mean they play or even like F1 games. We on the other hand know the game inside out.
Do I like being a beta tester? Hell no. On the old codemasters forums I made many many posts criticising codemasters for same problems we face now. But the devs are like us. They go on to work to pay the bills. They can only work within the resources and time allocated to them by non gaming money hungry board members
Also as the EA community team are the middlemen that communicate with us and codemasters. The only posts other than bug reports that codemasters see are constructive criticism or suggestions. Anything that is aggressive in tone won’t be:
