av8orDave

In fairness, the OPs statement and need to publicly announce that he won't be buying the module comes across as a bit arrogant. He could find literally dozens of reviews of the flight model on youtube, reddit, the ED forums, etc, but these reviews, a couple of which are from actual Kiowa aircrew, aren't up to his standard?

Yeah, I totally agree with this. Additionally, in going to monthly updates, we now have to wait until ED sees fit to push out anything that could fix the problem. In my opinion, making changes that break the game in a meaningful way for a large group of users, then expecting that they wait until mid-September for a fix is unreasonable and borders on ridiculous. It is only a video game, I get it, but my guess is that across the aircraft modules, terrains, and campaigns that I own, I'm pushing $1,500 USD spent on software alone, not to mention the state of the art supercomputer I have to have to run the game, the peripherals, etc. Sorry, but it is definitely a major frustration.

Just a thought, but I’m pretty sure artillery is carried utilizing a two-point hook method. The change log specifically says single-point sling loading works.

Was it all tested in the same mission, i.e. with the same weather conditions? DCS helos seem to be very sensitive to any little bit of wind. You can take off with very little pedal input in no wind, but might need a whole foot-full of pedal in a slight breeze. Just a thought.

As the title implies, central position trimming mode doesn’t seem to function properly. It works the same as instant trim. When you press the trim button, the trim immediately takes effect rather than waiting until the stick / pedals are returned to center to take effect.

I think the folder name might be CH-47FBL1... looks like you're missing the "F" in "FBL1". Awesome, I was hoping for this. Thank you!

Take a look in the manual that comes with the module. You'll need to open the folder/docs directory where the module is installed, as the link in this thread is to an old manual (you'd think ED would update the manual posted on their site). Yes, the autopilot ("Bob") works quite well. You engage him, then the cyclic stick controls speed with fore / aft movement of the stick, heading with side to side movement of the stick, and altitude with movement of the collective. I've been very happy with how it works.

Ok, so complaint #1,472,356 about DCS; I downloaded the early access manual on the official ED website yesterday; the post from @BIGNEWY in this very forum links to it. Not a single instruction about how to use "Bob" in that manual. I see @jonsky7 post above showing a screenshot of the Bob instructions and believe, legitimately for about 10 min, that I'm losing my mind. I search the early access guide I downloaded for it. Nothing. I finally realize I need to go in to the folder in the "mods" section of the program directory, and find an updated manual. Ugh. The nice part: Bob does, indeed, work really well right now. I'd love to see the same approach to controlling the AI in the Apache and the Kiowa.

Some very basic things are way problematic with this release, even for an early access state, and it makes me believe something is seriously amiss at Eagle Dynamics.

Gotta admit; it is pretty dang frustrating. Campaigns and modules that we've paid good money for are now barely functional. I'm fully in favor of returning to the Open Beta / Release format if ED is going to use the current setup as a test format where we're supposed to accept ridiculous steps backwards in performance while they figure their stuff out. Ugh.

Looks like Mig Killers didn't make the update? Any idea when it might be released?

Gotta think it is planned as part of the update.

This seems to be the trick. If I’m in track when I undesignate, it redesignates back to the same spot. Thx for the help.

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.

Or, since there’s a business relationship that you’re consumers rely on, sort it out in court.

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.