Wicked.-

I agree the new AMD chips are powerhouses for multi-core, multi-thread applications and programs. What was suggested originally (when discussing best upgrade for FPS in DCS VR) is that AMD is the better chip for DCS. Disregarding all software other than DCS and focusing only on VR FPS in DCS, which is better? Intel or AMD?

Where are the benchmarks for DCS? Has anyone posted them or started a thread I can go look at and compare? Thanks

I switched to the beta and along with no longer needing controllers to operate the camera or overlay, the image seems clearer with my same setting and no stuttering.... yet

Supmua answered on another post but look outside the overlay when pressing the button. It works.

It's working for me. Once I looked outside the overlay. I was able to start programs on my desktop while looking through the camera. Saved me $300! Very happy!

This problem with locking targets seems to be getting worse. I'm not new at the 18 and have flown at least 100 hours in it almost all online. Tonight on our squad server, I'm hot on a 29 at 15 miles, he's hot, PRF set to INT, angels known and dialed in. I can see his D/L contact in red but the radar will not resolve it. I keep locking the trailer. over and over this is happening. If he hostile was notching I can understand but even then in INT, at some point when it scans medium PRF it should lock it up. I really only fly online unless I'm testing VR settings. Could it be a data connection issue or are others having issues in single player as well?

I purchased the FSSB3 Lightning with the angle adapter. I bought the F-16 locking collar and DMS switch from Shapeways. I'll see how those work out and whether or not I get the F16GSRH before getting the neck piece.

Lol yep, it shipped 10 hours ago.

I decided to try the new beta. I like it. I didn't change any other settings though. Still at 148 custom res and 138 DCS SS. Everything looks cleaner and that was flying online on my Wing's server. No stutters at all.

It was mounted on a stand behind and above my computer screen. Even with two, the way my rig is set up makes me keep them in a narrow angle and I still have problems if I turn around an lean out a bit. Honeslty my Oculus sensors are better at keeping track in the same area. It's the only part of the Index I'm not really impressed with; especially considering the cost.

Well.... shit. I guess I'll place an order lol. Question. How well does the Warthog hold up when used with the FSSB's? I'm worried it's going to break. Luckily I have two but I'd rather have the other as a backup and use it for center stick flying. I know several people who would by a TQS regardless of price. Me being one of them. I have 1 fully functioning TQS with TUSBA and two others for parts because they don't last. I think I've had 6 cougars since 2001.

I have the Index and after making some cockpit camera adjustments/up, down, left, right positioning in the jet and getting a good IPD number in DCS VR settings (58) I can see the MPCD and read the CAS and ground speed numbers at a glance. I can also read the top row of numbers as well; clearly. The DDI's are crystal clear as well. That said I'm pretty sure that in the Reverb sweet spot it's probably clearer and takes less power to run as it doesn't need the SS scaling having a higher overall resolution. Still, I'm happy with the Index and should be for quite some time.

I ordered mine with the angle adapter today. Any idea how long they take to ship? I remember it being like 3 weeks for my TUSBA.

I ordered the FSSB3 Lightning today and would have ordered the F16GSRH but I've received no response from them about availability. It says out of stock but also says new orders by purchase order? Does that mean they build to order? The forum was no help either. Do you guys have an idea of availability?

I thought I saw something come out yesterday but it wasn't for the stable version which I'm now using. Anything new in the new one worth testing????? Inquiring minds want to know lol.

I went with the Index as my IPD is 58 and needed mechanical adjustment. Couldn't be happier. As stated above the Index has better resolution and is VERY well made and thought out.

If anyone is interested I'm selling my touchscreens. I have a Dell 21.5" and an Acer 27". If interested I'll post actual model numbers. Both are in excellent shape with no dead pixels and would come with an articulating desk mounted arm.

They are.

I get both but I'll get a square on a hostile instead of a diamond until the radar has a confirmed lock. Only then will it go to a diamond. I don't have this problem inside of 10NM using boresight. I would really like having the vertical scan in ACM mode work as well.

I don't expect to see 60-90 FPS on my Index but I never did. Having had the CV1 first I am totally happy with 45 FPS. At that frame rate everything is super smooth and there are no distracting hiccups or screen tearing killing immersion. When I've set the Index to 120hz or 80hz it always falls back to 40 and seems to fall below 40 more easily than when I have it set to 90 and it falls back to 45 FPS. No idea why but my Index likes 90Hz. Honestly, I'd sacrifice FPS above 45 for clarity. This isn't a monitor, I'm in the jet, totally immersed and surrounded by the jet. As long as it's a smooth ride I could care less about the specifics.

I've flown about 16 or more hours with the latest stable and probably won't go back to the beta unless I hear of dramatic changes to clarity. I can see everything with smooth framerates unless on a heavily populated server. Even then, once I'm off the ground I'm still mostly maintaining 45FPS. While I'm all for helping with making SteamVR better, if it ain't broke, don't fix it lol.

Awesome. Thanks for the confirmation!

I think I answered my own question but will leave the thread up for comment. When I have IFF and Data Link enabled, AWACS and I assume, friendly units with data link are sending me contacts. Originally the D/L contacts were on the SA page but now they are also on the radar screen. Typically if I roll my cursor over the D/L linked contact on radar I can't lock it because I don't have the radar scanning the right altitude. So using the above method to get the right altitude I try and lock the target but it goes to another target not in the brackets. However, if I wait a second or more I see the altitude pop up on the right of the bracketed contact. At this point, if I lock the target it's almost always right. If I lock early I'm guessing the radar has not swept enough to resolve the contact and instead auto locks whatever contact it does see. This became an issue after flying online with EWRS enabled for several months. Without it, I found I was always looking for the altitude to scan. Using the SA page to get altitude then switch back to radar is very quick but you still have to wait for the radar to resolve the target before locking.

I agree it's a losing battle with the current software but I can't say I've seen DCS benchmarks where AMD performs better than an intel chip; whether i7 or i9. Granted, I'm basing that on what I read here on the forums and the PC specs I see in people's signatures. Is this a new reality that AMD is the way to go? I ask because I'm not opposed to switching as I'm married to neither brand. But, I'd rather not have the same let down as when upgrading from a 1080Ti to a 2080Ti.

Over the last couple weeks I've noticed that when I lock an air to air target it will jump to another target outside the cursors instead of the one they're on. This has happened multiple times recently for no reason. My process for locking a target begins with pointing in their direction, when available getting a bogie dope mainly for altitude but to confirm bearing/aspect as well. If I'm on a server and comms are flooded I'll make the SA page SOI, slide my cursor over the D/L provided contact and get altitude. After which I switch back to radar adjust antenna elevation and TDC depress to lock. For whatever reason, many times it locks a completely different target and most times a friendly one. The only thing I can see causing this is bad D/L data showing the contacts bullseye position. However I'm sure if I just used AWACS BRAA calls to find them on radar without using the SA page to get there more quickly it would put me in the right spot. Is it possible my bullseye setting is off? This has only started happening recently and I've been flying the 18 since it was released. With the Viper to be released soon I've begun using my bullseye in the jet, whereas I didn't before. Anyone else having this issue?