Smoky

Everything on mine works great until I specifically select that I want to configure F14 commands. That is when it stops acknowledging ALL USB controls. Since DCS stupidly maps multiple controls to flight axis by default this means I cannot fly F14 until this is fixed. Probably best to wait for this to get out of OpenBeta. It just never goes well.

I just starting having this issue as of installing F14. Unplayable at the moment

This is OT but I wanted to respond to your comment so you knew...atm Frontier has no plans to support 0.7. I've rolled back to 0.5 due to major graphics degradation in E : D with 0.6. So, for now anyway, if you play E : D you have to roll back to 0.6 or 0.5 depending on what works best. But 0.7 will cause E : D to throw an error and crash. https://forums.frontier.co.uk/showthread.php?t=188839 This was one reason for my post...I'm wondering if I can keep 0.5 and still take advantage of the advances for DK2 support in DCS, or if DCS requires 0.6 or 0.7. Basically just need to know if I need to swap drivers when I go from one game to another. That and the whole zoom thing.

I found when I was using the TrackIR it was still very useful to control zoom on an axis, so that I could set where my eyepoint was being tracked from. So if I'm just en route, I'd have the entire panel in view which game me good situational awareness for navigation. If I needed to use the HUD I would zoom in a bit so the HUD became legible. If I need to evade I would zoom out all the way so I could scan for things like SAM launches. I've heard this response that "zoom isn't broken on the Rift, just move your head closer." Well even with a TrackIR that would mean leaning REALLY far forward unless I configure that TIR axis to be really strange. Being able to assign a zoom axis to a control remedied all of this, and quite effectively in my case. So I guess I don't see why it would be such a "frowned-upon" addition for Rift users. It seems like it would be really useful, especially while the VR hardware evolves, because zooming helps to overcome the legibility issues we VR users often encounter. As an aside, leaning all the way to where my headset is actually touching the tracking sensor and I still can't read the HUD.

With the latest DCS updates, can you now read the gauges using DK2? The Hud? Is the zoom fixed? (Biggest issue with DK2 in DCS was the lack of zoom....head tracking works but you can't get close enough to read the HUD). Also, what DK2 runtime version is everyone using with DCS? is it safe to continue using the .5 beta drivers on DK2 with DCS? Or did everyone have to upgrade to .6 or .7? Elite:Dangerous doesn't work with .7 and they say they don't plan to fix it! Trying to find a version that's lowest common denominator for all my games is getting to be a challenge.

When stuff like this happens I roll back to the last previous version that worked, get it running, then try patching again. That usually solves it. You may have to ping ED for temp FTP access to the archive if you've deleted your older files.

Ok. Sorry for speaking up. Won't happen again. Enjoy the server.

My server still connects however the biggest issue I am seeing with the latest rev is crashes.

Master Server seems fine now. My Eagle Squadron training server is up.

Try our server "Eagle Squadron" Most often I have Dragon's daytime training scenario loaded and folks tend to be well behaved. If you find otherwise let me know the names of the offending players and I'll ban them for you. :)

Hi folks I have been experiencing this issue since a few patches ago at least. Searching didn't reveal anything useful. When I do a ramp start, and following all procedures to the letter using the manual, the radio menu is empty. I see the tags "Interphone" "VHF" etc. But there are no items to select. The situation changes once I am airborne. Then the menu items appear and work properly. I have tried flipping the "easy communication" option on and off with no effect on this issue. Sorry if this has been discussed already. But I couldn't find this issue specifically. Thanks

All solved thanks to you folks. Turns out because the Warthog was so new to him that he didn't understand what I meant by lift the throttles past the idle detent into cutoff. He THOUGHT he had it done but realized later that he really had to lift up on them. This got me at first too. I still don't get why they don't move at all in-game until this is done. Mine does not behave this way. They always move for me. But I guess everyone's setup is a little different. Thanks again for everyone's help. He was out dropping bombs in no time.

We will try all these suggestions this evening. Thanks folks The bizarre part of it all is that my setup does not exhibit this behavior. Ramp start, air start, doesn't matter on mine. Cold and dark, my throttles have and still do always work fine from the get go. I wonder what the difference is between setups that makes this an issue for some and not others?

Why the use of quotes, as if to suggest I am lying? Seems antagonistic. No need for all that. I posted on his behalf as a favor because I am more familiar with this sim and the terminology used therein so it's easier for me to post a query. Sorry if doing so has rubbed you the wrong way for some reason. To others, very useful suggestions so far and they are appreciated. My buddy is following the thread and we're going to troubleshoot more tonight. Thanks for the help!

I think you are correct. Will recheck my procedure this evening. Thanks!