vicx

It is a sandbox with simulated elements. Can deliver more game or more simulation depending on what you pursue.

I would like to see DCS level, Ground Attack, LGB delivery but in a cockpit without MFDs. Does anyone know what aircraft would tick those boxes?

Good news to have some proper dates. It is easier now to enjoy what we have and to make plans. I will be working VR optimisation project for Caucasus Map. Seeking people who have experience tweaking textures and lua configurations. editing and modifying edterrain objects. editing shaders Hah that doesn't worry me at all. If that worries you ... you worry too much.

jimcarrel of course it could be your imagination. Still I did enable a debug setting for cockpits last week that draws a box on all types of visual elements and overlays. Every now and then a tiny little box would pass by or through the canopy. Was it a software bug or a feature bug? This was in the Sabre ...

I have seen a similar thing happen in DCS 2.0. I haven't seen 9M311 miss targets so wildly before.

joebloggs might be right. It could be that Nevada and DCS 2.0 are highly tuned to deliver ONLY 60fps or in very difficult scenes a lower target than even that. My testing seems to be showing that any scene with more than a dozen LOD0 terrain objects just can't render fast enough ever. I don't think VR SLI is going to solve this. I doubt even raw clockspeed will be enough in the short term. I think mking VR work with Nevada will require changes to the DCS 2.0 renderer and/or the assets which seems unlikely ... in the short term. I think encouraging ED to make an updated Caucasus map VR friendly is an approach we should take. It seems to make a visual difference to me using the built-in techniques. It isn't that taxing because it is other stuff that is doing the damage. === i7 3820@3.6Mhz 16GB | GTX780 3GB (very similar to a 970) Everything set on extreme low settings Other custom "extreme" low settings via lua edits to - config\graphics.lua - config\terrain\terrainoptions41.lua - config\terrain\low.lua Added information for DE

It is a crazy story if you can't post a picture to back up what you claim. You know this is the picture I wanted to see. --- You recognise rightly that I am interested in improving spotting in DCS and I think the important things are for it to be consistent in how it works customisable for personal preference controllable for use on servers The spotting performance in DCS up to now has not been consistent in how it works customisable for personal preference controllable for use on servers The new feature which I don't see as a solution yet (it is more of an experiment) doe meet one requirement. It is at least customisable for personal preference So we have 1/3 requirements. From here ... if we have people helping and not people making wild claims, we will see about meeting the other two requirements. In my opinion all three requirements are equally important.

I'm very interested in this subject. Take a picture showing the "bad thing" and post the picture in this thread. Without pictures I can't see that anyone is going believe your crazy stories about seeing an aircraft from 100km away.

I am doing some pretty intensive testing with VR and Nevada. It is pretty early to be making guesses as to what is causing the framerate problems .. but I think that some rendering techniques in Nevada are problematic for VR in particular. The actual objects that cause problems might be able to give some clues. The Trees in Nevada have a problem but it might be something specific to the technique used rather than just their numbers. I have been trying to turn off some of the rendering passes in Nevada so that I can look at stuff in isolation. So far I have only identified one thing (and there could be many others) that causes a hit to framerates. *Note* This is running everything on an extremely LOW settings ALREADY. And still there are highly unusual drops in framerate that are not easily explained. So these pictures will tell a story of this first thing I have found. I don't know whether doubles-sided polygons are the actual problem. Or they are just a a tiny bit more expensive than single sided and that turns out to be a problem for VR. Could be specifically double-sided polygons with a different texture on each side. Could be specifically double-sided polygons having a normal map. I don't know. I have seen objects having double-sided polygons causing a drop in the VR framerate from 75fps to 50fps. Being close can cause the drop or just having more than a few objects with double-sided polygons in the viewport. It could be coincidence ... but it could also be something for ED devs to look at. For most people going from 75-50fps is no big deal but for VR it is very bad.

I think everyone with a DK2 who plays DCS is finding that those specs are probably the minimum to play the DCS too. At least the Nevada map. I still think there is something not quite right in DCS 2.0 at the moment. People with a GTX980 should be able to get a consistent 75fps on LOW setting. I am doing some experiments to work out what might be the problem.

Frusheen. I use DxTory ... I paid for a license. For me at the moment sound does not work with DCS. If you can try the DxTory trial and get your sound working ... I can fully recommend it based on all the features it has that I am quite happy with.

Preach it, Eightball. It is amazing how many people have been trash talking the DOF feature for ruining their framerate in the cockpit ... but it's all just in their heads. Amen to that.

It works for me and many others. We can help you get it working but you need to follow the steps, or we can do nothing for you. Step 1: Get Tacview 1.4 working in DCS 1.2.xx (I assume you already have done this) Step 2: Open Directory C:\Users\%USERPROFILE%\Saved Games\DCS\ Step 3: Copy Directory SCRIPTS Step 4: Open Directory C:\Users\%USERPROFILE%\Saved Games\DCS.openalpha\ Step 5: Paste Directory If you still have no ACMI being written Step 6: Open Directory C:\Users\%USERPROFILE%\Downloads\Saved Games\DCS.openalpha\Logs Step 7: Read dcs.log Step 8: Post dcs.log here

Edge cases always need optimisation AKA dirty hacks that make it work.

Beeroshima, Step 1: Get Tacview 1.4 working in DCS 1.2.xx (I assume you already have done this) Step 2: Open Directory C:\Users\YOUR-USER-NAME\Saved Games\DCS\ Step 3: Copy Directory SCRIPTS Step 4: Open Directory C:\Users\YOUR-USER-NAME\Saved Games\DCS.openalpha\ Step 5: Paste Directory If you still have no ACMI being written Step 6: Open Directory C:\Users\user\Downloads\Saved Games\DCS.openalpha\Logs Step 7: Read dcs.log Step 8: Post dcs.log here

Do not reveal state secrets. Last warning.

Post a short ACMI recording ... we can see what is going on by looking at that.

Are you ready? http://www.seeedstudio.com/service/ It is both cheaper than you think but could end up being more expensive than you realise. When you make a mistake ... even on a small run or protoype it costs money. Let us know how you go.

It is a shame that terrain.cfg.lua is the ACTUAL file that ED choose to encrypt for their content protection system for Terrains. It means that the lua customisations for VR possible with the DCS 1.5.xx and the Caucausus map are not possible for DCS 2.xx and Nevada. It is a bit disappointing. I don't think it is a deliberate attempt by ED to stop customisation ... just an unlucky side effect of their content protection scheme. === What is awesome is that the mouse behaviour is fixed in DCS 2.0. Mouse stays in the window until you ALT-TAB.

I tried all the modern MBTs from both sides and some modern IFVs like BMP3 and M2A2. I will also make a test to see if it only works vs human controlled vehicles.

My testing in VR is showing that for chopper use you can radically reduce the VISIB DISTANCE a lot more than if you are flying aircraft at a medium level. There are also a lot of details that you can forgo in VR due to the compromised resolution of the HMD. What I found is that a lot of elements could be removed without affecting the feel of the sim. It does take lua mods to make most of these changes. The main thing is to focus attention on stuff you can actually see in VR. you can't zoom in VR so a lot of things at range can be removed without people really noticing. There are specific objects that can be FOCUSED ON because these things you DO notice. Textures road (increase range) at least 50km before fading rivers and lakes (increase range) at least 50km before fading Objects Large unique structures (increase range) There are specific objects that can have a REDUCED FOCUS because these things you don't notice notice or they are so small in size that they are just blurry most of the time Textures short range field textures (totally remove rendering pass) short range village and town ground textures (totally remove rendering pass) *Note - Long range textures still show up for long distances. You get town geometry closeup and town textures long distance. Objects forests (remove - this one is shame because they look good BUT THEY KILL FPS) :noexpression: Districts come with their own trees so you still get heaps of trees. It is a compromise. ground units (decrease range but increase visibility LARGE) street light poles (remove) electricity towers (reduced range) wire visibility (increase range slightly) traffic (low and reduce range) districts (reduce number of districts rendered but increase range) tree visibility (set to zero) Special case of trees explained below. Trees in 1.5.xx in DCS are weird. There are many types of tree object and each type has it's own settings. Trees also destroy the framerate the most of any object in 1.5.xx. Forests are just the worst. It is worth knowing how trees work in DCS in more detail. I do know that by tweaking some lua settings you can choose to render only certain tree groups for a given visibility range. I am still not sure how this is achieved ... I am not sure which settings are make this possible. Work will focus on DCS 2.0 when I finally get to run it.

Yeah that is interesting. I wonder if that uncanny body effect is more noticeable in room-scale applications. In a cockpit I do want body representation but something that is a fuzzy generic shape rather than an attempt at photorealism. I guess that does qualify as an attempt to avoid the uncanny valley.

Has anyone had problems with mouse behaviour in VR since DCS 1.5.xx In VR ... once the mouse leaves the window it is out of sight and gets lost. If you click accidentally click outside the DCS window it loses focus and you can't even see the mouse passing over the DCS window. === Frusheen ... can't wait to finally open Nevada. I think that tweaking setting will take us a long way optimising for VR. I hope that all the LUA setting available in DCS 1.5.xx remain for DCS 2.xx. I noticed that without a terrain installed in 2.0 I am missing terrain.cfg.lua and more generally the Bazar/Terrain directory. That particular file is where I was able to optimise VR peromance the most ... for my purposes.

I was in the Ka-50 the other day and the high pitched whine was starting to bug me. I was wondering if I should be wearing a set of earplugs under my headphones. ... virtual hearing protection would be fine with me.

It's pretty clear if you read the Nvidia information releases on Gameworks VR, available on their site. Confirmed by plenty of people on Reddit