wju

yep, that is true, recenter button is the must, when using AS; Lefuneste´s check-6 is much more comfortable from this point of view; on the other hand - this utility works in DCS too... and I use it also to reduce brightness, as Reverb is too bright for me; unfortunatelly this brightness slider cannot be mapped to controller

@Lefuneste: do not map keys for IL2 ´, You have to do it for OpenVR Advanced Settings, see below: well, i did a bit more detailed "how to" it works flawlessly, both in IL2 & DCS; I use only two buttons from OpenVR Advanced Settings - 180 Snap View. First thing: it has nothing to do with IL2, nor DCS nor any other game - all the setting is done in SteamVR and OpenVR Advanced Settings (OVRAS)!!! my settings in OVRAS: at SteamVR: - the most tricky part (at least for me) was to find where and how to setup these buttons in in SteamVR: Important! - this must be done for the right application, nor IL2 nor DCS but OpenVR Advanced Settings. I could not to find it for a while, as it is named "Advanced Settings" only and nothing more Steam VR Settings menu looks like this, recommend to click "SHOW" in Advanced Settings (bottom left) then You can see purple option "SHOW OLD BINDING UI" - click it (note, this is not OpenVR Advanced Settings, it is just the same name for more options in Steam VR settings) now one can see list of apps, the right one is at the bottom of this picture: after clicking "Advanced Settings", one can see something like this: choose "Create new Binding" then you can bind your controller (I use x-box gamepad) Snap-Turn Left and Snap-Turn Right mapped to Pad buttons on gamepad, after some clicking, it should look exactly like this: (yes, only one button is necessairy in this case, as 180 turn left or right is the same) save it a that is all! 🙂 well, for DCS was also necessairy to check "Enable Motion When in Seated Mode (Experimental)" under OVRAS setting menu I did this settings only once, few monts ago and it works, survived all updates.. I use only these two buttons mapped to "SnapView" and angle set to 180 deg; combined with Lefuneste´s 3Dmigoto mod zoom and "recenter" button from game on the same x-bx gamepad hope it helped 🙂 PS: I use both SteamVR and WMR beta and OpenVR Advanced setting the last version- 4.0.1. https://github.com/OpenVR-Advanced-Settings/OpenVR-AdvancedSettings/releases https://github.com/OpenVR-Advanced-Settings/OpenVR-AdvancedSettings

I confirm this: in 4.004 no or negligible FPS impact in the test but significant improvement in VR MP smoothness. 🙂

BOX 4.004, Steam verison - problem persist 😞

probably not, I was just curious

why do you have the line "motionReprojectionMode" : "auto" twice?

I have asked the fpsVR developer to implement frametimes logging and also some kind of time snapshot for histograms. He responded positively. Feel free to encourage him at the link below. 😉 https://steamcommunity.com/app/908520/discussions/0/1750142176477291142/

no offence, but it is a problem - at least for some not native english speakers, trust me, I am one of them. They may just lost patience with you. It is not only about typos; try to slow down a bit and rearrange your ideas/hints/ questions into correctly build sentences. Read everything at least twice before clicking submit. If I were a developer, your posts would be at the end of my to-do list. 😉

well, here you are: add 1) yes I have 4x8GB CRUCIAL Tech part no. BLE8G4D34AEEAK.K8F, xmp enabled add 2) Noctua NH-D15S with 2 fans add 3) my cpu is delided, over 4.7GHz no way, even single core, max voltage => overheated, unstable add 4) see below - both high/low clouds 3 times just to be sure; 4 run with MSI log enabled as you can see - almost no impact except GPU load is higher at high clouds, but rarely >95% MSI log html with gpu & cpu all cores load are attached, one can see, that both CPu&GPU are slacking, or the code is not so good optimized 🙂 clouds high: 2019-12-09 20:29:03 - Il-2 Frames: 22625 - Time: 180000ms - Avg: 125.694 - Min: 84 - Max: 215 2019-12-09 20:33:06 - Il-2 Frames: 22576 - Time: 180000ms - Avg: 125.422 - Min: 84 - Max: 215 2019-12-09 20:37:36 - Il-2 Frames: 22341 - Time: 180000ms - Avg: 124.117 - Min: 83 - Max: 215 clouds low: 2019-12-09 20:43:00 - Il-2 Frames: 22696 - Time: 180000ms - Avg: 126.089 - Min: 83 - Max: 214 2019-12-09 20:47:24 - Il-2 Frames: 22361 - Time: 180000ms - Avg: 124.228 - Min: 81 - Max: 214 2019-12-09 20:51:17 - Il-2 Frames: 22324 - Time: 180000ms - Avg: 124.022 - Min: 83 - Max: 214 cloud high + MSI log 2019-12-09 21:13:27 - Il-2 Frames: 22210 - Time: 180000ms - Avg: 123.389 - Min: 82 - Max: 212 cloud low + MSI log 2019-12-09 21:22:57 - Il-2 Frames: 22145 - Time: 180000ms - Avg: 123.028 - Min: 82 - Max: 213 MSI_Log.rar

well, you are right - "horizon lock" may be a bit confusing term, it is named "camera shake" or so in Dirt Rally; and yes, it is about personal preferences - I would prefer "outside lock" against "instrument panel lock" in case there would be such option, because I look outside the cockpit much more than on gauges. In the real life brain automaticaly switch between both cases and fixes "camera" what one is looking at. option would be nice, we do not have such option in BOX yet VR is amazing 🙂

i am sorry, but I do not agree: in airplane is just one dimension more, think a bit about it. i do not want to fix stick´s input. By the same token, "fix to horizon" does not fix wheel´s inputs in car i am talking about turbulence incase of plane as equivalent to uneven road in car btw; we have it partly in BOX already: it is "F2" camera; unfortunatelly outside of cockpit; and the cam does not follow the direction

well, I still believe, that developers will sometime take into consideration "camera fix option", as it is usual in car simulators, analogy is not far, as driving car on unevenroad is the same like fly in plane with wind turbulence i.e. option between these two: a) fix to outside => jerky cockpit gauges b) fix to cockpit => jerky outside now, we have in VR option b) only, what is very unnatural, because during fly you look outside much more than on gauges.. it is not so important on monitor, but in VR is see the video:

👍 ok, reported:

Brief description: It seems that the "No wind" setting doesn't have any effect Detailed description, conditions: * in singleplayer, Quick mission, weather settings wind 2m/s, turbulence 2m/s * settings/custom/simplification the option "No wind" has no effect * tested both VR and monitor * tested with Spitfire IX gunsight and A-20 bomsight on Rheinland map Additional assets (videos, screenshots, logs): Your PC config data (OS, drivers, specific software): BOX 4.002, Steam verison WIN10 1909 Nvidia latest drivers

@snipertonthanks for confirmation! * wind vs turbulence - yes, it is different matter, but turbulence is much easier to detect and option "no wind" is supposed to eliminate both as written in option´s note * fighter vs bomber - I have just test it in A-20, both in cockpit and bombsight view: "No wind" has no effect for both is there a way how to report it to developers to fix it?