[=;355297]
Oh yeah, let’s start another discussion wether VR will be the next big thing or an epic failure (nothing in-between, of course). My position is fairly simple: Epic tells the people that the engine is ‘ready for VR’ and this people are trying to create VR projects with it. So it would be nice, if at least the basic stuff (like actually working camera controls) and detecting if a HMD is active would work as expected in the major releases.
I am not even talking about performance optimizations or VR project settings, just the basics.
Oh, and I am pretty sure that DX12 integration isn’t currently postponed about all that stuff about ‘ugly VR glasses’…
[/]
Hey ,
Let’s be nice 
I wholeheartedly understand a bunch of your frustrations as I’ve dealt with a lot of the ups and downs ever since 4.0.0, and believe me, I’ve found some bugs that made me nearly rip out my hair but I held strong and worked closely with Epic Support as they genuinely wanted to do their best to support me and help me nail out any issue that ever comes up.
Of course I have also found issue that made me scratch my head as to why they still existed but again, staying on top of the keeping the Support Team informed got me past any major issue I’ve come across thusfar.
The primary title I’m working on is a heavily VR based title but since there is no support for DK2 yet in Win10, I haven’t been able to test a build or see if the Preview is broken for me as well. But if there are some issues broken with VR, let’s do our best and help Epic understand what is going down so this no longer holds you back buddy 
Okay, so VR Preview is broken for you, do you have any links to AnswerHub posts regarding this that you have previously posted? If not, let’s get one up there and reply back with the link. Epic will get a technician assigned and make sure when you receive any email of activity from that thread, make sure to get back to the awesome Epic staff and if you respond timely, they’ll be much quicker to reply back as it likely raises in their queue.
Another thing is the issue might actually not be Epic’s fault at all and could potentially be the graphics driver you currently have installed. (In the meantime, I’d try a couple different drivers and see if they yield different results). It can also help Epic QA the issue faster if you have those results beforehand.
The second Win10 support is live for DK2 + latest support for DK2 in UE4, I’ll be more than glad to do some testing and share my results if it helps resolve this issue for you.
But trust me, I’ve been in your shoes and I know it can get upsetting and make you feel as though Epic doesn’t care but trust me, they really do and honestly want to see the best for us. As developers, we should all understand that sometimes you can’t test every single permutation through QA and just the sheer size of the engine currently makes it even more difficult.
However, all of us that have dealt with some of the downsides to being early adopters, we are clearly still here for a reason! We love the Unreal Engine and want to see it evolve into something amazing! 
Let’s continue to do our best helping the amazing staff at Epic out because at the end of the day, for all of us to have this opportunity to have “full” access to the engine, which used to cost an amount of money that most of us wouldn’t be able to previously afford, they are doing an amazing service for everyone. They are also the 1 company out there with a Game Engine that supports and embraces their community more than any other company out there.
Hope everyone is having a great week and if I can help out in any way , let me know and I’d be glad to lend a hand. Take Care guys and have a great Monday!