whitav8

OK, StrikeEagle345, Please tell us approximately what is the scenario for seeing the Tanker at 22.5 nm - are you below him and see him in the light blue sky. Did you use radar or a callout of his heading to get looking in the correct direction? That is quite a claim and I want to try it since I have the Odyssey+ as well. Just what are your SteamVR settings for SS - I do have the renderTargetScale set at 2.0. Do you wear glasses? Thanks for your help! Dave W.

OK - I found the problem! I only have 12gb of memory and had just reloaded Windows 10 build 1803. But I didn't setup a big enough pagefile so I was running out of memory when I got to 8gb. I don't know how that all works but anyway, once I set the pagefile to 12gb, everything worked fine. STRANGE Dave

As far as repair and reinstall, I have done that a few times already! I test after the repair and it all compiles fine and runs well. Then I install the kegetys mod version 2.5.3.21107 exactly as the readme discusses (I have successfully installed this mod many times over the last three or four months and seen much better FPS performance for VR). Only this time with 2.5.3.23954 have I experienced this compile / crash problem. I really wonder if this version of the mod that I am getting from the first page of this thread is correct. Anyway, my current approach is to uninstall DCS World and reinstall everything from scratch, install the fast mod, and retest. If that still fails, then it must be my hardware (older i7 - 980X and DK2) or some dependency on the Windows 1803 build. Thanks for any ideas to try. Dave W.

I tried updating the current (11/12/18) of OpenBeta with the version of this VR mod named "DCS VR Shaders performance mod for 2.5.3.21107" and the nonVR load crashed when starting a mission (of any kind) and then with the VR mode, it stopped with "Failure to build metashader - and gave a list of about 5 or 6 .hlsl files that didn't compile - most in the terrain area. This is for 2.5.3.23954

Can the most recent version of the VR mod be downloaded from the first page - or do we have to wade through all these pages?

The reason that resolution is a problem for the current generation of VR is simply that to provide immersion, the field of view is doubled from what we typically use on our monitors. It is over 100° instead of just 50° . Therefore if you were to look at an HD monitor you would be seeing half of that resolution with a rift. The use of what’s called pixel density override or super sampling setting up to 1.5 off will improve the quality of the image because it’s rendered at hi-Rez and then down sampled. The Samsung odyssey has approximately 40 to 50% more pixels and is available for about $400 and some are saying that that works pretty good.Currently I have to lean in to read most of the EFIS displays in the cockpit. The old steam gauges are fine though.

What do we need to do I if anything) in order that an editing change to a shader source file will definitely get recompiled? Where is the result of a shader compile placed? Does the folder C:\Users\USERNAME\Saved Games\DCS.openbeta\fxo have the shader compiled files? Also, I renamed the C:\DCSWorld\DCS World OpenBeta\Mods\terrains\Caucasus\misc\metacache\dcs as per the author's directions but never saw any new files generated. Dave W.

@M1Combat, Could you then please point out the thread entry number (upper right) or at least the page of the ResolveDepth fix - difficult going through all 13 pages. Dave W.

Actually not - there are two different loading errors - one has to do with the Glass shader and the other has to do with ResolveDepth - and that one has not been solved or temporarily fixed. I have no idea why some of us need a fix and others don't even though we have the same openbeta version od DCS. It sure would be nice if Kegetys would take a look. Dave W.

Me too!! ?? After I backup the original shaders directory do I merge the new shaders files or simply just copy the new shaders? I would think I would need mostly the original shader files and then have replaced the 16 or so of them with the new ones??

Same here in VR - I am not able to hold a constant 45 fps. This was fine a few days ago - wonder what version we should go back to. Dave W.

The explosions are happening to me as well on the Stennis. For fun, I am landing an A-10C Warthog on the carrier - full speedbrakes, full flaps, 115 knots (no weapons) - and then taxiing back for takeoff and occasionally, I get the blowups at the stern areas - seems to happen both port and starboard. Dave W.

NOTE: I don't have the F-18 yet so I just used my UH-1 - I'm using 2.5.2.17978 DCS Here are my CPU Utilization snapshots. I am showing my 6 core at 4.2 Ghz with no mission before starting DCS, then with no ProcessLasso so it uses all 6 cores, then with ProcessLasso confining DCS to CPUs 1,2, and 3. I have read that DCS uses only 2 cores but it is hard to be sure of that since Windows will move a thread around amongst the cores if it wants to. BTW, the Mission was with a Huey flying to land on the Stennis carrier with the rest of the task force destroyers and cruisers along with several flights of F-18s, AV-8s, CH-53s, and SH-60s. Dave W.

Here is a Carrier Task Force Mission that is fun in a UH-1. Lots of ships underway to land in. Works fine in VR as well. Carrier_t1_UH1_Best.miz

Here is a generic Carrier Task Force mission file with no player so you can add your F-18, but also your UH-1 or A-10, or... quickly with the Mission Editor. It has a 4 flight of F-18s, AV-8s, the USS Stennis with some static aircraft and some cruisers and destroyers, CH-53s and SH-60s. This lets you fly your UH-1 around and try to land on the various ships or fly in formation with the other helicopters. Or with your choice of jets, fly in formation with the F-18 or AV-8 flights. I made it with no player so you will see it in your Missions list no matter what aircraft you own. I get very smooth performance in VR! Enjoy Dave W. Carrier_TaskForce_noPlayer.miz

First off, the Carrier Battle Group scenery looks terrific - near reality - except the wake trails for the battle group ships are a very simple, unmodulated , semitransparent stripe behind the ships. It really needs to have modulation like the wakes along the side of this center path. Thanks for a great looking carrier environment! Dave W.

@Pimp, Could you explain he modifications via the Mission Editor? Thanks for the MIZ file though. NOTE: Figured it out. Just add static aircraft using most expanded scale and proper heading with Link Unit = Carrier Unit and Link Fixation set. Icon is forward centerline of Carrier.

I have the X box controller as well - can that be used at all instead of Touch? I really appreciate your info on this! Dave W.

@dburne, I don't have (nor want to buy ) the Touch controllers. Is there any hope for me to use Rift Core Beta with just a mouse - that is, could I just start applications with a mouse (even if I have to use a Windows 10 Icon outside of the Rift. Right now, I use the "classic" home but I wonder if they will take that away eventually. Thanks Dave

One thing I forgot to mention is that I use Project Lasso to make sure that OVRserver_x64.exe runs at high priority. I started that a couple months back because I was noticing that Oculus Home was "sluggish" - I don't know if that helps tracking. You could try by using Task Manager.

@SkateZilla, I flew around with heavy maneuvering and lots of head turning in Aerofly FS2 in an F15 today for a half hour and didn't see any problems with 1.11 Runtimes.

@MrReynolds, Glad you have the DK2 going - except for a little more SDE than CV1, I think you will like using the old unit - it has advantages (no god rays, stays cool, only requires 75Hz, not 90HZ which gives you 20% more chance of keeping up with Riftsync). Also, I run my CPU at 4.2Ghz and with that and an Nvidia 970, I am able to run with SuperSampling at 1.5. I do not like ASW so I turn it off with CNTL+Numpad_1. I do wish the framerate of DCS was better - more like Aerofly FS2.

@MrReynolds, Just to give you confidence, I have a DK2, and running the latest Oculus Drivers(1.10.2.322199) on Windows 10, DCS runs fine in VR.

Yep, I'm seeing a steady 25 fps taking off in formation with a couple other A-10s and it should then go to 40 or so but it doesn't. This is with ASW off - with it on, I get some really strange texture distortions and not really any faster anyway. Dave

Let's forget the missions - just an A-10C ready for takeoff as a test. I agree that the frame-rates are down - with both 1.5.5 and 2.xx. With a A-10C facing away from Las Vegas at Nellis, with 2.xx (not VR) - I see ONLY 54 fps - that won't cut it in VR and any kind of RenderScale (SuperSampling) settings. With the A-10C ready for takeoff in 1.5.5, I see about 94 fps - still not enough. We need about 150 fps or more in nonVR mode. What has happened?? Dave