- Joined
- Aug 30, 2006
- Messages
- 7,197 (1.12/day)
System Name | ICE-QUAD // ICE-CRUNCH |
---|---|
Processor | Q6600 // 2x Xeon 5472 |
Memory | 2GB DDR // 8GB FB-DIMM |
Video Card(s) | HD3850-AGP // FireGL 3400 |
Display(s) | 2 x Samsung 204Ts = 3200x1200 |
Audio Device(s) | Audigy 2 |
Software | Windows Server 2003 R2 as a Workstation now migrated to W10 with regrets. |
For clan matches, I would recommend:
1./ From the command console
2./ Play the troublesome area
3./ Reducing mesh and terrain quality. Also ambient occlusion. These cause slowdowns with complex buildings and dense map areas
4./ Play again. Any improvement on the detailed CPU and GPU stats?
5./ I would not recommend a downgrade to 1280x1024. Every pixel you lose it a headshot harder to find
1./ From the command console
render.perfoverlayvisible 1 - When set to 1, this command displays a small chart on the bottom left corner of the screen designed to provide you with key information about your system's performance during BF3. It shows your graphics card (GPU) usage as a green line, and your processor (CPU) usage as a yellow line. The aim is to ensure that during gameplay neither lines spike frequently to very high levels, as this indicates that the particular resource is being overtaxed, and possibly causing lag and instability. If necessary experiment with your in-game settings until you see a reduction in such spikes. Use render.perfoverlayvisible 0 to close the overlay.
2./ Play the troublesome area
3./ Reducing mesh and terrain quality. Also ambient occlusion. These cause slowdowns with complex buildings and dense map areas
4./ Play again. Any improvement on the detailed CPU and GPU stats?
5./ I would not recommend a downgrade to 1280x1024. Every pixel you lose it a headshot harder to find