[DE] T-Bone

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.

Thanks for your feedback and tips, I have already implemented some of the points. I will reply in more detail tonight about what has been done so far.

I myself have recently become the owner of a 7900 XTX and also have the problem with MSAA. The picture was much better before with a 2070 S than now with MSAA.... FSR is not an alternative due to ghosting... @Flappie You were involved in the topic here and gave good tips. Unfortunately, driver reset and reinstallation did not help at all. Has ED addressed the issue or not? Do you need more data?

@Lord Vader I kindly ask if these two threads can be merged, and if one of you could perhaps ask internally how far the topics MPSM and rocket zones are. Thanks

Then it is all the more impressive what Apache's systems are capable of in terms of performance. If you both confirm this as you have described it, then I will accept it and deal with it accordingly. As I mentioned above, some positive improvements are noticeable. However, my impression is still based on a personal, summarized assessment based on experience in DCS, other professional simulators and input from pilots in your field. If the flight model is indeed as you have described, this is sufficient clarification for me. Thank you very much for your answers and detailed explanations - I really appreciate it.

I completely agree with you on this point: The system should enable an appropriate response and respond precisely to control impulses. However, I am of the opinion that the CAS should not work as linearly as it is currently represented in DCS. Especially in relation to the high weight of the aircraft, the movement does not appear to be represented correctly. This is particularly noticeable in hovering flight, where the exaggerated reaction of the system is unrealistically pronounced and the actual inertia of a heavy mass is not sufficiently simulated.

It's great that there have been noticeable improvements in some areas. In particular, the behavior during taxiing has improved significantly, and the overall behavior during flight is also more pleasant. However, there are still critical points, particularly with regard to the flight model (FM). This currently conveys too much of an arcade-like impression. The transitions between inputs and reactions are too fast and lack the feeling of mass and inertia. For example: Flight behavior in turns: When initiating a turn, the aircraft descends immediately instead of gradually, which impairs the physical credibility. Pitch reaction: When pulling the pitch, the variometer reacts immediately and without delay, which seems unrealistic. Hover behavior: The control inputs from the Cyclic are implemented directly without delay instead of showing a certain inertia. Overall, the Apache does not feel like a heavy helicopter, but rather like an element from other, less simulation-oriented games.

Unfortunately, the question has not been answered for six months. After all, the variable zones for rockets are a core feature, is this still on the development list or not?

You can try deleting the controls.lua and reassigning it. Off the top of my head it should be in a folder like this: c/users/name/saved games/DCS openbeta/input/...

Dann bestelle dir lieber den ffb Rhino von vpforce für etwas Grundsolides. MOZA hat die telemFFB Software wohl kopiert und mehr schlecht als recht implementiert bzw. versteht teilweise nicht, was der code macht...

Du wolltest doch eine 10cm Verlängerung haben, richtig? Ich denke TOniMOntana meint diese hier, habe sie ebenfalls im Einsatz und bin absolut zufrieden: Joystick Extension for Thrustmaster and Virpil (VPC) [TMVPCStickExt] : QR4rigs, Quick Release Mounts for Sim Rigs, Change your rig in seconds, spend more time in the game! Ist bei mir schon zu lange her als ich bei Q4rigs bestellte, informiere dich hier über die Kosten: Zoll online - Internetbestellungen

Schau mal hier deren Produkte durch, denke bei den Virpil-Verlängerungen wirst fündig werden. All Products : QR4rigs, Quick Release Mounts for Sim Rigs, Change your rig in seconds, spend more time in the game!

Are the cockpit vibrations set too low in the special settings by any chance? Worth a try...

Thank you very much for this great explanation!

Negative, in the apache the raindrops are wiped away... Anyway, offtopic, apparently the windscreen wipers are still wip in the Chinook.