Difference between revisions of "Arma 3"
Line 335: | Line 335: | ||
}} | }} | ||
− | === | + | ===Failed to initialize BattlEye Service: Driver Load Error (577).=== |
{{Fixbox|1= | {{Fixbox|1= | ||
{{Fixbox/fix|Verify game cache}} | {{Fixbox/fix|Verify game cache}} | ||
Line 342: | Line 342: | ||
# Right-click the game title. | # Right-click the game title. | ||
# Select Properties, the Local files tab, then click on the Verify integrity of game cache button. | # Select Properties, the Local files tab, then click on the Verify integrity of game cache button. | ||
+ | }} | ||
+ | |||
+ | ===Forcing correct monitor=== | ||
+ | {{Fixbox|1= | ||
+ | {{Fixbox/fix|}} | ||
+ | # Edit '''Arma3.cfg''' in your config folder. | ||
+ | # Find '''forcedAdapterId''' parameter, set 0 for primary monitor, 1 for secondary, etc. | ||
+ | |||
+ | {{Fixbox/fix|Specific parameter for linux users only :}} | ||
+ | You can also use <code>--eon_force_display=x</code> command line parameter on linux builds, where x is your monitor ID. | ||
+ | Under steam, set command line like this : <code>%command% --eon_force_display=0</code> | ||
}} | }} | ||
Revision as of 16:13, 21 April 2016
Cover image missing, please upload it | |
Developers | |
---|---|
Bohemia Interactive | |
Engines | |
Real Virtuality 4|Real Virtuality|Real Virtuality 4 | |
Release dates | |
Windows | September 12, 2013 |
macOS (OS X) | Early access[1] |
Linux | Early access[1] |
Arma | |
---|---|
Arma: Cold War Assault | 2001 |
Arma: Armed Assault | 2006 |
Arma 2 | 2009 |
Arma 2: Operation Arrowhead | 2010 |
Arma Tactics | 2013 |
Arma 3 | 2013 |
Arma Reforger | 2022 |
Key points
- Game engine suffers from a critical issue, see Engine not utilizing CPU correctly.
General information
- Port Report: Arma 3 Alpha
- Bohemia Interactive Forums
- Startup Parameters
- Armaholic Community Forums
- Feedback Tracker
- Steam Community Discussions
- Performance Guide
Availability
Source | DRM | Notes | Keys | OS |
---|---|---|---|---|
Developer website | ||||
Green Man Gaming | ||||
Steam |
- All versions require Steam.
DLC and expansion packs
Name | Notes | |
---|---|---|
Helicopters | ||
Karts | ||
Marksmen | ||
Zeus |
Essential improvements
Skip intro videos
Instructions |
---|
Skip launcher
Instructions |
---|
Game data
Configuration file(s) location
System | Location |
---|---|
Steam Play (Linux) | <SteamLibrary-folder>/steamapps/compatdata/107410/pfx/[Note 1] |
Save game data location
System | Location |
---|---|
Steam Play (Linux) | <SteamLibrary-folder>/steamapps/compatdata/107410/pfx/[Note 1] |
- Steam Workshop mission files are also stored in
%USERPROFILE%\Documents\Arma 3 - Other Profiles\<user-id>\Saved\steam
Save game cloud syncing
System | Native | Notes |
---|---|---|
Steam Cloud |
Video settings
Field of view (FOV)
Instructions |
---|
Some suggested FOV values in radians[2] for typical setups are:
Setup Type | fovTop | fovLeft |
---|---|---|
1920×1080 at 90 FOV | 1.03 | 1.83 |
1680×1050 at 90 FOV | 1.13 | 1.80 |
2560×1600 at 90 FOV | 1.13 | 1.76 |
Notes
- Range finding by using certain scopes like the PSO scope might not be accurate anymore when playing on a non-default FOV.
Input settings
Audio settings
Network
Multiplayer types
Type | Native | Notes | |
---|---|---|---|
LAN play | |||
Online play |
Connection types
Type | Native | Notes |
---|---|---|
Dedicated | ||
Self-hosting | ||
Direct IP |
VR support
Devices | State | Notes | |
---|---|---|---|
TrackIR |
Issues fixed
Forcing game to use all RAM
Instructions |
---|
Failed to initialize BattlEye Service: Driver Load Error (577).
Instructions |
---|
Forcing correct monitor
Instructions |
---|
Issues unresolved
Engine not utilizing CPU correctly
- The Real Virtuality 4 engine suffers from a massive issue in utilizing multi-core CPUs.[3][4]
- And due to the CPU not being utilizing correctly then nor will the GPU be utilized correctly.
- Real Virtuality 3 has the same issue
This issue is critical and all users with multi-core processors are suffering from it. The developers have yet to comment on this issue on the official bug tracking site.
This critical engine issue gives users a ~40% performance loss at all times, the reason is that the engine has what is called a Engine Limitation, in this case it means that only a few processing cores are being utilized and take big hits that might be the reason for game stutter as the CPU can't handle all the requests on high-end settings.
System requirements
Windows | ||
---|---|---|
Minimum | Recommended | |
Operating system (OS) | Vista SP2, 7 SP1 | |
Processor (CPU) | AMD Dual-Core Athlon 2.5 GHz Intel Dual-Core 2.4 GHz |
AMD Phenom II X4 940 or better Intel Core i5-2300 |
System memory (RAM) | 2 GB | 4 GB |
Hard disk drive (HDD) | 10 GB | 20 GB |
Video card (GPU) | AMD Radeon HD 3830 NVIDIA GeForce 8800 GT Intel HD Graphics 4000 512 MB of VRAM DirectX 10 compatible | AMD Radeon HD 7750 NVIDIA GeForce GTX 560 1 GB of VRAM DirectX 11 compatible |
Notes
- ↑ 1.0 1.1 Notes regarding Steam Play (Linux) data:
- File/folder structure within this directory reflects the path(s) listed for Windows and/or Steam game data.
- Use Wine's registry editor to access any Windows registry paths.
- The app ID (107410) may differ in some cases.
- Treat backslashes as forward slashes.
- See the glossary page for details on Windows data paths.
References
- ↑ 1.0 1.1 Cite error: Invalid
<ref>
tag; no text was provided for refs namedExperimental Ports
- ↑ http://www.dayz.co/change-your-fov-in-dayz/
- ↑ http://feedback.arma3.com/view.php?id=716
- ↑ https://www.youtube.com/watch?v=vDMdzwanxnY