Difference between revisions of "Call of Juarez"
From PCGamingWiki, the wiki about fixing PC games
Line 60: | Line 60: | ||
|4k ultra hd wsgf award = gold | |4k ultra hd wsgf award = gold | ||
|widescreen resolution = true | |widescreen resolution = true | ||
− | |widescreen resolution notes= To remove the black bars, see the [http://www.wsgf.org/dr/call-juarez WSGF entry] | + | |widescreen resolution notes= To remove the black bars, see the [http://www.wsgf.org/dr/call-juarez WSGF entry]. Image gets cut on top and bottom at certain 16:9 resolutions.<ref>[http://screenshotcomparison.com/comparison/208635 1280x720 vs 1366x768]</ref> |
|multimonitor = hackable | |multimonitor = hackable | ||
|multimonitor notes = See the [http://www.wsgf.org/dr/call-juarez WSGF entry] | |multimonitor notes = See the [http://www.wsgf.org/dr/call-juarez WSGF entry] | ||
Line 67: | Line 67: | ||
|4k ultra hd = true | |4k ultra hd = true | ||
|4k ultra hd notes = | |4k ultra hd notes = | ||
− | |fov = | + | |fov = false |
|fov notes = | |fov notes = | ||
|windowed = true | |windowed = true | ||
|windowed notes = | |windowed notes = | ||
− | |borderless windowed = | + | |borderless windowed = false |
|borderless windowed notes = | |borderless windowed notes = | ||
|anisotropic = true | |anisotropic = true | ||
|anisotropic notes = | |anisotropic notes = | ||
|antialiasing = true | |antialiasing = true | ||
− | |antialiasing notes = | + | |antialiasing notes = Up to 8x [[FSAA]]. |
− | |vsync = | + | |vsync = hackable |
− | |vsync notes = | + | |vsync notes = Can be forced through the graphics card control panel. |
|60 fps = true | |60 fps = true | ||
|60 fps notes = | |60 fps notes = |
Revision as of 18:19, 2 May 2017
This page is a stub: it lacks content and/or basic article components. You can help to expand this page
by adding an image or additional information.
Developers | |
---|---|
Techland | |
Publishers | |
North America | Ubisoft |
Europe | Focus Home Interactive |
Engines | |
Chrome Engine 3|Chrome Engine|Chrome Engine 3 | |
Release dates | |
Windows | September 5, 2006 |
Call of Juarez | |
---|---|
Call of Juarez | 2006 |
Call of Juarez: Bound in Blood | 2009 |
Call of Juarez: The Cartel | 2011 |
Call of Juarez: Gunslinger | 2013 |
General information
- Steam Community Discussions
- Steam Users' Forums for game series
Availability
Source | DRM | Notes | Keys | OS |
---|---|---|---|---|
Retail | SecuROM 7 DRM disc check | |||
Steam | Can be played without Steam running.[1] |
Game data
Configuration file(s) location
Template:Game data/row
System | Location |
---|---|
Steam Play (Linux) | <SteamLibrary-folder>/steamapps/compatdata/3020/pfx/[Note 1] |
- CD-key is stored in
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Techland\CallOfJuarez\SerialNumber
Save game data location
Template:Game data/row
System | Location |
---|---|
Steam Play (Linux) | <SteamLibrary-folder>/steamapps/compatdata/3020/pfx/[Note 1] |
Save game cloud syncing
System | Native | Notes |
---|---|---|
Steam Cloud |
Video settings
Input settings
Audio settings
Localizations
Language | UI | Audio | Sub | Notes |
---|---|---|---|---|
English | ||||
French | ||||
German | ||||
Russian | ||||
Spanish |
Network
Multiplayer types
Type | Native | Notes | |
---|---|---|---|
LAN play | Versus |
||
Online play | Versus |
Other information
API
Technical specs | Supported | Notes |
---|---|---|
Direct3D | 9, 10 |
Executable | 32-bit | 64-bit | Notes |
---|---|---|---|
Windows |
System requirements
Windows | ||
---|---|---|
Minimum | Recommended | |
Operating system (OS) | 2000, XP | |
Processor (CPU) | Intel Pentium 4 2.2 GHz AMD Athlon 2400+ |
Intel Pentium 4 3.0 GHz AMD Athlon 3000+ |
System memory (RAM) | 512 MB | 1 GB |
Hard disk drive (HDD) | 2 GB | |
Video card (GPU) | Nvidia GeForce 6600 ATI Radeon 9800 DirectX 9.0c compatible | |
Sound (audio device) | DirectX 9 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 (3020) may differ in some cases.
- Treat backslashes as forward slashes.
- See the glossary page for details on Windows data paths.
References
- ↑ Verified by User:Vetle on 2016-06-02