Our website is made possible by displaying online advertisements to our visitors.
Please consider supporting us by disabling your ad blocker.
Please consider supporting us by disabling your ad blocker.
-
Announcements
-
=ADK= Discord Link 04/24/2017
Come join us in =ADK= Discord To download the Discord app go here: https://discordapp.com/ Discord is going to have a small learning curve over teamspeak so be prepared, but the fellow members as well as the Admins will gladly help you if you have any issues with installing or using the app. Once you have Discord installed all that's left to do is click the button below. Welcome to the future of the =ADK= Community. Click Here To Join!
-
Search the Community
Showing results for tags 'performance meter'.
Found 1 result
-
All, I came across an article a little while back while I was tuning my system for BF3 and I thought I would share what I learned with you. Before I read the article, I didn't really know what I was looking at with respect to the performance meter, but now that I know I've found that it can be a handy tool and useful for providing insight into how your system is performing with the Frostbite 2 engine. Although I haven't seen it yet, I suspect Frostbite 3's performance meter will be similar. Variable used to show the performance meter: (entered using either the console (~ key) or by inserting the lines into your user.cfg file) Render.PerfOverlayEnable 1 Render.PerfOverlayVisible 1 Green line = GPU (video card) performance Yellow line = CPU performance Bottom red horizontal line = 0ms (time zero) - Vertical (from zero) = increasing response time Red horizontal lines = 20ms Red vertical lines = 3-second intervals What this example chart shows is that this guy's GPU lags his CPU in average processing time by about 8ms. In other words, his GPU is his system's bottleneck. Also, no lag spikes are present during this roughly 3.5 second time window. From what I can see (based on the average GPU processing rate (in milliseconds), this guy is churning a smooth 55.5 FPS (a nice picture on a 60Hz monitor). Later, I will post a screenshot of my performance meter for comparison (can't b/c I'm @ work right now ;) ) war FPS = 1/processing time in seconds (in this case 1/0.01803) 18.03 ms = 0.01803sec
