Wicked.-

It's not just the Cougar that has this problem. Even if you program the slider or the coolly hat to perform the same function on a Warthog, the behavior is the same. It's an axis and input problem not specific to any one controller. It does need to be fixed but seeing it's not a show stopper I wouldn't hold my breath for a quick fix.

Agreed. I posted a slightly snarky comment on the YouTube comments for the trailer. I said what good is TWS when you can't see the contacts because the MFDs are so dark. Then I asked if they could add the EXP option in the FCR. Wags replied and said YES, the EXP addition will be in this update as well. While that doesn't fix the MFDs, it does mean we can EXPand the view, or zoom in if you will to separate overlapping contacts. Well done Wags.

You can always tell the Index owners are happy.... it's crickets in here again lol.

No, but they don't ALL work for other headsets either. Other than the negative LOD for OpenGL, the settings I've applied work with VR.

No idea, it was there so.... lol

That doesn't surprise me at all. However mundane they are though, they work! lol

I have an "almost" perfectly functioning Cougar TQS with TUSBA and I fly with a Warthog throttle. The reason is thus..... available input buttons. Another reason is the lack of friction since the piece of plastic disintegrated circa 2006. Duct Tape supplies friction now and I have to reapply it about once every two weeks since by then it wears down and goes slick. Another reason is they will eventually fail. They're made out of Zinc. While re-attaching the grip to the arm on one of the many TQS' I've had over the years, the grip shattered in my hand. It's time for a new solution. There aren't that many TQS' is the wild anymore and you'll pay out the ass for what is essentially a temporary fix.

Sorry it took so long to get this SS. Every time I'm on I'm flying and end up forgetting lol.

Agreed. Your better bet is Aerotronics in Florida. Even then you're looking at between $4,000-$10,000.

Sounds like Foxy software without the programming language..... I LIKE IT!

The only issue I have is the Trim hat input being too much. Nothing drastic though, for the most part it flies like I'm used to on another sim. At least with regards to trimming it. I drive the Viper like I stole it and she never complains for the most part.

In this situation it would be a toss up for me. Get a new HMD like the S or the 2080Ti? In the end I would choose the 2080Ti simply to get it out of the way and be ready for the next gen of VR headsets. It's expensive as hell but you WILL need it in the future.

Excellent temporary fix!

Afterburner response is off. I posted a description of the changes made to the F-16C Block 50 written by Lockheed Martin. It states that the Block 50 CJ should go from idle to full AB in 2 seconds. Not seeing that at all but hopefully we will as it's fleshed out.

Flying the Hornet will make you a better overall pilot as you have a lot more work to do when taking off, landing and flying in general. That's not a criticism at all, it's just the nature of its digital flight control system. It's nowhere near as synthetic as the Viper. If you're really good at flying the Hornet, you can make the Viper your bitch ������ I have the Hornet, Tomcat, Mirage, Mig21, F-86, L39, A10C, AV8B and FC3. Since release, I only fly the Viper and I fly almost exclusively online. The others were placeholders until it came out. I've flown it on another sim for 20 years and I know it inside out, backwards and forwards. Therefore I don't run the risk of negative training. What I've done is fly it like an A model.except it has 120's and CBU97's. So which one should you fly? Whichever you enjoy more of course lol. As to the drag model and overall PFM, sadly it's a work in progress and it is what it is. I also agree with you on roll rate. The Mirage roll rate makes the Viper seem to roll like a Cessna. I set my roll curve to -18.

You can run the Index on a 1080Ti provided you have I would say a minimum of 4.9Ghz processor. It takes a LOT of power to run at decent frame rates and look good. Overall even if I could use the Reverb I'd choose the Index. I also have a budget that allows me to buy the fastest hardware. If you can afford the upgrades it's worth it. Right now, the only module where I'm not happy with it is the Viper. Every other module looks beautiful so hopefully as the Viper progresses they'll fix the aliasing and optimization. Lastly, I think you would be happy with the Reverb and it will easily run on a 1080Ti. My buddies run there's on regular 8Gb 1080's.

It's the best for me. My IPD is 58 which excludes the S and Reverb. I've tried both and I was not impressed with the S other than to say it's much clearer than the CV1. I started with the CV1 and love the catchers mask style mounting. The S uses the Halo style mount which tends to not sit flush on my face. The CV1 had excellent speakers, the S speakers are crap. It does have a jack for a headset or use one connected to your computer. The problem is, it's awkward with the Halo. However, for $400 out the door, if you can wear it, it's got good visuals and Oculus software. The Reverb has the clearest image of all. It also has the narrowest FOV and a big heavy cable that's awkward. It has a higher resolution (pixel count) than the others and doesn't need a lot if any super sampling to look great. However my experience with it lasted until I realized the IPD would only go to 59 which left me crosseyed. I'll defer to Imaken for a more thorough review of it but he sent it back and kept the Index. I don't even want to discuss the Pimax. I've seen many posts from those that love it. For the life of me I can't understand why. The drivers absolutely suck. It IS cool to fly at 120 degrees field of view but it's a stuttering jaggy mess the whole time. I thought I was having problems with the Index overheating and sent it back for another. When that one arrived, my picture quality was shit and so was performance. I originally thought it might have been DCS but on further inspection, my motherboard was going bad. With that said, the Index is the only choice for me but not just for the IPD setting. It's a high quality piece of kit that makes all the others seem like toys and with the right settings looks amazing. It's expensive though. I could not check six with one base station so I bought another which puts it at $800 for the setup. I have no need for controllers. That isn't the only cost though. Unless you have the fastest processor and a 2080Ti, you should upgrade. The Index uses a lot of super sampling to look really good and that takes clock speed in DCS. Others get by with slower systems by lowering settings but I won't lol.

Tracers definitely help but if your pulling G's and the target is rolling it's a bitch. You're best bet is to have patience and close on the target, dump your G load and shoot. When I say close on the target, I mean to a distance where the target fills at least a quarter of the HUD. Any time you reload with ground crew, choose the top option for gun rounds. HEI with tracers I believe.

Do you know if it's modeled that way in the software? Typically an input like a joystick will have a delay set for the buttons. This is if they're to have not only a momentary push button but a press and hold feature. In this instance it's an easy fix of adjusting the delay. If the sim is modelling the actual electromechanical functions of the trim system in the Viper, that's gonna be a bitch to find and fix..

That's odd it didn't take much trimming. While the Viper is full on FBW, it isn't that good! Lol. You should have had to trim an equal amount of deflection as the stick was on take off. It can trim that much but not on its own. I've not seen the FBW system help that much before.

Next time you trim, watch the trim wheel on the back of the left console and see how many clicks it's moving when you press the trim hat. If everyone does this we can confirm it's and input delay problem and an easy fix.

I've run into this more recently. When trying to trim the jet say after firing a heater, it is very difficult to get the trim wheel to move one click when clicking the hat. Regardless of direction. I've watched the wheel which is on the left console at the aft section while clicking the hat switch and it's almost acting like an axis instead of a switch. The wheel will move multiple clicks for what feels like a very short press of the trim hat. I think it needs a longer delay programmed in to the binding. In other words I should have to hold the trim hat in position for a longer period of time (measured in milliseconds so not really a long time) before the button press is activated again. It should be a pretty simple fix of adjusting the delay. If it's in a LUA file we can probably adjust it ourselves. As to trimming the Viper in general, it only takes a lot if its unbalanced by armament, damage or tanks. This applies to both real world and the behavior I've experienced in the module. If balanced out you will rarely need to trim. That said, when I do trim, I usually over trim on accident because of the above behavior.

If you fly the refuel mission in instant action I'd say it's fairly close. At least in the Index for me. I'm just happy there is zero frame drop when doing it!

Dig-key.com or Mouser. If it's made they have it.

I set the negative LOD for both options at -1.375. I did notice sharpening and so far no extra shimmering. As far as the rest of the settings, it's pretty vanilla but I'll post a SS tomorrow.