JJP
Formula 4 2nd Driver
Hello guys,
As many of you know, when Project Cars 2 (and 1?) UDP protocol is enabled, it may mess up online lobbies performances and stability.
My technical explanation is that it is partially due to the nature of UDP (LAN broadcast), and partially due to some weird PC2 netcode, which somehow pushes those UDP packets to the whole lobby over internet.
So today I created a firewall rule allowing UDP for the localhost (the PC you're gaming on), but blocking it from going "outside".
On my tests, it worked perfectly.
Once the rule enabled, UDP telemetry application running on my PC is OK, while a dashboard app running on my phone is KO (OK without the rule).
I need to give it a try in an actual lobby when we get a practice session, but I believe it would be best if others test it at the same time. Anyone interested, please follow this how-to.
Keep in mind that it will break connectivity with apps running on separate devices (such as smartphone dashboard apps). Unless they rely on a server app running on the PC (this is getting too technical ...) acting as a relay.
First you need to know your LAN subnet IP and mask ...
For most it should be 162.168.1.0/24 or something similar.
If you have no idea what I'm talking about, give a try to those links, ask Google, and if still too complicated, PM me.
Then, onto the rule.
On Windows, run "wf.msc". It should open the firewall interface. Create a new outgoing rule.
Configure the rule as follows :
Rule type = [Custom]
Program = [All programs] (or go find pCARS2AVX.exe if you really fancy)
Protocol and Ports = [Type : UDP] / [Local Port : All] / [Remote Port : Specific - 5606]
Scope = [Local IP : Add your subnet/mask here] / [Remote IP : Any]
Action = Block
Profile = tick everything
Name = whatever you want
Once created, the rule should appear in the list and be enabled by default.
As many of you know, when Project Cars 2 (and 1?) UDP protocol is enabled, it may mess up online lobbies performances and stability.
My technical explanation is that it is partially due to the nature of UDP (LAN broadcast), and partially due to some weird PC2 netcode, which somehow pushes those UDP packets to the whole lobby over internet.
So today I created a firewall rule allowing UDP for the localhost (the PC you're gaming on), but blocking it from going "outside".
On my tests, it worked perfectly.
Once the rule enabled, UDP telemetry application running on my PC is OK, while a dashboard app running on my phone is KO (OK without the rule).
I need to give it a try in an actual lobby when we get a practice session, but I believe it would be best if others test it at the same time. Anyone interested, please follow this how-to.
Keep in mind that it will break connectivity with apps running on separate devices (such as smartphone dashboard apps). Unless they rely on a server app running on the PC (this is getting too technical ...) acting as a relay.
First you need to know your LAN subnet IP and mask ...
For most it should be 162.168.1.0/24 or something similar.
If you have no idea what I'm talking about, give a try to those links, ask Google, and if still too complicated, PM me.
Then, onto the rule.
On Windows, run "wf.msc". It should open the firewall interface. Create a new outgoing rule.
Configure the rule as follows :
Rule type = [Custom]
Program = [All programs] (or go find pCARS2AVX.exe if you really fancy)
Protocol and Ports = [Type : UDP] / [Local Port : All] / [Remote Port : Specific - 5606]
Scope = [Local IP : Add your subnet/mask here] / [Remote IP : Any]
Action = Block
Profile = tick everything
Name = whatever you want
Once created, the rule should appear in the list and be enabled by default.
