fausete

Yes, when you load it, payload weight will be accounted for automatically but fuel tanks need extra internal calculations due to their changing mass. So, in principle, everything should be fine the moment you start the mission even if the fuel tank is not accounted internally but things (both fuel and physics calculations) will become less correct as the simulation progresses.

Hi, @grim_reaper68, The RPL201 would need internal code changes for it to work correctly in a flyable aircraft, as each payload has its own mass, CoG and inertia -and fuel in the case of external tanks- calculations that are run internally. Just adding the payload to the lua won't be enough to make it work correctly. We have an internal task to eventually add the RPL 201 but we have more pressing tasks to complete first. I think I has mentioned it in a previous conversation.

Hi, it's been there since the beginning. It's possible that the recent tweaks to the rolling moment have made it more apparent. It is also represented visually (both permanent and elastic deformation in the wing are) but not too noticeable. Note that it's also possible to jam the slats in a different position, which will also induce some roll. Take into account that the maximum G rating of the F1 is 7,5. PS: In the title you are describing 2 different phenomena than the permanent deformation of the wing. Adverse roll might be experienced at high aoa due to asymmetric stall and at high speeds (above the aircraft limit of 750 KIAS) you might experience it due to wing torsion. Those 2 are completely unrelated with the permanent deformation of the wing.

A pretty significant change regarding the lateral-directional behaviour was implemented in the November OB update, including asymmetric payload behaviour.

Hi guys, ED is implementing a standard way of adjusting GBU laser codes during the mission. We prefer ED's solution (more realistic and standarised) to creating our own kneeboard implementation.

Hi, Just to clarify, the E mode works differently depending on the model of the aircraft. The manuals that are publicly available, such as those of the ED, correspond to a different logic than the models we are simulating.

No problem!

Hi @Caput_58, In both modes the delta height is displayed in thousands of feet. In E (constant elevation angle) mode the number is changing as the strobe is moved along the vertical axis because the antenna elevation angle is kept constant. In D (constant height difference) mode the antenna elevation is changing as the strobe moves. And as the delta elevation is displayed, it is still a constant value.

It's fixed internally, thanks for the report!

Fixed internally

Can you post a track in the Caucasus map, please?

Amazing!

It's also worth noting that the aircraft has to be stopped, have the canopy open and the engine off.

Thanks! We'll try to identify it and reproduce the causes

It was identified before release but unfortunately after the commit deadline. The fix will be in the next update, thanks for the kind words btw.

Hello, this bug seems to be difficult to reproduce. Can you please attach a TRK (in SP in the Caucasus)?

Okay, thank you! Fixed internally now.

Okay, the problem is that the aoa value sent to the slats/flaps was the raw one instead of the corrected one. Now the corrected is sent, but keep in mind that the value won't always coincide 100% with the one given by DCS.

I'm unable to reproduce. Can you provide a trk recorded in the Caucasus in SP?

Hi, we can't reproduce the issue. Can you provide a TRK?

Fixed but I don't think it will make it to the November OB.

It seems there was a problem in which the speed for max dynamic pressure was being used for the whole range. I'm working on correcting it.

Hello, is this in SP or MP? Can you attach a track?

After changes to the 3D model, we're not able to reproduce this bug. The fix should be available in the next OB update.

We will investigate, I think a user had a similar problem in the past and managed to solve it changed the config of a the software/hardware that was causing the issue. If you don't manage just tell me and we'll try to include an 'Always deactivate FFB' option in the Special Options menu.