[rFactor2] RF2Rift Oculus Rift Plugin

[VELOCIPEDE]

Vittorio ha rilasciato il nuovo RF2Rift, un plugin per far funzionare il già noto Oculus Rift con rFactor2; qui di seguito dettagli e spiegazioni:

Installation and usage
Assuming your rFactor2 installation dir is: C:\Program Files (x86)\rFactor2
and your Packages dir is: C:\Program Files (x86)\rFactor2\Packages
rFactor2 Oculus Rift Headtracking Plugin installation

• Download Rf2Rift_1_0.zip (see Attachments) and extract
• Copy Rf2Rift_1_0.dll to C:\Program Files (x86)\rFactor2\Plugins
• Copy Rf2RiftOccupy.exe to your Desktop (so it’s easily accessible)
• Remove the file C:\Program Files (x86)\rFactor2\Plugins\TrackIR_rF2_Plugin.dll to avoid a conflict (keep a backup)

Change following settings in C:\Program Files (x86)\rFactor2\UserData\player\player.PLR:
Glance Rate=”200.00000″ // Rate to follow controller for glancing
Look Up/Down Angle=”1.00000″ // Angle to look up/down (pitch) w/ controller in radians (= degrees / 57)
Look Roll Angle=”1.00000″ // Angle to lean head (roll) w/ controller in radians (= degrees / 57)
Glance Angle=”1.00000″ // Angle to look left/right (yaw) w/ controller in radians (= degrees / 57)
Lookahead Angle=”0.00000″ // Angle to lookahead (yaw) w/ steering in radians (= degrees / 57)
Head Rotation=”1.00000″ // Additional head physics multiplier affecting rotation only
Exaggerate Yaw=”0.00000″ // Visually exaggerates the heading angle of the vehicle by rotating the head (which may improve “feel”)
Cockpit Vibration Mult1=”0.00000″ // Primary aerodynamic vibration multiplier affects eyepoint position (base magnitude is in VEH or cockpit file)
Cockpit Vibration Freq1=”0.00000″ // Primary rate of vibration affects eyepoint position (higher framerates allow higher rates)
Cockpit Vibration Mult2=”0.00000″ // Secondary aerodynamic vibration multiplier affects eyepoint orientation (base magnitude is in VEH or cockpit file)
Cockpit Vibration Freq2=”0.00000″ // Secondary rate of vibration affects eyepoint orientation
Car Vibration Mult1=”0.00000″ // Primary engine vibration multiplier affects position of cameras attached directly to the car
Car Vibration Mult2=”0.00000″ // Secondary engine vibration multiplier affects orientation of cameras attached directly to the car
rFactor2 Oculus Rift Headtracking Plugin usage
I assume you have Tridef beta with Oculus Rift support installed (see Tridef beta installation and settings below). Since Tridef uses the Oculus Rift headtracker the plugin wouldn’t have access anymore. Rf2RiftOccupy.exe is needed to prevent Tridef to use the headtracker.
To start rFactor2:

• Start Rf2RiftOccupy.exe (if not already running)
• Start Tridef 3D Ignition and rFactor2 (Launcher)
• Enter Single Player or Online Race
• Wait 15 sec (you will hear a beep after the 15 sec, the headtracker got released by Rf2RiftOccupy and is ready)
• Enter Race (or enter a server for Online Race)

Sensor calibration
The “Look Down” key is used for calibration. Assign it to a button on your wheel so it is easily accessible:
SETTINGS->CONTROLS->CAMERA and assign “Look Down” to a button on your wheel.
When you press the Look Down button (in car) the headtracker gets recentered and calibration starts.
Look left past 90 degrees and hold it for a second. Return to center. Look right past 90 degrees and hold it for a second. Return to center. Finally look up past 90 degrees and hold it for a second. You should see a message “Oculus Rift calibration finished.”
Known problems
When entering a race (or practice ..) the plugin doesn’t work for the first ~13 sec. This is a known bug in the rF2 plugin system and hopefully gets fixed soon! If you are prone to motion sickness it’s best to not move your head during that time. Wait for the message “Oculus Rift is ready.” (AFAIK there is no message after restart race)

rFactor2 Oculus Rift Customized HUD installation
(Like every other rfcmp):

• Download riftmultidial_0_8.zip (see Attachments) and extract
• Copy riftmultidial_0_8.rfcmp to C:\Program Files (x86)\rFactor2\Packages
• Start rFactor2 Launcher
• Click Manage Mods
• Check Viewing: Components
• Select Rift Multi Dial
• Click Install

In rFactor2 Single Player:

• Enter CUSTOMIZE->ONCSCREEN DISPLAY
• Select RIFTMULTIDIAL

rFactor2 Oculus Rift Customized HUD usage
The customized HUD is needed to be able to see necessary informations in race. These are:
Flags and symbols (top left). Messages (top). The HUD MFD (bottom right, access with key 6 by default) and the HUD Stats (bottom, access with key 4 by default). Virtual mirrors aren’t visible, they would break immersion anyway.
Tridef beta installation and settings
Follow http://www.tridef.com/forum/viewtopic.php?f=24&t=3907 for installation.
These settings are known to provide good results (using Tridef 3D V5.9 and Tridef Ignition 3.7.6 beta 4):
rF2:

• SETTINGS->DISPLAY->VERTICAL FOV: 88

Tridef:

• 3D->Scene Depth: 60
• 3D->Custom Focus: On
• 3D->Near Plane: 0
• 3D->Far Plane: 100
• HMD->World Scale: 0.05
• HMD->Force FOV: Output
• HMD->Output FOV: 95
• HMD->OSD Depth: 0.50
• HMD->Output Quality: High
• (HMD->Head Tracking->everything off)

TODO Test new resolution possibilities Tridef Ignition 3.7.6 beta 4 provides to optimize FOV and FPS.
These settings are known to provide good results (using Tridef 3D V5.9 and Tridef Ignition 3.7.6 beta 2):
rF2:

• SETTINGS->DISPLAY->VERTICAL FOV: 88

Tridef:

• 3D->Scene Depth: 60
• 3D->Custom Focus: On
• 3D->Near Plane: 0
• 3D->Far Plane: 100
• HMD->World Scale: 0.05
• HMD->Force FOV: Output
• HMD->Output FOV: 95
• HMD->OSD Depth: 0.30
• HMD->Output Quality: High
• (HMD->Head Tracking->everything off)

History

• 15.08.2013: Initial release. Rf2Rift V1.0, riftmultidial V0.8
• 16.08.2013: Added to installation description to remove TrackIR_rF2_Plugin.dll
• 16.08.2013: Added Tridef Ignition 3.7.6 beta 4 settings

download qui http://isiforums.net/f/showthread.php/14441-Rf2Rift-rFactor2-Oculus-Rift-Plugin-and-Tools?p=196575&viewfull=1#post196575

http://www.youtube.com/watch?v=yPi7uLkRAJ8&feature=player_embedded

[VELOCIPEDE]

nuova versione disponibile

 

 I got rid of the initial added height of the neck&head model, so initial eye position = cam position of the mod,
and changed the prediction modes to:
* Oculus Rift prediction = Off
* Oculus Rift prediction = 5 ms
* Oculus Rift prediction = 10 ms
* Oculus Rift prediction = 15 ms
* Oculus Rift prediction = 1 frame
* Oculus Rift prediction = 1 frame + 5ms
* Oculus Rift prediction = 1 frame + 10ms
* Oculus Rift prediction = 1 frame + 15ms
* Oculus Rift prediction = 2 frames
* Oculus Rift prediction = 2 frames + 5ms
* Oculus Rift prediction = 2 frames + 10ms
* Oculus Rift prediction = 2 frames + 15ms
Although it seems the default mode: Oculus Rift prediction = 1 frame is a good value anyway.

[TaurineZ]

finalmente un thread sull'Oculus!

[Filodream]

Funziona benissimo..

E' un peccato che rfactor2 si fermi a 100 come valore di FOV massimo.. servirebbe qualcosa in più.

 

C'è, inoltre, un modo per abbassare un po' la luninosità in pista?