wrl11

With the new update today my axis bindings on the warthog are broken. I tried deleting the config/input directory and starting over but no change. The controls page shows it correct (thrust L/R, rudder, pitch all showing correct with the little movement bars as I move the controller) but when in the plane, the left throttle controls the rudders, the throttle slider controls both engines and rudder toe brakes cause the pitch controller (joystick) to change. Crazy. No idea what to do about this one.

That's the way it is in real life too, only in one eye.

Just tried this thanks. But unfortunately no impact with the Rift S.

Higher gamma makes it a brighter grey sky that further washes out everything. I saw posts on the net that Elite Dangerous looked good in rift s, so maybe its something in DCS, the way they are doing the black sky vs Elite. Not sure.

I really like my rift S, much clearer. But I did my first night flight and was disappointed. The black sky is a grey sky, you can't see the stars. Its hard to see cockpit controls. I turned gamma down to 1.0, no improvement. I erased the spud directory like you could do with the old rift to make night black, no effect. Anyone figure out how to improve it?

I have had occasional white flashes. I assume Oculus and or Nvidia will fix that soon, its not often, maybe once or twice a mission. Not sure what you mean by crashing to grey. If you do Passthrough the video goes grey to see outside via camera in front, are you talking about that? If so you may have a button assigned to the Passthrough command.

I have found a good position to make it less blurry on edges. Like someone suggested here, I made it a bit tighter and also pushed it down against my nose. Seems to work best. After a couple more hours of using it today, I still highly recommend.

I played with my Rift S for about 2.5 hours and really like it. PROS: I can read all the displays without leaning forward, and that is after lowering PD to 1.0. Frame rate was slightly slower but never dropped below 40 in big missions so still strong. Everything seems more crisp, very little screen door effect. Super easy to set up. Comfortable (Rift was as well). No sensors anymore, and there was no delay in my head turns. The touch controllers work great and are feather light vs the Rift ones. Moves in and out to accommodate glasses, which is very nice. CONS: Sound is terrible. But they have a jack to plug in earbuds, so I plugged in my Bose and sounds great now. There is a smaller sweet spot then with the Rift. Its like the Odyssey. As was mentioned a few posts ago, you have to actually turn your head to see it crisp vs keeping head straight and just moving eyes. It blurs at the edges unlike the Rift. It took me a while to find the best position. The headset is a bit heaver. Overall, I highly recommend it.

I get this also. I end up just going into the serverSettings.lua and deleting the mission list line to clear it. Using the Web GUI does not do it.

I had this happen to me too. I could not reset the radar, the scans were stuck on the left side.

That makes sense because I am using a slightly older driver that works best with my system (419.67).

We had two guys crash after Mk20 release also. But I did not, not sure why the difference.

That's interesting. I have always had that patch in the PG map, but when I just checked, I don't have it anymore. Not sure what update made it go away but probably a recent one.

It was slower on the benchmark (3D mark time spy) for me. 13200 vs 14000. I rolled back to the prior driver.

The ones I'm dropping today are dead on accurate.

LTOD works. If you push it, then put the time in the ufc such as 230500 for 11:05pm and hit enter it changes the time. So sometimes when I start a mission I change the local time to my real time so I can keep track.

Having the tacview streaming on another monitor (or computer if you don't have 2 monitors) made it much easier to track what was going on. Great addition!

Great update Bankler, thanks! What are some of you high scorers getting on groove times? Normally my groove time was good with human LSOs (I know, subjective), but I am getting a few seconds higher then I would think from the program.

I rewatched Wags video, and at 8:31 it does not show the range and vec info either so maybe that is just the way LTWS is... I might have to uncheck that mode and wait for TWS. But Wags does say the LTWS is for surveillance and not engaging since you get detailed info on up to 3 contacts.

I noticed that too, I hope its a bug that will be fixed as the range and closure info is very important.

Shift means the laser designator is shifted to another target. I have also had him call abort when I have a different weapon from what he requested or its set up wrong.

Its easy and free to have both stable and OB on your computer. You can just copy your control config settings into both saved games directory and you are done. No need to get upset.

With the new SA page on the FA-18, I can now see what the AWACs is seeing and have been surprised how often contacts drop or don't appear (just SIL your radar and turn off F/F and just get data from AWACs). I have not done testing as to why, but as the AWACs turns, contacts can drop and also depending on the AWACs aspect to the target as it moves on its orbit, contacts can drop. Not sure how realistic this is but now I don't have the same confidence in its calls after seeing this on SA.

The SA page has been enlightening to see just how much the AWACs do not see. I have not tested why exactly this happens (noching, cross section exposure etc) but I can have AWACs detecting a couple high flying migs just fine, then the AWACS turns in its racetrack pattern and they are gone, with "Picture Clear" despite them being 20 miles from me. Same if the migs turn, they can disappear from AWACs. I now take the picture clear call with some caution.

I have set up my dedicated server, but the clients are not recording anything but themselves. Any tips on getting it running? When I do the server the old way, the tacview is fine, so it is set up in the host server machine. Thanks