Render Stats App?

Hello,

I would like to have an explanation on the meaning of the blue curve, and PHY_LATE.

In this thread I found nothing.

http://www.assettocorsa.net/forum/index.php?threads/application-statistiques.37203/

If this application is available for us, it must be understandable, I think.

If it isn't possible, never mind.

Thanks so much

 

I explained the meaning of PHY_LATE in my previous post. As for the graph, I do not know.

 

Ok but,

It is really sad not to be able to be informed, when one try of interested, i dont understand why

 

The blue curve is the graph for the PHY %.

 

We go round in circles, Phy_late = 0, = 105, = ....... , that means what, it is good has which moment

 

Sorry, maybe it is the language barrier, but... I already explained you. Here: http://www.assettocorsa.net/forum/index.php?threads/render-stats-app.1990/#post-757676

If you read the post by Stefano that I linked you can deduct that PHY_LATE counts the frames where PHY was over 100%, meaning it took over 3ms for that step of the physics calculation, so it's "late" in that frame.

For a more detailed explanation of how physics calculation is done you can watch that recording of one of Stefano's live streams, around 39:55m onwards:


As such the physics isn't impacted by the graphics performance (as they are separate threads) but if the physics thread is late in its calculation the game gets slowed down.

Now, don't take just my word for it though. There's no full official explanation of this on the website, as such I cannot tell you what that all (especially the graph) means exactly. Stefano might have mentioned the graph in a stream a while ago, no idea.

 

Sorry! yes I had badly interpreted, (language), in retrospect, it's more clear, thank you of your patience, and to have explained me again.

Thus, "phy_late" should be at the minimum, minimun of delay,latency (Number of times "max 3ms"), it's just ?

 

It's just a counter. In your logs you might find some "WAS LATE, HAD TO LOOP n times" error messages, and that's the sum of them. It means that at some instant your CPU couldn't prepare a frame in time for the physics engine that runs at a constant rate.

 

ok guy i understand , it's appens only on some track, for example SPA for me.

 

And red?

 

FPS graphically? It follows fps at least.

 

That one shows the FT or frame time. The higher it is, the longer it took to render the each frame, and thus the lower the framerate.