ducs Posted September 4, 2017 Posted September 4, 2017 I know one other person is having the same issue. Anyone else having it or have figure out a solution?
dburne Posted September 4, 2017 Posted September 4, 2017 I know one other person is having the same issue. Anyone else having it or have figure out a solution? No problem on my end, however I use the Oculus Tray Tool with a profile for BoS to disable it. When I was running a benchmark a couple days ago with BoS I was trying to disable with the ctrl + numpad 1, it would stick for a short bit and then would kick back in, so there may be something up with using the keyboard command...
TG-55Panthercules Posted September 5, 2017 Posted September 5, 2017 I've just been turning it off with CTRL+1, and have not noticed any situation with it turning back on by itself. When I turned it on specifically for a test (using CTRL+4) it locked everything to 45 FPS (which is well below the average FPS in my tests) so I assume I would have seen some evidence like unexpectedly low results from my tests if it were coming back on by itself. However, I haven't been looking out for this behavior specifically - will try to keep an eye out for it in my next few tests. I'm running with 385.41, too.
ducs Posted September 5, 2017 Author Posted September 5, 2017 (edited) The problem is that ASW is forced on and the ctrl+1,2,3,4 shortcuts are no longer working. Its just automatically on and I cant shut the thing off. The problem seems to have only happened once I installed the new nvidia drivers, but it makes no sense on how that would make ASW stuck in auto/enabled Edited September 5, 2017 by [TWB]ducs
dburne Posted September 5, 2017 Posted September 5, 2017 The problem is that ASW is forced on and the ctrl+1,2,3,4 shortcuts are no longer working. Its just automatically on and I cant shut the thing off. The problem seems to have only happened once I installed the new nvidia drivers, but it makes no sense on how that would make ASW stuck in auto/enabled Ok so this sounds simple but I only mention it as I have done this myself, are you sure numlock is on?
SCG_Fenris_Wolf Posted September 6, 2017 Posted September 6, 2017 ctrl+1 2 3 4 do work for me. Check your numlock. Check that you have selected the IL-2 mirror window. Make sure to keep the headset on, don't leave the proximity sensor.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now