-
Content Count
5,350 -
Joined
-
Last visited
-
Days Won
2
Posts posted by steviejay69
-
-
I didn't watch that properly.
-
7 minutes ago, Ramonedagain said:Done it, i Want to play the game soon, o hope i get chosen.
You mean TEST the game?
-
2
-
1
-
-
7 hours ago, eMc0B said:It would be nice to see a new installment before its release in stores. I signed up. It doesn't hurt to try
🚗💨
And question out of curiosity: how many people are to be selected depending on the platform?
In previous years it has been 300 per platform. One year the pool was extended during the beta to increase the MP mode testing, but only for about the last 10 days I think.
-
1
-
-
14 minutes ago, Xanthus9986 said:I’m new to sim racing, I have the Thrustmaster Tx for Xbox one, tss Sparco mod handbrake is not being detected on Dirt 2.0. Is there anything I I'm doing wrong? I have it directly connected to the steering hub.
Apart from posting this in the F1 Technical Assistance? 🙂
The TX firmware should be v55 and there is a 1.18 firmware for the TSS Handbrake.
Connecting to a PC should allow you to update if you haven't already done this Thrustmaster - TTRS_2020_1
http://ts.thrustmaster.com/download/pub/webupdate/th8rs/TSS_Firmware_Update_Process_V118.pdf
You can also calibrate the handbrake on PC, that will then update the device for use on your console.
-
8 hours ago, MarcoRozema said:And still no update or fix?? Having the same problem with brake bias in RaceRoom
Then is this a Logitech problem rather than just a Codemasters one?
-
1 hour ago, pachedupdemon said:Glad you got it working, sorry you had to waste time on blanket guess work before that
None of the steps were wasted. They have worked for others and updating is almost always advantageous. It's not guesswork if it's based on the information provided. I'm happy for you to step up if you feel you have something to contribute, but it is the easiest thing in the world to be critical in hindsight.
-
3 hours ago, Ardent71 said:- I've been testing a bit and I honestly think it's maybe the Bluetooth headphones that were causing the issue. I've been playing with wired headphones and the issue hasn't been happening. It might take a few more days to confirm that though since the bug takes awhile to happen
When there is a secondary sound card, either USB or BT, it seems to cause issues of one kind or another. @BarryBL just something to take into the beta.
-
3 minutes ago, Ialyrn said:It sounds like you have messed around with the steam controller settings, so my advice would be to disable that in the game propherties. You do this by right clicking on the game in question and selecting "properties", and then under the "general" tab, changing "Steam Input Per-Game Setting" to "forced off". In this case, you would right click on F1 2019. This is most likely an issue with steam, since you state your wheel works in Dirt Rally 2.0. I was playing F1 2019 last night on a T300.
I should spend more time playing than in here. However, I've never had reason to even know that setting exists, so thanks 👍 205 hours in game, probably pales into insignificance compared to time spent here 🙂
-
8 minutes ago, CrashEd1664 said:Yep..
I'm not uninstalling DCS, its a 250GB multiple install. The error repoted is likely to do with its updater s/w...
OK, I understand but the type of error (BEX64) is related to DEP which can have system wide consequences.
Can you just temporarily try msconfig to stop it loading? Or delete (recycle) a startup folder shortcut (it can be restored) or manually export the registry key that loads it and then delete it? You can restore a registry fragment by double-clicking the exported file.
-
There is also a firmware update to v11, looking at your driver screenshot. There is a separate routine in the Thrustmaster program group for 'Firmware Update'.
-
1
-
-
Just now, CrashEd1664 said:Thanks, did all that but still no dice.
Did you spot the additional stuff I added?
1 hour ago, steviejay69 said:The name of the motherboard is not picked up, can you please add it?
Nvidia drivers are a known issue, please revert to 442.74.
Windows 10 is EOL May 12 2020, please use the feature update to 1909.
WER is highlighting DCS.exe (Digital Combat Simulator?) as a Buffer Overflow Exception, please uninstall it.
-
UEFI BIOS update 1903 (this is a legacy board last updated 2013).
Please take special care with regard to memory configuration 24GB is an odd size (Manual section 2.2.4 page 27).
If you can create an optimal 16GB configuration, try that also. Make sure you have left the page file setting as 'System managed'.
-
1
-
-
18 minutes ago, CrashEd1664 said:Thanks. Here you go.
The name of the motherboard is not picked up, can you please add it?
Nvidia drivers are a known issue, please revert to 442.74.
Windows 10 is EOL May 12 2020, please use the feature update to 1909.
WER is highlighting DCS.exe (Digital Combat Simulator?) as a Buffer Overflow Exception, please uninstall it.
-
2 minutes ago, CrashEd1664 said:Yeah I’ve done all of that, but it doesn’t appear in the game at all. In Dirt 2 it just worked.
As I said before the ONLY WAY I can get the wheel to respond in the game is by frigging it in Steam to make it look like an Xbox controller. It’s not a solution, I only did it to get ‘something’ working in the game.
Might just go back to 2018, at least that worked. I won’t be buying 2020...
Listen, I have the same wheel. It definitely works, so there is something on your system that is affecting it.
Post a dxdiag and I will take a look.
-
18 hours ago, DjMC said:Would you care to elaborate? I'm not sure what cloud save has to do with this anyway? If the game save in your user data folder's different you get an option to either upload that or download the cloud save.
My issue's trying to use a gamesave created with a different steam ID, unless having steam cloud enabled affected that?
I'm listening for the Codemasters response, but it's not as simplistic as just copying a file.
-
Yeah, don't run the game through GeForce Now.
And the fix for the 1070 is pinned above, revert the driver to 442.74. This came to light after you first posted.
-
20 hours ago, CrashEd1664 said:I have just purchased F1 2019 for Steam and I cannot get it to recognise my Thrustmaster T300RS wheel. I have just spent many hours trying to get it to work, unsuccessfully.I have installled the latest driver and firmware and windows 10 recognises the wheel. I have also purchased Dirt Rally 2.0 and the wheel worked first time, straight off the bat. So there is no issue with the wheel. The wheel is recognised in Steam. I can allocate functions to the buttons in Steam, however this sets the device up as an Xbox type of controller i.e. no FFB, just buttons and axis. It's pretty useless setup like this, however at least I can see an input from the wheel in the game. I've tried numerous USB ports (no hubs) and re-installing the game, but to no avail. I've also removed all uneccessary controllers. Zilch, nada, nowt, nothing...Your website says that the wheel is supported and there are many others using it, so in theory it should work. But it doesn't.To back up and expand on what @UP100 is saying, I think you are doing something wrong. If you installed the driver, the Thrustmaster Control Panel is installed, this is where you set up your wheel, FFB and DOR, etc. test calibration and axes response, update firmware etc.
Then the controller appears on the in-game menu as a control schema.
So I don't understand what you are doing in Steam, unless that is how people configure extra controller options. Welcome to the world of wheels.
-
21 hours ago, cedlaf said:1. I just bought a thrustmaster ferrari 458 wheel and pedal kit. When i plug it and open f1 2019, it will not let me use it. No buttons on the wheel is doing anything.
2. I dont see the version. Its f1 2019 on pc with steam.
3. I want to continue career mode as i played with a xbox controller before.
4. Its an ongoing issue. Just bought it.
5. On going issue.
6. I tried to change my keyboard binding for pedals and boutons on the wheel but no luck there.
7. Thrustmaster ferrari 458 wheel and pedals xbox version
8. No video
You need drivers for the wheel on PC. It's not just plug it in like on console.
The 458 Spider is an Xbox only wheel, it does not work on PC https://support.thrustmaster.com/en/kb/104-en/
The Ferrari 458 Italia is an emulated Xbox 360 controller https://support.thrustmaster.com/en/product/ferrari458italia-en/
As is the Ferrari Vibration GT Cockpit 458 Italia Edition https://support.thrustmaster.com/en/product/ferraricockpitf458-en/
Or you might actually have the TX Racing Wheel Ferrari 458 Italia Edition https://support.thrustmaster.com/en/product/txracingwheel-en/
You can see why we need people to be specific 🙄
There's even a 458 Italia add-on wheel, but I'm gonna assume it's not that....
-
4 hours ago, RAFAGF said:Yes, I run on Directx 11. I have tested at 59Hz too. I have also tested with another RAM memories, but I will run Memtest anyway. Do you guess it is incompatibility with A320 and my graphics card is Ok?
Quite honestly, IDK.
I know much more about hardware I've actually used or can test. Let's see what the Memtest returns. The only other factor might be the speed at which the RAM is running (2667MHz should be ideal). Can you tell me the name of the module so I can look up it's spec?
Can I just check you updated BIOS to F50 (or any above F40) via F32?
CPU temps seem ok (40-50) but is that idle or load, are you using Wraith Stealth (supplied with R5 1400)? It would seem OK for idle if you were but if that is under load then you're using some other CPU cooling (maybe WC)? Sometimes, the software for Corsair has been known to interfere with games.
Finally two of the dumps are USB 3 related - revisiting the dxdiag I can see a VIA USB 3.0 controller? Is that an add-in card or hub? Can you remove it for testing please?
Also if you can list the USB devices - keyboard and mouse I get (try using the USB 2.0 connectors on the rear panel under the LAN port) also a device with vendor ID Gear Head? And the CMI sound device I believe is a headset? - remove this also. Also, front USB will be 2.0 if you used twin motherboard headers (12 on mobo layout in manual), they will be USB 3.0 if using the USB composite (11).
But I am unsure. If you list any add-in cards, connected USB devices and where; that might be easier than me trying to translate lots of Portuguese and looking up VEN/DEV IDs.
But hey, you've improved the cooling on the R7 370. We've got some bonus!
-
3 minutes ago, neonpa said:I have encountered a problem (or maybe I just noticed it now), anyhow, when the car on screen is stationary everything looks great. But as soon as I go into motion all the white lines on track start to flicker... does anyone know of a setting or something like that?
Can you post a bug report and video?
-
54 minutes ago, Pawel567 said:
Most likely your graphics card or motherboard has gone wrong. I would advise you to buy a new one.Most unlikely until we exhaust the options!
-
Can you physically look at the mainboard?
There are 6 possibles for B85M-D3H (rev. 1.0/1.1, 1.2, 2.0 and 2.1 and A rev 1.0).
We will go with updating the BIOS and then memory testing.
-
If I could add some experience of what I have seen to be the KEY FAILINGS of PREVIOUS BETAS (17, 18, 19)
To all the participants
The quality of your feedback is important - if I look at a sample of bug reports posted in the TA forum currently, it is very NOISY!
It will not win you favour by trying to find the most bugs. It is not a competition and there is no prize.
It helps if you complete the bug template, every time on a new bug, and you state what you have tried to prove it is a bug and not just a kink in your setup. Replication is important.
It helps if you can confirm and add evidence to exisiting bug reports. You can even disprove them, or say how you found a solution.
It helps if you do not jump in and out of Multiplayer lobbies looking to race elsewhere or when you crash out. Spectate and rejoin the session at the next race. Stay connected.
We do not need endless posts about people's thoughts about the game. It is a BETA. You will be asked your opinion so save it, and take the opportunity at the end of each focus period (usually a week). Far more chance of it getting read then, than lost in hundreds of (hopefully) quality bug reports.
Look for similar bug reports and add to them. Find and confirm bugs in your current game are fixed!
To the moderators (keep reading participants)
Sorting the wheat from the chaff - merging threads and deleting (or dumping posts) is key to retaining focus. I hope you have some kind of standard message to send to a user informing them that their post has been removed due to being incomplete, not contributing or spam.
Consider removing those from the program that have difficulty signing up. It is no good having people who cannot communicate what they have found or are not technically minded enough to do the simplest things like sorting out emails and usernames.
In the end
To be a beta tester you should be able to produce diagnostic information;
the Report Code
a dxdiag, a crash dump, hardware settings file
the ability to take and share screen dumps, post video to email or share privately (not unlisted) on YouTube (visible to only yourself and the Codemasters beta e-mail address)
a detailed description of how to recreate the issue
DO NOT sign up if you just want early access to the game - you will be disappointed, the game is not usually made fully open, you will get specific modes and be asked to use them for a period of time. If you can find and quantify ONE bug during this period it will be helpful. If you can confirm TWO others, that's great.
It will not be open all the time, you may have periods where you are locked out. PS4 users have previously snoozed the game to get around this. Don't bother posting errors, they don't count because the condition is not normal. It has been general that you have been granted access to play according to the time you log in. Codemasters, I suggest if you can somehow log people out of sessions automatically once an hour has passed beyond the sign-in cut off that would be good.
-
5
-
1
-
12
-
-
18 hours ago, perrune said:the OSW is listed as simu cube on the supported device list, but no reaction when trying to activate right/left
You'll get more luck here I think.

Samsung CRG9 / 49" / 32:9 Monitor (5120 x 1440 1000 HDR)
in Technical Assistance
Posted
Wouldn't try it on an Intel GPU if that's what you're asking.