fausete

We think this issue is now fixed internally.

Hello @TLTeo,
This is known, the radar is still heavily WIP, and this will be fixed when the radar is completed. Thanks for taking the time to create a clear and straightforward report with a TRK tho.

Hello. The real F1 was quite sensitive to this kind of oscillatory behaviour induced by the pilot on the pedals on take off, with future pilots being trained on how to avoid it. Nevertheless we will review the intensity at some point down the line. If you find it too uncomfortable, using curves will probably help.

Hi @Bestandskraft, good catch. Some sort of argument mixup problem happened at some point in the past months. We realised some weeks ago and it's fixed internally, so it will be available to you in the next OB.

Hi @jaguara5, we'll take a look at it but if it's not in-game already we think other weapons will have priority over it. Thanks for suggesting it anyway!

Correct, only with radar missiles and R530IR (if there's a radar lock).

@Thinder my role here is not to moderate discussions but I would appreciate if you were more polite when addressing @Bremspropeller.
@Istar_Eldritch from what you describe, the problem seems to be that vJoy is tripping the automatic FFB stick detection. I have no experience with this software but, if it has an option menu, can you check if there is an option related to FFB? Otherwise, if you don't want to uninstall the software, in the DCS MISC. Option menu, try unchecking the Force Feedback checkbox. If it still doesn't work correctly, please report back and we will see if there's something we can do about it.

Hello,
This is a known bug introduced in the last update. We have an internal fix for it that will be made available in the next update. In the meantime, turning off and on again the yaw damper (3 position switch in the front left panel, close to the gear lever) ends the oscillation events. Sorry for the inconvenience.

Fixed internally

Hello, it's been fixed internally.

Hello! The radar is probably the most WIP item in the plane. Reports from our SMEs (both pilots and technicians) indicate that the noise levels should indeed be generally lower, so we are aware of it. Thanks a lot for the report and the video tho.

It's fixed internally, thanks for reporting!

Hi @firefox121. So, both in pitch and roll, you can use the sliders to select the minimum (centered) and maximum (full displacement) strengths you want to experience in your FFB.
Additionally, the pitch chain has a component called ARTHUR, which (in automatic mode) adapts the stiffness of the flight stick as a function of flight conditions (altitude and Mach), there's another option that allows you to regulate the difference between maximum and minimum ARTHUR values. I recommend that you play with the GRAND and PETIT ARTHUR options in the ARTHUR switch in the front left panel to see what adjustment suits you best.

Hi,
First of all sorry if it was not too clear, we try to maintain a balance between length and clarity and we've been working on improving the wording, I'll pay more attention to it in the next update.
So the control surface test is basically a test that pilots performed after a certain number of flights to check the electro-hydraulic flight control system, the autopilot and the automatic flaps/slats were working correctly. Basically, you deploy combat flaps, and then flip on the test switch (which is under guard in the rear left panel of the cockpit). Then a counter starts (each number corresponds to a specific failure), if the counter stops at any number, you have to write it down to know what is failing and press the button in the test panel (except at 35 and 40, in which you have to connect the AP and the ALT mode respectively). If you reach the number 88, everything is working fine. You also have to check if the flaps/slats retract.
Missile masking is a situation in which the aircraft body (either fuselage or wings) is blocking the line of sight between missile and target. When that happens the amber 'locked' light of the corresponding missile flashes and launch is not possible. Harmonization time is the time that the radar missile seeker takes to syntonise the right frequency for a radar lock, you can think about it as the time it takes for the missile to lock the target, it is a few seconds. Both of these features can be dissabled in the mission editor for a more 'gamefied' experience.
The automatic launch is controlled by a switch in the armament panel. Basically, when that option is selected, a radar missile will be launched as soon as the target is locked and the aircraft is within range. Yes, as dangerous as it sounds.
The Magic/SW on switch is also located in the armament panel and it energises the seeker head cooling and the gyroscopes of the wingtip missiles.

Hi guys,
If I'm not mistaken this is not an issue. There's a chance that the initial position might still be correct, or even that the error will be smaller than the accuracy of the INS.
Then that is compounded with how the RNG works. Basically it will always use the same seed unless you close the game and open it again.

Hello,
You should worry about it, as it might lead to failures if it's on for a long time. In auto mode it usually works very well, have you made sure that the AUTO/MANUEL switch is on AUTO? On the other hand, if you're flying the EE I've just noticed that the HOT/COLD argument is inverted (which will be fixed), maybe that is contributing to the issue you are describing.
If none of this helps, please provide a track so we can check what is going on. Thank you.

Hi, this was fixed internally a while ago and will be available in the next update!

Hi! It's fixed and overhauled internally, will be available with the next OB patch.

Hi! ALCM works with the previous memorised heading, if it was not right (say if Enigma is not using the 'INS always right at start option' or the aircraft was moved with the INS not in NAV mode) then the end result won't be right. In any case, there's some issues in the alignment we're ironing out.

Fixed internally, thanks for reporting!

Hi, thanks for reporting! We caught it a bit too late but it's already fixed and will be in the next update.

Hi!
So the alignment starts when you press the asterisc button and takes the coordinates that are being shown in the screen of the INS as initial coordinates. So if your starting coordinates are correct, just press asterisc while in PP display mode.
If they are not, you will have to introduce them into a waypoint in the list, have the display option POS selected and the waypoint with the correct starting position being displayed when pressing the asterisc to start the alignment.

Hi guys.
We have reworked the pitch control to reduce sensitivity, I think you'll find that curves become much less necessary after the next patch. More than an FM issue it's an issue of how a 'home' control stick that has no trim movement or reaction forces is represented in-game (this is a design choice for the developer).
Regarding lateral stability, at high AoA it's recommended to use the rudder. We've also reworked the NWS controls and the result is a more satisfactory behaviour on the ground now. Keep in mind it will still be quite sensitive, according to how it is in the real aircraft.
Some work on high AoA behaviour will continue to be done after this update.
Also, @chichowalker is a former F1 pilot so he will be able to solve your doubts better.
In general, the next update will change many things and I think you will like the changes.

Added them internally, should be available in the next update.

Hello Jaguara,
Thank you for your feedback, a couple of things to comment.
1. The anticipation does not exist in the Spanish F1s, the paragraph about the anticipation is completely absent from the manuals we use and this has been confirmed by an SME.
2. The test switch does work, but it is too slow. The correction will be available to the public soon.
3. The lighted ranges brightness can indeed be adjusted by the rheostat in the instrument, and the miscellaneous instrument rheostat controls the brightness of the indicator tape, as it should.