av8orDave

I'd say it depends on what exactly you'd like to do with DCS. If you're planning on flying simple, single player missions, like shooting case I approaches on the supercarrier, for example, you can get by on many modern CPUs with acceptable performance, heck maybe even a rock-steady 72 fps. If you plan to fly complex missions in DCS Liberation, Retribution, or Multiplayer, the world's most powerful supercomputer won't provide smooth framerates in VR.

I'm sure there is a healthy amount of user-error involved here, but here is what I am trying to figure out: - I have multiple JDAMs on the jet, as well as an ATFLIR pod - I put all JDAMs in TOO mode and wait for them to align - I use WPDSG to slew the ATFLIR to the first target which is pretty much aligned with waypoint 5 in this instance, then sweeten the solution by slewing the pod over the target and designate - I drop successfully on that target - I try to slew to the next waypoint, in this case waypoint 6, and the pod still goes to waypoint 5. I even use the undesignate/NWS button to undesignate the first target, then try to use WPDSG to slew to waypoint 6, but it still slews to waypoint 5. What am I doing wrong? THANKS!

I'll have to see what kind of results I get on VD with no AA. Might be worth a try as I've never really considered it. Thanks for the suggestion!

A couple comments and a couple questions: Questions: Are you using both Oculus Debug Tool and Oculus Tray Tool? You should only use one. I'd recommend Debug Tool. Is your DCS pixel density set to 1.0 (in the VR options in game)? Comments: DCS badly needs optimization and particularly in complex missions, you'll never see great performance, even with a robust system. I have a 7950x, 4090, and 64GB DDR5 and am usually pretty happy when I am getting a consistent 72 fps. The current update, even with settings turned kind of low, features a widely-reported small "micro-stutter" that seems to be impossible to tune-out of the picture, so no need driving yourself nuts looking for the perfect settings. Regarding ghosting, I'd suggest turning the pixel density to 1.0 in the Oculus software, leave DCS pixel density at 1.0, but try turning the Oculus Debug Tool pixels per display override to 1.8 or 2.0. I run DLSS, which has a small amount of ghosting, but better than the performance I get out of MSAA or no anti-aliasing settings. I often run complex DCS Retribution missions, so I need DLSS turned on or the performance sucks. You may not need this. I'd also leave the refresh rate at 72 hz. Your DCS Settings look fine. You may think about turning visibility range down to medium, and maybe shadows up to high (I like the higher fidelity of the "high" shadows). You might consider turning Grass/Clutter to "0" as it looks kind of rough and hits performance, and isn't really visible from the air, where you'll spend 99% of your time. You might also consider turning the LOD switch factor to 0.5, as it gives a performance bump. All of that to say getting rid of ghosting in DCS's current state is pretty difficult, even with a nice system. Your best bet is figuring out the right combination of anti-aliasing, upscaling (DLSS), and pixel density to give the best appearance / performance tradeoff. Don't be afraid to experiment. Edit: One more suggestion: you might consider giving Virtual Desktop a try. It has some benefits over the Meta software, is wireless, and gives pretty good performance.

I have that system, and that much beef doesn’t resolve it. Badly in need of “optimization.”

Yes. Here's the layout: Modem (or router) LAN to dedicated router WAN (ethernet). Router LAN to computer ethernet port. Headset wirelessly connects to network from dedicated router.

Any other virtual desktop users getting a wicked micro-stutter since the last DCS update? I’ve always been very pleased with the “smooth” experience provided by virtual desktop, but man, it’s really stuttery at the moment. I don’t seem to get the same problem with the link cable right now. I’m using a Quest 3 with the latest nvidia drivers. I also tried rolling the drivers back to 552.44 to no avail. Has anyone tried rolling DCS back to 2.9.5? Did that work? System specs: Ryzen 7950x, 4090, 64G DDR5

This has been an issue for a bit. Ever since it started rendering the carrier in the background of the menu, the performance has been horrendous. My solution has been to not use the Supercarrier theme as my menu background.

Yeah, I think I agree that VD is the way to go. I hate having to play over wifi and really wish there was a wired-option, but I think it is preferrable to the Meta Link software.

What it sounds like you are describing is why I stopped using the original Pimax Crystal. My experience with the headset was that the "sweet spot" in the middle of the screen was so small it was practically useless. Any slight mispositioning of the headset, or glance with your eyes to the right or left, and you'd get a ton of "distortion." I also never solved the pretty significant "fish-eye" effect of the lenses. Sure, it has a sharp image in the middle, assuming you can get it perfectly aligned on your head, don't move too much, and are ok with the fish-eye / barrel effect.

Are you using the new launcher? I only ask because the launcher automatically sets "Easy Communications" to on even if you uncheck it. If you uncheck it and start the game without using the launcher, it sticks. Just FYI.

I agree with the OP. I fly in VR and I have the HMD set to render in only the right eye. Having said that, the targeting cross is rendered to the left-side of the lens, meaning you need to look out the side of your left eye to align it to your target. Doesn't seem quite right.

I'm enjoying the book. Thanks for the recommendation!

I'm still getting crashes, for what it is worth. Flew a mission in the PG map. Fired up the TPOD, selected LMAV, armed the laser, then used WPNDESG on the HSI to slew to the waypoint. As soon as I clicked WPNDESG, I got a crash to desktop. Annoying. Edit: I was dumb enough to try again. This time I didn't arm the TPOD laser until after I slewed the TPOD to the target using the "WPNDESG" button on the HSI, since that is where it crashed before. The TPOD slewed to the target successfully. I sweetened the TPOD lock with the TDC, redesignated, then clicked the switch to arm the laser... and as soon as I did, it crashed to desktop. Whatever the "fix" was in the hotfix didn't "fix" the problem.

Sorry to be blunt, kind of frustrating. The only real selling point of the new launcher as best I can tell is that it is a quality of life improvement for VR users (I am one), but it is mega-frustrating to have to disable easy comms every time you boot the game. I had hoped based on the numerous bug reports about this that it would be fixed for the hotfix... apparently unfixed, however.

Well said. I agree.

I know you said that landing on the carrier is a separate issue, but i'm gonna drag the conversation there anyway. Both aircraft are easy to fly, and both have relatively easy systems to manage. The F/A-18 has more weapon types in it's arsenal, so there is a bit more to learn. The F-16 has the HARM Targeting Sensor, which is one unique system, but really both aircraft are pretty straightforward / easy to learn. The difference between these two aircraft is that one is carrier-capable, the other is not. Learning to launch & recover is really very gratifying. Mastering a proper CASE 1 and CASE 3 approach is basically a whole world in itself, so whether you want to do this probably ought to dictate which one is the appropriate module to try to learn.

Now, this is thinking in four dimensions. Why did I never think of this?

I agree. Nothing is more immersion-breaking than moving your arm and seeing one visualized on the screen remain static. Or looking down at your legs, which are occupying the wrong position in space compared to your real legs. Yuck.

For those of you who fly with the pilot body visible in VR, how do you use the stuff on the side panels or anything obscured by the pilot body? Do you have the “hide” key mapped to your HOTAS?

Cool idea, I second it. Might be cool to include modules I don’t own as well, to inspire future purchases.

Perfect! Thank you for the response. Count me in for early access.

I was wondering if it was just me. Seems like a "fix" would entail the radar working without me messing with my system date (and then correcting whatever havoc that might create).

A few things here: First, ED called it "force trim" themselves, so if anyone is creating confusion, it might be ED? Exact verbiage from the newsletter was: "After Early Access Launch Features DAFCS trim system and force trim." Second, a few people have requested clarity on what trim function exactly will be included in Early Access, but no moderator or official source has responded yet. Doesn't exactly instill confidence.

Thanks for the response. For those of us considering pre-purchase, can you elaborate on what “basic trim” entails and whether force trim in the traditional sense is what will actually be missing at initial release?