Forum Discussion
@sleepaholic wrote:@EA_Atic Please find my DxDiag attached.
Thanks for the dxdiag - please confirm your X570 mainboard model and UEFI version please.
You have a variety of drives installed in the machine with odd drive letters - can I ask if Steam is installed to the default location?
There are connected pedals but no wheel I can see.
Also, your 32GB of RAM is it 2x16GB or 4x8GB and are the sticks identical matched?
Thank you for stepping up, @SteveJackson!
My mainboard model is MSI's "MPG X570 GAMING PLUS" (MS-7C37).
My UEFI/BIOS version is A.H0 (19.05.2022)
My pedals are connected via USB, my wheel as well, but the latter has been turned off when creating the DxDiag report. Also disconnecting the pedals does not lead to any success, unfortunately.
My RAM is 2x16GB and running in Dual Channel-Mode (DIMMA2 + DIMMB2).
My drives are regular SSD drives, just named slightly differently than the standard. I am trying to run the game via Origin,
Both, Origin and Steam are not installed on C, which is my Windows drive (if that is what you mean with "default" location). Nevertheless, Origin and F1 22 are both installed on the same drive (E in my case).
- SteveJackson3 years agoHero (Retired)
@sleepaholic wrote:Thank you for stepping up, @SteveJackson!
My mainboard model is MSI's "MPG X570 GAMING PLUS" (MS-7C37).
My UEFI/BIOS version is A.H0 (19.05.2022)
My pedals are connected via USB, my wheel as well, but the latter has been turned off when creating the DxDiag report. Also disconnecting the pedals does not lead to any success, unfortunately.
My RAM is 2x16GB and running in Dual Channel-Mode (DIMMA2 + DIMMB2).
My drives are regular SSD drives, just named slightly differently than the standard. I am trying to run the game via Origin,
Both, Origin and Steam are not installed on C, which is my Windows drive (if that is what you mean with "default" location). Nevertheless, Origin and F1 22 are both installed on the same drive (E in my case).Can you uninstall the main board driver from Programs and Features, reboot then install the v4 chipset driver.
https://drivers.amd.com/drivers/amd_chipset_software_4.08.09.2337.exe
DDU in safe mode then reinstall the Nvidia driver.
https://www.wagnardsoft.com/forums/viewtopic.php?t=4097
Don’t alter any settings in the driver, delete the hardware_sertings_config.xml before attempting to relaunch.
You might post your wheel and driver, consider using the RJ-12 cable as a workaround after first checking the pedals in the Fanatic Driver whilst it is USB. Do not connect the two cables at the same time, either USB or RJ-12.
- hoihman3 years agoNew Traveler
Support has been kind of ridiculous.
I submitted a report about the game crashing on my windows 10 PC since patch 1.09. The game crashes as soon as i press a button when prompted.
Now suddenly my case is closed and i get a message the my email is no longer monitored.
If i try to open that specific case in my cases, it just won't open at all. Is this how issues are dealt with? just close them & igore them? and hoping it goes away.
Why is there no "quick fix" when more people affected and this is a game breaking issue? - SteveJackson3 years agoHero (Retired)
@hoihman wrote:Support has been kind of ridiculous.
I submitted a report about the game crashing on my windows 10 PC since patch 1.09. The game crashes as soon as i press a button when prompted.
Now suddenly my case is closed and i get a message the my email is no longer monitored.
If i try to open that specific case in my cases, it just won't open at all. Is this how issues are dealt with? just close them & igore them? and hoping it goes away.
Why is there no "quick fix" when more people affected and this is a game breaking issue?Because it’s your issue. Patch 1.09 would have to break a lot of machines and the fact is it did not.
- 3 years ago
@SteveJackson I tried all your suggestions, Unfortunately, the game is still not launching.
My wheel is the Fanataec CSL DD, driver 445.
- 3 years ago
@EA_Atic Is there any update from your side? What is the timeline regarding an official fix for the launch/boot issues that is currently being worked on?
- SteveJackson3 years agoHero (Retired)
@sleepaholic wrote:@SteveJackson I tried all your suggestions, Unfortunately, the game is still not launching.
My wheel is the Fanataec CSL DD, driver 445.
Can you repost the updated dxdiag?
Do you have the page file disabled or set at automatic?
Do you have any third party AV software installed or is Protected Folder access enabled in Windows Security?
Do you get any error messages or just a hang? Video may help
- 3 years ago
@SteveJackson Please find my update DxDiag attached.
Ironically, there are many more errors than prior to trying to fix the F1 22 related issues ☹️
The game is not launching with neither page file enabled nor disabled. Also smaller or bigger page file sizes do not change anything. Neither does setting it to automatic size or manually choosing values.
No 3rd party AV installed, no protected folder in place. On the contrary: F1_22.exe + the whole F1 22 game directory where excluded from protection in windows security. Also, completely disabling the firewall does not help.
When launching the game (as administrator or not results in the same), I do not get any error message. What happens?: I start the game (launcher = Origin), a selection screen appears (Play F1 22 OR Play F1 22 VR), I select Play F1 22, A black screen appears for up to ~5 seconds, there is no sound, the black screen disappears, I am back on my desktop with Origin open. That's it. (Sorry, but currently, I am not able to record a video).
When selecting "Play F1 22 VR" I get the error message "VR initializatin error. Installation path could not be located (110)." - I don't have any VR setup in place, so that might be the reason, but I am not sure about that.
Edit: Actually attaching the file 🙂
- 3 years ago
@EA_Atic Is there any update from your side? What is the timeline regarding an official fix for the launch/boot issues that is currently being worked on?
- 3 years ago
@EA_Atic Just to make it clear: Also today's hotfix did not help to fix the issue, unfortunately.
- 3 years ago
@EA_Atic Why do we not get even the slightest of an update from your side?
- 3 years ago
The game is still not launching for me. When can we expect an update?
- 3 years ago
Another day without the ever so slightest sign from EA. I am flabbergasted by this utter lacker of interest.
- 3 years ago
Why is there no update?
- 3 years ago
@EA_Atic, @EA_Barry, @CM_TGK @EA_Kent @jenny_a_m When can we expect a resolution of this issue? Could anyone of you please provide an update?
It has been a month now since i have bought the game and all i have seen until this point is a black screen. Wonderful!
- 3 years ago
Please find my update DxDiag attached.
Have you found any solution to this?? Been trying to talk/ & get help from EA but no response. All i get is wait & watch. How stupid is that.
Same issue as yours 👇
When I launch the game (as administrator or not results in the same), I do not get any error message. What happens?: I start the game (launcher = Origin), a selection screen appears (Play F1 22 OR Play F1 22 VR), I select Play F1 22, A black screen appears for up to ~5 seconds, there is no sound, the black screen disappears, I am back on my desktop with Origin open. That's it. (Sorry, but currently, I am not able to record a video).
When selecting "Play F1 22 VR" I get the error message "VR initialization error. Installation path could not be located (110)." - I don't have any VR setup in place, so that might be the reason, but I am not sure about that.
- 3 years ago
@EA_Atic Do you have any update for us?
- 3 years ago
Bump.
- SteveJackson3 years agoHero (Retired)
@abhishekvora045 wrote:Please find my update DxDiag attached.
Have you found any solution to this?? Been trying to talk/ & get help from EA but no response. All i get is wait & watch. How stupid is that.
Same issue as yours 👇
When I launch the game (as administrator or not results in the same), I do not get any error message. What happens?: I start the game (launcher = Origin), a selection screen appears (Play F1 22 OR Play F1 22 VR), I select Play F1 22, A black screen appears for up to ~5 seconds, there is no sound, the black screen disappears, I am back on my desktop with Origin open. That's it. (Sorry, but currently, I am not able to record a video).
When selecting "Play F1 22 VR" I get the error message "VR initialization error. Installation path could not be located (110)." - I don't have any VR setup in place, so that might be the reason, but I am not sure about that.
This looks like an EA Account issue at least. It's literally saying Another User owns the game, it does not have sharing on either Origin or Steam. Only the original account holder can play. If it is the correct account then only EA can fix that.
I haven't looked at the dxdiag because of that.
About F1® Franchise Discussion
Recent Discussions
- 21 hours ago
- 3 days ago
- 4 days ago
Weekly Warrior Trophy
Solved16 days ago