TZeer

Looking at the leaks so far it brings a complete new gameplay into the DCS World. M4 shooting from inside the chopper, live feed from drone etc.

This is gonna be buy on first day!

@SkYwAlK3R-_ Try this: Shadows: Flat only SSS: Off Visib Range: High Terrain Objects Shadows: Off Shadows can be taxing on your system. Im running an AMD 6900XT overclocked on an AMD 5800X, I have the above settings right now, on top of that I'm running foveated rendering on a pair of Quest Pro. WIth those settings I'm not always able to keep the framerate @ 72FPS even on Nevada.... All depends on how many units need to be rendered in the background.

Looks sick!!

Base for the cyclic? @Jester_74

When you have this performance issue, what is happening with your hardware? Is the GPU maxing out? VRAM? GPU? Is the CPU maxed out on one of the cores?

Just some observations. - You say you don't see any difference if the mirrors are off or on. This seems strange as it's usually a resource intensive thing to have on. Specially in VR. Can suggest you have a bottleneck somewhere that covers whatever performance drop you might get from mirrors on/off. - Some of you settings seems optimistic with the hardware you are running. A few things you can try just to see where the issue is. * Reduce the pixel density inside DCS from 1.4 to 1.0 * Reduce your resolution of cockpit display from 1024 every fram to just 1024 or 512. * Visible Range, reduce to something less. * SSS, Off If you are able, use something like MSI Afterburner and check how you GPU behaves when you fire up the Apache Vs all the other modules that work ok. But just for info, Apache module gives my system a run for it's money as well. Of the modules I have, I think the Apache is the most taxing module to run by far in VR. You can also try this one: Empty VR hangar for less VRAM usage and faster F-10 ingame map. Basically removes the plane and hangar on the menu screen. Saves about 800 MB - 1 GB of VRAM. As it's alway active in the background. Again, how much you save is based upon how high you have your settings. https://www.digitalcombatsimulator.com/en/files/3336353/

C-Scope: As you said, radar icons on IHADSS. LINK: Ability to link TADS to radar. So when you use radar to target, the TADS will automtically slave to the target. ZOOM: Ability to zoom on your radar display. Making it easier to seperate targets close to each other.

Had a test in VR now, and can confirm. There is now stutter with both PNVS and TADS If you are flying in 2D I can understand some poeple don't see it. But in VR with face down in the VR-set and the IHADSS covering large part of the FOV, it's impossible to miss. It's also a very large difference how much it "bothers" people when flying. 40-50 feet above ground and your eyes get tired real quick. It's like flying with the VR-set constantly out of sync. If you are at 400 feet and just flying and looking straight, things moves slowly, and using the nightvision is not as painful. But still get exhausted in the eyes quickly. As it is now, I can't fly at night without seriously getting real uncomfortable in my eyes.

Could someone do a doublecheck? From my point of view it seems the stutter is on the TADS as well now when using it as nightvision. I have only tested on monitor, will do a test in VR later today.

Bump @BIGNEWY Any news regarding this issue? Regards

Nice to see people with the knowledge mentioning this. Always felt the yaw a little bit "funky". But as I'm not a pilot, I would have no idea if it's supposed to be like this. Is this also the reason for the excessive "crabbing" while in aerodynamic trim? @bradmick @schoolio64D

When the "weight on wheels" switch dissengage due to getting light on the wheels, the heading hold mode should go active.

A map I have been looking forward to. Purchased

A lot of good feedback here Will try and put it into practice. My approach to this is usually "slow and smooth" as @Floyd1212 mentioned. And I don't have much trouble with the lift or loosing it as I transition. It's more of the sudden kick/extra input needed on the yaw in the envelope. When I smooth that out, I'm golden

As title says. Does any of you out there have any secrets to share when moving from forward flight to hover? I have noticed there is a very "sudden" change in aerodynamics when moving from forward flight to hover, and I feel the need for input on the yaw changes very abruptly when moving into hover. I have no way of knowing if this is real or not, but I guess it would be normal to a point, as you will need more collective/torque to compensate for lift lost as speed slows down, and will again transfer to more rotational forces on the helicopter. Holding in the FTR works to certain degree, but at some point in the envelope, maybe around 15-30 knots, it seems as someone "pulls a rug" out under you. And the yaw starts kicking out. So far I have moved my pedals in small increments and trimmed as I have moved through the envelope. This way I leave most of the work to the SCAS and only "refreshing" it's trim to keep the YAW from saturating. But I'm dependent on the joystick overview for that method to check that the YAW is not getting close to the saturation level, kinda breaks imersion. I'm using virpil stick, collective and pedals. My pedals are modified with a dampener mod, so no re-center to trim. So in theory I should have everything I place to get this as smooth as possible. I don't have any curves on the collective or pedals. I have no problem in hover. I can sit stable forever if I want to, without engaging Hover Hold sub mode. It's just the transition into hover I'm wondering i'm overlooking something basic. Is it down to me and my lack of skills? Or is it a combination with the unfinished FM?

Yeah, sometimes the FPV is almost gone from my HUD view when trimmed and looking straight ahead. Waaay out to the right....

There is a bug, reported and worked on, on the SCAS for the Yaw- channel. You can easily see this if you pull up the controll indicator (Ctrl + Enter). Have a look at the indicator for the Yaw-channel, and you will see the system is constantly oscillating left/right. It's not much, but it's enough to make the Apache go left/right when trying to fly straight. You also see the FPV move around left/right. If you hold trim, the oscillation stops, release and it will start oscillating shortly after.

Got my tracking now. Will arrive on friday. Live in Norway.

The SCAS is WIP. There is oscillation on the yaw channel. This makes it almost impossible to keep it stable over time. I have reported it, and it's known for the team. I have also noted the excessive "crabbing" behaviour while trying to fly straight. Think the worst episode was looking out through the side glass while in aerodynamic trim , to see where is was going.

You can also check the SHOT list. All targets fired upon with a hellfire (Laser & Radar) will populate that list. Targets identified by the FCR will have type of target in the details, AD, tracked etc. While those shot at with the help of TADS will not, as the FCR has not given any identity to it.

Currently focused on the Apache. But I do have the A-10C, F/A-18C and the Huey. Looking for realism when it comes to the use of airframes and tactics, with a dash of good fun on the side. Primarily a rotorhead, but can be chased into a fixed wing if needed Fly with VR. Have been in a Virtual Squadron before, but that's many years ago now.

Bump

SCAS on the YAW channel has a tendency to start oscillating while flying straight. See attached track. After I take off I fly straight for a while. At some point it starts oscillating. I push and hold the trim reset button and the oscillation stops. When I relase it, it seems fine for a moment. Until I make tiny adjustment on the cyclic and it starts to pick up again. It starts small and escalates. In the end one can see the SCAS is oscillating left/right of the trim reset point in the YAW channel. Only solution to make it stop for now, is either hold the trim reset til everything is stable and don't touch anything after it's released, or engage attitude HOLD mode. Wind is set to 0 knots. AH64D_YAWOscillation.trk

I agree. Such a hightech equipment, and all other kind of systems integrated, but no consideration to the terrain infront of the apache when deciding scanelevation in automatic mode.