gtrdrt

Are they pretty good about monitoring these forums and answering questions? Would it be better for me to contact them rather than relying on them to find my question and answer it?

I'm also running the 0.6.01 Runtime with DCS in Extended Mode without trouble, so I'm unsure of what you mean. Runtime 0.7 will no longer have extended mode. Only Direct Mode will be available, but I think it's supposed to be an improved Direct Mode with better performance than anything they've had prior to Runtime 0.7. But for the current version of DCS, it won't work with 0.7 if its Rift integration was built using a Runtime earlier than 0.6. If it was built with a Runtime earlier than 0.6 (Wow, I should have said 'Runtime 0.6 or later' instead of what I now have underlined. So sorry.), then I would be able to upgrade my Runtime to 0.7 and still be able to run DCS in Oculus Mode, as long as DCS has the capability of running in Direct Mode. Does it? I haven't checked for that in a while. Guess I better get busy... :smilewink:

Which Oculus Runtime version was used to integrate Rift? Hi - As some may know, the Oculus folks are going to release a new Runtime version soon (0.7). Unless the DCS devs used Runtime version 0.6* and above to integrate the Rift, DCS won't work for people who've installed the new Runtime version. So in order to decide if I want to install 0.7, I'd like to know which Runtime version the DCS devs used to integrate the Rift, because I doubt I'll want to install the new Runtime if DCS won't work with it. *I'm not certain about that number; it might be an earlier version. Regardless, I'd still need to know which Runtime version DCS used. Thanks...

Today's (sep24) update appears to have fixed the mouse problem. Thanks! Also, I stumbled across the reason for my keyboard not actuating the commands assigned to them; under Options>Gameplay:Difficulties, Game Flight Mode needs to be unchecked. (I don't think Game Avionics Mode needs to be unchecked, but I don't recall exactly, so you might want to test that for yourselves.) Thanks again for getting that mouse thing fixed. Another great help would be to make it so that info on the screen isn't outside of the Rift viewing area, and to make aiming reticles and target indicators and such be where they're supposed to be in the Rift display. Hope those aren't difficult fixes. Meanwhile, I'm having a great time learning how to make the Huey do what I want it to do and sometimes what I don't think a real one is capable of doing. This is some awesomely fun stuff...

Could someone tell me some possible reasons why I can't get my keyboard to actuate cockpit commands that mouse clicks can actuate, even though there are keys or key combinations assigned to the commands? Toggling "LAlt + C" seems to make no difference. thanks...

Nope, changing refresh rates didn't solve it either. So, maybe it would help if I posted some specs: GeForce GT 630, Windows 8.1 64 bit, Intel Core 2 Quad Q6700 @ 2.66GHz (64 bit), 6 GB ram. So is the problem on my end or on the DCS end? I do notice that no one who has viewed this thread has posted anything saying anything like 'me too.' I can fly, but I can't do a lot of cockpit stuff. I never have been able to get my keyboard to do some of the things I can do with my mouse and the little yellow crosshair. Any hints regarding that too would be welcome. thanks...

No, I don't have mouse trails on, and I've tried with Aero scheme both on and off. I've been trying tons of stuff, and still I get two mouse cursors in the Oculus display. To me, it looks like the left and right 3D cursor images are failing to converge. I can sometimes find the spot between the two cursors I see that is where I think the 3D cursor should be and that will allow me to click what I want to click. I just checked and found that I have my Rift set at 75Hz and my main monitor set at 60Hz. I'm going to go ahead and post what I've written here and then report back to see if making some changes will solve the problem...

I don't know yet if it's just my setup that's causing the problem, but since the latest update I'm getting two mouse cursors in the Oculus Rift, and it's a point somewhere between the two where the actual clicking occurs. Makes it extremely tedious to find and flip switches etc. in the cockpit. Any suggestions or info would be appreciated. thanks...

Yes, that same thread is where I found the suggestion to stop the ovrservice from within Task Scheduler as opposed to Task Manager. And since I did that, I no longer have to open either of them. I just have to open the Oculus Configuration Utility to pause the service... :)

Like I said, I don't have to open task manager; all I have to open is the Oculus Configuration utility and do those two simple tasks. Do you have Windows 8.1? If so, try just to pause the ovrservice from within there to see if you can get by without having to use that software you mentioned.

Yeah, I had already tried disabling wscript, but that didn't work either. In fact, I think it was *after* I did that that ovrservice started refusing to stay stopped. Then again, maybe I'm confused; I tried so many things. I should have taken notes. But now I remember that I followed a suggestion someone made here - https://developer.oculusvr.com/forums/viewtopic.php?f=26&t=11455&p=166497&hilit=task+scheduler#p166497 - to go into the Task *Scheduler* and disable ovrservice. (I'm using Windows 8.1, by the way.) That may have done the trick, because I'm happy to say DCS and DK2 are working for me now! And I only have to jump through *a couple* of hoops any more to fly: Prior to running DCS, I just have to go into the Oculus Configuration Utility and, one, put it in Extended Mode and, two, pause the service. That's it. Plus, I can open and exit DCS multiple times after that without having to pause the service each time. Hoping this helps others... :thumbup:

If only some of the folks who post those amazing DCS/Oculus Rift videos would share how they managed to set it all up so successfully. That there are videos of it has to prove that positional tracking can work brilliantly, but I've tried just about all of the suggestions I could find in this thread and still can't get it to work at all. For example, could it have something to do with the fact that I can't even get OVRService_x64.exe to stop automatically coming back on before I can get a chance to restart DCS? Has this happened as well to any of you? It's weird. Here's hoping there won't have to be many more of these cries for:helpsmilie: