VireioPerceptionManualv1 1 14

Vireio Perception 2.1.
4 Instruction Manual
The latest version of Vireio Perception is 2.1.4 - available here (http://www.mtbs3d.com/downloads-section/
viewdownload/17/67) . Items marked below with (coming soon) will be included in the next release.
Copyright 2012 Andres Hernandez
Vireio Perception Version History:
v1.0.0 2012 by Andres Hernandez
v1.0.X 2013 by John Hicks, Neil Schneider
v1.1.x 2013 by Primary Coding Author: Chris Drain
Team Support: John Hicks, Phil Larkson, Neil Schneider
v2.0.x 2013 by Denis Reischl, Neil Schneider, Joshua Brown
v2.0.x - v2.1.x 2014 by Grant Bagwell, Simon Brown, Neil Schneider
All trademarks mentioned belong to their owners, third party brands, product names, trade names, corporate names and company
names mentioned may be trademarks of their respective owners or registered trademarks of other companies and are used for
purposes of explanation and to the owner's benefit, without implying a violation of copyright law.
All information and content (texts, graphics and images) are reported to the best of our knowledge, public knowledge, if unintentionally,
has been published or copyrighted material in violation of the law, please inform us and we will immediately remove it.
The Vireio Perception OS project has no responsibility for the sites can be accessed through links contained within this document. Vireio
Perception OS project does not intend to violate any copyrights.
Ratings Note
We have given each game a rating based upon our testing and personal opinion. This includes whether it has a working VR
Boost profile, how many visual artifacts there are and generally how well the game lends itself to VR. These were made on
machine that were able to run the game comfortably at 75FPS.
Donations
We have been asked by many users if there is any way to donate to the project. VP is open source which means any
programmers can actually help build the driver and add to it. Users can also add new game support (using the inbuilt shader
analyzer and Cheat Engine to produce a VR Boost profile). However if you would still like to donate some money we have
formulated what we feel is the fairest in that any money received will go to adding games, or supporting software to the
developers accounts. Please see the below page on how to donate steam wallet codes and thank you very much for your
generosity.
http://www.mtbs3d.com/donate
Vireio Perception User Guide: 1/60
Current Request List + Status

Call of Juarez (Original) - No way to change FOV - Status: Abandoned
Rainbow Six Vegas 2 - FOV fixed as per RSV1 :-( Couldnt find anyway to change and way too low for OR Status: Abandoned
FEAR 3 - Crash on initial inject. Left for now.
RUST - Anti Cheat Technology prevents use on injection
FSX Microsoft Flight SImulator - Launcher Causes SwapChain issue - Status: Investigating / May need special
Direct3dDevice. Appears this will be getting a proper mod via http://www.dcoc-vr.com/fsx so abandoned until we hear
more from that project.
Psychonauts - Constant Table Not available for Vertex - Status: Currently Investigating - use new constant rules to add
support.
Consortium - Injection causes an error
GTA IV - Currently Investigating - Status: Got injection working with geometry 3D. Need to look at VR Boost / 1st Person
Mod
ARMA 2 - Currently Investigating - Status: Error on 3d scene
Dead Island - Currently Investigating - Status: Looking Great So Far. VR Boost done. Awaiting investigation into vertex based
3d
Homefront: Injecting fine with dx11 off. 3d working fine. Few shaders and VR boost needed then will be great title
Mount & Blade: Warband - Awaiting Investigation
Shadow Warrior - Awaiting Investigation
Garrys Mod - Awaiting Investigation
The Long Dark: Awaiting Investigation
Pinball FX2: Awaiting Investigation
Star Wars Republic Commando: Awaiting Investigation
Thief: Deadly Shadows: Awaiting Investigating
Metro: 2033 - Awaiting investigation
Deadfall Adventures - Awaiting Investigation
Dark Messiah of might and Magic - Awaiting Investigation
Dark Souls: Prepare to Die Edition - Awaiting Investigation
Outlast - Done!
Bulletstorm: DONE!
Crysis - Status: DONE!
Crysis Warhead - Status: DONE!
Betrayer - Status: DONE!
Far Cry 3: DONE!
Far Cry 3 Blood Dragon: DONE!
The Old City Leviathan - DONE!
Doc Changelist
v1.0.0 - 18/11/2014 - Initial Document (GB)
v1.0.1 - 18/11/2014 - Added link to Borderlands Config Editor (GB)
v1.0.2 - 18/11/2014 - Added notes to Dishonored (GOTY Edition)
v1.0.3 - 19/11/2014 - Added brief how-to for creating shader profile and some other edits (SB)
v1.0.4 - 22/11/2014 - Added Rainbow Six Vegas (GB)
v1.0.5 - 23/11/2014 - Added QUBE (Standard Edition) (SB)
v1.0.6 - 23/11/2014 - Added Portal (Original) (SB)
v1.0.7 - 24/11/2014 - Added QUBE (Directors Cut) (GB)
v1.0.8 - 24/11/2014 - Some additional information in the scanner guide (SB)
v1.0.9 - 28/11/2014 - Added results of VSync testing to Stanley Parable
v1.0.10 - 02/12/2014 - Added results of VSync testing to Portal 2, and other small tweaks (SB)
v1.0.11 - 02/12/2014 - Added Vireio DLL Symlink Installer details and The Vanishing of Ethan Carter (SB)
v1.0.12 - 03/12/2014 - Added Zeno Clash (GB)
v1.0.13 - 03/12/2014 - Added Chivalry: Medieval Warfare (SB)
v1.0.14 - 03/12/2014 - Added Fallout 3 / NV Testing
v1.0.14 - 03/12/2014 - Added link to fixed version of symlink installer (SB)
v1.1.01 - 19/12/2014 - Added update as Bioshock HUDs now customisable (GB). Updated rating to Excellent.
v1.1.02 - 23/12/2014 - Added A Story about my Uncle, Batman: Arkham City GOTY + Other small tweaks (SB).
v1.1.03 - 06/01/2014 - Alice: Into Madness, Hot-key update, scan assist details (SB).
v1.1.04 - 06/01/2014 - Added info about new method of ensuring 75hz (GB). Updated links to new release today 2.1.2.
v1.1.05 - 07/01/2014 - Added a troubleshooting section for more general issues (SB)
v1.1.06 - 21/01/2015 - Added stubs for upcoming games in new release (Dead Island / Betrayer / Crysis)
v1.1.07 - 01/02/2015 - Details for Crysis and Overlord (SB)
v1.1.08 - 01/02/2015 - Started to add details for Far Cry 3(SB)
v1.1.09 - 15/02/2015 - Added Bulletstorm (SB)
v1.1.10 - 28/02/2015 - Released VP Version 2.1.3
v1.1.11 - 08/03/2015 - Added notes to Outlast
v1.1.12 - 10/03/2015 - Added notes about donating
v1.1.13 - 11/03/2015 - Added Duck and Cover mode instructions
v1.1.14 - 12/03/2015 - Released Version 2.1.4
Table of Contents
Vireio DLL Symlink Installer
DLL Copying is a thing of the past
Instructions for use
Installing / Creating Symlinks
Removing / Deleting Symlinks
Points to note
Game Support List
General Settings
A Story about my Uncle (Vireio VR Rating: Great)
Alice Madness Returns (Vireio VR Rating: Great)
Antichamber (Vireio VR Rating: Okay)
Batman: Arkham City GOTY (Vireio VR Rating: Okay)
Betrayer (Vireio VR Rating: Excellent)
Bioshock (Vireio VR Rating: Excellent)
Bioshock 2 (Vireio VR Rating: Excellent)
Borderlands (Vireio VR Rating: Excellent)
Bulletstorm (Vireio VR Rating: Excellent)
Chivalry: Medieval Warfare (32 and 64 bit support) (Vireio VR Rating: Good)
Crysis (Vireio VR Rating: Excellent)
Crysis Warhead (Vireio VR Rating: Great)
Initial Setup (one time only)
Dead Island (Vireio VR Rating: TBA) (coming soon..)
Dear Esther (Vireio VR Rating: Great)
Dirt3 (Vireio VR Rating: Good)
Dishonored (Vireio VR Rating: Good)
Fallout 3 (Vireio VR Rating: Great)
Fallout 3: New Vegas (Vireio VR Rating: Great)
Far Cry (Vireio VR Rating: Great)
Far Cry 3 (Vireio VR Rating: Great)
Far Cry 3 Blood Dragon (Vireio VR Rating: Great)
Homefront (Vireio VR Rating: TBA) (coming soon.)
Left 4 Dead (Vireio VR Rating: Good)
Left 4 Dead 2
Mirrors Edge (Vireio VR Rating: Good)
The Old City: Leviathan (Vireio VR Rating: Excellent)
Outlast (64bit) (Vireio VR Rating: Great)
Overlord (Vireio VR Rating: OK)
Portal (Vireio VR Rating: Good)
Portal 2 (Vireio VR Rating: Great)
QUBE (Standard Edition) (Vireio VR Rating: Excellent)
QUBE (Directors Cut) (Vireio VR Rating: Excellent)
Rainbow Six: Vegas (Vireio VR Rating: Okay)
Skyrim (Vireio VR Rating: Good)
The Stanley Parable (Vireio VR Rating: Great)

The Vanishing of Ethan Carter (32 and 64 bit support) (Vireio VR Rating: Good)
Zeno Clash (Vireio VR Rating: Poor)
Vireio Perception - Shortcut Keys
Toggles and Menus
Adjusters
Duck and Cover mode
Overview
Configuration
Disclaimer
VRBoost Memory Scanner
How to use the new VRBoost Memory Scanner
Creating Shader Profiles
Troubleshooting - Tips and suggestions
Vireio DLL Symlink Installer

DLL Copying is a thing of the past
Previously, if Vireio did not inject when the Perception app was running, then it meant having to copy the Vireio DLLs to the
games folder in order for Vireio to inject. This was both cumbersome and error prone, as well as a barrier for those not au
fait with the filesystem of their PC.
In the absence of a full injection solution at this time, a utility has been written to assist with the copy/removal of the Vireio
DLLs. The Vireio DLL Symlink Installer (henceforth Symlink Installer) will make it much easier for those unfamiliar with DLLs
and the filesystem to get Vireio working for them against their favourite supported titles. If you wish to remove Vireio from
a particular game this utility will manage that too.
The advantage of this tool to the previous copy+paste approach is that it doesnt physically copy DLLs around the file
system, but simply creates links (known as symlinks, or symbolic links) from the game folder to the DLLs residing in the
Vireio bin folder.
Another, and probably more significant advantage is that if you upgrade Vireio, then simply putting it in exactly the same
location means you wont need to recreate the symlinks as they will point to the updated DLLs location already.
Instructions for use

Installing / Creating Symlinks
1.
Run the VireioDLLInstaller.exe found in the Perception/bin folder, this program requires Admin privileges and will
therefore request them on start-up
2.
The app should automatically locate your steam games folder
3.
Simply select the game you wish to inject Vireio into, we will choose Borderlands for this example:
4.
Click OK. The utility will then scan all sub folders looking for an executable that matches one in the Vireio profiles
configuration. If it cant find a supported game, then it will fail and report an error
5.
If it successfully finds a supported games executable you will be asked if you wish to install Vireio DLLs (create
symlinks), If you are certain, agree to the confirmation:
6.
The utility will then attempt to create symlinks to the Vireio DLLs in the games folder, if it succeeds youll see an
Install Complete Message Box.
Removing / Deleting Symlinks
1.
2.
Repeat steps 1-4 above

You will be asked if you wish to uninstall Vireio DLLs (remove symlinks), If you are certain, agree to the confirmation:
3.
The utility will then remove the symlinks from the game folder and next time the game is started it will not have Vireio
injected
Points to note
The utility will open on the same folder that was last used for install/uninstall (useful if you are switching back and
forth between Vireio and 2D)
Sometimes a game may have multiple executables (such as 32 and 64 bit) in different folders, do ensure that it is
going to create the symlinks in the appropriate folder in order for Vireio to work correctly.
For Example:
Bioshock 2 has Single and Multiplayer folders with the same named executable in, ensure that you select the single player
folder in the tool:
If Vireio DLL symlinks are already deployed to the folder (from a previous version for example), then the utility will
detect them and ask if they should be removed (as in the example above)
If you delete Vireio, ensure you remove all the symlinks from game folders first, otherwise the game will not run
until you do
If you deploy Vireio and it doesnt inject, ensure it created symlinks in the correct folder
Game Support List

General Settings
As of release 2.1.2 there are two recognised methods of ensuring games run at 75hz/FPS.
The new recommended method is to have the rift as extended (secondary) but have its position set to the left
of the main monitor (see below). Using this method the Rift can be set to 75hz whereas the monitor can be set to
standard 60hz. This has been tested working on Nvidia cards. If you find this does not work use the old method of
having both screens as 75hz.
Alternate (old) method - the Oculus DK2 should be set to extended (secondary). Both displays should be set to
1920x1080x75hz. If this is not possible for your monitor, you can either create a custom resolution (at your own
risk) or choose a lower sized resolution for your monitor that supports 75hz (usually 1152x864x75hz).
In the Vireio window select Oculus Rift (All Variants) from the drop down list of adapters.
When starting any game read the below instructions. Upon starting press Shift + R to reset the tracking position.
If the IPD feels off or you get a crossed eyed sensation you can adjust this with LCtrl + Shift + Mousewheel. Shift +
I will reset this to 0.
During Gameplay click the mousewheel button to look around the screen (disables in-game headtracking). For a
full list of helpful functions and settings see the Brassa menu (LCtrl + Q) and also the list of hotkeys below.
In all games the HUD size can be configured. We recommend using the Brassa menu to assign a hotkey to the
switch GUI or HUD option and setting sensible sizes. You generally want the small setting to be where the
complete HUD including items on the periphery can be easily seen. We then recommend a larger option that you
can switch to and use in conjunction with the above screen view.
Note: Games will only have a GUI control or HUD control. You can easily tell which by switching the options to see
which has an effect.
Also ensure you read how to run the pointer scanner to get some of the below list working with VR Boost. VR
boost is vital for low latency headtracking, definable FOV and gamepad support.
Note: For the Pointer Scanner to work properly, ensure that the FOV is set to the default and not changed for any
reason, by other injection drivers for example (if you haven't touched it, don't worry about it), follow per-game
instructions below.
There is a good chance that you can add your own profiles to get other games, not on the list below working. We
are always looking for volunteers to add official support (usually requires creating profile and specifying problem
shaders). If you would like to help contact neils@mtbs.com.
Use the in-game FPS counter (Shift + F) unless not available in the game you are playing (see below) to ensure
you are getting a solid 75FPS. When using a DK2, anything below 75FPS will have judder and be a sub par
experience so we do not recommend continuing to play.
A Story about my Uncle (Vireio VR Rating: Great)

1) Run ASAMU as per normal (without Perception). Set the resolution to 1920x1080. Set Vertical Sync to on. Set
the FOV to 120.
2) Use the Vireio Symlink Installer (instructions at the start of this document) to deploy Vireio to the game folder
To Run (each time)
1) Run Vireio Perception as an administrator
2) Run ASAMU
3) Once in-game use the pointer scanner to load VR Boost (see below instructions).
Known Issues
This game is very dark (dark caverns etc), so in the DK2 this causes significant black smear artifacts. Vireio now provides
basic black smear correction, which is turned off by default, to enable use SHIFT+B which will remove any black smearing
issues this game has
Alice Madness Returns (Vireio VR Rating: Great)

1) Run Alice Madness Returns as per normal (without Perception). Set the resolution to 1920x1080. Set Vertical Sync to on.
Turn off dynamic shadows. Turn off motion blur.
2) Open %USERPROFILE%\Documents\My Games\Alice Madness Returns\AliceGame\Config\AliceEngine.ini and change
bSmoothFrameRate=TRUE to bSmoothFrameRate=FALSE
3) Open %USERPROFILE%\Documents\My Games\Alice Madness Returns\AliceGame\Config\AliceInput.ini and add the
following:
Bindings=(Name="NumpadFive",Command="FOV 120",Control=False,Shift=False,Alt=False).
4) Open %USERPROFILE%\Documents\My Games\Alice Madness Returns\AliceGame\Config\AliceInput.ini and set
bEnableMouseSmoothing=false
To Run (each time)
2) Run Alice: Madness Returns
Known Issues
FPS can be a bit hit-and-miss, was sub-75 on my GTX-780 in the orphanage at the beginning, but then held steady 75fps
once I left the building.
This is 3rd person only, no cheats exist to make it first person (apart from at the beginning on the game when there is a 1st
person mode), despite the fact it is 3rd person, it is very playable, and a very enjoyable experience
Antichamber (Vireio VR Rating: Okay)

1) Find the BaseEngine.ini file
Location (Steam Version) usually:
C:\Program Files\Steam\Steamapps\common\Antichamber\Engine\Config\BaseEngine.ini
Open BaseEngine.ini using Notepad or WordPad.
find the entry for bSmoothFrameRate and set to FALSE
find the entry for UseVSync and set to True (You do want VSync on or you get tearing)
2) Run Antichamber as per normal (without Perception). Set the resolution to 1920x1080.
To Run (each time)
2) Run Antichamber
4) Antichamber does not have a working FOV adjuster, so you need to open the developer console with TAB after
you have run the VRBoost scanner and type the following and press ENTER: fov 120
5) DO NOT USE THE FPS COUNTER This seems to cause terrible FPS loss
Batman: Arkham City GOTY (Vireio VR Rating: Okay)

First, youll need to make sure it runs in DX9 mode, start the game through Steam, select Configure PC Options:
1.
2.
3.
4.
5.
6.
Go to Settings, Disable DirectX 11 Features

Disable DirectX 11 Tessellation
We suggest setting detail level to Medium and turning off Dynamic Shadows
Set VSync = Yes, Resolution = 1920x1080, Fullscreen = Yes
Exit the settings editor
Use the Vireio Symlink Installer (instructions at the start of this document) to deploy Vireio to the game
folder
Next go to the following location:

C:\Users\{username}\Documents\WB Games\Batman Arkham City GOTY\BmGame\Config
Open the file BmInput.ini:
Change the following to false
bEnableMouseSmoothing=false
Add the following at the end of the section [Engine.PlayerInput]
Bindings=(Name="NumPadFive",Command="fov 120")
Open the file BmEngine.ini

Ensure that frame rate smoothing is turned off
bSmoothFrameRate=FALSE
If you find the above settings dont stick, then you can go the following folder (C:\Program Files (x86)
\Steam\SteamApps\common\Batman Arkham City GOTY\BmGame\Config) and edit the default settings files,
if you do this, back them up first!!!
To Run (each time)
2) Run Batman AC
Known Issues
FPS take occasional hit sometimes, no apparent reason, lowest quality settings helps
Look will partially lock onto a target, this manifests as judder when moving head, it will also prevent mouse from
scrolling quite as smoothly
VRBoost has been known to cause game to crash when it is loading next stage
Betrayer (Vireio VR Rating: Excellent)

1) Run Betrayer as per normal (without Perception). Set the resolution to 1920x1080. Set Vertical Sync to on. Turn off
shadows, depth of field and light shafts. Set FOV to 110.
2) Open %USERPROFILE%\Documents\My Games\Betrayer\UDKGame\Config\UDKGameEngine.ini and change
bSmoothFrameRate=TRUE to bSmoothFrameRate=FALSE (There are 3 instances of this)
To Run (each time)
2) Run Betrayer
Known Issues
This is a hungry game. On my GTX980 / I7 4790 I had to set all detail levels to medium and turn off anti aliasing, to hit 75fps
and even then I saw dips suggesting even less details should be shown.
There is a Colour / Contrast menu in-game whilst playing. You can turn the saturation up to play the game in colour as
opposed to its default black and white.
Bioshock (Vireio VR Rating: Excellent)

1) Run the game normally and set the resolution to 1920x1080. Windowed mode to false. Turn off dynamic
shadows (Shadow Maps). Also turn off Directx 10 textures.
2) Open the launch properties from within Steam and enter "-nointro -dx9" (without quotes)
To Run (each time)
2) Run Bioshock
Known Issues
Some lights shown in mono. Can be solved by turning down textures.
Bioshock 2 (Vireio VR Rating: Excellent)

1) Run the game normally and in graphics options set the resolution to 1920x1080. Set Vertical Sync to true.
Windowed mode to false, Shadow Maps to false. Also turn off Directx 10 textures. Exit the game.
2) Open the launch properties from within Steam and enter "-nointro -dx9" (without quotes)
3) Use the Vireio Symlink Installer (instructions at the start of this document) to deploy Vireio to the single-player
(Bioshock2\SP) game folder
4) Press WinKey+R to open the run dialog. Enter %APPDATA% and hit enter. This will open your roaming profile.
Open Bioshock2Steam. Open User.ini. Scroll down of use CTRL+F to find the 1st entry of: NumPad5=. Change this
to be NumPad5=SetFOV 75. Save and exit (This is required by the scanner to locate the FOV address)
To Run (each time)
2) Run Bioshock 2
3) Once in-game use the pointer scanner to load VR Boost (see below instructions). Please note that step 4 above
is vital to load saved games.
Known Issues
HUD / GUI not scalable The HUD was made scalable in Vireio 2.1.2
Borderlands (Vireio VR Rating: Excellent)

Follow this exact order after installing:
1) Find the BaseEngine.ini file
Location (Steam Version) usually:
C:\Program Files\Steam\Steamapps\common\Borderlands\Engine\Config\BaseEngine.ini (path may be different
on your computer)
Open BaseEngine.ini using Notepad or WordPad.
2) Run Borderlands as per normal (without Perception). Set the resolution to 1920x1080. You are free to set all
other graphics option to your pleasing apart from "Dynamic Shadows", which must be set to Off. Exit Borderlands
3) Download the Borderlands Config Editor v2.1.4 (http://www.mediafire.com/download/in2oo6tkddo0y54/
Borderlands+Config+Editor+v2.1.4.exe - If this link gets broken let me know and I can upload my copy) and place
it in the C:\Program Files\Steam\Steamapps\common\Borderlands\Binaries folder. Run as Administrator and set
the following options:
Disable Startup Movies - Ticked (Unless you really want to watch the logos)
Disable Mouse Smoothing - Ticked
Enable V-Sync - Ticked
Leave all other options unticked.
To Run (each time)
2) Run Borderlands
Bulletstorm (Vireio VR Rating: Excellent)

This guide is for the Origin version of the game, results with the Steam version may differ
First, download BulletstormINIeditor_v1.1 as you will need this to edit the config files
1) Run BulletStorm as per normal (without Perception). Set the resolution to 1920x1080. You are free to set all
other graphics option to your pleasing (On my GTX980 I can set everything to high, but turn AA off, and I get solid
75FPS everywhere and it looks great)
2) Using BulletstormINIeditor_v1.1 Open %USERPROFILE%\Documents\My
Games\Bulletstorm\StormGame\Config\StormEngine.ini and change all instances (usually 2) of
bSmoothFrameRate=TRUE to bSmoothFrameRate=FALSE
3) Using BulletstormINIeditor_v1.1 Open %USERPROFILE%\Documents\My
Games\Bulletstorm\StormGame\Config\StormCamera.ini, set the following:
DefaultCameraFOV=120
TargetingFOV=110
SpectatingCamAimingOffsetBack=120.0
SpectatingCamRunningFOV=110
To Run (each time)
2) Run Bulletstorm
Chivalry: Medieval Warfare (32 and 64 bit support) (Vireio VR Rating: Good)
WARNING: Chivalry is an online multiplayer game, if you attempt to play on a public server using Vireio and
especially with VRBoost then it will probably be detected as an attempt to cheat and you may face a lifetime
ban.
DO NOT TAKE THIS WARNING LIGHTLY, any ban or caution you receive whilst using Vireio with or without
VRBoost on a public server is entirely your own responsbility.
You have been warned.
Chivalry: Medieval Warfare can be run in either 32 or 64 bit.
1) Run the game normally and set the resolution to 1920x1080. Set Vertical Sync to true. Windowed mode to
false.
2) Dsiable the following in the configuration settings: Dynamic Lights, Dnyamic Shadows, Motion Blur
3) set FOV to 120 (it absolutely has to be this value in order for the VRBoost scanner to succeed)
4) Use the Vireio Symlink Installer (instructions at the start of this document) to deploy Vireio to the 32 or 64 bit
game folder depending on the platform you intend to run
To Run (each time)
2) Run Chivalry: Medieval Warfare, select either Play Chivalry: Medieval Warfare (which is 64-bit) or Chivalry:
Medieval Warfare (32-bit):
3) Once in-game use the pointer scanner to load VR Boost (see below instructions)
Known Issues
There are a few known issues with this game, none of them serious, but best to be aware of them in advance:
Even at 75FPS this game does periodically judder in some of the environments, currently unknown what
the cause is
Pitch is locked to a max of 60 degrees up and down, dont be alarmed if you try to look up and the view
starts to move with your head, youve hit the limit. This is a feature of the game and is not possible to
bypass
Pitch also causes slightly odd translation of position, this is also part of the game mechanics (they havent
positioned the POV in the center of the head) and is therefore unavoidable
Roll can cause some odd behaviour with some shaders, it is fairly rare, but more apparent in some
environments than others
Crysis (Vireio VR Rating: Excellent)

1) Run the game normally and set the resolution to 1920x1080.
Windowed mode to false.
Turn off Motion Blur.
Shadows to Minimum,
if your system can handle it, crank everything up as far as you can (on my GTX980, with the following steps to get Very High
quality it looks awesome and holds 75fps: http://www.tweakguides.com/Crysis_13.html ).
2) Youll need to remap the suit -function quick access button in the game to something other than the mousewheel click, otherwise youll be constantly switching disconnected screen view on and off.
3) Open the launch properties from within Steam and enter "-dx9" (without quotes)
To Run (each time)
2) Run Crysis
Known Issues
Mouse separated for each eye.
FPS counter (and brassa generally) will drain the FPS if turned on. Not a huge issue but you wont get accurate FPS reading.
Crysis Warhead (Vireio VR Rating: Great)

Windowed mode to false.
Vertical Sync to true.
Turn off Motion Blur and set shadows to minimum.
If your system can handle it, crank everything up to Enthusiast level (GTX 980 held a steady 75 with these settings)
2) Youll need to remap the suit -function quick access button in the game to something other than the mouse-wheel click,
otherwise youll be constantly switching disconnected screen view on and off. If you have more mouse buttons than 3,
those are usually ideal.
3) Open the launch properties from within Steam and enter "-dx9" (without quotes)
4) The introduction movies (crytek logo etc dont play). These take up a long time anyway and are easily removed.
To automatically skip all of these, go to your steam common folder then Crysis WARHEAD\Game\Localized\Video
directory and rename all the .sfd files starting with Trailer_, as well as Crytek.sfd and Intro.sfd, and the
Trailer_Rating files under the \English folder to something else. Better yet, create a new folder under the \Video
directory (e.g. \Nomovies) and move all the above .sfd files to that new directory - I don't recommend deleting
them. The next time you launch the game it will automatically skip all these introductory movies.
To Run (each time)

2) Run Crysis
Known Issues
Mouse separated for each eye.
FPS counter (and brassa generally) will drain the FPS if turned on. Not a huge issue but you wont get accurate FPS reading.
Odd rotation issue when using stationary weapon. Mini map ceases correctly to function whilst in vehicle.
Notes
No introductory movie tip credit goes to http://www.tweakguides.com/CrysisWar_3.html
Dead Island (Vireio VR Rating: TBA) (coming soon..)
Dear Esther (Vireio VR Rating: Great)

There should be no need to copy any DLLs, as Vireio should inject by itself, however if it doesnt follow the same
instructions as above for deploying Vireio to the games folder.
Note: There may have been previous times where the notifications had to be switched off to play this game. This
is fixed in the latest build so you should always run with notifications="1" in the config.xml
To Run (each time)
2) Run Dear Esther
3) Once in-game, click the left mouse button and the FOV should adjust correctly (seems there is odd behaviour
whereby FOV changes dont immediately take)
No requirement to use the VRBoost Memory Scanner
Dirt3 (Vireio VR Rating: Good)

1) Run the game normally and set the resolution to 1920x1080. Windowed mode to false.
2) Browse to the following location and open the file: hardware_settings_config.xml
C:\Users\{username}\Documents\My Games\DiRT3\hardwaresettings
In there you will need to set:
<directx forcedx9="true" />
Ensure the resolution is set to 1920x1080 and vsync is on:
<resolution width="1920" height="1080" aspect="auto" fullscreen="true" vsync="1" multisampling="16xmsaa">
Make absolutely sure the refresh rate is set correctly to 75Hz:
<refreshRate rate="75" />
3) If you cannot run your monitor at 1920x1080x75 (usually a custom resolution) then you will have to set the
Rift as the primary monitor for this game to run correctly, or the resolution will not take and it will use the
resolution and refresh rate of the primary monitor.
To Run (each time)
2) Run Dirt3
No requirement to use the VRBoost Memory Scanner
Known Issues
Mouse issue?
Dishonored (Vireio VR Rating: Good)

1) Run the game normally and set the resolution to 1920x1080. Windowed mode to false. Turn on Vertical Sync
and set the FOV to 110.
2) Open: C:\Users\%USERPROFILE%\Documents\My
Games\Dishonored\DishonoredGame\Config\DishonoredEngine.ini
3) Find the line bForceNoStartupMovies
4) Change bForceNoStartupMovies=false to true.
5) Save the document.
6) Go to C:\Users\%USERPROFILE%\Documents\My
Games\Dishonored\DishonoredGame\Config\DishonoredInput.ini and open in Notepad.
7) Search for line m_PCBindings=(Name="Zero",Command="GBA_Shortcut_9") and add these lines after it:
m_PCBindings=(Name="NumPadFive", Command="FOV 120") and save the document.
To Run (each time)

2) Run Dishonored
3) Once in-game use the pointer scanner to load VR Boost (see below instructions). Note for some reason at the
very start of the game the scanner does not function. Once you have control of Garrett at least get off the boat
before running it. Scanner will take control of FOV for this game, hence the key binding requirement above, only
Orientation is identified by the scanner
Notes
There have been some reports that the GOTY edition EXE is named something slightly different. If this is the case
and you are receiving errors, then rename this to Dishonored.exe (courtesy of xcxv). It is possible that the scanner
will not work for the GOTY edition as the executable might be different, in which case you will need to use mouse
emulation (press NUMPAD8 when Vireio asks you to run the scanner, you may also need to enable head roll in
the BRASSA menus Overall Settings)

Known Issues
Currently HUD / GUI are not scalable. Head tracking does not function during in game cutscenes. Water
reflections incorrect.
Fallout 3 (Vireio VR Rating: Great)

1) In the launcher set the resolution to 1920x1080 "Full Screen".
2) As this can be a demanding game on hardware, set Detail levels to low, to ensure you have a solid 75FPS then
increase settings whilst ensuring it remains at 75FPS
To Run (each time)
2) Run Fallout 3
Fallout 3: New Vegas (Vireio VR Rating: Great)

1) Run the launcher and set the resolution to 1920x1080. Windowed mode to "Full Screen" and turn on vertical
sync. Adjust any graphics options you see fit but you must ensure that you are getting 75FPS in game. Generally
we have found a GTX 980 should handle this on a Ultra High, but set to a low value and work upwards if
necessary.
To Run (each time)
2) Run Fallout 3: New Vegas
3) This game has stable pointers so currently there is no need to run the scanner.
Far Cry (Vireio VR Rating: Great)

You need to start the Far Cry configuration tool. As this is an old game, most rigs will probably be able to handle maxed out
settings. Despite its age, this game actually looks pretty good in the rift.
It is also essential that you make the following changes:
1) Set the resolution to 1920x1080
2) Go to Video Options (Advanced) tab
3) Click Customize, and go to the Environment Quality tab
4) Set e_vegetation_sprites_distance_ratio to 9999.0

Setting FOV
In order to permanently set the FOV to something HMD friendly, go to the game_specific folder in the Vireio release
archive, open the Far Cry sub folder, follow instructions in the README.txt document to copy the Scripts.pak file to the
appropriate location (backing up the existing one first!)
Once you are in-game, you will need to click the right-mouse button for the new FOV to take effect.
To Run (each time)
2) Run Far Cry
3) When you exit the game it crashes every time, this is a known issue, simply push the return key to dismiss the crash
handler dialog
Far Cry 3 (Vireio VR Rating: Great)

These notes arent finished yet
Shadows to Low, turn everything else down to get 75FPS then slowly increase stuff (dont use FPS counter, this will reduce
FPS, use the new FPS counter on the Perception App)
Disable Overlay in UPlay
Reassign grenade launch (otherwise every time you use disconnected screen view, you throw a grenade)
DX9 - through in-game Menu
Use Flawless Widescreen (http://www.flawlesswidescreen.org/ ) for FOV of 120, as 110 isnt quite enough, settings I use:
VRBoost scanner uses below the horizon approach, when scanning, dont look above the horizon unless specifically
requested to do so by the scan assist.
Far Cry 3 Blood Dragon (Vireio VR Rating: Great)

Disable Uplay Overlay(accessible through settings)
Run the game once normally. Set Resolution to 1920*1080. Set vertical sync to on. Set Direct X version to DX9.
Reassign grenade launch key (as conflicts with disconnected screen)
Shadows to Low, turn everything else down to get 75FPS then slowly increase stuff (dont use FPS counter, this will
reduce FPS, use the new FPS counter on the Perception App)
5) Use Flawless Widescreen for FOV, as 110 isnt quite enough (see Far Cry 3 for reference)
6) Use the Vireio Symlink Installer (instructions at the start of this document) to deploy Vireio to the game
1)
2)
3)
4)
folder
How to get rid of scanlines:
1. Go into <path-to-game>\bin
2. Open FC3.dll in hex editor (HxD for example).
3. Search for COverlayTrack and change its corresponding hex values to zeroes. Save and enjoy.
To Run (each time)

2) Run Far Cry 3 Blood Dragon
3) Once in-game use the pointer scanner to load VR Boost (see below instructions). Please note that when scanning you
must keep his view below the horizon for it to work.
Known Issues
Some objects do not react to positional tracking. There are only a few but if this bothers you turn off positional tracking for
those scenes (Shift + P)
Homefront (Vireio VR Rating: TBA) (coming soon.)

1) Run the game normally and set the resolution to 1920x1080. Windowed mode to "Full Screen". Vertical Sync on and
Make sure DX11 is turned off
2) Smoothing
To Run (each time)
2) Run Homefront
Known Issues:
Left 4 Dead (Vireio VR Rating: Good)

1) Run the game normally and set the resolution to 1920x1080. Windowed mode to "Full Screen". Turn off
vertical sync and also lower the Film grain gauge until it is off.
To Run (each time)
2) Run Left 4 Dead
Left 4 Dead 2
Not test as yet in the current version (but thought to be working without the need to copy DLLS)
Mirrors Edge (Vireio VR Rating: Good)

1) Find the TdEngine.ini file
Location usually:
C:\Users\{username}\Documents\EA Games\Mirror's Edge\TdGame\Config\TdEngine.ini
Open TdEngine.ini using Notepad or WordPad.
2) Find the TdInput.ini file
Location usually:
C:\Users\{username}\Documents\EA Games\Mirror's Edge\TdGame\Config\TdInput.ini
Open TdInput.ini using Notepad or WordPad.
Add the following line as the first entry in the Bindings list (necessary for VRBoost scanner to succeed):
Bindings=(Name="NumPadFive",Command="FOV 120",Control=False,Shift=False,Alt=False)
3) Run Mirrors Edge as per normal (without Perception). Set the resolution to 1920x1080.
To Run (each time)
2) Run Mirrors Edge
3) Once in-game use the pointer scanner to load VR Boost (see below instructions). Ensure you are moving the
view slightly all the way through to ensure it doesnt discount valid addresses
4) DO NOT USE THE FPS COUNTER This causes massive frame-rate drops for some reason
The Old City: Leviathan (Vireio VR Rating: Excellent)

1) Find the UDKEngine.ini file
Location usually:
STEAM_DIRECTORY\common\Old City\UDK Game\Config\UDKEngine.ini
Open TdEngine.ini using Notepad or WordPad.
Find all entries of bSmoothFrameRate and set to FALSE
2) Run The Old City as per normal (without Perception). Set the resolution to 1920x1080. Full screen. V-Sync on.
Motion Blur Off.
To Run (each time)
2) Run The Old City
3) Once in-game use the pointer scanner to load VR Boost (see below instructions). Ensure you are moving the
view slightly all the way through to ensure it doesnt discount valid addresses
4) Change FOV using console
1. Press (the / @ key on UK keyboards) to open the developer console.
2. Type fov XX (replacing XX with your desired fov, I.e. 120).
3. Press enter to apply the new fov.
Outlast (64bit) (Vireio VR Rating: Great)

1) Run Outlast as per normal (without Perception). Set the resolution to 1920x1080. Set VSync to true and motion
blur to off. Set shadows to Very Low (this helps a lot with performance)
2) Open OLEngine.ini file
Location usually:
C:\Users\{username}\Documents\my games\Outlast\OLGame\Config\OLEngine.ini
Open OLEngine.ini using Notepad or WordPad.
find all entries for bSmoothFrameRate and set to FALSE
3) Find the OLGame.ini file
Location usually:
C:\Users\{username}\Documents\my games\Outlast\OLGame\Config\OLGame.ini
Open OLSystemSettings.ini using Notepad or WordPad.
Change DefaultFOV to 110/120 (whichever is your preference)
Change RunningFOV to 110/120 (whichever is your preference)
Change CamcorderNVMaxFOV to 110/120 (whichever is your preference)
Change CamcorderMaxFOV to 110/120 (whichever is your preference)
To Run (each time)
2) Run Outlast
3) Once in-game use the pointer scanner to load VR Boost.
4) Press Shift + P to turn off Positional Tracking. The shadows do not work well with positional. This is of course
at your discretion. You can play with positional if you dont mind the few issues.
Notes
VRBoost scanner uses below the horizon approach, when scanning, dont look above the horizon unless specifically
requested to do so by the scan assist.
Overlord (Vireio VR Rating: OK)

1) Firstly run Configure Overlord and set the resolution to 1920x1080.
To Run (each time)

2) Run Overlord
3) The game doesnt have a VRBoost profile (doesnt really need one).
Known Issues
FOV cant be adjusted, and it is a bit on the low side
Some loading screen objects only appear in one eye, but doesnt happen during normal gameplay
Portal (Vireio VR Rating: Good)

1) Add the following to the command line parameters, this will ensure Portal runs using DirectX 9 and has the
correct resolution:
-dxlevel 90 -w 1920
To Run (each time)
2) Run Portal
Once in-game:
3) I havent checked dynamic shadows, but in Portal 2 they do not work with Vireio, to resolve this if you are
getting bad visual artifacts, open the Developer Console (using ~ , you will have to enable it in the Options) and
type the following then press return: r_shadows 0
4) use the pointer scanner to load VR Boost (see below instructions).
Known Issues:
The original Portal only allows an FOV maximum of 90 and theres no way to get around this. Its not a disaster,
simply set the amount of Distortion in the BRASSA Overall Settings menu to a figure such that the view looks
natural. It does mean you will see the edges at the top and bottom, but you soon stop noticing them, and this
game looks good in the rift; I think youll be prepared to forgive it.
Tracking anomaly with head roll (some movement in the Y axis), it seems to be an issue with the lower distortion
required, but is not significant.
Portal 2 (Vireio VR Rating: Great)

1) Ensure resolution is set to 1920x1080
2) Set vertical sync to either disabled or double buffered (triple buffered will cause a perceivable lag in
headtracking). My personal preference is disabled (for this one game only). Please note that changing this setting
whilst Vireio is running will cause a blank screen. You should change this setting without Vireio first.
To Run (each time)
2) Run Portal 2
Once in-game:
3) Portal 2s dynamic shadows do not work with Vireio, to resolve this open the Developer Console (using ~ ) and
type the following then press return: r_shadows 0
4) use the pointer scanner to load VR Boost (see below instructions).
QUBE (Standard Edition) (Vireio VR Rating: Excellent)

Location usually:
C:\Program Files (x86)\Steam\SteamApps\common\QUBE\UDKGame\Config\UDKEngine.ini
Open UDKEngine.ini using Notepad or WordPad.
To Run (each time)
2) Run QUBE
4) You will need to re-run the scanner each time you complete a sector as it appears to reset, just hit NUMPAD5
and it will do the rest.
QUBE (Directors Cut) (Vireio VR Rating: Excellent)

Location usually:
C:\Program Files (x86)\Steam\SteamApps\common\QUBE Directors Cut\UDKGame\Config\UDKEngine.ini
Open UDKEngine.ini using Notepad or WordPad.
To Run (each time)

2) Run QUBE
4) You will need to re-run the scanner each time you complete a sector as it appears to reset, just hit NUMPAD5
and it will do the rest.
Rainbow Six: Vegas (Vireio VR Rating: Okay)

1) Run the game normally and set the resolution to 1920x1080. V-Sync on. Turn off motion blur. Hardware
Skinning On.
3) The default button assignments conflict with some of ours. Ensure that throw grenade is not assigned to Q
else you will have a big surprise when you enter the BRASSA menu. Also set zoom to be something different then
Mouse 3 (Mouse wheel click)
To Run (each time)
2) Run Rainbow Six Vegas
Known Issues:
The guns are generally 2d which can be a bit distracting.
No VR Boost profile present / Fixed FOV.
Skyrim (Vireio VR Rating: Good)

Follow this exact order after installing vanilla skyrim:
1) Run the game launcher and set the resolution to 1920x1080. Non Windowed mode.
2) We recommend for new users to complete at least the character creation at the start of the game in non-VR
mode before playing.
3) Close the game and open Skyrimprefs.ini (usually located in Documents/my games/skyrim). Find the settings
for the following and update the values:
fShadowDistance=0.0000
fInteriorShadowDistance=0.0000
fShadowLODStartFade=0.0000
bDeferredShadows=0 (Add this line in [Interface] if you don't see it.)
To Run (each time)
2) Run Skyrim
3) Once in-game use the pointer scanner to load VR Boost (see below instructions) - This has been changed to
use the scanner as there were some issues people were having with the existing VRBoost approach. If you have
problems with the scanner, edit the profiles.xml and change the following entry: VRboostRules="TESV.MTBS"
Notes: From feedback it would seem that sometimes, especially on non-steam versions on when launching with
mods or through a mod manager such as Mod Organizer or Nexus that the game won't inject or the VR Boost will
not engage. To fix the injection a work around is to use the Vireio Symlink Installer (instructions at the start of
this document) to deploy Vireio to the game folder. Unfortunately there is currently no fix for the VR boost, the
scanner may resolve the issue, but this is not guaranteed. You should be able to use mouse emulation instead
(see Overall Settings in the Brassa menu).
The Stanley Parable (Vireio VR Rating: Great)

1) Run the game launcher and set the resolution to 1920x1080. Non Windowed mode. Set vertical sync to either
disabled or double buffered (triple buffered will cause a perceivable lag in headtracking). My personal preference
is disabled (for this one game only). Please note that changing this setting whilst Vireio is running will cause a
blank screen. You should change this setting without Vireio first.
To Run (each time)
2) Run Stanley Parable
3) use the pointer scanner to load VR Boost (see below instructions). Note: Ensure you are not running the game
with the launch property "-console" as this will prevent the scanner from working and will give some rather
unpleasant lighting issues
Known Issues:
Headtracking does not function during (spoiler-MC) level. Shadow fix caused some menu issues. Suggest using
disconnected screen view whilst in menu
Other Notes:
Shadows have been fixed, but are not in the latest release. For the latest download the file here (https://
github.com/cybereality/Perception/blob/11acfa1f9772f370024dbfe8e270f775f4a712e3/Release/Perception/cfg/
shader_rules/stanley.xml) or contact one of the team for support.
The Vanishing of Ethan Carter (32 and 64 bit support) (Vireio VR Rating: Good)
1) Run The Vanishing of Ethan Carter as normal (without Perception). Set the resolution to 1920x1080.
2) In the in-game controls configuration; set the following to ensure the most comfortable experience:
Mouse Sensitivity: 5
Camera Head Bobbing: No
Camera Smoothing: 0
Set the FOV to 120 (it absolutely has to be this value for the VRBoost scanner to succeed)
3) This game has very high graphical requirements (but oh man, is it pretty!), ideally you should aim to get 75FPS,
but that will be difficult to do with anything but a very high-end gaming rig. Suggestion is you dial everything back
to low and turn off AA and ansiotropic filtering, and then add effects and gradually in order to maintain a steady
75FPS framerate
4) Use the Vireio DLL Symlink Installer to deploy Vireio into the correct game folder for your OS, please follow
instructions at the start of this guide.
IMPORTANT NOTE: The Vanishing of Ethan Carter is one of the first games to get 64-bit Vireio support (which
enables the use of high resolution textures). In order to ensure Vireio injects correctly you need to deploy
Vireio to the correct bin folder depending on the platform the game is running on.
If you are running a 64-bit OS then the game will always run in 64-bit mode, you therefore need to select the
Win64 folder in the symlink installer in the games folder, e.g.:
If you have a 32-bit OS, then you will only be able to run the 32bit version of the game, and therefore have
to deploy Vireio to the Win32 folder. Both platform variants of the game are supported and have working
profiles.
To Run (each time)
2) Run The Vanishing of Ethan Carter
4) Gaze in awe at the beautiful scenery and then sob gently as you realise your rig isnt beefy enough to sustain
75FPS unless you are staring directly at a wall
Zeno Clash (Vireio VR Rating: Poor)

1) Run the game launcher and set the resolution to 1920x1080. Non Windowed mode. In advanced menu, Set
shadow to Low and Vertical Sync to Disabled.
2) Copy the items in the following Zip file (https://drive.google.com/file/d/0BzqmJ69EehZ0Vk5EOWt4NWRWRzg/
view) to Steam/SteamApps/common/zenoclash/zenozoik/scripts overwriting the ones currently existing.
To Run (each time)
2) Run Zeno Clash
3) use the pointer scanner to load VR Boost (see below instructions). Note: Ensure you are not running the game
with the launch property "-console" as this will prevent the scanner from working and will give some rather
unpleasant lighting issues
4) We recommend playing this game with positional tracking off.
Known Issues:
Positional tracking causes sky tearing issues. Items at wrong depth. When locked onto an enemy you lose
headtracking.
Vireio Perception - Shortcut Keys

Toggles and Menus
Key
LCTRL + Q
Alternative Key
Double-Click Start
button on Xbox 360
Controller
Function
Show/Hide BRASSA Menu
RSHIFT
Select item in BRASSA Menu
ESCAPE
Close BRASSA Menu
LSHIFT + F
LCTRL + F
Show FPS / Frame Time counter
LSHIFT + H
LCTRL + H
Show/Hide HMD Stats
LSHIFT + R
LCTRL + R
Reset HMD Orientation / Position
L+R Shoulder
Buttons on Xbox 360
Controller
LSHIFT + P
LCTRL + P
Toggle Positional Tracking
LSHIFT + L
Toggle Depth Perception Mode (ALPHA)
LSHIFT + DELETE
Toggle Oculus VR SDK Pose Prediction (default is on, and

recommended it remains like that, only turn off if you are
experiencing judder to see if it helps)
LSHIFT + B
Toggle DK2 Black Smear Correction (default is off)
LSHIFT + J
LCTRL + J
Toggle Chromatic Aberration Correction (default is on)
LSHIFT + X
Toggle Free-Pitch / Unlocked Mouse y-axis Mode (when

using VRBoost)
LSHIFT + V
Show VRBoost Active Axes and Addresses (for debugging

scanner profiles)
LCTRL + NUMPAD 0
Toggle VR Mouse
LCTRL + NUMPAD 1
Toggle Floating Menus
MOUSE WHEEL
BUTTON
LCTRL + NUMPAD 2
(hot-key for this can
also be defined in the
Disconnected Screen View
BRASSA menu)
RCTRL + *
Take Stereo Screenshot
LEFT ALT + MOUSE

WHEEL BUTTON
CHEAT: Telescopic Sight

For games that support a WorldFOV adjustment in VRBoost,
this cheat mode will enable a telescopic sight (toggle)
LCTRL + +
Restore current maximum distortion
NUMPAD 5
LCTRL + /
Run the VRBoost Memory Scanner (on compatible games)
NUMPAD 8
LCTRL + ;
Dismiss scanner messages and use Mouse Emulation for

head tracking
NUMPAD 4
LCTRL + ,
Move to the Previous candidate scan result (Scan Assist

Mode)
NUMPAD 6
LCTRL + .
Move to the next candidate scan result (Scan Assist Mode)
Adjusters
Key
Mouse
Function
LCTRL
MOUSE WHEEL
Distortion Intensity (Zoom in/out)
LCTRL + TAB
MOUSE WHEEL
Adjust Y offset of Display
LCTRL + LSHIFT
MOUSE WHEEL
Adjust IPD image separation
LCTRL + ALT
MOUSE WHEEL
Adjust World Scale (use with extreme caution)
LCTRL + SPACE
MOUSE WHEEL
Adjust Convergence (use with extreme caution)
Pressing the backspace on most value adjusters in the BRASSA menu will either return it to its default value or 0
Duck and Cover mode

Overview
Duck and Cover mode is an extension to the positional tracking implementation, that allows you to configure in-game
actions based on your stance.
Until now, if you were playing standing up, then crouching down would move the camera down with you, but as far as the
game-engine is concerned your avatar would still be standing up, and therefore not protected or out of sight.
With Duck and Cover, you configure the key presses that are used for Crouch, Prone (if the game supports it) and Jump
(which can be disabled). You then go through a very quick calibration to set the trigger heights and from then on, crouching
lower will cause your character to crouch, and similar for prone and Jump (extreme caution required when jumping with a
HMD on your head!).
Since Crouching, lying down (or crouching very low) and Jumping up and down arent really activities associated with a
seated experience and the fact that you would probably not be able to use the keyboard very well, use of an Xbox 360
controller is strongly encouraged.
NOTE: Some games (Far Cry 3 for example) disable the use of the mouse and/or keyboard when a 360 controller is plugged
in, which can be problematic. Whilst it is possible to perform a VRBoost scan under these circumstances, you might have to
try a few times. Games that disable the keyboard entirely cannot use Duck and Cover mode, since it is only able to supply
keyboard events to trigger in-game crouch/prone/jump.
Configuration
First D&C mode needs to be configured, open the Vireio Perception in-game menu (LCTRL+Q), go to the Positional Tracking
menu then go to the Duck and Cover Configuration sub-menu.
In this menu you can set whether Crouch/Prone is a toggle key (press and release) or hold (hold to engage, release to
disengage), and the key used to trigger crouching in-game. Similar for Prone and Jump if you wish to use them (Jump can be
enabled/disabled from here). Once you have set these, use the Calibrate option to run through a set of steps which will set
the y-positional heights that trigger the events.
If the game doesnt support Prone position, then push the B button on the 360 controller when this part of the calibration is
shown.
Once calibration is complete, Duck and Cover mode is enabled, and Y-Positional tracking will be reduced, but will trigger
in-game actions with your real world movements. D&C can be disabled through this same menu (and y-positional tracking
will be fully reinstated).
Disclaimer
You use this feature at your own risk. Any personal or third party injury or damage sustained whilst using this feature are
in no way the responsibility of the Vireio Development team or any associated person or organisation.
VRBoost Memory Scanner

How to use the new VRBoost Memory Scanner
The VRBoost Memory Scanner avoids the need to spend a long time finding stable pointers to memory locations
that control aspects of the game vital to the VR experience. Primarily these are orientation (Yaw, Pitch, Roll) and
additionally FOV, in order to have a low latency and improved VR experience the VRBoost library is now able to
scan the process memory of a game while it is running to identify (using a pre-configured scan profile in the form
of an XML file) the addresses the game is using for orientation and FOV.
In most cases, the scanner is able to identify these addresses fairly easily, but in others some assistance is
required to get it to the correct locations. In most cases the results with the scanner should be fairly consistent,
however it is possible that a large number of applications in memory or significantly different hardware may
result in games being loaded into different areas of memory which will adversely affect the ability of the scanner
to succeed.
To maximise the chance of success with the scanner, the following approach should be taken:
Most Important: Before starting the game, try to reduce the number of applications running to as few
as possible. Too many applications in memory will potentially move target scan addresses (orientation or
FOV controls) to other areas of memory that the scanner will not be configured to check and therefore
the scan will fail
Do not start a scan until you are in-game and able to change the orientation by moving your head.
Mouse emulation is enabled before and during the scan so that head tracking is working, this also assists
the scanner in finding stable addresses
Dont look straight ahead, look below the horizon and to the right to help (the scanner ignores 0 position
values, so if you happen to be looking directly ahead at the time the scan starts it may dismiss valid
locations)
Start the scan with Numpad 5
The scanner will first do an initial scan of the process memory looking for candidate locations that control
orientation or FOV
Once that stage is complete, the scanning begins, at this point the status will change to SCANNING and to
assist the scanner it is best to start moving the view around with the mouse or your head.
Moving the view in a very small, but noticeable circle is good
Look slightly right first
Sometimes we have found that the speed of head tracking invalidates standard addresses. If you
are finding that scans are successful but then orientation doesnt work, then try using the mouse
to move the view during this stage
If the game requires the scan assist step, then this will start now (see further instructions below)
Hopefully after a few seconds, the scanner should lock onto stable addresses and the FOV should change
appropriately (if the scanner for that game supports FOV)
If the scan fails then you can restart it with Numpad 5
If it continues to fail, you can either just continue to play with mouse emulation turned on or you could
restart the game and try again. This may result in success as the memory location will change and if it
was outside of the scanned region (unlikely, but not entirely impossible) then a restart might set it to
something the scanner can detect.
If you have a successful scan with working orientation try to avoid running this again as doing so may
invalidate the addresses, however future versions of Vireio should allow the scan to be run as many times
as you wish
If you do run the scan again and it fails, then you may need to reset the FOV to what the scanner is
expecting as per the games instructions, if it was changed by VRBoost then it might cause future
scans to fail
If the scan claims it was successful, but you have no head tracking then run the scan again, sometimes
it might take a few goes to hit on the correct addresses (has been seen in Mirrors Edge), alternatively it
might have multiple candidates (see the scan assist section below)
However, if VRBoost loses the stable addresses (the game may move them sometimes, this has been seen
in Bioshock 2 when it loads a new level) then it is necessary to re-run the scanner, repeat as above. This
scenario is instantly noticeable as you will lose head tracking.
If you find you periodically lose head tracking and a mouse movement restores it, then this is because the
minVRboostShaderCount is set too low in the profiles.cfg and VRBoost is not being utilised, reduce this
number slightly and it should occur less frequently.
Crashes - It is not unheard of for the scanner to crash, this can be for a number of reasons, if you are
already into a game before you run the scan ensure you have recently saved to avoid losing anything
The scanner runs on a separate thread to avoid causing serious delays to the rendering, it is
possible (but rare) that it can access a memory location that was previously valid but has since
become invalid during the scan
Exiting the game to a main menu page can also rarely cause a crash, this is because the game may
no longer be using the known memory locations for orientation, but for something else (or have
de-allocated them entirely), but VRBoost continues to write to them. If this is happening to you it
is advisable to configure the VRBoost toggle hot-key and ensure you disable VRBoost before you
exit the game to a menu.
Scan Assist
In order to improve the ability of the scanner to find orientation addresses, a scan-assist mode has been added
for some of the more awkward games that directs the user to look in specific directions in order to isolate
potential orientation addresses.
At the end of the scanning stage, if the game requires scan-assist, you will be asked to look straight ahead
(doesnt have to be exact) and press the scan initialisation key (NumPad 5), this will initiate the scan-assist
stage. Usually you will then be directed to look up before the countdown completes, and then down before the
countdown completes. At this point the scanner should have found at least 1 potential candidate.
If it fails with No viable addresses, just restart the scan (with Numpad5).
Scan assist tips:
When looking up or down, dont try to look as far as possible in the direction, just make sure you are
mostly looking up or down, potential injury might result if you do, and we will not be held responsible.
If and when it completes, it says it has multiple candidates, but you dont appear to have working head
tracking, then use NUMPAD 4 or 6 to iterate through the candidate addresses (there should only be a few
at most), youll know when you have selected the right one, as head tracking will instantly start to work.
Creating Shader Profiles

How to create a basic shader profile for currently unsupported games
1. If Vireio doesnt inject when the Perception App is running ensure you have copied the Vireio DLLs to the
appropriate folder for your target game.
2. Find out what game engine your game uses (examples: Unreal (UDK), Unity, Gamebryo, Source etc)
3. Create a new entry in profiles.xml, for best results copy one that uses the same game engine, remove any value for
VRboostRules and shaderModRules (set them to ), set rollEnabled=true
The game types can be seen below (these are taken directly from the vireio source, note that the presence of a game in the
list below doesnt mean it works/is supported):
SOURCE = 100,
/**< Source is a 3D video game engine developed by Valve Corporation. */
SOURCE_L4D = 101,
/**< !! */
SOURCE_ESTER = 102,
/**< !! */
SOURCE_STANLEY = 103, /**< !! */
UNREAL = 200,
/**< The Unreal Engine is a game engine developed by Epic Games, first illustrated in the 1998 first-person shooter game Unreal. */
UNREAL_MIRROR = 201,
/**< !! */
UNREAL_UT3 = 202,
/**< !! */
UNREAL_BIOSHOCK = 203, /**< !! */
UNREAL_BIOSHOCK2 = 204, /**< !! */
UNREAL_BORDERLANDS = 210, /**< Borderlands(TM) */
EGO = 300,
/**< Ego Game Technology Engine (more commonly referred to as Ego Engine or EGO, stylised ego) is a video game engine developed by
Codemasters. */
EGO_DIRT = 301,
/**< !! */
REALV = 400,
/**< Real Virtuality is a proprietary computer game engine developed by Bohemia Interactive (BI), originally called Poseidon. */
REALV_ARMA = 401,
/**< !! */
UNITY = 500,
/**< Unity is a cross-platform game engine with a built-in IDE developed by Unity Technologies. */
UNITY_SLENDER = 501,
/**< !! */
GAMEBRYO = 600,
/**< Gamebryo 3D and LightSpeed engines are owned by Gamebase Co., Ltd. and Gamebase USA and have been used by several video game
developers. */
GAMEBRYO_SKYRIM = 601, /**< Skyrims Creation Engine still has at least some Gamebryo in it. */
4. Add 10000 to the value for the game_type in profiles.xml, this will start Vireio in shader Analyser mode - example:
if the game type is 201, it should now be 10201
5. I suggest that when performing the following, you use a monitor for the display in Vireio (but the rift must be
plugged in and turned on for it to work), it is easier to see progress of the shader analyser
6. Start the game and ensure that Vireio has injected correctly
7. Open the BRASSA menu (CTRL+Q) and go into the Shader Analyser sub menu
8. Select Create new Shader Rules and play the game for a while, you should see green dots appearing in the top-left
corner of the right eye, this is the analyser identifying the various shaders and projection matrices
9. Once it has not added any green dots for a bit, go into the BRASSA menu -> Shader Analyser menu and select Save
Shader Rules
10. Exit the game, edit the profiles.xml and remove the extra 10000 - example, if the game_type is 10201 change it to
201 again
11. Now start the game, if it worked you should now get stereo separation!
NOTE: Some games require some specific handling for certain rendering scenarios, hence the enumeration with specific
game entries in it. If you find that you get some graphical anomalies then try a different game_type from the list that
matches the game engine
The above is the bare minimum required to get a game working, however you will likely see graphical glitches and artifacts,
more detailed tweaking of the shaders in the Shader Analyser is required to eliminate these.
Troubleshooting - Tips and suggestions

This section contains more general suggestions that people have found sorts out issues for them, you may wish to try
some of them if you have a similar issue to see if it helps (this list will increase over time). The idea is these help if you have
crashes, or other non-game specific problems (such as blank screen in some games):
when I run Skyrim, I only see a black window taking up a portion of the screen
Toggle Windows Aero to off and see if that helps
Can see edges of screen when playing or have borders
Eye are misaligned or dont take up the whole view
Firstly ensure that the resolution ingame is set to 1920 x 1080
Increase the Distortion Scale through overall settings in the brassa menu til the borders disappear
If you see a border at the top or bottom only, use Y-Offset to move the display up and down a bit to see if you can eliminate it without increasing
distortion any further
Ensure that IPD-Offset (BRASSA Menu -> Overall Settings) is set to 0 to begin with, then adjust for personal preference
VRBoost not affecting the FOV
Some game configurations dont allow for the FOV address to be easily found by the scanner, in these cases the FOV is adjusted using a key binding or
some in-game option (though occasionally this is done to give the scanner a hint), and once set to something HMD friendly, theres no need for it to
change.
I am getting judder even though the FPS reading is a steady 75fps
Try turning off Pose prediction (Shift + Delete)
Try switching the headtracking to Beginning of scene (Alt + Down arrow)

VireioPerceptionManualv1 1 14

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

VireioPerceptionManualv1 1 14

Transféré par

Droits d'auteur :

Formats disponibles

Vireio Perception 2.1.

Vireio Perception User Guide: 1/60

Current Request List + Status

Vireio Perception User Guide: 2/60

Vireio Perception User Guide: 3/60

Vireio Perception User Guide: 4/60

The Stanley Parable (Vireio VR Rating: Great)

Vireio Perception User Guide: 5/60

Vireio DLL Symlink Installer

Instructions for use

Vireio Perception User Guide: 6/60

Removing / Deleting Symlinks

Repeat steps 1-4 above

Vireio Perception User Guide: 7/60

Game Support List

Vireio Perception User Guide: 8/60

Vireio Perception User Guide: 9/60

Vireio Perception User Guide: 10/60

A Story about my Uncle (Vireio VR Rating: Great)

Vireio Perception User Guide: 11/60

Alice Madness Returns (Vireio VR Rating: Great)

Vireio Perception User Guide: 12/60

Antichamber (Vireio VR Rating: Okay)

Vireio Perception User Guide: 13/60

Batman: Arkham City GOTY (Vireio VR Rating: Okay)

Go to Settings, Disable DirectX 11 Features

Next go to the following location:

Vireio Perception User Guide: 14/60

Open the file BmEngine.ini

Vireio Perception User Guide: 15/60

Betrayer (Vireio VR Rating: Excellent)

Vireio Perception User Guide: 16/60

Bioshock (Vireio VR Rating: Excellent)

Vireio Perception User Guide: 17/60

Bioshock 2 (Vireio VR Rating: Excellent)

Vireio Perception User Guide: 18/60

Borderlands (Vireio VR Rating: Excellent)

Vireio Perception User Guide: 19/60

Bulletstorm (Vireio VR Rating: Excellent)

Vireio Perception User Guide: 20/60

Vireio Perception User Guide: 21/60

Vireio Perception User Guide: 22/60

Crysis (Vireio VR Rating: Excellent)

Vireio Perception User Guide: 23/60

Crysis Warhead (Vireio VR Rating: Great)

To Run (each time)

Vireio Perception User Guide: 24/60

Dead Island (Vireio VR Rating: TBA) (coming soon..)

Vireio Perception User Guide: 25/60

Dear Esther (Vireio VR Rating: Great)

Vireio Perception User Guide: 26/60

Dirt3 (Vireio VR Rating: Good)

Vireio Perception User Guide: 27/60

Dishonored (Vireio VR Rating: Good)

To Run (each time)

the BRASSA menus Overall Settings)

Vireio Perception User Guide: 29/60

Fallout 3 (Vireio VR Rating: Great)

Vireio Perception User Guide: 30/60

Fallout 3: New Vegas (Vireio VR Rating: Great)

Vireio Perception User Guide: 31/60

Far Cry (Vireio VR Rating: Great)

Vireio Perception User Guide: 32/60