This is now outdated as at 26/12/20 - please go to this post instead : https://robertsspaceindustries.com/spectrum/community/SC/forum/50174/thread/vorpx-guide-for-3-11-3-12-with-new-headtracking-et So - prerequisites : 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) The headtracking profile (sc-31ptu-mongrel.ini) in this dropbox folder for use with Opentrack (updated) : https://www.dropbox.com/s/e6dr0yp4cv0as54/SC310PTU-mongrel.ini?dl=0 4)User.cfg from https://www.dropbox.com/s/3z1tqwmfxqtj32a/user.cfg?dl=0 I play in VR with a HOTAS and a Razer Orbweaver sat next to my throttle. I recommend this strongly, to prevent you scrabbling around trying to find keys with a HMD on. I also STRONGLY recommend an MMO mouse with a bunch of programmable side keys, so you can map VorpX and Windows functions to them and have them easily accessible while in HMD (ie to bring up the in game VorpX menu, to toggle edgepeek on/off, and a macro for “alt+tab” to switch in and out of star citizen easily - also in game things like Mobiglass, light on/off - is frustrating/impossible to play if constantly having to take HMD on/off to find keys to do these things). How this works : Custom Resolutions available for the game to play at (in the options/graphics menu) are present if you have set them as a custom resolution in Nvidia Control Panel beforehand. So if you set a custom res for a resolution you want to play at there, it will then be available to you in game. Google how to set a custom resolution in Nvidia control panel if needs be. For this to work, you need to set up two custom resolutions - one that loads up at load-in via user.cfg and has a specific ratio that alters the FOV slider values the game lets you use (so 1050 x 500 or 2100 x 1000 if using a standard 110 FOV HMD or 3900 x 1000 if using an Index with a 120 odd FOV) and another that suits your HMD's resolution that you use to play the game in (for which I am currently using 1920x2160 to play the game in). The ratio of 1050 x 500 or 2100 x 1000 in user.cfg gives an FOV range from 94 to 108 - it's convenient because you can use 94 for playing on a monitor and 108 for the HMD. This 108 value is good for standard FOV headsets (Vive, Vive Pro, Rift, Rift S, Quest with Link). If you are using a Valve Index, you will get better results with a wider FOV (like around 121 - 122). You can get this FOV slider range by using r_Width = 3900 and r_Height = 1000 in user.cfg - but whichever ratio you specify in user.cfg, that same res needs to be set-up in NVIDIA control panel as a custom res beforehand. I will update this again with even wider FOV values for Pimax. Obviously if playing on monitor you use 94 for FOV and don't activate Vorpx and if you want headtracking/facetracking via webcam you will need to go into the options menu for that and re-set that up (because following this guide we will set it up to use TrackIR which will be spoofed by the HMD and Opentrack). If using SteamVR (so Vive, Pimax or Index) and you add Star Citizen to Steam ("add non-steam game") and change it's properties within steam to include it in the VR LIbrary, it allows you to set a custom render resolution for it in steamvr settings using the "per application display settings", and access/modify the HMD screen refresh rate. I set the resolution slider here to 100%. At the moment, I am using 1920 x2160 to play in, but you can try for higher values - just whatever custom res you decide to play in has to also be put into the NVIDIA control panel ahead of time or it won't be available to select in the graphics options of Star Citizen's menu. In user.cfg for a Rift or Vive Pro I am using r_Width = 1050 and r_Height = 500 now (the ratio of the two values is what effects the FOV slider, so either of 1050x500 or 2100x1000 is the same result - I reduced the resolution to 1050 x 500 because some people with monitors with resolution less than 1920 x 1080 couldn't get 2100x1000 to get added to NVIDIA control panel as a custom res reliably but either one of those values should be fine and both will produce the same change in FOV slider values) which sets the FOV slider range from 94 - 108 ; you can use 94 for monitor play and 108 for HMD play. If you edit it to r_Width = 3900 and r_Height = 1000 you will get a range from 121 - 132 which is good for Valve Index (I use 121 for Index). Steps: 1st. So, with the above in mind, first step is to import Star Citizen into steam (add non-steam game option in steam) and add it to the VR Library so you can set custom render resolutions in SteamVR for it using the custom resolution slider. In steam, once you’ve added it to the library, go into properties for Star Citizen and check “Add to VR Library” . Now, if you restart SteamVR - Star Citizen should come up in the list of VR applications, and you can set a custom render resolution slider for it in SteamVR. I have my Refresh rate set to the lowest (so 80Hz on Index - try higher if you aren't getting any reprojection/you want) and I have “Force Always On ” on for motion smoothing - I don't know whether this is the best option or not but I read somewhere that it might be. 2nd. Optional but helpful step - Then go into the Vorpx app config menu (the one 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 else similarly 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” bound to my mouse side keys (using the mouse software - it is one of the reasons to have an MMO style mouse with fifty buttons on the side), but you can get by with just the two. 3rd. NVIDIA Custom Resolutions - (resolution differs by HMD). Go into NVIDIA Control Panel and set up two different custom resolutions - one that matches the resolution you specify in your user.cg (so 2100 x 1000 / 1050x500 or 3900 x 1000 if using Index), and another that matches the resolution you are going to use to play in so Star Citizen has these resolutions available to itself as options in the graphics settings menu in-game - so 1920x2160 which is what I am using at the moment; sometimes this 1920x2160 is there already (if you are using a 4K monitor) so good luck to you if it is but sometimes you have to set it up. 4th: Set up a custom user.cfg file for Star Citizen. This sits in the C:\Program Files\Roberts Space Industries\StarCitizen\LIVE folder, and isn't there by default. Download my copy from the above Dropbox link - this is set to 1050x500 but can be edited with notepad to whatever you want to try for different in game FOV slider settings. If you would prefer not to download it, here are the contents of it: Con_Restricted=0 r_DepthOfFieldMode=0 r_MotionBlur=0 r_Width=1050 r_Height=500 -> copy and past these into notepad and save as user.cfg. Change the values for r_Width and r_Height to 3900 and 1000 if using Index. Transfer it to the right folder (see above) and you should be good to go. 5th. Download the headtracking profile from Dropbox. 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 file (sc-310-mongrel.ini) into the config directory, then restart Opentrack. The new tracking profile should now be selectable in the drop down box next to the word "Profile". Select it. Now select your input depending on your HMD (Valve SteamVR for Vive/Vive Pro/Pimax or Oculus Rift runtime 1.4 for Rift) from the dropdown box on the left, and then click the hammer icon next to it. Select First Available. Then select "freetrack 2.0" from the output box below. Leave the filter box blank or add a filter if it makes tracking smoother for you. Hit start and move HMD around (make sure SteamVR is running first) the pink octopus should move around with your HMD. "CTRL + C" is set to recenter the headset - this can be edited in Opentrack in the profile options. Hit recenter if your tracking goes wonky in game. 6th. Start Vorpx and then load star citizen. When you load star citizen up, if Vorpx is doing it’s job it should now get thrown up into your HMD by vorpx, and you will see it loading into the menus. A blank black screen but can hear music playing might mean you are in fullscreen mode and it's not liking it so try pressing "Ctrl + Enter" to switch to windowed mode if you are getting that - I have had best results with running this is windowed mode myself so if this problem happens repeatedly you should set your graphics to windowed or borderless fullscreen (ie turn fullscreen off in graphics options of star citizen) and re-try. There is another problem that can happen sometimes if using fullscreen which is where you load into the menu and the user.cfg sets the FOV range to what you want, but then when you load into the game, the FOV range drops back to a range from 90 - 100. This is sometimes because you are in fullscreen mode and/or you haven't set the NVIDIA resolution up for your user.cfg and gameplay resolutions - you can get around this 95% of the time by making sure you have switched fullscreen to off and don't have borderless windowed mode on. 2ND PART OF POST BELOW