dot

Interesting video if you haven't seen it before: [ame] [/ame]

Compliments on an excellent hotas choice :)! Too many people these days are happy with using joysticks with springs, which makes me sad :(

I wonder if elmor plays DCS, and what are his frame rates :) http://hwbot.org/submission/3086732_elmor_cinebench___r11.5_core_i3_6320_7.92_points

Thanks, I'm just wondering whether I'd need both. I've heard somewhere that buttkicker mounted on a racing rig turns the whole rig to a low frequency speaker with slight delay, which might be annoying. Have you experienced something similar? Hm, in that case I think the only thing that can be done on our end is to overclock the i5 (or i7, but not sure if the price difference is worth it for DCS ) as much as possible and wait for multithreaded rendering support. Also, your one core should be close to 100% if not, we can probably expect a patch that will improve performance by at least 20% soon :)

Here is some info about binaural hearing in humans: The benefits of binaural hearing are numerous. Not all sounds bend equally around the head. Short wave lengths associated with high pitch sounds tend to be reflected before reaching the other side, while long wavelengths associated with low pitch sounds may reach both ears more readily. Having two ears is like a blind spot detector for hearing. When one ear is in “auditory shadow”, the other is in “auditory light”. The brain also makes use of minute differences in signal strength, time of arrival and phase of soundwaves between the two ears to locate the direction of sounds. These differences between the ears also help our brains to suppress background noise and focus our hearing on the things that matter most. Individuals who lose hearing in one ear find that the auditory landscape becomes less three dimensional and have greater difficulty focusing in background noise or telling where sounds come. https://www.amplexhearing.com.au/from-ear-to-brain/ (P.S. My wife is an audiologist :)

Butticker users (giggles:) ) how would you compare a buttkicker and a 400-500w active sub woofer mounted directly under the seat?

That seems to be a problem with single threaded engines... I have 8 core xeon @ 2.5 ghz so I'm in ever worse situation. I'll probably swap for i5 and overclock it as much as I can, that seems to be the best thing I can do until we get better multi core support. I've misread the post, thanks for pointing that. I never had SLI or crossfire (some things are better left to people who have time to tinker with them), so for me VR is probably first good reason to consider multiple gpus. However, if only one of your cpu cores is feeding the data to the gpu then the gpu spends most of it's time waiting for the cpu, which is great for the environment but not for fps or latency. Adding 2nd gpu in the mix might not help.

I'd suggest checking your GPU and CPU utilisation. If you don't notice a big improvement in FPS with 980ti, it could be that your GPU is waiting for CPU to build a command buffer with all those buildings and objects so adding a faster GPU might not help as much as you might expect.

I should probably check this myself, but do you know aprox, what is your cpu and gpu utilisation with DK2 compared to single screen? If you are not already at the limit, try increasing the cpu frequency a bit more, when you are near a city all those buildings need to go through cpu first. i7 at 4.2 should be good enough for DCS in rift, it probably takes time to tweak the engine for VR so I'm sure you'll see improvements in the future. Also, you can't buy much faster cpu than your, and oculus baseline is i5@ 3.7ghz max... I'd be happy with this :) With Oculus, or HD projector, I'm not a big a fan of tripple monitors

Mutliple GPU support is quite important, here is an interesting talk from Valve: Go to 13:21 for mutliple gpu part [ame=https://www.youtube.com/watch?v=JO7G38_pxU4&feature=youtu.be&t=801]link[/ame]

or they could have gone with front facing camera like Vive...

No, screen is usually split in half so each eye is seeing half resolution image each frame. They had 2 billion reasons to sell out, that's the only math you need to know.

I've said IF it's pentile, read my post again. About DCS performance, talk to DCS guys, maybe they'll listen to you and implement multi threaded rendering...

741 euros is a bit steep, I'm sure that some game developers and GPU manufacturers are now curled up in a ball, sipping whiskey under the desk and rocking back and forth... Lots of people will be priced out, and once you've paid 741 euro for the rift, there is less money for games and hardware upgrades. How many of you now plan to buy both headsets (vive and rift)? I'm still waiting to hear what the actual screen specs are. If it's pentile then it will have LOWER sub pixel count than a puny 1080p RGB screen, and LOWER refresh rate than Morpheus. Yet again proving the point that they are greedy sell outs. The main reason to sellout to Facebook is to get the best screen on the market, which looking at the specs it clearly isn't.

Hi all, I've recently tried 1.5 beta again (wasn't working great after launch). I have to say that I'm impressed! the game looks and runs much better on DK2 than the previous version. I sometimes get black square flickering in the right eye, but that might be me pressing keyboard or mouse buttons (it's very easy to switch to windows of another app when oculus is in direct mode). The only thing I should mention is that colors look very washed out compared to the picture on the screen. This is probably due to DK2 pentile screen. I'm wondering if DCS guys tried playing with contrast and exposure as CV1 looks like will have crappy pentile screen as well?

I'm really hoping for improved multithreaded rendering performance at some point, for now overclocked Pentium G3258 (~60$) probably performs better than my 8 core Xeon e5 2650 ($1000) :joystick:

http://hexus.net/tech/news/graphics/86636-nvidia-pascal-gp100-gpus-spotted-transit-tsmc/ This should help with VR rendering...

Same here, dk2 screen is too bright, crashes all the time and framerate is quite choppy and laggy. Single screen performance and gfx quality seem much more improved now although I'm still struggling to keep 75FPS when flying close to the ground. The only way to get constant 75 FPS is to eject :) win7 xeon e5 2650, 16gb ddr3, gtx 670 Logs.rar

I have a similar problem. Last time I played DCS I've set 2560x1440 resolution to get some eye candy from supersampling. My monitor is 1080p, now when I start DCS I have no way of changing the resolution as I can't see the edge of the screen. Win 7 64bit MSI GTX 670

DK2 seems fine when looking at close up objects, however looking at distant stuff reminds me of my childhood playing 480x320 resolution games. In DK2 the main problem is pentile screen, which is marketing bs to say that they have 1080p or 1440p screen in Gear VR, in reality you get one third less RGB pixels and it shows horribly when looking at text. Another problem in HMDs is FOV, CV1 lenses spread 1080x1200 resolution screens across 100-110 fov and that is much more than when you look at your monitor (probably ~20 degree fov). This results in 'bathroom tile size pixels', like we had back in the 90-ties. You can get rid of the grout, but you are still looking at bathroom tile size pixels.

bdw, this is what I've meant to post earlier :) http://vrfocus.com/archives/18180/flyinside-fsx-kickstarter-goes-live/

Yes, orange light should be on in direct mode standby, and goes blue when you start a VR game. In extended mode blue light should stay on constantly (maybe it goes back to orange if you turn on the screensaver option in configuration utility, but I'm not using that). I remember a lot people saying that DK2 screendoor effect was practically eliminated just as oculus opened DK2 preorders, so I'm going to wait a bit before jumping on hypetrain for CV1 Technically speaking screendoor effect might be eliminated completely on CV1 (no black border around individual pixels), however this won't save you from the low res screen. When looking at distant objects, does it still look like you're playing a game with 480*320 resolution, or have they managed to make it look like you've playing 800*600 game on PC monitor now? If they manage that, it would be a huge improvement...

I'd to hear which one is better (crescent bay or vive) from devs, if they are allowed to tell us. I'm most interested in tracking and image quality.

What are the recommended specs to run DSC1/2 on oculus rift and htc vive at 90FPS? Any plans for multithreaded rendering, sli/crossfile and direct x 12 support?

What about HTC Vive support? DCS is Steam game so I'm hoping someone is looking into this. Do ED guys have Vive devkit? Edit: They do! \o/ http://forums.eagle.ru/showpost.php?p=2417071&postcount=89