Cant open F1 24

[evil_mercenary]

unfortunately, Logitech GHub 2024.4 hasn't made a difference in my instance, nor the others on discord

[cdm_slumbdog]

---

@Crusader765 wrote:

I just bought the Steam version and have no issues running the game at all. Part of the reason people pay for EA Play Pro is to play games ahead of the release date. EA should really just give vouchers to EA Play Pro members to buy/play the game from Steam at this point. 

---

That's interesting - you are unable to play the EA Play Pro entitlement, but can launch on Steam. That's good and bad - good you can play the game and that you aren't having the issue some others are. Bad that the EA Play Pro entitlement was causing problems, I can follow that up as it will be tracked elsewhere. I'll share what I learn. Thank you for coming back to post about your experiences. 

[cdm_slumbdog]

---

@evil_mercenary wrote:

unfortunately, Logitech GHub 2024.4 hasn't made a difference in my instance, nor the others on discord

---

Sorry to hear that. Rules out the Logitech known issue and moves us on to other things that will take more investigation. Is anyone getting a ".running" file created. It would persist after a crash, but if it isn't making it then that tells us when in the application start up we are failing to initialise. 

[Karlo3110]

@cdm_slumbdog group of us tried couple of things in discord.
We all have different manufacturers of gpu (not gpu related)
Some of us have UEFI on and some off (not boot related)
Not cpu related .. basically we can say it is not component related.

Next.. we have talked about logitech. Tried uninstalling it and reinstalling.. different versions and nothing helps. Not logitech related for us (had to make sure just in case).

We have talked about inputs in the pc (not input related)

We have tried reinstalling AC and installing all certificates and giving ownership rights to the ac but nothing happens.

Why I think it is AC related is because every time I press verify game files it finds 3 files (ALWAYS THE SAME) and it says that it will be reacquired.
Files are: EAAntiCheat.GameServiceLauncher.exe, EAAntiCheat.GameServiceLauncher.dll, preloader_l.dll

They get downloaded but after download when I press play same thing happens. If I try to verify my files again on the steam it says that same 3 files are missing and it redownloads again.. basically infinite loop.

I strongly believe it is AC related since I had the exact same issue on installed FIFA. Uses the same AC.

In env viewer it says EAAntiCheat could not find origin directory.. all the pointers are pointing to the one thing (towards AC). I don't know how it is not related when multiple instances show that it is related and multiple logs show that AC is the issue. Can you deep dive into this?
Might there be a depricated path env variable set up in AC to look for something that does not exist? Are some of us, users, stuck in some cached cdn from steam and keep getting the same file?

I have tried enabling outbound connection on firewall but that doesn't help. Inbound are okay.

It is not AV connected at all. Disabled and still the same issue persists.

[atAJJ141]

@cdm_slumbdog Nope, no ".running" file created. I don't think the game even has time to "crash"

[cdm_slumbdog]

Such great detective work, much appreciated. 

• Can you check the version of EAAC you have installed?

• Navigate to C:\Program Files\EA\AC
• Right click EAAntiCheat.GameService.exe and go to Properties
• Click on the Details tab
• Report back the number listed in Product Version such as 0.0.6106184

Then, please try and start the game using a trace for us: 

• In Steam (or EA app) advanced launch parameters, add --traceid f1_20240529_<Username> where you can each put your Answers HQ username after the final underscore and run the game.  When that's done, please post here what string you chose after traceid  so we can look up if we have any more details on the crash. Please also give us the time you ran it in UTC so that we can check other crash reporting systems for more data. 

[Tasdefleia]

@cdm_slumbdog I found a solution that I already used with FC 24, also from EA Play Pro.
So the source of the problem is the EA App itself, I'm simply using Origin along with a modification that rejects the attempt to change to the EA App and suddenly the game launched for me.
I don't know if I can promote this here, but I think you are able to come to a solution, knowing that the problem is in the EA App.

Of course, I'm talking about my case, I don't know how about others, especially the users of Steam, but the message from Event Viewer which says that AntiCheat can't get the directory of Origin they had reminded me of this solution, so that's some indication.

[atAJJ141]

@cdm_slumbdog 0.0.6114120

[cdm_slumbdog]

---

@Tasdefleia wrote:
@cdm_slumbdog I found a solution that I already used with FC 24, also from EA Play Pro.
So the source of the problem is the EA App itself, I'm simply using Origin along with a modification that rejects the attempt to change to the EA App and suddenly the game launched for me.
I don't know if I can promote this here, but I think you are able to come to a solution, knowing that the problem is in the EA App.

Of course, I'm talking about my case, I don't know how about others, especially the users of Steam, but the message from Event Viewer which says that AntiCheat can't get the directory of Origin they had reminded me of this solution, so that's some indication.

---

I can discuss with the EA App team. I can see already the issue is being tracked internally. I'll report back if I learn more. 

[evil_mercenary]

@cdm_slumbdog this one's an interesting one - in my EA\AC directory it's listed as "Product version" "0.0.6114120".
in the F1 24 game install directory there is a separate version of the anticheat installer and files that are also of the version 0.0.6114120.

however, i notice when launching theyere is a *.exe_b file created.... are those of any assistance?

i've just used "--traceid f1_20240529_evilmercenary" based on your recommendations in steam.
i'm running it in UTC+1 (BST) and just finished attempting to load at the time of this post (0900 UTC/1000 BST)