fausete

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 @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.

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

Okay, thank you!
Fixed internally now.

Thanks for the compliments and the thorough report. Will share this with the team and we'll try to fix it soon.

Hi,
You'll get the P-3, hopefully in the next 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,
Did the rear pilot select the control of the radar with the appropriate pushbutton (on the left console, besides the throttle)?

Hi, your engine is destroyed. Try to cut the throttle as soon as engine stall signs start to develop. When the symptoms subside, advance the throttle forward and command an engine relight once you are within the allowed zone with the in-flight relight lever below the throttle (not with the usual starter).

Hi @Sknusk,
There is no dedicated intercom button in the BE.

As far as we can tell it's a problem associated with the simplified gear logic. We recommend using the regular logic until the problem is fixed.

Hey Brems!
Feature, the Spanish aircraft (and I think potentially others) use this knob to control the input heading for the CAP mode of the AP. The BIP trim is present in the Spanish F1s too but only to adjust the heading in the base mode of the AP, within a certain range of the initial value and only in 'blipped' inputs.
Cheers

The afterburner throttle position does indeed affect thrust significantly. You can check it on the ground by setting the parking brake. In minimum afterburner, the brake will be able to hold the plane in place but not in maximum afterburner.
The next OB update will include some tweaks to supersonic drag that might affect the situation you describe. Something to consider too is that, in supersonic regimes, thrust will generally always increase with speed.

Hi, this has been discussed in-depth before.
Essentially the current behaviour is approved by SME with thousands of hours in the plane and verifiable by the performance data. Some errors here and there might still be present (and the behaviour at very high AoA and with asymmetric payloads will be reviewed). But, especially for subsonic speeds, we are confident that the model is very accurate.
Some tips/clarifications: the F1 can carry a lot of fuel for its size, so I'd recommend not dogfighting unless you're below half full. It also likes to stay fast. It's possible to outrate other contemporary fighters but only with low fuel and keeping the speed high. Disengaging and extending to search for more favourable fight conditions also works quite well.

Hi, this is up to ED. We have asked for the new ammo types and they are in the process of implementing them.

Hi, ground power should be used for the test. Alternatively, you can press the Test Oxy button (besides the oxygen instrument) while performing the test. This will temporarily energise the system with the battery bus.

Hi guys,
We've corrected the problem that made the aircraft have a tendency to go left when braking on take-off (there was an initialization issue in the rudder trim, and it was left the majority of the time but it also went to the right at times). The braking instability still remains, we are investigating what adjustments might be needed. Keep in mind work with the BE might take priority, so bugs/problems/features might take a bit longer than usual to be resolved.

@dresoccer4 the main difference of the AI airplanes is the payloads they can carry.

Hi @Proper Charlie,
It's not a bug, with an excessive tail wind, the engine RPMs have to be kept high (above 7000-7500) to avoid the engine shutting down. Same if you're performing a hammerhead.

Hi,
EM -> radar
IR -> infrared 

Hello.
We always check reports of 3D model/texture issues and correct them when needed. For example, we have already internally corrected some other issues reported by @Aircul.
Possibly not the case here but in some instances it turns out that the instruments in a particular model are slightly different than the instruments in another one, as has also been the case with some other reports.

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.