fausete

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.

Hi, I experience exactly the same as @Tiromir describes. If I force the FFB option in our internal code, I see the same issue as @Chokaa is describing. So my assesment is the same as it was in the beginning, there is something in your computer that, for whatever reason, DCS detects as a FFB stick. Can you please try going to the Options menu and then to the Misc. submenu and deselect the option called Force Feedback?

Hi, how much RAM do you have available and what graffic settings are you using? One of the crashes seems related to memory when loading the F1 textures and the other to a terrain.

That's weird. Can you run a repair on the install?