Ralgh

At my airline the strobes are always left in auto and navligts in 1 or 2 even when the plane gets powered down.

I personally find the centerline light nose gear bump sound really annoying. I’ve been an airline pilot for 28 years and have not flown with anyone who was content to just keep running over the centerline taxiway or runway lights and listen to the bumping noise. In fact most airports have the centerline lights offset from the painted center lines. KMIA is the only one I have been to where the lights are on top of the painted center lines. I find a lot of developers overuse this sound since in real life when a pilot starts hitting those lights they will make a deliberate effort to move off of them.

I just checked to make sure and I am on 1.0.8. I took a screenshot of what I am seeing. There are still a ton of scratches visible on the windscreen for me.

Now I have never been on a real A350, but I have flown the EMB-120, 727, Fokker 100, 737-800 and A320 family of aircraft during my career and you can't hear the flap's movement in any of those planes. I've also been on the jumpseat of multiple other types and have never heard the flap's movement from the cockpit. I'm guessing the pilots don't hear the flap movement in the A350 either. Could someone please have a look and see if the sim is representing the real world flap sounds for an A360?

I have been a real world airline pilot for almost 29 years now and the number of scratches on the windscreen is excessive compared to what I have seen in real life. In fact, it would be unusual to see even a few of the scratches present on the simulator's windscreen. I appreciate the developer's effort to make the plane look like it has experienced some wear and tear but what is represented on the sim windscreens is way over done compared to real life.

https://forum.inibuilds.com/topic/25808-green-wires-on-the-outside-model/ Try the above link for a possible solution.

In the MSFS world the windows are built into the model so they cannot be plugged like we could do in the P3D world. They would have to make a model for every different window option.

Disregard. Misread post.

Here you can see on the ORCKA departure out of LAX and the LENDY arrival into JFK the active fixes on the SID/STAR are displayed on the 160 mile range. The same fixes remained displayed on the 320 mile range too. Again there are other SID/STAR fixes displayed but I still am not sure of what the criteria is for that because not all the other SID/STAR fixes are displayed.

Okay, I fly a trip tomorrow and will try to remember to get a pic of it. Interestingly enough I was paying particular attention to it on my last trip, and it was often showing one or two fixes beyond the active fix on the arrival. I don't know if it has to do with distance between fixes or what criteria it was using but the active fix was always displayed.

In the simulation the aircraft is not starting to slow to 250 knots until reaching 10,000 feet in the descent in managed speed. It should plan to be at 250 knots when reaching 10,000 feet.

The active waypoint is not being displayed on the nav display when the range is greater than 80 miles. Is it correct that the waypoints on the SID and STAR aren't displayed above 80 miles range except the active waypoint is always displayed in the real world aircraft.

When starting the engines the lower ECAM page should stay on the ENGINE page until the ENG mode knob is returned to the NROM position. In the current version of the simulation the lower ECAM page automatically switches to the WHEEL page at about 52% N2 which is not correct.

We don't have the A320 NEO but I do fly the A321 NEO with the CFM LEAP at my work and the engines do respond much quicker when setting takeoff thrust than what I am seeing in the simulation. My real world experience matches what is shown in the linked video above.

here’s a link to the video. https://youtu.be/N4cxNccH66U?si=0Ep_l0Kh122dfE2V