Difference between revisions of "Robin Hood: The Siege 2"

From PCSX2 Wiki
Jump to navigation Jump to search
(added test and screenshots)
 
Line 2: Line 2:
 
|image            = Cover_Robin_Hood_The_Siege_2.jpg
 
|image            = Cover_Robin_Hood_The_Siege_2.jpg
 
|caption          =
 
|caption          =
|developer        = Mere Mortals
+
|developer        = [[Mere Mortals]]
 
|publisher        = [[Phoenix Games]]
 
|publisher        = [[Phoenix Games]]
 
|genre            = Action
 
|genre            = Action
 
|wikipedia        =
 
|wikipedia        =
|gamefaqslink      = [http://www.gamefaqs.com/ps2/939341-robin-hood-the-siege-2 Link]
+
|gamefaqslink      = [https://www.gamefaqs.com/ps2/939341-robin-hood-the-siege-2 Link]
 
|gameinfo          =
 
|gameinfo          =
 
<!-- General props -->
 
<!-- General props -->
Line 29: Line 29:
 
|Region=PAL
 
|Region=PAL
 
|OS=Windows
 
|OS=Windows
|CPU=Intel Xeon CPU E5-1620 3.60GHz (16GB RAM)
+
|CPU=Intel Xeon E5-1620 @ 3.60 GHz
 
|GPU=NVIDIA GeForce GTX 680
 
|GPU=NVIDIA GeForce GTX 680
|Revision=1.5.0-dev-2286-g41c49faa8
+
|Revision=1.5.0 (dev-2286 g41c49faa8)
|Graphics=GSdx 20180213122600 (MSVC 19.00 SSE2/AVX) 1.1.0 [GSdx32-SSE2]
+
|Graphics=GSdx SSE2 1.1.0 (2018-02-13)
|Sound=*SPU2-X 20180213122600 2.0.0 [Spu2-X]
+
|Sound=
*LilyPad (20180213122600) 0.12.1 [LilyPad]
+
* SPU2-X 2.0.0 (2018-02-13)
|Comments=The game is playable but check the known issues below for more info.
+
* LilyPad 0.12.1 (2018-02-13)
D3D 11 (HW) 3x Native / Antisotropic Filtering= 2x / Preset= 2 - Safe (Faster)
+
|Comments=The game is playable but check the known issues below for more info. RAM: 16 GB.
 +
Direct3D 11 (Hardware) 3x Native / Antisotropic Filtering = 2x / Preset = 2 - Safe (Faster)
 
|Tester=Gryphin
 
|Tester=Gryphin
 
}}
 
}}
Line 62: Line 63:
 
* Also known as '''Robin Hood 2: The Siege'''
 
* Also known as '''Robin Hood 2: The Siege'''
  
<!-- Remove comment signs and add issues here -->
+
 
 
<!-- IssueLevel is issue severity level -1,0,1 or 2 (note, minor, serious and major accordingly)-->
 
<!-- IssueLevel is issue severity level -1,0,1 or 2 (note, minor, serious and major accordingly)-->
 
== Known Issues ==
 
== Known Issues ==
 
 
{{Issue
 
{{Issue
 
|IssueName=Glitched Graphics
 
|IssueName=Glitched Graphics
 
|IsFixed=0
 
|IsFixed=0
 
|IssueLevel=1
 
|IssueLevel=1
|Description=Graphics seem to get stuck on top of one another and freeze look at screenshots below, It seems to happen randomly I can figure out what causes it.
+
|Description=Graphics seem to get stuck on top of one another and freeze (see Gallery).
|Workaround=None
+
|Workaround=There is no known workaround.
 
}}
 
}}
  
<!-- Remove comment signs and add game screenshots or videos here -->
+
 
<!-- Replace FileName?.jpg with the correct filenames -->
 
 
== Gallery ==
 
== Gallery ==
 
<gallery widths="175px" heights="100px">
 
<gallery widths="175px" heights="100px">

Latest revision as of 22:26, 23 February 2018

Robin Hood: The Siege 2
Cover Robin Hood The Siege 2.jpg
Game general and emulation properties:
PEGI rating: 7+ (Violence)
Languages supported:
English: SLES-54122
Region PAL:
Serial numbers: SLES-54122
Release date: October 6, 2006
CRCs: 0x0C65902C
Windows Status: Playable
Linux Status: ?
Mac Status: ?

Developer(s): Mere Mortals
Publisher(s): Phoenix Games
Genre: Action


Winlogo.png Test configurations on Windows:


Environment Configurations Comments Tester
Region OS CPU/GPU Revision Graphics Sound/Pad
PAL Windows
  • Intel Xeon E5-1620 @ 3.60 GHz
  • NVIDIA GeForce GTX 680
1.5.0 (dev-2286 g41c49faa8) GSdx SSE2 1.1.0 (2018-02-13)
  • SPU2-X 2.0.0 (2018-02-13)
  • LilyPad 0.12.1 (2018-02-13)
The game is playable but check the known issues below for more info. RAM: 16 GB.

Direct3D 11 (Hardware) 3x Native / Antisotropic Filtering = 2x / Preset = 2 - Safe (Faster)

Gryphin


Trivia

  • Also known as Robin Hood 2: The Siege


Known Issues

Glitched Graphics

  • Status: Active
  • Type: Serious
  • Description: Graphics seem to get stuck on top of one another and freeze (see Gallery).
  • Workaround: There is no known workaround.


Gallery