Both of these resolutions need to be specified in your NVIDIA control panel as custom resolutions or they won’t be available to select within Star Citizen (and it will freak out on loading into the starting menu ie black screen or crash). You can also specify another resolution which matches your HMD resolution (as determined by SteamVR) to play the game in which you change into after you load into whichever game mode (PTU, Ac or SM) you want to play. So if you put the right resolution in your User.cfg, you have a HMD appropriate FOV slider range available to you in game. Basic premise is that resolutions in your user.cfg file can alter the range of FOV sliders available to you at menu load in, and these carry across into the game modes when you load in.
I know it is complex but I was trying to explain it all. Also, historically, this allowed for Z-axis (back and forward) head movement but this was removed by CIG when they re-did the whole headtracking system a few patches back (3.2 if I remember correctly) – but that was great while it lasted. This is so the head movement and gun aiming are separated in FPS mode, and so looking around your cockpit doesn’t thrust your ship around when in ship.
Opentrack can spoof a trackIR using a HMD running on steamvr or oculus – so star citizen can use the “fake” trackIR from your HMD+Opentrack for headtracking, rather than Vorpx’s built-in headtracking (which I recommend to turn right down to one notch above 0) which is sending a mouse-input like signal to the game to control head movement.
0 kommentar(er)
