Oesau

More workload = love it

Yes, was noted in Oct but no acknowledgment as a confirmed bug http://forums.eagle.ru/showthread.php?t=148434

All makes sense so I'm sure most will be happy with the the approach (as I am)

My one and only experience seeing the Viggen was on this rainy day.. Saab Viggen.jpg by Mike Abbott, on Flickr

The A-10A in DCS has a Penny pod attached and in missions it does provide a designation marker - I just tried out a mission with a A-10C lasing the target for a A-10A and it appears on the HUD. Of course I can't deploy laser weapons, but at least the target marker is working.

Getting the same thing

Sure IvanK will be happy to see these as well!

And a new one

Yes its one of the challenges with VR and the idea that HTC Vive is going with is a potential winner (though to be tested). The idea that people should adapt and use muscle memory works for some but not all - therefore the technology should (and needs to for mainstream adoption in the future) have a way to interact with the real world or provide virtual rendering of the interfaces (or provide a virtual render with touch gloves that provide tactile input).

Excellent - thanks for that

It appears to be fixed, so I don't have to do that every time. It's very strange behaviour to be honest and I'm not sure why that worked. BTW when I used the local account, I started DCS and it asked for license keys for all of the modules, I didn't enter any as I didn't want to use up any of the activitations but started a mission to test if DCS would crash (which is the reason th exports didn't work, because I wasn't in the cockpit view of the A-10C

Update: Tried version 2.0.0.5 without AV on - same result, DCS crashes when loading mission Tried version 2.0.0.6 without AV on - same result, DCS crashes when loading mission My thoughts were that this is a permission issue despite that I am a local admin,however with Win 10 you can choose to use local accounts or your Microsoft account. I am using the latter (MS account). Logged out of the MS account, then logged in as the local user, started uMFCD, then DCS and DCS mission loaded without issues (uMFCD status was running). There were no exports present, but at least DCS didn't crash. I then logged back into my MS account and started uMFCD, then DCS, loaded a mission and voila, uMFCD was working with a export! Win 10 Note Note sure if the other Win 10 users did the upgrade of the operating system and then a fresh install, however I only did the upgrade. Whether that is relevant or not I'm not sure, but thought it was worth noting for completeness. DCS v1.5 was reinstalled post Win 10 upgrade.

As a complete newcomer to this thread but have long had a interest in the VR application to flight sims I have to say I was encouraged by the news of the front facing camera. From my perspective I've struggled with the thought of using a VR and my HOTAS, series of switches and keyboard. Yes, HOTAS isn't a issue as it's a memory thing, but the keyboard and switches are a different story. I don't want or intend to have a home cockpit so having the option to see my other input controls is good news. Now without actually seeing how it works (or the options around it operation) it's difficult to know how it will work IRL. However, what I'm hoping for is: a button to switch this on or off as well as variable opacity control so that control it to the level I personally need.

Sgt_Baker - any ideas one what might be causing this?

I've been doing some testing and have had no luck as DCS is crashing when I get to mission loading progress approx 80%. Windows 10 .Net is up to date (followed the steps for updating that DCS - release 1.5 version Steps to replicate: 1 - start ULTRAMFCD 2 - start DCS 3 - DCS is detected by ULTRAMFCD 3 - load mission (A-10C), get to approx 80% and then DCS crashes Confirmed if I am not running ULTRAMFCD that the mission will load correctly. Have attached Windows & ULTRAMFCD logs for reference. 20160105 errors.txt

Do you have DOF (Depth of Field) enabled (it's in the settings screen).

Sgt_Baker - looking forward to this, thanks for continuing to develop what is a great app.

TDC can only currently be assigned to buttons, not axis. Devs have said they may implement axis as a few people have raised this. Note - what we are assigning to TDC isn't actually the TDC - it looks to be a input for a Russian type system (in other words it's a configuration entry hang over from another aircraft)

Great - was about to post a request to add that to the axis controls configuration (as well as the radar tilt axis)

Excellent - thanks Sergeiev

Just checked and I don't have this issue. GADGET - check your control configuration and if they are inverted, go to the Axis tune menu and select invert and that should resolve it.

Thanks for the manual - a good read

Yes it looks like the old textures are back and the trees look (from the cockpit view) very dark

+1 really like your series of videos Bunyap

I too have had this issue - It doesn't happen when I go to the options screen when first starting DCS, but if I try to map controls whilst in game (i.e. sitting in the cockpit) the interface becomes laggy (extremely laggy).