Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The option should be somewhere at the top of the file.
Thanks, it worked
Im a computer engineer
"battleye secure": true
change true to false to set it off
On a slower PC with mechanical drives this will most defiantly effect FPS.
Add to that contention with anti-virus, anti-mal and firewalls and your overhead goes up dramatically on the client side.
Truly its server hosts choice as to what level security they want to run on their servers.
As long as a control system exits to "keep em separated" its not a issue.
The hack vs legit argument is a mute point, so time some of you got off your high horses on that.
Most, if not all modern processors will not have any issues running BattlEye, so the difference is insignifcant unless you're running a computer that's at least 10 years old. If you are, consider chunking it into a shredder and getting a new one, because that's ridiculously outdated.
I'm using a 4th generation i3, there's literally no difference for my computer, and 4th gen i3s came out at least 2 years ago.
Actually the biggest BE problem comes from disk storage if you have 24tb of data on analog drives its wants to test all of that in background and that a large overhead.
200gb on ssd and its over in a flash.
Most people have 500~750 GB hdd space at most, so that's not even relevant...
Relevant is the fact that there are issues using BE at this point I'm just pointing out some of the potential factors involved.
Potential, but not likely. The most likely cause of most of the problems is because it was newly integrated; it's bound to have bugs.