Frusheen

It's a bug and already reported. You can use a joystick mapping program as a work around. http://joytokey.net/en/ There are several others.

It works from the keyboard but not when mapped to a joystick button.

Yes I can use the trackball in the rift and I use Vaicom for radios so I seldom need a keyboard. Mine are a good few years old now and have held up well. I modified them as there was slop or play in the axis which I shimmed out. I also switched out the control board as it was only 10bit. I think the new models now use a 12bit controller. They are well made but honestly I regret not having gone komodosim all round. I just hadn't the budget at the time though so as a cheaper alternative they work very well. The komodosim cyclic is a much more polished piece of kit though.

I've no experience with leap. If it can emulate a mouse then I'm sure it could be made to work. I've read mixed reviews about its accuracy though. I'm more inclined to wait for some form of hand tracking to be added to the rift SDK and implemented by ED. I've no updated pics of my G-Seat setup as it's still a work in progress. Here is a picture I took early on in the construction before adding the belts and flaps. You can see the trackball on the collective head.

These effects are not present in a real aircraft. No part of the flight stick is connected to the wheels so I'm curious to know why you'd want to introduce them in a sim.

I'm not one bit surprised by that news. I predicted $1200 for the Vive months ago and that was before the $600 rift price tag.

No ability to peek in the consumer version but the foam could probably be cut around the nose if absolutely needed. I currently use a trackball instead of a mouse. I have it connected to my collective as my controls and seat are away from my PC. It's very easy to use in the rift with clickable cockpits. No fumbling to find it like you may have with a mouse.

I tested this again (1.5.2) and I am seeing my last core is being utilized heavily when observed in afterburner at about 80%. When I check with core temp the value is much lower ~20% on that same core. very confusing.

It doesn't work via a joystick button. That's what the op is referring too. You can get around it by using joytokey or other key to joystick mapping software.

Are you looking at a total % for all cores or 10-12% on a single core?make sure you view each core. I've done a lot of experimenting this evening and can't recall which map I was on for those figures. I'll have to double check.

Seems to me that GameworksVR wouldn't make things any better. Based on the usage I am seeing since upgrading my graphics card the bottleneck seems to be the CPU. Still it's alpha software and I'm sure we will see more improvements as time goes on.

I'm only seeing about 40% load on my 980ti with DCS in the rift and cpu has one core at about 70-80%. Some serious optimization needed.

He's not talking about traditional sli. He's referring to multi GPU support from nvidia and AMD. These are the gameworksVR and liquidVR APIs I mentioned in my post. Traditional sli is not what we want for VR. It increases latency.

I'm at the limit on my cpu. I'd have to de-lid the chip to go higher. Even on my H100i cooler the temps are as high as I want to go when under very heavy load. I was unlucky in the silicone lottery I think. As to utilization I'd need to check this more closely. In the rift afterburner is reporting an average of 50% GPU load on the overclocked 980ti, graphics memory 30%, motherboard ram about 40% and cpu is at about 20%. Maybe one core is maxed so I'll have to check that more closely by monitoring each core and then consider if de-lidding the chip is required. I haven't played enough on a monitor to compare performance vs dk2. Just tried it a few times to see the fps. For now I'm reasonably happy. I think ultimately its optimizations by ED that will help improve performance.

You're welcome Hannibal Windows 7 i7 4770k overclocked at 4.2Ghz GTX 980ti overclocked at 1.5Ghz 8Gb of ram

Yes. In the dk2 with the current rift implementation and alpha state of Nevada. I'm including the Vegas strip in my numbers which is a lot harder on the system than flying out in the desert. Of course as VR matures and with it EDs implementation of the runtime improves this requirement will change. As we stand currently that is about the fps needed on a 1080p monitor for a smooth dk2 experience on all of the map EDIT: should say with my particular setup.

Sorry but you said if in a previous paragraph hence the misunderstanding. Sli is of no benefit in VR. We need gameworksVR or LiquidVR APIs to be implemented. Traditional sli actually increases latency. Vive camera doesn't appear to be all that great. It's a flat image which gives completely incorrect depth cues. See the video below

75fps is the stereoscopic refresh rate required for dk2. For example for me to have 75fps (all the time) in dk2 with Nevada my settings when rendered in non rift mode show fps of about 180-200

Do you know the screen specs or not? You say in the first line you don't know the specs and in the last line that based on the specs it clearly isn't the best screen on the market. It's custom screens and they've said they are the best they could make. You seem to measure quality based solely on resolution. If the resolution was any higher we couldn't run DCS on it. I have a 980ti that can only just maintain the required 75fps over downtown Vegas on dk2. Still not sure it'll be enough for the consumer rift at its resolution.

Doesn't look like the huge breakthrough is all that great. The camera gives incorrect depth cues which won't be good for augmented reality use. Perhaps the release version will improve on it.

Great video on Vive pre from Tested.

Import taxes and customs fees are included in the price.

Good stuff.

Try chrome if you can. I had issues on safari with the support page but it worked in chrome.

You can still preorder but the site is swamped. Lots of issues.