With a 2080Ti and the OBC framerate improvements this has become a much more viable option. Requires: 1) Vorpx - www.vorpx.com - NOT free 2) Opentrack - Head-tracking software than can use SteamVR or Oculus SDK tracking to spoof a TrackIR and thus work in Star Citizen/ Arma3 etc - download from here : https://github.com/opentrack/opentrack/releases 3) This headtracking profile for use with Opentrack : https://www.dropbox.com/s/yezoftsv2kf5sqj/sc-33-mongrel.ini?dl=0 ** This is a new version of the profile (much better) - stupidly is same name though - redownload even if you have a previous version of it ! If you find the AR info panels in your helmet moving around too much in game, you can turn off X and Y axes in the Opentrack config menu, or turn their tracking right down in the mapping, and they wont move around as much, but your head movement is more limited then (it's a trade off). Steps: 1st. Set up a custom user.cfg file. This sits in the C:\Program Files\Roberts Space Industries\StarCitizen\LIVE folder, and isn't there by default. Download my copy from here : https://www.dropbox.com/s/rttf34hjiac1a7y/user.cfg?dl=0 and save that to the LIVE folder. The ratio of r_Width and r_Height values in user.cfg has to remain 18:10 (Width to Height) in order to give you the FOV slider range of 100 - 114 (which is necessary for the HMD). EDIT : Have found 4400 x 1000 in user.cfg gives you a slider from 113 - 125 and setting it to 120 FOV is a bit better again. Try that if you are finding 114 FOV a bit too narrow for your tastes. For Pimax using Small FOV (ie lowest setting) - use 4400 x 1000. For Normal FOV (middle setting) use 3060 x 100 which gives you a slider from 131 - 140. I haven't been using Full FOV to save framerate, but am working on one for that using multi-monitor resolutions - will update when I find a good one. 2nd. Load up opentrack and click on the word Profile, this will throw up a dropdown and go to "open configuration directory". Copy and paste the downloaded headtracking profile into the config directory, then restart Opentrack. The tracking profile (sc-33-mongrel.ini) should now be selectable in the drop down box next to the word "Profile". Select it. Now select your input depending on your HMD (SteamVR for Vive/Vive Pro or Oculus 1.4 for Rift) from the dropdown box on the left, and select "freetrack 2.0" from the output box below. Leave the filter box blank. *EDIT: if using the newer beta of opentrack and can't get the filter box to remain empty/turn off, go into it's settings (hit icon next to the box) and set the sliders and deadzones to 0. That makes it work better. The non-beta version of Opentrack doesn't have this problem, you can just set it to no filter, so try using that version if having problems. Hit start and move HMD around, the pink octopus should move around with your HMD. "CTRL + V" is set to recenter the headset - this can be edited in the profile options. Hit recenter if your tracking goes wonky in game. In the Output tab under the Options window there is a custom centre pose and I have added 3cm positive to the Z value. This can be tinkered with as well, it's just what works for my setup. Try setting it to 0.00 if you need to. Mapping has taken a long time to get right for my set-up but it too can be tinkered with. It used to be that star citizen would crash if you had opentrack open and running at load time, (so you had to Alt + Tab out and start it after Star Citizen had loaded) but it doesn't appear to any more. 3. Start Vorpx and then load star citizen. One trick to using Vorpx is ensuring you can activate both "edgelook" and the "Vorpx in-game menu" using either a mouse button or a key-stroke such that you don't have to remove the HMD to bring up the vorpx menus. It becomes way too frustrating to use Vorpx if you constantly have to remove your HMD to bring up the menu and then put it back on to alter the settings over and over. Also too, you can't see the effects of the changes you are making in real time. So, for the love of god, go into Vorpx's config menu (in windows, not the in-game menu that is brought up within the game) and change the settings under "In Game Key Bindings" for "Vorpx in game menu" and "edgepeek" to something you can then map to your mouse or a macro key or something similar easily accessible while flying blind with your HMD on. I use "home" for edgepeek and "end" for Vorpx in game menu, and I then have home and end macro'ed to my mouse (it is one of the reasons to have an MMO style mouse with fifty buttons on the side). I also receommend using a Keypad / like a Razer Orbweaver - it just makes it all easier when playing in a HMD (not having to reach for the keyboard etc). So load star citizen up, and it should get thrown up into your HMD by vorpx. 4th. You should be looking at the star citizen menu. Whenever navigating the star citizen menus, it is best to go into "edgepeek" mode, so you can see everything. Go into options and ensure that your resolution is 1800 x 1000 and your FOV slider range is 110 - 114 ; If it isn't at that range then something has gone wrong, you may want to check your user.cfg is in the right place or has been edited correctly. If that is correct, then open your Vorpx in-game menu and set the following : Vorpx Settings Main Settings Tab Play Style: Full VR Mode 3d Reconstruction : Z-Normal 3D Strength: 0.65 - 0.85 Depth Weighting: 0.0 - 0.10 Focal Distance: 0.00 Head Tracking Sensitivy : 0.01 OR 3d Reconstruction: Z-Adaptive 3d Strength : 0.65 - 0.85 Depth Weighting (Near - Far): 0.0 - 0.3 Depth of Field: Off Focal Offset: -0.04 to 0.00 Head Tracking Sensitivy : 0.01 **Note using the default StarCitizen.exe Vorpx Profile you can use "3d Reconstruction: Geometry" ( ie true stereoscopic ) with the 3D Strength set to 0.10 if your rig can handle it - the fps drops though. Image Settings Tab Crystal Image : Aggressive Gamma (Brightness) : 0.90 Saturation: 1.35 Sharpness Amount: 0.00 Game HUD Scale: 1.00 Game HUD Scale Horizontal: 1.00 Aspect Ratio Correction: Pixel 1:1 Image Zoom : 0.997 - 1.314 i(try different values using shift + mousewheel in and out to get scale right - I often "zoom out" to about 1.0) Background Colour: None Display Settings Tab Default Head tracking Settings : On - sensitivity 0.01 -- > just so you can move your head around in edgepeek mode Controller Mode : Off Input Settings : All Default - you might want to disable mouse acceleration though - I don't play with a mouse (Hotas baby) VR Hotkey Menu Settings : All Default Obviously these are just what look good to my eyes - tinker away. 5th. So with that all done we come to the issue of Resolution. The way it seems to work is that when you load into the star citizen main menu screen, it looks at the ratio of width:height set in user.cfg and sets the FOV slider based on this. 18:10 gives you the 110-114 range, which is bang on for current HMD's - Pimax for eg will need a different ratio due to it's wider FOV. There are other ratios which can give you 120+ and 140+ etc, but this ratio is about right for current HMD use. So this happens when you load into the menu, and AGAIN when you load into the "level" ie Universe/PTU or arena commander or star marine. The ratio of resolution width:height determines the FOV range available. Here is the trick though - you can change the value of the resolutions after you load in and keep the FOV. So you can set a custom resolution in your NVIDIA drivers beforehand (so it will show up in the graphics options inside star citizen) and switch to that after you have loaded into the "level" (ie universe or arena commander or star marine etc) and you have the benefit of the FOV you set at load in (via the ratio in user.cfg) and whatever custom resolution you want. 6th. So when I first load the game, I check the FOV range is correct at the main menu, I then load into whatever game mode I wish to play, and then once loaded in, check my FOV is right (again) and/or change it if necessary, to these values: Rift is about 102, Vive is about 112 and Vive Pro is about 110 (experiment back and forth with those values or values near them (+/- 2 - 3 degrees) and see what works best for you - if you are getting distorting/stretching when you look around your FOV is too big, dial it back.) I then change my graphics resolution to that which matches my HMD - I use 2016 x 2240 (because this is the resolution SteamVR listed as 100% for Vive Pro) - 1344 x 1600 is for Rift and 1512 x 1680 for Vive. So I have those resolutions set up as custom resolutions in my NVIDIA driver panel, then I load into star citizen at the settings in user.cfg which sets my FOV slider range to 100 - 114, and switch resolutions once I am in, keeping the FOV. If you have a funky HMD with a different resolution, try setting up a custom res for that in your NVidia drivers (SteamVR will tell you what 100% resolution for it is under the graphics options when looking at the supersampling slider in Settings/Video/Application Resolution). For better performance, you can lower the values of these resolutions, just keep the ratios for each HMD the same as above (use an online ratio calculator to work out the values). I have been using 2560 x 2180 at FOV 120 (on Vive Pro) which has been good. I now have my HMD resolution running with a wider FOV, and if Opentrack isn't running already, I can Alt +Tab out, hit Start then centre it via Ctrl + V, and I also have full 6-DOF head tracking.