Description
basically whenever i use the speed brakes i can never get them to retract down fully because of an issue with the speed brake lever.

Steps to reproduce
Steps to reproduce the behavior:
once in the cockpit raise the speed brakes and try to lower them again and it will only go back half way

Expected behavior
it is expected to go back into position completely

Screenshots
here is a link to a youtube video demonstrating the issue https://www.youtube.com/watch?v=tZw6J9_LAOg

Description
When selecting reverse thrust the reverser levers do not move upwards with the levers when moving into the reverse detent

Steps to reproduce
Steps to reproduce the behavior:

1. Go to Thrust levers
2. move from idle into reverse
3. Levers move down but reverse levers do not move

Expected behavior
The reverser levers should come up

Screenshots
Video showing issue
https://youtu.be/IFKzfa-_t6Y?t=321

Additional context
Using full TCA quadrant with add-ons

Just in case: Known issues:
-Mouse-controlled spoilers and reversers do not work; use keybinds or peripherals to control them
-Rubber on sidestick is wrong (black, should be blue)
-No icing or wingflex yet
-Rudder is too sensitive
-Windshield makes things slightly blurry

Description
A clear and concise description of what the bug is.

When on the ground the GPWS reports 5 feet instead of zero. When landing the GPWS reports 5-15 feet above ground when first touching down on the ground

Steps to reproduce
Steps to reproduce the behavior:

1. Set plane to short final
2. Watch Altimeter screen
3. Listen to GPWS callouts
4. Observe height above ground, orange number on altitude screen its 5-15 above ground at point wheels make contact with ground when it should be )

Description
The panels nor the MCDU are working no matter what I try.

every time I load up the aircraft no matter what livery I am using and no matter how much times I start it the panels nor the MDCU work.

Description
A clear and concise description of what the bug is.

Steps to reproduce
Steps to reproduce the behavior:
fmc do not work

Description
On the F-PLAN page of the MCDU, the DIST number at the bottom of the screen only shows the distance of the entire route instead of remaining distance of the flight.

Steps to reproduce
Steps to reproduce the behavior:

1. Program and activate a flight plan
2. Observe distance shown on F-PLAN page (it will be the distance of the entire flight).
3. Take off
4. Observe the distance at any point in the flight; it will not change.

Expected behavior
The distance should constantly show the distance remaining in the flight, not the entire route from start to finish.

Screenshots

Description
Lower Ecam does not work it only shows one information.

Expected behavior
It has to have diferent informations like APU BLEED COND or DOOR

Description
Master warning while working and making sounds has no text or light appear on the buttons themselves.

Steps to reproduce
Steps to reproduce the behavior:

1. Have an action done which causes master warning to go off
2. Look at screen panel where master warning is but no light or text on it
3. Click button that should be normally lit up to turn off master warning alarm.

**Expected behavior”
When warning goes off these buttons should illuminate red or yellow depending on the button

Additional context
Not super important as the button still works and it is just a visual thing.

1- The chrono button is at the wrong location on the first officer side
2- The EMERG button near the lower ECAM buttons has a non-transparent cover
3- The engine mode selector has no illumination

Thank you!

Description
The spoilers will remain at half, when trying to push beyond half, they retract all the way back.

1. Set spoilers to full
2. Lift to half
3. try to lift all the way

to bring up all my spoilers

Good evening, and congratulations on the release.

I am the developer of Find My Plane which is a free and open-source flight tracker for MSFS2020. This allows flight tracking on any device (computer, iPad, phone, etc) with minimal setup and overhead.

Users can do this by way of my own simple client (https://github.com/hankhank10/findmyplane-client) but also by way of integration with third-party tools and aircraft. I am currently integrating with the MSFS Mobile Companion and it already allows tracking of the Fly By Wire A320nx through their API.

Is this something you would consider adding as a function? The platform works through a simple and open-source API (https://app.swaggerhub.com/apis-docs/hankhank/FindMyPlane/) and could be easily called from simple javascript in the CDU.

If this is something you would consider I would be very happy to assist in raising a pull request.

To be clear: Find My Plane is free and open source and will remain so.

Description
speed brake does not shift back to 0% after setting it to 50%

Steps to reproduce
Steps to reproduce the behavior:
mouse control the speed brake to 50 percent, then try to reduce to 0 percent

Expected behavior
control lever does not move back to 0 percent

Clicking wipers to slow or fast doesnt work, the wipers dont move.

Steps to reproduce
Steps to reproduce the behavior:

1. Go to '...' The A330
2. Click on '....'Wipers slow or fast
   Expected behavior
   Well its obvious what to expect ;/

Screenshots

Description
A clear and concise description of what the bug is.

Steps to reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

1. i make now a test flight from eddf to wsss aircraft feels and flys well. But there is one major think... i fly in Virtual Reality and the mouse can use only when i close one eye to navigate. there is a double effect.

2. with a full Tank i can Fly from Frankfurt to Sydney?

i on Fly EDDF to WSSS and i have planed 76tonnes of fuel....
Arr in Singapur i have rest of 35Tonnes...

There must be something wrong...

3. After Takeoff when i direkt use AP aircraft runs do full power and doesnt manage clb speed.. after 1 min aircraft break and it runs normal...

4. with thrustmaster TCA thrustclimb not perfect managed to basesettings of the throttle

BEST REGARDS
and big thanks for your work for us all

Description
A clear and concise description of what the bug is.

Steps to reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Looking at the side of the plane, one can see the front looks kinda bulbous. On inspection this is actually caused by the area near where the front of the wing connects to the body of the plane being raised up higher than where it normally is behind and in front, creating the bulbous look. I can apply a photo with this area circled if need be.

Leveling this spot on the underside of the plane with the rest of the fuselage will greatly improve the quality of the planes body.
Also to add on the top part at the front (above cockpit to start of wings) is a little high but not as bad of a difference as the low section mentioned above. It’s hight creates a slope that technically shouldn’t be there.

Description
Attempting to program a route to a waypoint via an airway results in a direct track to a waypoint.

Steps to reproduce
Steps to reproduce the behavior:

1. Program any flight plan that uses airways (for this example it will be a route from RCTP-VHHH).
2. In this example, I want to fly to MKG via the T3 airway. I input T3 in the "VIA" column and MKG in the "TO" column.
3. The result is a track direct from my previous waypoint to MKG

Expected behavior
The resulting route from this input should follow the T3 airway. In this example, that route would be CANDY AJENT MKG instead of direct to MKG.

Screenshots

It should also be noted that one can work around this issue by simply programming every individual waypoint, however this is incredibly manic and time consuming so the sooner this feature can be made to work as intended, the better. Try it in the A32NX mod for a sense of how it should work.

App speed in the MCDU is 260 when it should be 160

Description
A clear and concise description of what the bug is.

Steps to reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Description
Animation freezes mid-flight. I'm able to look around bu the aircraft isn't moving and the GPS is frozen. The buttons are inoperable.

Steps to reproduce
Unsure. Leave it on Autopilot for a bit

Expected behavior
They keys in the cockpit become inoperable. I can rotate the view and switch between cameras, but the aircraft isn't moving.

Screenshots
Don't have them

Additional context
I love this job on this aircraft, so I just wanna see it get better

Description
The aircraft can cruise at FL540. It has incredibly excessive climb rates and had it not been for Asobo's high FL invisible wall they have it could quite easily go higher. I was able to overspeed the aircraft in climb thrust at FL540.

Steps to reproduce
Steps to reproduce the behavior:

1. Takeoff and climb to a high FL - I tried this on about 50% fuel and was able to climb to FL540 and maintain mach .81.
2. Observe V/S

Expected behavior
A much shallower V/S especially in higher FL and the aircraft should not be able to maintain FL540 (the altitude of some Concorde flights)
Screenshots

Additional context
N/A

Hello dear Developer i wanted do ask if you can Fix the texture bug on the Wing by the Flaps pls here is a picture what i mean

Hey,
one example:

you are on 30k ft with your plane, set the speedbrake full and want to descend to 22k ft, the autopilot puts the plane on 60(max) vertical speed and starts losing speed. I think it should increase its speed while descending with 60 vertical speed?

Kind regards

Description
A clear and concise description of what the bug is.

The main problem with the bug is very simple. When you approach the landing, you will experience that RCA is correct. But just when you flare, you notice that you have a touchdown, even though RCA clearly states it’s still about 10 feet till you will touchdown. After you end your flare and bring your nose down, it will still report 5 feet till touchdown.

Steps to reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

As I tested it in Europe, try reproducing it there (EGLL airport)

1. Takeoff from other airport as you would normally do
2. At the approach phase, closely monitor RCA callouts
3. When on final, be sure to have RCA callouts in clear view
4. On flare, you should notice that on touchdown you will still have about 10 feet till touchdown.
5. After you end your flare, it will still say 5 feet till touchdown

Expected behavior
A clear and concise description of what you expected to happen.

It should obviously say 0 on touchdown, although due to it’s tilted gear, it might say 1 or 2. After touchdown and the end of flare, RCA shouldn’t be visible at all.

Screenshots
If applicable, add screenshots to help explain your problem.

I do not have any ScreenShots as for now. Easyjetsimpilot did a live stream testing A330. You can check there for how it looks.
Here’s the link: https://youtu.be/su73s1vnWZE

Additional context
Add any other context about the problem here.

Great Freeware Aircraft, with some fixes it will be definitely a huge pleasure to fly with! Thanks for your hard work :).

#Description
A clear and concise description of what the bug is.

Steps to reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Description
Climb rates, bank angles, descent rates etc. when using managed mode on the AP are too extreme, causing 6000 FPM climbs and almost 90 degree banks.

Steps to reproduce
Steps to reproduce the behavior:

1. Load in A330
2. Load in a flight plan
3. Take off
4. Set AP to climb, or deviate off course and set AP to follow flight plan, both via managed modes.

Expected behavior
Less extreme banks, climbs, and descents

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Description
A clear and concise description of what the bug is.

Steps to reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Flight Plan distance ether goes up or freezes

How to replicate:
Have a ils flight plan.

Description
The Auto Thrust disables it self if the Throttle is manually set to Idle.

Steps to reproduce
Steps to reproduce the behavior:

1. Manually put your throttle at any level that is not idle.
2. Enable the Auto Thrust.
3. Manually put your throttle to idle.
4. The Auto Thrust is going to disable itself.

Expected behavior
What was expected to happen is to have the Auto Thrust still enabled even if the Throttle is manually set to Idle.

Additional context
This can happen in any stage of the flight.

the Climb gate on the throttle
when it's positioned in CL currently it still thinks it's in FLX MCT

Re-devleoping the throttle is the best solution to all this

Description
As the title states.

Steps to reproduce
Steps to reproduce the behavior:
It is difficult to know the exact conditions under which I found this bug, so take this with a grain of salt.

1. Fly at cruising altitude (in this case 38,000 feet) with full exposure to sunlight (the angle of the sunlight may also play a role).
2. As shown in the video, this flickering should be visible within the cowling and fan blades.

Expected behavior
There should not be flickering within the engine cowling and fan blades..

Screenshots

VR: Very blurry looking out of cockpit windows.
Zoom with right-click does not work both in flat-screen and VR.

Climb detent is very difficult to hit with a Honeycomb Bravo.
Distance reader to destination in flightplan is frozen.

Description
The Altimeter knob needs more than 1 click, or mouse wheel spin to change the value on it.

Steps to reproduce
Steps to reproduce the behavior:

1. Put your mouse on top of the altimeter knob.
2. Click one time, to increase or decrease, it doesn't matter.
3. The Value won't change unless you click multiple times.

Expected behavior
What was expected to happen is to have the values changing with one click only, not multiple ones.

Screenshots

Additional context
I suspect it could be a default A320 issue. But since i never experienced this with it before, i am reporting this to you to see if there's anything you can do about it. Good luck guys! And nice job so far!

Description
VR mode issues. Mouse does not display correctly in VR, and right click to zoom function in VR does not work

Steps to reproduce
Steps to reproduce the behavior:
Enter VR mode

Expected behavior
mouse appears as two separate pointers in VR. Zoom function does not work.

Description
AP would not follow flight plan, missed half of it. Auto throttle targeting excessive speed. As can see on N1 i had reduced to around 50% but engines till above 87
Steps to reproduce
Steps to reproduce the behavior:

1. Go to runway and take off
2. after take off engage AP/AT
3. Look at ND
4. See screenshot for errors

Expected behavior
To follow flight plan and not target excessive speeds

Screenshots

Additional context
auto throttle targets 447kts. engines was reduced to 50% N1 but stayed above 87. this has happened twice after taking off so far.

First and foremost..what an amazingly built plane..congrats to the dev team!

A few things I noticed on a short flight within Netherlands this evening:

On my descent for some reason, on managed speed, the speed climbed all the way up to 445 knots triggering the overspeed warning .. not sure why this happened

The main panel floodlight didn't seem to be very effective during sunrise in Amsterdam with a glaring sun.

The pedestal flood light seems to not operate as expected.. the slider only has two modes on and off rather than a gradual increase/decrease.

The localiser button didn't seem to intercept the runway approach when less than a mile from the perpendicular point. However approach button seemed to capture the glideslope so all good.

The ground power unit doesn't seem to visibly connect a cable near the front landing gear. (Comparing this to a32nx..apologies!)

The door panels show a visible rectangle border with a different shade of white from the rest of the aircraft. Visible at certain angles but affects all doors. Not sure if it's livery specific but tested this with FedEx livery.

Despite the few comments mentioned above...the aircraft is superb..aesthetically and performance wise..looking forward to future updates!

Description
A clear and concise description of what the bug is.

Steps to reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Description
Nose shaping is too stubby and APU area is too blocky

Steps to reproduce
Steps to reproduce the behavior:

1. Load up
2. Observe nose and APU exhaust area

Expected behavior
Should be shaped a little differently, APU should be smaller and rounder while nose should be rounder and less stubby

Screenshots
Ingame:

IRL:

Ingame:

IRL:

Additional context
Add any other context about the problem here.

Description
Hi, first thanks for this amazing plane, and thanks to all the people involved. It´s an incredible job!!!

Ok, I just downloaded this plane and tested from cold and dark and i saw this bugs:

1. The plane doesn´t start in cold and dark. It auto-starts up engines when you enter in the plane but it only works on the left engine, The right engine doesn´t finish the start up process, even if you do it manually.
2. The ground power button cannot be disconnect

Steps to reproduce
Steps to reproduce the behavior:

1. Start with the plane at gate ot ramp
2. You will appear at the ramp with fuel pumps, apu, apu bleed and the external power already connected. (not expected)
3. Both engines will autostart. (not expected) And they start at the same time (not expected)
4. Right engine will stop at N1 25% (like when you start up with the fuel valve closed)
5. From this point is impossible to start up right engine manually. I also tried with the copilot taking the control of the plane, and autostart but it doesn´t work.

Expected behavior
Cold and Dark when starts in the gate or ramp.
Right engine start up.
Ground power button working properly.

Description
When turning on the Logo lights the tail plane is not illuminated
Steps to reproduce
Steps to reproduce the behavior:

1. Go to 'Nav & logo lights'
2. Turn on

Expected behavior
The Logo light should illuminate the tailplane

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Description
Spoilers lever will not retract past 50% and constraints not followed on approach

Steps to reproduce
Steps to reproduce the behaviour:

1. Fly A330 on approach (ILS) in managed mode
2. Click on manage mode on AP for approach (before first constrain)t. Use mouse on spoiler lever to control amount of spoilers (50% or more)
3. wait till next constraint and try retracting spoilers using lever
4. altitude does not change and spoilers lever sticks between 50% and 100%

Expected behavior
Spoilers to be able to be fully retracted and altitude constraints followed.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Description
I used the a330 300 for a flight from Madeira Airport LPMA to Tokyo Haneda RJTT 100% fully tanked with increased sim rate and as soon i reached tokyo, there was 70 % left in the fuselage. i dont know if it is because of the sim rate or not...

Steps to reproduce
Steps to reproduce the behavior:

1. Increase Sim Rate
2. Full Tank
3. Fly long distances
4. See decreased fuel usage error

Expected behavior
The A330 300 should have run out of fuel or should have more fuel burned

Description
Playing multiplayer with people who have the A330 installed only renders the cockpit in game.

Steps to reproduce
Steps to reproduce the behavior:

1. Load into the game with another player who has the A330.
2. See flying cockpit.

Expected behavior
Render of plane appear instead of flying cockpit.

Screenshots

Description
Hello, I know that the project is new but i'm a flying for more than 1 hour and an unexpected problem happened

Expected behavior
The cockpit fully desappear when i was flying.
Before I had this bug, i was trying to see the different views of the airplane. Then when i try the external 13, i return to the cockpit and i had this issue

Screenshots

Additional context
Hope that you can fixe it and i'm available for other question about it
Have a good day
LePiloteBleu

Description
It seems that the tail on the A330 is not centered. See image below.

Screenshots
https://imgur.com/a/hfE45sp
https://imgur.com/a/9o6zrL8
https://imgur.com/a/5QJkdLl
https://imgur.com/a/eG5oHOm