ACC - Significations des infos serveur et graphiques

Tu as mis le doigt où ça fait mal, apparemment

Perso, très intéressé par quelques éclairages

pour suivre

Bjr,

Savez vous comment on procède pour supprimer cette fenetre ?

On n’avait jamais répondu à Rick Block

51EC0BDF-DCB2-40C7-A5C7-DE43955C3A43.png

Citation

CPU: Left side is the % occupancy in average over the last seconds, right side is the peak value. If the peak is below 100 all the time, the server can be regarded completely healthy in terms of computing power. If the peak goes close to - or a bit above 100 occasionally, it's still ok but an indication that the server is on the edge. If this happens frequently or the number is growing a lot, you can expect problems and bad netcode.

QoS: Checks the connection quality, left side is the average of all connections between the server and the connected clients - right side is the worst connection. If both are at 100%, connection is fine. If left is 100 but the right side shows something like 98 or less, the server is fine but there's one client with a bad connection. However if the left side drops below 100, the server's internet connection is not capable of hosting races.

Lat: Average ping of all connections. Should be around 20-150 ms all the time, dependent on who is online from where. If this number skyrockets to many hundreds or even thousands, the server has a CPU or bandwidth problem and is not capable of hosting races.

Ping: Your last ping measurement. Can be a bit jumpy due to timing, but that's not an issue.

Overall, as long as everything is white the server is fine; once things become yellow or red it's an indication that this server is not up to the game, and you may want to find a better one.

Afficher plus

Et pour le second encart :

Citation

FPS: frames per second.. should be easy enough

MS: milliseconds per frame.. it's basically ~ 1000/FPS , programmers tend to prefer MS to FPS to measure performances

PHY
O: % occupancy for the physics calculations, more AI = higher occupancy
L: How many times the physics calculation was "late", in other words, how many time occupancy went over 100%
B: "Blend counts", how many times the graphics could not interpolate between a physics state slightly in the future and one in the past. If it's not clear don't worry, it's not something you should be worried about at all.

The FMOD stuff should be a % of CPU usage
The other 2, no idea..

As for "ranges".. you want FPS as high as possible, MS as low as possible, O as low as possible (close to 100% and you might experience bad things), L & B can be ignored unless they start to go into the >10K count. FMOD as low as possible.

Afficher plus

Pour cacher ces infos, il faut aller dans le dossier ...\Documents\Assetto Corsa Competizione\Config, éditer le fichier hud.json avec un éditeur de texte :

- Ligne 13 => "fPSVisible": 0,

- Ligne 28 => "serverStatsVisible": 0,

Remplacer le 0 par un 1 pour afficher ces infos

Merci à vous deux, cela a fonctionné en passant par Notepad++, j'ai juste eu a passer la ligne 13 en 0, la ligne 28 étant déjà à 0