[DE] T-Bone

You're not doing anything wrong, it's a known bug.

Please try the following procedure: Pedals: Remove the centering spring from the pedals Install the damper Flight: Special Options: Pedals without springs In straight and level flight, hold the FTR (Force Trim Release) button Use the pedals to bring the helicopter into aerodynamic trim Release the FTR button and leave the pedals in their current position Check if the yaw neutral point matches the current pedal position In a helicopter, your pedals are "almost always" in an asymmetric position depending on flight condition and trim. Watch this video series to understand how the trim works in the AH.

It "could" get better for you, you just have to try it out and decide for yourself. For me, a damper brought more control, but that’s just my subjective opinion.

I would say so, because with the damping forces you can control things more precisely. At least, that’s my personal experience with my damped pedals...

Regardless of the fact that the yaw channel is currently oscillating a lot, I recommend keeping the speed above 40 knots on the targ tapproach. In practice, I have achieved good results at 50-60 knots. Without heading hold sub-mode, the reticle can be aligned cleanly to the target with gentle pedal inputs without the system trying to push the aircraft into a different heading.

Who knows how it happened? The important thing is that the issue is being addressed now.

Swap McDonals for Fritzlarer Dombräu brewery pub... it's worth it

Changes to the FM take time and are not easy to make. Furthermore, it has already been said that the point has been taken up, discussed and placed internally.

This should be considered an improvement or update rather than a direct bug: The St. Peter’s Cathedral (Dom St. Petri) in Fritzlar features two towers and is located further up the slope compared to the version currently placed in the DCS map. It is clearly visible from the airfield to the south and represents the town’s most prominent landmark, a true must-have for accurate representation.

I can confirm that there is an issue with POINT-XMIT. FARM messages, PP, and BDA are working correctly. However, as soon as an attempt is made to transmit a target point via POINT, an error message appears. ah64_datalink_test_heli2.trk ah64_datalink_test_heli1.trk

One of my wishes would be to expand the Dolan Barracks (AAF) in Schwäbisch Hall. The site is located about 70 km northeast of Stuttgart, in the middle of a very beautiful town and a charming surrounding area. Until 1992, the A/5-159 (formerly 180th Company, Chinooks) and the 203rd Aviation Company with Black Hawks were stationed here. Even today, the airfield is regularly visited by various aircraft, for example from Katterbach. If aerial photographs or documents are required, I will be happy to provide them. https://www.erwinschumacher.de/dolanbarracks.htm

Aktuell zu Verkaufen: Saitek Rudder Pedals

FFB VPforce Rhino

Problem is known and can currently only be solved by hot start.

I cannot confirm this after the current patch. It is still very unstable in the yaw channel and the error pattern is still there. As long as there is nothing in the patch notes, I think the impression is rather subjective.

No changes were listed in the patch notes. What exactly is supposed to be more stable?

+1

Thanks for the tip about pressing the FTR for a long time. This has weakened the oscillation somewhat, but it is still present. In the attached tracks I was still able to reproduce the described oscillation behavior with long press FTR - both in hovering flight and in forward flight at low speed. Yaw channel: You can clearly see that the yaw channel takes over the new zero position for a brief moment and damps it slightly, but then starts to oscillate left/right and only then levels off again. ATT hold: I was also able to reproduce the forward and backward pitching of the ATT hold, even though the helicopter was well trimmed when the mode was activated and no control inputs were made. The behavior no longer occurred until the helicopter was aligned again using FTR. This phenomenon occurs for the first time when using the mode and then only very rarely during flight. The yaw channel shows a control problem, as it swings up after a short damping. The ATT hold mode occasionally exhibits faulty behavior, especially when first activated. Deactivating the position hold has already brought a significant improvement, which must be mentioned positively . However, there is still a need for optimization, but that has already been communicated by you. pitch_oszilate_ATT-Hold.trk yaw_oszilate_10-30kt.trk yaw_oszilate_hover-heading.trk

Would be nice to see some pictures of Fritzlar

I think this will be exactly what you are looking for: GitHub - Special-K-s-Flightsim-Bots/DCSServerBot: Manage your DCS World servers with lots of extensions and possibilities (with Discord integration)

A reproducible oscillation is noticeable in the yaw axis, which was previously absent or only slightly pronounced. Even in ATT hold in hovering flight, there is occasionally a deflection in the pitch axis despite good trim. However, this phenomenon only occurs very sporadically and is not always reproducible by me. Tracks attached. yaw_ATT_oszilate_2_20250324.trk yaw_oszilate_1_20250324.trk

Hi, switch the ACQ to TADS and the IHADSS will show you where George is looking with the sensor, see picture. You should see the distance to the target via the IHADSS directly or TADS video. Alternatively, you can also create a WP/TG on the TSD where George is aiming and then select it via ROUTE-DIR, then you will also have the distance in the sighting system. Try this out. See here for a detailed explanation:

Thanks for your detailed explanation and the examples, I think I'll have to live with it. Unfortunately it is a very unsatisfactory picture with MSAA and TAA+FSR is not an option with the excessive ghosting. I hope that the implementation of Vulkan and hopefully the newer FSR versions that will follow will help, otherwise it is very unsatisfactory as an AMD user.

APKWS will not be available with our model

The following was done: Delete metashader and fxo folder -> No improvement Reset to factory settings -> No improvement Uninstall the driver with DDU + reinstall -> No improvement It is still a very angular image at the edges with msaa, as described by other users. See pictures. I have the impression that there is almost no difference between MSAA Off, 2x and 4x. Also, it looks like certain angles are not being processed properly as some spots look fine. Something is not right here.