fausete

Thanks! We try to do our best

Hi, our SMEs have responded. Apparently there is a little mistake in our implementation, as the wingtip missile jettison was not protected by a weight on wheels switch (we will correct this). This means that, IRL, this button was extremely dangerous, as the jettison could be activated on the ground. As a consequence, at least in the SpAF, the button was deactivated very early on and then removed in subsequent versions of the aircraft (EE and M).

Hi @grim_reaper68, You have uncovered a mistake in the external lights logic stemming from a misunderstanding between the flight manuals and our SMEs feedback, as well as slight differences in the Spanish versions. We are working on fixing it.

Hi guys, The logic is not WIP, a refactor was carried out a couple of months ago to prepare the code for the F1M and the F-104, which introduced some bugs (the fix will be available in the next update). Regarding the missiles, launch only occurs when a heat source is present. We will ask our SMEs why the jettison button was removed in the EE.

Hi, thanks for the report. We are checking.

You are right, the M also doesn't have it. From what I've been told, adding an interrogation function to an old radar is not something easy to do.

Fixed internally, will be available in the next OB update.

Hi, thanks for the reports. Will take a look at the second issue, it has probably been introduced recently. Regarding the first, a TRK would certainly help.

Hi @J79, This is a bug introduced in the latest update. It is already fixed internally and will be available to the public in the next update.

Thanks for the report, just fixed it internally. We've made some significant modifications to the armament code to prepare it for the F1M, so some bugs have been introduced (although others have been fixed). We will make sure all the new reported armament bugs are fixed ASAP.

Hi @Mordants, What you are reporting here is related to a core DCS feature, so it has to be reported in the specific DCS bugs forums.

Hi, @AlpineGTA It is fixed internally, we just didn't make it in time for the update. It has not been an easy fix, as this is the first collimator in DCS occluded by cockpit geometry, so it has required a lot of testing and tweaking.

Hi, thanks for the report but it's something we probably can't fix. Can you report it to ED, please?

Yeah, it's a feature, any payload can be ripped by excess of Gs depending on its weight and a small random component.

Yep, that's right. It is the same for all versions (except the M)

Hello @SEEADLER 111, Ripping at 6 Gs seems excessively low so we will tweak it, but take into account that the CLB4 is only rated for 5 Gs.

Yep, correct

Hi, there's not been an OB update since the issue was reported, but it is fixed internally and committed to ED. It will be available to the public in the next update.

Hi! If you can reproduce it in SP (preferably Caucasus), please record a trk.

Yes, that in particular will be checked.

Hi @Scrub, Some minor adjustments might still be done here and there but the FM is much more accurate now than it was before the update, according to both manuals and our SMEs. To clarify, it's still possible to enter a spin, just in more specific conditions, given that the roll instability forces play a larger role now than they did before. This is the condition known as 'self barrel roll' (autotonel, in Spanish), that appear as a consequence of asymmetric stall. In most spin conditions, the aircraft recovers by itself pretty quickly. Carrying a ventral fuel tank makes the aircraft more unstable, due to ventral fin shielding. PS: There are interesting videos in YouTube that show an F1 in a situation of loss of control which can be reproduced almost perfectly with the module.

Hi, It is mentioned in the tooltip in the corresponding option in the Special Menu. Basically the maximum force in pitch is about 20 kg and about 10 kg in roll. The minimum forces are about 2 and 1 kg respectively. So if your stick has a maximum force of 20 kg, you would set the options as follows: Minimum FFB force in pitch: 10 Maximum FFB force in pitch: 100 Minimum FFB force in roll: 5 Maximum FFB force in roll: 50

Hi, Of course there shouldn't be a difference between SP and MP. If it happens again please attach a TRK, it might be useful. A possibility I that could fit what you described is that the rear pilot had accidentally opened the fuel-cut switch (or the front pilot not closed it). Also keep in mind that pressing the starter button for too long might damage the starter.

Hi, this was fixed by ED in May of last year.

Hi, If you hadn't done the rebinding after the BE update then the only possibility is a manual rebind, yes. If you were up to date, this update shouldn't have broken your keybinds. As I said, no major changes on our side so using the previous .cfg should be okay. Regarding the F-104, it is being developed with all the input options accounted for, so there shouldn't be any major remappings needed.