Jump to content
Want to report an issue? Have a bug to report? Please look here first!!!! Read more... ×
Christmas Period - Codemasters Staff and Support Read more... ×

Archived

This topic is now archived and is closed to further replies.

F1 2017 Crash on joining multiplayer lobby

Recommended Posts

Every time I'm in a custom lobby with other players, it either immediately, or freezes for a few seconds, before crashing to desktop with no error message. I tried joining my friend's game, hosting my own game, or joining a public game. It always crashes to desktop. I can join an in-race game just fine and spectate. I can host my own lobby without anyone fine (but as soon as someone joins, it crashes). Time trail works just fine. I have tried reinstalling 3 times, validating games every install. I have a crash dump file which I don't know how to upload on to here.

My specs is as follows:
4790K
1070
16gb

I have a laptop with the following:
7700HQ
1060
8gb

My laptop works fine, plays online without a hitch. 

Any ideas? Thank you!

Share this post


Link to post
Share on other sites
@cheekymunkey78 suggestion is to alter your career driver or start a new one.

Please post your findings here

http://forums.codemasters.com/discussion/132428/f1-2017-crash-to-desktop-ctd-on-joining-pc-multiplayer-lobby-patch-1-13#latest


Share this post


Link to post
Share on other sites
I found the solution.

Enter the Windows Defender Firewall with Advanced Security. Check and make sure both Inbound Rules and Outbound Rules contain a rule for F1 2017 which are "Allow". I didn't have one for Outbound, so I made one, directed to the  "F1_2017.exe" in the install directory. 

Problem solved!

I also had a weird issue where the game had problem performing first time setups (kept giving "This installation package could not be opened” error). The fix for that was to move the install directory local C drive. Having the game at local D drive kept spouting that error. Just putting this out there.

@cheekymunkey78 suggestion is to alter your career driver or start a new one.

Please post your findings here

http://forums.codemasters.com/discussion/132428/f1-2017-crash-to-desktop-ctd-on-joining-pc-multiplayer-lobby-patch-1-13#latest


My problem is slightly different from his. From his wording, it seems the problem goes away after restarting PC. Mine does not, mine can't get into a multiplayer lobby no matter what I did.

Share this post


Link to post
Share on other sites
This is not a solution. Your machine is incorrectly configured. The Windows firewall exception is created automatically. If you use a third-party firewall, sharing the information may be helpful.

I would suggest that choosing C:\ as an install path is a workaround for bad programming. The game should be able to use system variables to find files regardless of the actual filepaths used.

But just because you can install to different drives doesn’t mean anyone should, as for various reasons performance might suffer.

Share this post


Link to post
Share on other sites
This is not a solution. Your machine is incorrectly configured. The Windows firewall exception is created automatically. If you use a third-party firewall, sharing the information may be helpful.

I would suggest that choosing C:\ as an install path is a workaround for bad programming. The game should be able to use system variables to find files regardless of the actual filepaths used.

But just because you can install to different drives doesn’t mean anyone should, as for various reasons performance might suffer.
"Your machine is incorrectly configured". I am not using a third party firewall, nor have I done any tweaks to the default firewall. The game simply did not make a rule automatically. So yes, it is a solution for those that have this same issue.

Yes, choosing C:\ is a workaround, but until a better proper solution is found, this is what I know that fixed the first time setup issue. Which from nearly an hour of googling, no one had any solution to the problems I had.

Share this post


Link to post
Share on other sites
This is not a solution. Your machine is incorrectly configured. The Windows firewall exception is created automatically. If you use a third-party firewall, sharing the information may be helpful.

I would suggest that choosing C:\ as an install path is a workaround for bad programming. The game should be able to use system variables to find files regardless of the actual filepaths used.

But just because you can install to different drives doesn’t mean anyone should, as for various reasons performance might suffer.
"Your machine is incorrectly configured". I am not using a third party firewall, nor have I done any tweaks to the default firewall. The game simply did not make a rule automatically. So yes, it is a solution for those that have this same issue.

Yes, choosing C:\ is a workaround, but until a better proper solution is found, this is what I know that fixed the first time setup issue. Which from nearly an hour of googling, no one had any solution to the problems I had.
If the game creates the firewall rule automatically then your difference is not installing to C:\

It's a bad assumption to make by the developers, but if you choose not to go vanilla on installs then there be demons. Maybe if the install runs a script then it maybe could not complete the install by not finding files in places to register them or them being in non-standard paths. Is it Steam not installed to C:\ ?

Which installation packages gave errors? I think a first run installs DirectX, Kinect Speech Libraries and possibly other MS runtime libraries depending on the Windows version (7 may be different to 8.x and 10).


Share this post


Link to post
Share on other sites

×