Difference between revisions of "Requiem: Avenging Angel"
From PCGamingWiki, the wiki about fixing PC games
(added Steam) |
(cleanup instructions (not tested)) |
||
Line 17: | Line 17: | ||
|winehq = 6733 | |winehq = 6733 | ||
}} | }} | ||
+ | |||
+ | '''Key points''' | ||
+ | {{ii}} The game requires DirectX 6.1 to run and it won't run on newer versions. Patch 1.3 updates the game to run on DirectX 8, but the game still won't run in Windows 7. | ||
+ | {{--}} Some players have reported game breaking bugs that may occur during playthrough. These bugs usually affect doors which don't open when they're supposed to and the player gets stuck. If such problem occurs it can be worked around by using the "no clip" cheat. | ||
'''General information''' | '''General information''' | ||
Line 30: | Line 34: | ||
==Essential improvements== | ==Essential improvements== | ||
===Patches=== | ===Patches=== | ||
− | [http://www.fileplanet.com/ | + | * [http://www.fileplanet.com/22394/20000/fileinfo/Requiem:-Avenging-Angel-v1.2 Patch 1.2] |
+ | * [http://www.fileplanet.com/56584/50000/fileinfo/Requiem-v1.3-Update-(D3D) Patch 1.3 (D3D)] | ||
+ | * [http://www.fileplanet.com/56586/50000/fileinfo/Requiem-v1.3-Update-(Software) Patch 1.3 (Software)] | ||
==Game data== | ==Game data== | ||
Line 60: | Line 66: | ||
|fov = hackable | |fov = hackable | ||
|fov notes = Open the console and enter <code>-FOV120</code> (replace <code>120</code> with desired value).<ref>[https://www.gog.com/forum/requiem_avenging_angel/does_this_have_widescreen_support Does this have widescreen support?, page 1 - Forum - GOG.com]</ref> | |fov notes = Open the console and enter <code>-FOV120</code> (replace <code>120</code> with desired value).<ref>[https://www.gog.com/forum/requiem_avenging_angel/does_this_have_widescreen_support Does this have widescreen support?, page 1 - Forum - GOG.com]</ref> | ||
− | |windowed = | + | |windowed = hackable |
− | |windowed notes = | + | |windowed notes = See [[#Windowed|Windowed]]. |
− | |borderless windowed = | + | |borderless windowed = hackable |
− | |borderless windowed notes = | + | |borderless windowed notes = See [[#Windowed|Windowed]]. |
|anisotropic = hackable | |anisotropic = hackable | ||
− | |anisotropic notes = through graphics driver | + | |anisotropic notes = Force through graphics driver. |
|antialiasing = hackable | |antialiasing = hackable | ||
− | |antialiasing notes = through graphics driver | + | |antialiasing notes = Force through graphics driver. |
|vsync = hackable | |vsync = hackable | ||
− | |vsync notes = through graphics driver | + | |vsync notes = Force through graphics driver. |
|60 fps = true | |60 fps = true | ||
|60 fps notes = | |60 fps notes = | ||
Line 76: | Line 82: | ||
|color blind = unknown | |color blind = unknown | ||
|color blind notes = | |color blind notes = | ||
+ | }} | ||
+ | |||
+ | ===[[Glossary:Windowed|Windowed]]=== | ||
+ | {{Fixbox|1= | ||
+ | {{Fixbox/fix|Use wndmode|ref=<ref>http://habrahabr.ru/post/133956/</ref>}} | ||
+ | # Download [https://bitbucket.org/veg/tinyddraw/downloads wndmode] and unpack into the installation folder. | ||
+ | # Open <code>wndmode.ini</code> with a text editor. | ||
+ | # Set <code>UseCursorClip</code> to <code>1</code> to lock cursor inside game window. | ||
+ | # Set <code>Border</code> to <code>0</code> to disable window border. | ||
}} | }} | ||
Line 129: | Line 144: | ||
==Issues fixed== | ==Issues fixed== | ||
− | === | + | ===Running the game on modern systems=== |
− | {{ | + | {{Fixbox|1= |
− | + | {{Fixbox/fix|Use D3DWindower}} | |
+ | # Install the game. | ||
+ | # Install [http://www.fileplanet.com/22394/download/Requiem:-Avenging-Angel-v1.2 Patch 1.2]. | ||
+ | # Install [http://www.fileplanet.com/56584/download/Requiem-v1.3-Update-%28D3D%29 Patch 1.3 (D3D)]. If it won't install due to unspecified Windows error, then overwrite <code>D3D.exe</code> within the installation folder with this [https://dl.dropbox.com/u/8746642/Requiem%20AA/D3D.exe D3D.exe file]. This file was extracted from the patch setup. | ||
+ | # Install and run [[Glossary:Windowed#D3DWindower|D3DWindower]]. | ||
+ | # Add the <code>D3D.exe</code> file to the list. | ||
+ | # Select the newly added file in D3DWindower and open the configuration box. | ||
+ | # Browse for the hook DLL; use <code>D3dHook.dll</code> which comes with the program. | ||
+ | # Set the resolution and check the "Use windowed mode" box. | ||
+ | # Run the game from within the D3DWindower. The credits videos and intro should play and the game menu should appear. The game menu will be stuck in 640x480 resolution and will not stretch within the D3DWindower box but it should be operable. Fortunately, the game itself will stretch to fill out the entire window. | ||
+ | # Set the resolution in the game menu to the one specified in D3DWindower. This part may be tricky as the game will be off at registering the mouse clicks. Try moving the mouse pointer around or even click outside the window to change focus. | ||
+ | }} | ||
− | + | {{Fixbox|1= | |
− | {{ | + | {{Fixbox/fix|Use wndmode}} |
− | {{ | + | # Install the game. |
− | + | # Install [http://www.fileplanet.com/22394/download/Requiem:-Avenging-Angel-v1.2 Patch 1.2]. | |
− | + | # Unpack [https://www.mediafire.com/?oce83a59f8d3ytt Patch 1.3] into the installation folder (this will update software, d3d and 3dfx renders to 1.3). These exes are from official patch which won't install under modern OS, so, literally, its just an unpacked patch. | |
− | + | # Unpack [https://bitbucket.org/veg/tinyddraw/downloads wndmode] into the installation folder. It's a heavily modified version of D3DWindower. | |
− | + | # In <code>wndmode.ini</code> set <code>UseCursorClip</code> to <code>1</code> and <code>Border</code> to <code>0</code>. This will lock cursor inside game window and disable window border. | |
− | + | # Install [http://www.zeus-software.com/downloads/nglide nglide]. nglide is optional, but 3dfx render has less graphics bugs (comparison: [https://pp.vk.me/c616120/v616120184/db96/ri9BwpOy7CU.jpg 3dfx] vs [https://pp.vk.me/c616120/v616120184/db9f/qE6fcmI0was.jpg d3d]). | |
− | + | # Play the game via <code>3DFX.exe</code> or <code>D3D.exe</code>. | |
− | + | }} | |
− | |||
− | https:// | ||
− | |||
− | < | ||
− | </ | ||
− | |||
− | < | ||
− | |||
− | < | ||
− | |||
− | |||
− | < | ||
− | < | ||
− | |||
− | |||
===Impossible to select leftmost angelic powers with the mouse pointer=== | ===Impossible to select leftmost angelic powers with the mouse pointer=== | ||
− | The game allows to bring up a menu where angelic powers can be selected with the mouse pointer. D3DWindower will break immediately when mouse pointer is brought up by the game and the window will most likely lose the focus when a click is performed. This occurs when mouse pointer is positioned at the left part of the screen. This makes certain angelic powers unselectable through mouse pointer. | + | {{ii}} Occurs when running the game with [[Glossary:Windowed#D3DWindower|D3DWindower]]. |
− | + | {{ii}} The game allows to bring up a menu where angelic powers can be selected with the mouse pointer. D3DWindower will break immediately when mouse pointer is brought up by the game and the window will most likely lose the focus when a click is performed. This occurs when mouse pointer is positioned at the left part of the screen. This makes certain angelic powers unselectable through mouse pointer. | |
− | |||
− | |||
− | |||
− | = | + | {{Fixbox|1= |
− | + | {{Fixbox/fix|Workarounds}} | |
− | + | * Reduce Windows screen resolution to fit the resolution of D3DWindower box. | |
− | + | * Simply use in-game key bindings to scroll through powers instead. Unfortunately this isn't as efficient as selecting them by mouse | |
− | + | }} | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==System requirements== | ==System requirements== |
Revision as of 16:21, 2 October 2016
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.
This page may require cleanup to meet basic quality standards. You can help by modifying
the article. The discussion page may contain useful suggestions.
Developers | |
---|---|
Cyclone Studios | |
Publishers | |
3DO | |
Ubisoft | |
Release dates | |
Windows | March 31, 1999 |
Key points
- The game requires DirectX 6.1 to run and it won't run on newer versions. Patch 1.3 updates the game to run on DirectX 8, but the game still won't run in Windows 7.
- Some players have reported game breaking bugs that may occur during playthrough. These bugs usually affect doors which don't open when they're supposed to and the player gets stuck. If such problem occurs it can be worked around by using the "no clip" cheat.
General information
Availability
Essential improvements
Patches
Game data
Configuration file(s) location
Template:Game data/row
System | Location |
---|---|
Steam Play (Linux) | <SteamLibrary-folder>/steamapps/compatdata/493310/pfx/[Note 1] |
Save game data location
Template:Game data/row
System | Location |
---|---|
Steam Play (Linux) | <SteamLibrary-folder>/steamapps/compatdata/493310/pfx/[Note 1] |
Video settings
Windowed
Instructions |
---|
Input settings
Audio settings
Issues fixed
Running the game on modern systems
Instructions |
---|
Instructions |
---|
Impossible to select leftmost angelic powers with the mouse pointer
- Occurs when running the game with D3DWindower.
- The game allows to bring up a menu where angelic powers can be selected with the mouse pointer. D3DWindower will break immediately when mouse pointer is brought up by the game and the window will most likely lose the focus when a click is performed. This occurs when mouse pointer is positioned at the left part of the screen. This makes certain angelic powers unselectable through mouse pointer.
Instructions |
---|
System requirements
Windows | ||
---|---|---|
Minimum | Recommended | |
Operating system (OS) | Vista, 7, 8, 10 | Vista, 7, 8, 10 |
Processor (CPU) | 1.8 GHz | |
System memory (RAM) | 512 MB | 1 GB |
Hard disk drive (HDD) |
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 (493310) may differ in some cases.
- Treat backslashes as forward slashes.
- See the glossary page for details on Windows data paths.
References
Categories:
- Stubs
- Pages needing cleanup
- Windows
- Invalid template usage (Infobox game)
- Games
- Invalid template usage (Availability)
- Invalid template usage (Fixbox)
- Invalid section order
- Missing section (Save game cloud syncing)
- Missing section (Video)
- Missing section (Input)
- Missing section (Audio)
- Missing section (Localizations)
- Missing section (API)