Render Stats App?

Hi all.

Like many others I am enjoying your software. Have a few problems running Crossfire but that is to be expected with early release.

My question is the statistics that are displayed in the "Render Stats App" what do each of the figures represent?

Thanks, and looking forward to future updates!

Paul

 

I'll write them in order

F: FPS
F: time for each frame to be rendered (in millisecods)
D : number of draw calls
T : total number of triangles
B : average size of each drawcall
S : triangle on scene (after culling)
C : cpu time
O : cpu occupancy

 

Which is the minimum value of FPS in order to consider fluid the game?

 

[/quote]

Thank you, and the Blue and Red Graph lines below?

 

snip...

Woah... thanx for taking the time to explain/list these Giovanni.

Much appreciated...

 

Thanks for the info, Giovanni.

Cuco
San Juan, PR

 

Can someone give me info on what the figures mean on the Render Stats app since the latest version landed please.
I feel like a noob about this info listed.

 

Any one?

 

This is a insane old post to answer but the answer is: whatever makes the game feel fluid to you.

 

what are those red and blue lines? when red line starts peaking up-down-up-down, i have some fps loss..?

 

@Lord Kunos

Any chance you could clear this up for us all ?


FPS
FT
CPU
DIP
TRI
B.SIZE
SCENE
PHY
FMOD DSP
FMOD USAGE
(red/blue/teal graphic line into the box)

 

Sorry for digging out this old thread, but especially with several AI cars I sometimes get micro-stutters.
fps are ok rarely under 55fps, but it still stutters and there are regular significant peaks in the red graph of the app when the game stutters.

Does somebody know in the meanwhile what the red lines stands for and what these peaks could be?
Maybe a tip what I could change on my dated pc to get rid of these micro-stutters.

Weather/clouds and sun (rays)/shadows seem to also affect this problem.

 

I think I located my problem.

At the beginning of the session I went to my browser with ALT+TAB to look something up. So I only drove after the switch and had the peaks with stuttering.

With a new session it ran pretty smoothly with 23 opponents and only little spikes in the red graph, that also were a lot less frequent than the big peaks.

So just to check I switched once again and after that the peaks were back like in the previous session.

Don't know what exactly causes the stuttering after going back into AC, but now I know when this happens and to avoid switching tasks.

 

Do alt+enter after you alt tab back to AC. If you don't, AC won't be running in true fullscreen anymore and stutters might occur.

 

You're me hero, mate.

Works like it should after Alt+Enter, no more of those big peaks. Maybe a tiny bit more spikes than with a new session, but that might be due to some other reasons or just my imagination.

Never in a million years I would have figured this out, and then it's such a simple solution.

 

Probably AC was making full use of the vram, so if you return to a gpu accel enabled program like a browser that also claims some and then back again to AC, you'll need to swap some stuff back to your GPU from RAM during that session.
Try to disable your browser's 3D accel to see if it helps (60fps video playback will suffer a lot).

 

It's fine after Alt+Enter, no more micro-stutters and frame rate only drops on a few parts, but that's the same with a new session.

So I don't think it's necessary to change anything.
Also the session was with low sun, full grid and resource hungry clouds, just to stress the situation a bit and test the Alt+Enter trick.

 

Well... since the other thread was closed while I was typing a reply @miche and this one doesn't actually give the most up-to-date answer...

What I wanted to post:

Might be a good idea if Kunos posted an official short explanation somewhere in the FAQ. Nobody seems to know for sure what the graph is and nobody seemed to know what CPU and PHY really meant until Stefano explained it in a thread that's buried somewhere now and on one of the live streams.