Mad Dog 7.62

That did it, thanks!! It has been a very very long time since I messed with a batch file....MS-DOS days.....

I am trying the batch file route, but I keep getting error messages. I have checked the paths over and over and I cant see the problem. Here is my bat file: copy C:\Users\Mike\Saved Games\DCS.openalpha\Config\Source\options-VR.lua C:\Users\Mike\Saved Games\DCS.openalpha\Config\options.lua start C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\DCS.exe When I run the .bat file, under the first line it says the system cannot find the file specified, and under the "start" line it says Windows cannot find C:\Program I think its some kind of file syntax problem but I have looked at it 20 times and even double checked capitalization and tried removing the spaces.....anybody know whats wrong here?

You've always been able to use joystick buttons as modifiers. Do you mean you cant use them as modifiers with the VR controls?

Well this is annoying as shit. I downloaded this, struggled trying to get it to work after watching the incomplete tutorials that cut off right when they get to the part I needed, and THEN find out it doesn't work anyway.....awesome.

I'm only running 2.0 so I hope we get the VR improvements in that one soon. Any reports on the VR updates in 1.5?

Just in case you don't know, Steam and the Oculus store are both running some good specials right now. Picked up several titles I was planning to get anyway at good prices.

I have my Oculus software on my D: drive, and I got it working. You have to specify the file path under File in the debug menu.

Did you install the Oculus software in the default directory?

Wishlist item: A Icon or Command Line switch that lets you launch DCS in 2D mode for the times you want to use the editor, replay a track, make control adjustments, etc. that are better done in 2D.

Another item for the VR WISH LIST..... A icon or command line switch that lets you launch DCS in 2D, Non-VR mode for the times you want to use the mission editor or watch a track or whatever else, without having to be in the goggles. That would be nice!!!

OK....question. You can recenter the cockpit view with KP5, but when I try to use a HOTAS key combo for that, it doesn't work....seems to only work with the keyboard??

I am really having a blast in DCS with the Rift, to the point I haven't really messed with much else. The A-10 is awesome, and the Ka50 is cool as heck too. Blasting low over the Strip in the helo in VR is fun!!! Really looking forward to the improvements that are coming, but they only mentioned them for 1.5.....and hints when they might make their way into 2.02x?

Did you install Oculus in the default directory? If not, you have to specify the location under "File" in the SDK. I am also leaving the debug tool open, closing it seems to nullify the change sometimes.

Just use the tool in Rift setup......pretty simple.

VR-Hunter, I have tried some of your ideas, and I am seeing much less judder. I am using Medium on Visibility Range and Low on Heat Blur and getting very smooth performance, but I agree turning down MSAA and Anistropic Filtering gave a boost.

Wags said several days ago the menus are fixed on their internal build, but that change hasn't been pushed out in an update yet.

I think we will get those details back, with Generation 2 VR and the corresponding GPU's. Just give it a year or two.

Right Click the little speaker icon on your taskbar, and make the Rift the default audio playback device.

Not really anything to do with Oculus, its a limitation of the GPU. But it is not as bad as it sounds, and its worth it. Once you've flown in VR.....you wont go back. When you find yourself reaching for a knob or switch because your brain thinks its really there.....that's how cool it is. A 2D cockpit is pretty blah after just a short while in VR.

System specs are in my signature, nothing extravagant. I don't see over 50% CPU or memory useage, so the limiting factor is certainly the GPU. Not sure of actual frame rates, but its smooth UNLESS I am over downtown Vegas, then I notice some judder. Also, I just confirmed having the Debug tool open causes judder in some other apps, so I suspect it causes a hit in DCS as well.

The only thing that's made me really sick was a No Limits 2 roller coaster. I would just try some gentle flying in DCS to get used to. Save the dogfights for when you are more comfortable, but just flying and practicing shouldn't be too bad.

I have had my Rift for a few days and have had to ask a lot of questions and do a lot of tweaking to get it to where I am fairly happy with it. I want to share what I have found and maybe save some others some time and aggravations. First of all, you're going to want your sensor pretty much directly in front of you. I had mine off to one side, and it tracks perfectly fine, but I had trouble working the switches on the side consoles. Putting it in front pretty much solved that. Second, I would make one of your HOTAS buttons Active Pause. Things are not perfect yet in the world of VR, and sometimes you have to come out of the goggles to find a keyboard combo, misplaced mouse, or something. Next, download and install the Oculus SDK. There are instructions on YouTube, and its pretty simple. This lets you bump the cockpit resolution, but in my experience I still need MSAA set at 16Q along with upping the pixel density via the Debug tool to get a clear cockpit. Also, turning on console lights even in the day makes the labels easier to read in VR. Here are the settings I am using, I am still experimenting but this seems to be close to where I will end up: Textures: Medium Terrain Textures: Low Civ. Traffic: Low Water: Low Visibility Range: Low or Medium Heat Blur: Low Shadows: Flat Res. of Cockpit Displays: 1024 Every Frame MSAA: 4X HDR: Off Depth of Field: Off Lens Flare Clutter: 0 Trees: 6000 Preload Radius: 100000 Anistropic Filtering: Off Flat Terrain Shadows: Off Note:Edited above for better frame rates! My startup routine is to start Oculus Home, load the Debug tool, set Pixel Density to 2.0, load DCS World, close the Debug Tool, and then use Alt+Enter to make DCS Full screen. If you don't make DCS full screen you will have troubles with your mouse working properly. There are some people who leave the Debug tool open, but others say it causes judder. (I am now leaving the Debug tool open....closing it seems to nullify changes to pixel density at times). All the above give me a very readable cockpit. The HUD is clear, the instruments are clear, even most of the smaller labels are very readable. VR certainly is not perfect as yet.....but after a short time in VR, going back into a 2D cockpit is like stepping back from playing a modern sim to the Atari days. Its that bad. Hopes this helps someone! Mad Dog

Thanks SkateZilla I knew I had seen a post about that but couldn't find it.

Go to the Oculus thread, and find the info on using the SDK to bump the pixel density. It makes the cockpit gauges and labels much easier to read. Enjoy! Got mine yesterday!

I thought I had read or seen something about this issue, but I couldn't find it in this thread. Thanks for the info! I can live with things until more of the bugs get worked out. It is certainly amazing....so realistic I have found myself trying to rest my arm on the cockpit rail or reach down to switches and wondered why my hand wasn't finding anything!