Jump to content

Recommended Posts

Posted

Hello. Today I bought the Mirage and i'm quite pleased with it :thumbup:

 

I'd like to mention a few things that I noticed in both the release and open alpha (don't know if they've been reported already):

 

- Rudder authority: it's very very hard to steer the aircraft in the speed range of 40-110 Kts (takeoff or landing)

 

- Wheels animation: when doing tight turns, the inside wheel is spinning way too fast

 

- Nose steering: when standing still, steering the nose wheel doesn't produce any movement on the aircraft (try to do the same in the A-10 and you'll see the nose move slightly). It seems that the gear in this case is not reacting to real physics, kinda like the old Lock On.

 

- twitchy elevon movements: on the ground, try to push the stick to the limits in a circular motion (like they do on carriers to check controls before launch). Look at the elevons and you can see that they kinda jump from one position to another at some specific stick positions. The same is visible in the axis window (rctrl+Enter).

Windows 10 - Intel i7 7700K 4.2 Ghz (no OC) - Asus Strix GTX 1080 8Gb - 16GB DDR4 (3000 MHz) - SSD 500GB + WD Black FZEX 1TB 6Gb/s

Posted

-Rudder Authority: that's why you align up first, crosswind can be countered by full pedal if required.

 

-Nose Steering: Haven't looked into the specifics but given that this is a FBW plane it might be the computer overriding the steer command due to the lack of forward speed.

 

-Twitchy Elevon: I think it's the FBW system mixing the different input signals.

Posted (edited)
-Rudder Authority: that's why you align up first, crosswind can be countered by full pedal if required.

 

Yep, I know about line-up. Still normally the rudder has enough authority to provide positive directional control at speeds where the nose wheel is disengaged. In the F-16 this happens at 70 Kts, in the A-10 at 60Kts. Now the Mirage 2000C automatically disables NWS at 40kts, which is indeed quite slow compared to other aircraft.

 

So as I see it we have 3 options:

 

1. The behaviour is realistic, and the real Mirage 2000C has very poor control on the ground

2. The real aircraft has a much more effective rudder at slow speeds

3. The rudder is modelled correctly, but real aircraft doesn't disengage the NWS at such low speed.

 

-Nose Steering: Haven't looked into the specifics but given that this is a FBW plane it might be the computer overriding the steer command due to the lack of forward speed.

 

Press F2 (external view) and you can see that the NWS is fully functional when stationary

 

-Twitchy Elevon: I think it's the FBW system mixing the different input signals.

 

This is also what I think it is, but the fact that they are jumping instantly form one position to another doesn't look very realistic. Also, the positions are not symmetrical: with left-forward stick the elevons are at one position, while with right-forward stick they are at a different angle.

I wonder if this is a bug in the FBW logic and if it has effects while in flight, or if it's just a visual thing.

 

I'm really enjoying the Mirage so far, I hope it gets better and better :joystick:

Edited by bkthunder
correction

Windows 10 - Intel i7 7700K 4.2 Ghz (no OC) - Asus Strix GTX 1080 8Gb - 16GB DDR4 (3000 MHz) - SSD 500GB + WD Black FZEX 1TB 6Gb/s

Posted
Thank you for catching that controls difference, it's small but there, I'm looking into the reason for it now

 

Are you talking about the Twitchy Elevon? Because I observed that too, it looked like the system was unsure what to do when the aircraft was at rest.

Posted
Thank you for catching that controls difference, it's small but there, I'm looking into the reason for it now

 

You're welcome, I hope you can correct this ;)

Windows 10 - Intel i7 7700K 4.2 Ghz (no OC) - Asus Strix GTX 1080 8Gb - 16GB DDR4 (3000 MHz) - SSD 500GB + WD Black FZEX 1TB 6Gb/s

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...