MD82

Forgot to mention. Navigraph NavData and SU15 Beta (.12) and ini livery N173UP -600F.

On KRFD to KSLC. Via NORDK6, OCS transition. ILS 16L via WEBER. On the ground, I set both departure and arrival. No issues. I removed STAR WEBER and connected ILS 16L WEBER under NORDK. No issues. I took off and flew to about 500 miles to destination. I manually set 15000 at CARTR, then set a speed transition of 250/15000. Total freeze MSFS.

Referencing the A310 Sperry manual p. 38 Chapter 3.2 1st sentence. - The FROM waypoint (or the waypoint you have passed) should be the actual time you crossed it. As of now, the FMC just calculates the estimated time overhead from actual position back to that waypoint. Referencing the A310 Sperry manual p. 38 Chapter 3.3, bullet points 2 and 3. - The distance between the FROM waypoint to the current active fly-to waypoint should display actual distance between the aircraft and the waypoint. As of now, total leg distance remains displayed. - In addition to the leg distance between the waypoints (which ever you have slewed the F-PLN to) in lines 2 and 3 should display the course in addition to the usual distance, in the format of DIS/CRS°. As of now, only distance is shown between all waypoints .... including the ones between lines 2 and 3. Xander

Please the below forum post. It is still the same in 1.10. It's not an install issue. I tested it yesterday, and I don't remember a changelog item where this is addressed.

SU15Beta

Let me correct. it is the same problems as are being reported. Airplane flies, but panel is unresponsive. ini livery N173UP

Hello, planned on doing the SCOLA1 STAR into KRNO. MVA transition. And the RNP Y 17L. - 1st step I did was to edit the 250-knot restriction from 250/FL100 to 250/FL150 as per my preference. No problem. - 2nd step was to connect the STAR to the APPR as it finishes on a heading of 333 after KLOCK. - I deleted KLOCK from the STAR end, and poof. Both FMCs stuck. Airplane flies. Just that I have no FMC's anymore. FMC 1 went blank together with a DSPLY legend light. FMC 2 froze where it was last at F-PLN. - Also, the route is completely gone from the ND and certain instruments are behaving strangely. Xander

To revisit the FCU brightness. Although what the brightness knob controls have been fixed, there is still a misunderstanding of what it actually dims. It dims the FCU Window "LIGHTS" not the FCU window LCD current. Think of the FCU digits as being the same as a classic digital watch. The digits themselves are energized liquid crystals. The A300 FCU is the same as that, but in reverse. The whole display is energized (black) and where a digit is needed, that area is de-energized so the digit forms white. What I am getting at is that the FCU brightness knob does not control that operation, it only adjusts the brightness of the lightbulbs behind and around each of those windows. This means that even if the FCU brightness light is fully turned off, you can read the digits if there is sufficient light to see the window. https://youtu.be/-U60iLommyI?si=9doRFfGqkjyQaHQ0&t=73 https://youtu.be/5rNgIO5b7mQ?si=YSLJcL-q-RSbw3bl&t=78 Look at these time stamps. It is daylight and the sunlight lets you clearly see the digits. It is exactly the same as if I have a simple Casio digital watch on my wrist. In the day, I can see it. If it is pitch black of course I can't see it. Press the light button casts light on the display and I can see it again. Without the FCU brightness, my ability to see the digits should be governed by light or shadow cast onto it. In daylight, turning the FCU brightness fully off, should only remove the yellowish glow of the light bulbs and leave the white over black effect of the LCD.

Hello, the engine reverse sleeves are an open/close operation. Meaning, it does not matter if you have selected idle reverse or full reverse, the sleeves will fully open. As it is now, the amount of reverse sleeve operation is equal to the amount of reverse thrust applied. Xander

Saw this too. Even if the max altitude for TO and LDG was 8000, the minima can never be 8000 as well as MDA is always higher. In the SPerry FMS manual, there is no mention of character limitations in this field.

I can't find any reference to it in the Sperry FMS manual.

That's correct. But now I have no official reference. So you can close this as I can't officially verify.

Hello, when selecting V/S mode and confirming on the FMA. I select V/S 0.0. If I now change the altimeter setting to a new value, and with V/S still active and 0.0, the autopilot will climb/descent to regain the original altitude. In other words, V/S will increase or decrease without pilot input and without a change in the selected V/S to regain an altitude which should not be the case. VS mode at VS 0.0 should be just that if I'm not mistaken. At least it is on all other autopilot systems I know.

Disregard above as my % reference is a B4 model. However, the difference in trip fuel remains.

Hello, if you have an airplane set up for pounds, the fuel weight correctly populates when imported from SimBrief (Have not tried manually entering a value), but when you apply the load to the aircraft, the fuel weight remains in kilograms. In other words you will see a pounds value in the top data field and a kilogram value at the bottom field (even though the unit says lbs.)