lboothby

@BIGNEWY So Oculus is now jamming through the V63 update no matter what you do. They hit my computer with it sometime today, even though I had auto-update turned off and had changed the file names. Bottom line.... Everyday more of your customers are unable to use your product. What is the point of working on a bunch of updates to DCS if a good chunk of your customers can't take advantage of them. Oculus is saying it is your problem, you guys are saying you are too busy to fix this, and more and more of us now cannot play DCS. THANKS PAL.

I realize this was not your fault, and I understand your reasoning......... You guys are making a real mistake with this one. There is a significant number of people out there who fly in VR and now cannot use your software. Your response comes across as "oh well, too bad for you". If windows were to some how send an update that bricked DCS for your customers, would your response be the same? You are now BADLY hurting your own reputation with your customers. You really should re-think this.

It says it is too big. I gave it to Strike earlier today so I think he is going to pass it along. Here is a video clip though. IMG_6637.mov

The wake turbulence issues are legit. Myself and another guy were on the USLANCOM server behind the tanker and the jet was a handful trying to plug into the drogue. Pitch sensitivity was very high when in the wake of the KC-135. I've been flying the hornet since it came out and I've got hundreds of tanks on servers. It is much more difficult to maintain pitch control. Today I was flying with a guy and we did a fan break. As he rolled in behind me and lowered his flaps and gear, the jet suddenly departed with no warning, rolled off, then pitched down violently and crashed into the ground from about 800 feet.

I just had the control lockup on the super carrier flying build 2.9.3.51704. Looks like the problem is still here.

Me too.

I found the same issue with a cold start. Radar Altimeter was working, but when I went to auto range the rockets or the gun, the high action display in the helmet sight still showed an "M" range instead of an "A" range. Also, this was on a server, not in single player.

No prob. Sorry I about the track file. It's a little big!

1: (Intermittant), power from standby to on, pod locks full aft position. Cycle standby to on, and then pod slews foward. 2: VVSL button gone. 3: (Intermittent), pod will not slew. A very small cross cursor slews around the screen but the primary cross will not move. Cycle into PTRAK then ATRAK and it will slew. 4: System will not drop designated target after all weapons are released. Target designation carrot and arrow stays in HUD in all master modes. 5: When you enter LST mode the screen goes to solid green with a large cross in the center. When the system acquires the buddy laser the screen changes to the camera view. When you release the SLT mode you have to select PTRAK then ATRACK to slew the pod. 6: When you select air 2 air master mode it brings up the TGP in the left DDI. It is the same if you select any air to air weapon on the stick All of this is on USLANTCOM multiplayer server. Track file is 166mb. I have the file but can't load it because of size. If you have an alternative send me a PM. .