dertien

I totally agree. That is why I bought and enjoy the 'oil fields' campaign for the Mi-8, I would also enjoy to fly gliders if DCS would feature a proper weather system with thermals and windsocks that are actually usable and any glider module with a PFM. Not even Aerofly FS 2 (which supports VR as well) is multiplayer capable at the moment. I don't know or played SF2, but I did play Falcon BMS with track-IR. What I miss in F-BMS is the ability to use VR gear. What I miss in DCS is an F-16...and a DCS VR-rendering capability that can keep up with the jet's speed. Aaah... decisions, decisions... Don't get me wrong, I have absolutely no issues with your desire to spend countless hours of flying above the ocean for realism sake sticking to using real time only, while you confine yourself to your seat for 6 hours on end - not sure that Vulcan Bombers had a toilet - while staring at the horizon and then enjoy 10 minutes of 'bombing action', since AFAIK the sim has no save function; and then ultimately 'navigate' 6 hours back to home plate. I am sure of two things however: 1) very few realism buffs - like myself - will go that far! PC's crash, Windows crashes and so does DCS ...occasionally; without even speaking of the 'time' factor. My game sessions are also very long (6 hours+) but my hands and brain need something to do. 2) I'd hate to be your keyboard when after 11 hours just before that succesful landing, Bill Gates' miracle OS decides to install updates :) no matter how 'zen' you are or how many yoga sessions you do every week. But...as in EECH and EEAH you have the whole of Georgia, which is not a small country... but yes if you fly at Mach 2+... The aerial re-fuelling bit is still usable (comparable to the same feature in Falcon BMS) even if you don't fly halfway around the globe; since due to weight and balance issues your fuel load will be a factor depending on your weapons package. I did not mean to minimize the "Combined Arms" module. I do not own it and my judgement is based on Youtube videos. The tank 'driving' that the module offers however is pretty minimal and if a level of realism could be obtained in DCS that could hold a candle to the way SABOW handles it, I would be very happy even on the existing terrain. Speaking of priorities terrain wise, how 'bout getting those trees usable as a terrain masking feature. I usually fly the Helicopter modules (because DCS gets more time to render the terrain for my VR setup with less hiccups than when I fly jets) it's absolutely aggravating that trees cannot be used for cover, a mundane feature which I feel is an absolute MUST on the DCS to-do list; I'm not even asking for different tree models! Just trees that will mask the sound of my chopper and incoming sams or AAA. I have Georgia on my mind, with better curves and collide-able t..rees before anything else. :) Could not agree more with that! On top of that, I would like to see a dynamic war system just like in EECH or EEAH, or like was done for ARMA 3 by the ALiVE mod team. One that would intelligently spawn and render entities depending on their distance from you, since the currently available quick-missions involving a lot of units (even those that cannot be seen) make DCS in VR a nauseating slideshow.

I apologize for coming a bit late to the party here and necro-ing this post: As for an elaborate answer to the vote on this poll: should the ED team focus on giving us 'the world, Chico, and everything in it' ? No, Some people here fail to understand the scope of DCS. This is not a 'Flight Simulator' like Aerofly FS 2 is, but it is a 'conflict simulator'. The focus of the controllable war machines is focused on Aircraft and Helicopters now, but in a distant future we might see DCS World include Tanks as well. And by driving tanks I do not mean the Combined Arms module, but something more akin to a simulation which does this quite in depth - Steel Armor Blaze Of War; where you can control either a T-55 or an M-60 Tank. DCS focuses on theaters of war (past and present) which are swathes of countryside where conflicts take/took place. Georgia was also a theater of war in Enemy Engaged Comanche Hokum / Enemy Engaged Apache Havoc, which had a dynamic campaign and where you could hop into any chopper on either side and fly different missions to win the campaign. Although this focused on Apache/Comanche vs Havoc/Hokum, I consider this to be a spiritual predecessor to DCS. Indeed, the devs are focusing on the right approach here. Normandy (WW2), The Nevada testing range and Georgia. What I personally would like to see is a few different conflict zones that topographically offer a different challenge: In no particular order: - (Northern) South Africa / Angola / Rhodesia (bush war) - Sierra Leone - RUF vs South African Mercenaries - Vietnam - Korea - Afganistan - Syria just to name a few. Why these zones? The conflicts fought here in the past offer a plethora of scenario possibilities using declassified hardware that already exists in DCS. I'd rather prefer the devs focus on getting Georgia into DCS 2.0 - streamlining it for VR and upgrading the topography of this existing landscape close to something we have in ARMA 3. Georgia was well chosen, because it has everything - seaside, hills and mountains. After this feat the devs could choose to focus on bringing in one (or a different) conflict zone(s) I enumerated above. Remember that sometimes 'Less is more'. My 2 cents.

@Jabbers and @M1Combat Thanks for the feedback. Assuming you have a VIVE, there is a program called 'shaperone switcher' created by Bilago. This progam allows you to change the 'render target multiplier' natively in SteamVR without the need to edit files. It's just a GUI basically. I was under the impression indeed like you said M1C that the ingame 'pixel density' and this 'render target multiplier' both were the same thing. Out of the box SteamVR comes with a setting of 1.0 'render target multiplier' Would it matter much or have any different results would one either choose to use identical settings either using the PD ingame or natively in steamVR ? I mean the visual result should be the same, but performance wise it might make a difference. I would say logically speaking that the less the (already strained) DCS engine needs to be pushed extra the better it should run. I'll test that out with settings with a maximum of 1.8.

Ok, not sure how this is supposed to work out... There are 3 profile files in here, but only two can be loaded. 1 Profile into the Mad Catz software 1 Profile into DCS. Am I missing something here or has DCS gone from 2 different profiles (one for the stick and one for the throttle) to a combined setting, and are these profiles obsolete ? The 'DCS Ka-50 X-55.pr0' loads into the mad catz software and works. Yes. BUT... DCS can only load and save one profile which includes both joystick and throttle settings. How I should load the 2 separate config files into 1 profile on DCS is a mystery to me. Load profile (in dcs under control settings) Ka-50X55STICK.diff.lua Load profile (in dcs under control settings) Ka-50X55THROTTLE.diff.lua Of course importing one clears the settings of the other and vice-versa. Instead of 2 lua files, we should only have 1 including both controllers. Does anyone have more luck with this ? Thank you Infernus for that clear image which tells where to bind what inputs to the X55

@NickD Don't forget that it is not ONLY a steamVR software issue, which has now been improved upon, and hopefully will keep improving as VIVE's software and firmware gets better. It was also Frontier Developments who improved Elite Dangerous which has since then not shown any "greyouts" as I like to call them in VR. DCS has been around quite a while longer than both headsets, so with each new iteration of the engine used by DCSworld; we'll eventually get there as well. It's just that throwing bigger and better hardware at something should not replace streamlined code, I'm aware that the software cannot be run on non VR hardware, but given the fact that my rig struggles to run DCS decently in VR (it's a I7 at 2.6 GHz) should give them some food for thought. Or at least... when one has the hardware that should perform brilliantly, one shouldn't have to fiddle 5 days to get maxed out settings combined with good frame-rates and no ingame intermittent loading pauses. Like I said, the settings I've posted are pretty good, but not perfect and in missions I still get the 'loading box' and stutter also seems to happen far too often. I would already be pleased if the VR setting would have LOW/MEDIUM/HIGH/ULTRA options (on top of the pixel density setting) so I don't have to micromanage all different non vr settings by trial and error myself. I mean it's nice to have them, but something that works out of the box would really make a difference here.

Okay, it took even a lot less time to get it sorted so for anyone with similar hardware, stutter free and 'loading box' or 'grey out' as good as gone. I have added Shabi's screenshot as a reference, and added the altered settings accordingly that seem to work with my hardware. Hardware: MSI Tobii dominator pro. HTC VIVE GPU: Geforce 1070 Ram: 16 GIG DDR4 OS: Win 10 DCS version: 1.55 Non steam DCS mods: - Reduced shadow draw range mod - Starways Black Sea Map 2.0 SETTINGS: For the MI-8 (and basically all slow moving craft like the Helos and the Dora) System settings tab - Heat blur: low - Shadows : Flat only - Resolution 1280*800 (I guess the lower the better since it only affects the distorted laptop view, and has no effect on VR) - clutter/grass: 0 VR settings TAB -Pixel density 2.5 For the MIRAGE 2000 (and faster moving aircraft) System settings tab same as above. You'll only have stuttering when flying at treetop level and looking to either side at your 3 or nine a clock facing the ground / trees as they whizz by. I mean IRL it will also be blurry, and that's kindof what it looks like. In contrast even at tree level and looking straight on, or keeping your eyes pointed at an object about 300 meters on either side, the stutter is gone as well. It's just noticeable when looking at trees flashing by at your 9 or 3 oclock low. - Pixel density 1.0-1.4 If you fly at higher altitudes where the terrain is rendered (or your missions take you there) you can bump up the pixel density to 1.9-2.0 since stutter will not be an issue there. Hope this helps anyone with this issue and comparable hardware. Thanks a lot.

Thanks for all your posts so far. I've been testing a bit to try to run it as well as can be expected. I purchased the VIVE more out of political reasons (because I don't like Facebook and the guy who 'invented' it) but that is another matter for another discussion. I haven't had time to read up on your full writeup Shabi, but in time I will get there. I have also installed the free Starway Caucasus DLC, now that doesn't seem to behave any different fluidity wise in relation to Stock Environment. It certainly looks beautiful. I used the MI-8 free flight mission as a benchmark to test different graphical settings. Flying around the airport you spawn at, the "loading box" that NickD was so kind to provide a screenshot of in his post above does not appear often if at all. Regardless of flying fast and low or high and slow. I took the flight to Kutaisi, and there, just before getting to the airport I got a whole lot of 'loading boxes' 5 or so in quick succession. It's very painful on they eyes and messes with your brain. The box seems to pop up every single time though when you are in the control config menu when you use the search function to find a control fast. For example you type 'Gear' and then it finds the relevant controls without showing the box. When you delete that word, to type in a new one, it always brings up that black box and the game environment is completely gone, it shows a void which is dark blue below and a light blue above the horizon, the black box with the 3 alternating loading bars that jump up and down sits in the middle of your viewpoint. I used to have it popup a lot ingame as well, every time when a radio message from an NPC/ATC were displayed on screen. That behavior seems to be gone now. Now Jabbers has something similar that used to be an issue I had in Elite Dangerous and is basically the same behavior. You got a grey-out, and the game world would vanish completely for a fraction of a second. I used to have this before the latest ED patch came out in November last year. Also HCT came up with a patch that introduced the asynchronous reprojection method, and since then I haven't had that issue and I can enjoy Elite Dangerous without the greyouts. Thank the maker because those greyouts were very powerful motion sickness enticers.Jabbers, I don't know how to solve this on the CV1 but on the VIVE it's completely gone. I have also dropped the Resolution of cockpit displays to 256 as well, since that seemed to help with the 'loading box' issue. Shadows are off as well, however it would be nice to have an option to switch off the tree shadows and keeping the shadows on for the aircraft, since it is a useful natural altitude indicator, especially in helicopters. Also I can play Elite Dangerous for hours without feeling discomfort. If I got this issue out of the way I could probably do this in DCS as well. I'll keep testing for the next couple of days and see what I can come up with and alleviate the problem (or at least minimize it) with the right mix of settings. The unfortunate thing is that VR being so new, there is no one-size-fits-all, even with 2 identical computers. Now if ED can iron out these things, I'm pretty confident the DCS team can do the same, even if both games are indeed fundamentally different.

@Dax I agree that a desktop PC and a Laptop are 2 different animals. However, this laptop was built for gaming and for VR. It is VR-ready and scores max on the steam testing tool. I run DOOM 2016 and even DCS without VR on max settings without stutters. I also have trackIR 5, and use that with BMS, but it's a bit hard to get back to flat screen simming if you're used to VR. The 1/3 rd screen is also visible in the youtube link below. Anyway, Hansangb told me that I could switch to full screen with the good old Alt_Enter. This keeps the mouse focused on the game screen and cannot wander off it. That's what I meant with focus. Yes, I have finally set the preload redius slider to max 150.000 and I get noticeably less of these "load pauses". The view range is set to high as well. @Hansangb Thank you for that, that solved the biggest issue of the mouse not staying in the game window. The setting 'Cursor confine to Game window' does not work on the VR settings tab, or at least does not what it should. @ all Finally I have found this thread https://forums.eagle.ru/showthread.php?t=172537 and... He's right: 'Shadows on' is the biggest frame rate killer and is also responsible for a lot of 'loading-stutters' when in game. The game engine stops responding for a second or less and shows the black box with the three animated bars. The same animation you get when you're waiting for your mission to load. Tuning the others up/down just helps framerates. I have also set the preload at maximum 150.000 The trees at 10.000 The grass at 900. - Anisotropic at 16 as well as 1.3 for the Supersampling in the VR window. Shadows off is not even half bad.

Hello fellow simmers, I have a VR ready gaming laptop (MSI Tobii Dominator with a Geforce 1070 on board and 16 Gigs of DDR4 ram) I try to enjoy DCS with the VIVE but a couple of things are really screwing up the fun of it all. I also have the impression that certain settings set to on or off either just don't do what they should or are just there for show. All drivers are up to date and VIVE software as well... so no need to go down that road... Here are my issues with the VIVE regarding gameplay on the MI-8 summed up from frustrating to annoying: 1) Mouse Cursor in VR keeps unfocusing after leaving the game window on screen. When playing in VR, DCS also displays the game in a view on the laptop screen in a window. This window however uses the full resolution for height (1080 pixels high), but it does not fill the screen in width, it crops it to 1/3 in width, and centers it giving you 640 pixels wide. This means that on either side of this game-window your Windows desktop is visible. When clicking switches in VR, the cursor is visible in the middle of the screen and you move the mouse with your head instead. The mouse cursor unfocuses from the game window if you turn your head 90° sideways to click on switches situated on side panels. It somehow doesn't seem to stay 'in the game'. So once your mouse pointer in your VR headset dissapears, you know that the DCS window is no longer focused and you are clicking on your desktop instead. There seems to be no way to set the DCS window on the screen to accomodate the full resolution in order to keep the mouse in the game window (albeit in low resolution - at 600*480 for performance sake) 2) Performance. It doesn't matter if I set the performance to VR, or LOW. running just DCS and closing down Firefox and other background processes.... DCS is just not made for VR at the moment benchmark wise. It plays well for 90% of the time and the fluidity of rendering is fine but every once and again, about every minute or so, the game just seems too much for the GPU and freezes while showing a black screen with a loading bar. Very annoying, even running this on the lowest of settings does not help to alleviate that problem. I can run Elite Dangerous and Aerofly FS on High to Max settings. 3) The SU-25 Flaps/gear/airbrakes do not like my X-55. I have them configured in game via button presses. They work in the Mirage 2000 (the gear and the airbrakes) and they work in the KA-50 (the gear) but the SU-25 does not seem to respond to these controls. Can anyone help with the first two issues, I can get by with the issues on the SU-25 since I don't fly that bird much. Please... A game that should be very enjoyable like ED and AFS 2 is slowly becoming a nightmare.