Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.


Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

Difference between revisions of "Battlefield 3"

From PCGamingWiki, the wiki about fixing PC games
(This is illegal.)
 
(Added workaround for predictive crosshair bug on helicopters.)
Line 65: Line 65:
 
*Then close the command prompt. You just told Vista to increase user virtual address (userva) space to 2500MB.
 
*Then close the command prompt. You just told Vista to increase user virtual address (userva) space to 2500MB.
 
*Changes take effect on reboot but don't reboot yet.   
 
*Changes take effect on reboot but don't reboot yet.   
 +
 +
 +
==Predictive Crosshairs on Helicopters==
 +
As of February 2012, there's a bug where using a weapon that does not have predictive crosshairs (heatseekers in attack helis, air-to-ground missile on scout helis) will cause the predictive crosshairs on the missiles (attack heli) or main gun (scout heli) to bug out. To fix this, just switch to third person view and back.
  
 
==External links==
 
==External links==

Revision as of 14:08, 21 February 2012

This page may require cleanup to meet basic quality standards. The specific problem is: 22:13, 11 February 2012 (UTC). You can help by modifying the article. The discussion page may contain useful suggestions.

Optimal Settings

Textures: Medium/High-At high settings you won't notice textures popping in. Ultra textures are loaded when you are up close to an object. GPUs with less than 1GB of VRAM may have stuttering issues on Ultra textures, due to thrashing.

Shadows: Medium- Even at low settings everything in the game casts a dynamic shadow. Raising the setting makes the shadow look softer.

Effects: Low- As the article states "Being honest, we struggled to find a difference between the lowest and highest settings in the Effects Quality settings;..."

Mesh: Ultra-Mesh has a big effect on the overall visuals.(The higher setting it is, the range at which you can spot enemies is increased)

Terrain: Low- Similar to Effects, not much difference between low and ultra.

Anti-Aliasing Deferred: 2x MSAA- Smooths edges, while not as well as 4x, you save yourself some FPS.

AA Post: Low- Minimal performance difference between Low and Ultra so if you can, go Ultra.

Motion Blur: This is a matter of personal preference and GPU capability. Some like it off, some like it on. If you like it on and you can afford the drop in FPS associated with it then turn it on. If not I suggest disabling it.

Anisotropic Filter: 16x- Minimum performance hit and it give a significant visual improvement.

Ambient Occlusion: HBAO- More modern than SSAO and doesn't require as many resources as it did in BC2.

Performance can also be increased by lowering the resolution, however, LCD screens perform optimally at their native resolution.

System Requirements

Mimimum:

  • OS: Windows Vista (Service Pack 2) 32-bit
  • CPU: Intel Core 2 Duo 2.4 GHz or AMD Athlon X2 2.7 GHz
  • Memory: 2 GB RAM
  • Hard drive space: 20 GB for disc version or 25 GB for online distributed version + 100MB for Origin Platform Installation
  • Video: NVIDIA GeForce 8800 GT or ATi Radeon HD 3870 with pixel shader 5.0
  • Sound: DirectX compliant Sound card

Recommended:

  • OS: Windows 7 64-bit
  • CPU: Intel or AMD quad-core
  • Memory: 4 GB RAM
  • Hard drive space: 20 GB for disc version or 25 GB for online distributed version + 100MB for Origin Platform Installation
  • Video: NVIDIA GeForce GTX 560 or AMD Radeon HD 6950
  • Sound: DirectX compliant Sound card

32 bit fix

A lot of people using 32bit Operating Systems have issues like the game crashing after a couple of minutes of playing. This is sometimes caused by the game using more memory than windows allows it to do. If you experience those or similar issues you can try the 32bit fix:

for windows XP 32bit

  • Find your Boot.ini located usually on the C:.(If you cannot see it, you probably have system files hidden, then follow these instructions at microsoft (also uncheck "hide protected operating system files")
  • Right click on the boot.ini and choose properties. Uncheck "read only"
  • Open the boot.ini by double clicking it.
  • Under the section called find the line that says "multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Professional...". Yours may look a bit different. We are going to make a duplicate, so that if you make a mistake you will not harm yourself from booting into your computer. Drag you're mouse across the entire line, right click and choose copy. Then right below the line you just copied right click your mouse and choose paste. You should now have two lines one after another that are exact duplicates.
  • Change the bottom line that you just copied with the following addition on the end. Add a space at the end of the line and then this without the quotes "/3GB /USERVA=2500"
  • In that lower boot entry you just made, find the name of the operating system in quotes and change it to something like "Windows XP 3GB", so you can differentiate at boot up.
  • Close and save the boot.ini.
  • Right click on the boot.ini, hit properties, check read only.

for Windows 7/Windows Vista

  • In Windows 7/Vista go to Start menu. Go to Accessories. Locate the command prompt shortcut and hover mouse over it. Right Click on the shortcut then select Run as Administrator.
  • In the command prompt type this exactly: bcdedit /set increaseuserva 2500.(or 3000) Then hit enter.
  • Make sure you get a message back confirming the change was made. To verify the entry is there you can type just bcdedit, hit enter, and you should see the entry now listed.
  • Then close the command prompt. You just told Vista to increase user virtual address (userva) space to 2500MB.
  • Changes take effect on reboot but don't reboot yet.


Predictive Crosshairs on Helicopters

As of February 2012, there's a bug where using a weapon that does not have predictive crosshairs (heatseekers in attack helis, air-to-ground missile on scout helis) will cause the predictive crosshairs on the missiles (attack heli) or main gun (scout heli) to bug out. To fix this, just switch to third person view and back.

External links

Symthic is a website which has statistics of all the weapons, vehicles and attachments that are present in game. It allows you to see which setup fits your playing style the best, and allows you to see equipment before you unlock it in game.

Battlefield 3 on Origin Store