=RS=rulezcz Posted September 15, 2020 Posted September 15, 2020 (edited) I am not sure , perhaps this has already been solved but It bothered me a bit because i was not being able to show off my shooting skills to my friends who were distracterd by screen mirroring of both eyes view. So when Steam VR allowed to mirror VR view on the screen I was happy but some of you ,ight realize that you always had to have generic BOS double view window on the top of Steam VR view. To solve this I changed BOS startup.cfg . I changed line desktop_center = 0 (was 1 before) , and then miniaturized the generic BOS window by changing lines win_height = 12 (was 720 or so) win_width = 24 (was 1240 or so). Now spectators can enjoy almost full screen view of my spectacular skills. See screenshot if interested( note the browseer below steam VR view window and tiny BOS generic window in the very top left corner. I don' t know , perhaps this helps someone. Cheers Edited September 15, 2020 by rulezcz 2 2
Impalor Posted January 25, 2021 Posted January 25, 2021 (edited) It did not work for me. Reducing window size below full screen limits the mouse to that area in VR, so I cannot even log in. desktop_center = 0 did nothing. Edited January 25, 2021 by Impalor
dburne Posted January 25, 2021 Posted January 25, 2021 IL-2 GB used to render in only one eye on monitor back when they first implemented their VR support. Never understood their reasoning behind moving to rendering both eyes.
SCG_Fenris_Wolf Posted January 25, 2021 Posted January 25, 2021 5 minutes ago, dburne said: IL-2 GB used to render in only one eye on monitor back when they first implemented their VR support. Never understood their reasoning behind moving to rendering both eyes. "Community request" that never made any sense. They should just put in the right eye.
HansBlitz Posted January 25, 2021 Posted January 25, 2021 I believe the switch from what we had, to it showing both eyes, was a performance thing, to improve FPS -- as in send to screen the same as what is sent to the headset and remove processing that was required to output those different views at the same time. Send something different to the screen than what is going to the headset = extra lines of code/processing needed to do that additional thing, rather than output the same already rendered/configured image to two destinations, and the impact of the needed extra CPU cycles on FPS. 1 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now