Lesson Overview

Welcome to Module 6 of the Flight Sim Mastery Academy.

This module focuses on the iniBuilds A350 Airliner, a modern long-haul Airbus aircraft available for both Microsoft Flight Simulator 2020 and Microsoft Flight Simulator 2024. The product includes detailed flight-management, navigation, display, performance and aircraft-system simulations, together with built-in SimBrief and Navigraph functionality.  

The A350 is significantly more complex than a default aircraft. It contains:

• Large high-resolution cockpit displays.
• Advanced Airbus flight-management systems.
• Electronic checklists.
• An Onboard Information System, or OIS.
• Detailed fuel, electrical and hydraulic simulation.
• Long-haul performance calculations.
• Integrated charts and airport-navigation functions.
• High-resolution cockpit, exterior and cabin assets.

This lesson provides a practical gate-to-gate introduction. It does not attempt to reproduce every real-world airline procedure or abnormal checklist. Students will instead learn how to install the aircraft correctly, configure the essential options, complete a normal flight and test its effect on simulator performance.

Lesson Objectives

By the end of this module, students will be able to:

Install iniManager and the correct A350 package.

Keep MSFS 2020 and MSFS 2024 installations separate.

Update the aircraft and install compatible liveries.

Create the correct SimBrief airframe.

Connect SimBrief and Navigraph.

Configure the A350 OIS and performance options.

Calibrate throttle controls.

Load passengers, cargo and fuel correctly.

Prepare the aircraft from cold and dark.

Program the flight-management system.

Calculate take-off data.

Start the engines and taxi safely.

Use Airbus managed and selected modes.

Complete climb, cruise, descent and approach.

Land, taxi in and shut down.

Test CPU, GPU, RAM and VRAM behaviour.

Diagnose long-flight instability and add-on conflicts.

STEP 1 – INSTALLATION

Installing the iniBuilds A350

1. Confirm Your Simulator Version

Before installation, identify whether you use:

• Microsoft Flight Simulator 2020.
• Microsoft Flight Simulator 2024.
• Both simulators.

The iniBuilds A350 is sold for both MSFS 2020 and MSFS 2024, but each simulator has its own package location and Community Folder. Do not manually move one simulator’s installed package into the other.  

Students using both simulators should record:

MSFS 2020 Community Folder:

MSFS 2024 Community Folder:

Aircraft version installed in each simulator:

2. Create an iniBuilds Account

Create or sign into the official iniBuilds Store account.

Use the same account for:

• Purchasing the aircraft.
• Accessing iniManager.
• Downloading updates.
• Installing liveries.
• Accessing support.

Check that the correct email address and account are used before purchasing.

3. Install iniManager V2

iniManager is the official application used to install and update owned iniBuilds products. It provides one-click product installation and automatically manages new product versions when they are released.  

Installation Procedure

1. Close Microsoft Flight Simulator.
2. Download iniManager V2 from the official iniBuilds website.
3. Run the installer.
4. Sign into the iniBuilds Store account.
5. Open iniManager Settings.
6. Allow the application to scan for simulator folders.
7. Confirm the MSFS 2020 Community Folder.
8. Confirm the MSFS 2024 Community Folder.
9. Correct any custom paths manually if the automatic scan is wrong.
10. Save the configuration.

Do not continue until the path shown for the selected simulator is correct.

4. Purchase and Download the A350

Inside the iniBuilds Store or iniManager:

1. Locate the iniBuilds A350 Airliner.
2. Confirm the product supports your simulator.
3. Complete the purchase.
4. Open iniManager.
5. Select the correct simulator.
6. Locate the A350 under owned products.
7. Select Install.
8. Confirm the installation location.
9. Allow the complete download to finish.
10. Do not launch the simulator while the installation is active.

The A350 contains a substantial amount of modelling, systems and texture data, so the download and installation may take longer than a simple aircraft package.

5. Confirm Adequate Storage

Before installing, confirm:

• The simulator is installed on an SSD or NVMe SSD where possible.
• The drive has sufficient free space.
• The Community Folder is not stored on a slow HDD.
• Windows has room for temporary installation files.
• The drive is not almost full.

Fast storage is especially valuable with a detailed wide-body aircraft because the simulator must load:

• Cockpit textures.
• Cabin assets.
• Exterior textures.
• Display files.
• Sounds.
• Systems modules.
• Livery files.

6. Aircraft Updates

iniBuilds distributes A350 updates through iniManager.

Recent updates have included refinements to:

• FMGS navigation.
• VNAV.
• Autoflight.
• ECAM.
• Thrust logic.
• Memory handling.
• WASM performance.
• General stability.  

Update Procedure

1. Close MSFS.
2. Open iniManager.
3. Select the correct simulator.
4. Select the A350.
5. Check whether an update is available.
6. Read the release notes.
7. Install the update.
8. Confirm the new version number.
9. Restart iniManager if required.
10. Complete a short test flight before beginning a long-haul operation.

Do not update the aircraft immediately before an important VATSIM flight without testing it first.

7. Installing Liveries

iniManager can install supported A350 liveries directly into the simulator’s Community Folder. Official guidance recommends setting the correct simulator path and then selecting Install on the required livery.  

Livery Installation Procedure

1. Open iniManager.
2. Select the correct simulator.
3. Open the A350 livery section.
4. Choose the airline and aircraft variant.
5. Confirm simulator compatibility.
6. Select Install.
7. Allow the download to complete.
8. Launch MSFS.
9. Confirm the livery appears under the A350.
10. Inspect it for missing textures or incorrect components.

Avoid:

• Installing the same livery twice.
• Keeping an older version active.
• Using an A350-900 livery on an incompatible variant.
• Copying MSFS 2020 liveries into MSFS 2024 without confirmation.
• Installing unrelated A350 liveries made for another developer’s aircraft.

8. Optional Livery and Cabin Components

The A350 supports aircraft-specific interior and exterior configurations associated with liveries. This can include airline-specific cabin or exterior equipment selections.  

Because these options add extra assets, students should begin with:

• The default aircraft livery.
• The default cabin configuration.
• No optional custom cabin packs.

Once the aircraft is confirmed stable, add custom livery components individually.

9. SimBrief Aircraft Profile

Use the correct SimBrief aircraft type for the exact model being flown.

Typical A350 codes include:

• A359 – Airbus A350-900.
• A35K – Airbus A350-1000.

Use an iniBuilds-specific airframe when available.

Confirm:

• Aircraft variant.
• Engine type.
• Passenger configuration.
• Operating empty weight.
• Maximum weights.
• Fuel capacity.
• Units.
• Registration.

Do not use a generic A350-900 profile while flying the A350-1000. The variants have different:

• Weights.
• Capacity.
• Fuel burn.
• Take-off performance.
• Landing performance.

10. SimBrief Pilot Identification

Depending on the current integration, the aircraft may request the numerical SimBrief Pilot ID rather than only the account username.

Record both:

SimBrief username:

SimBrief Pilot ID:

The Pilot ID can be found in SimBrief account settings under the user’s SimBrief data.

11. Navigraph Integration

The A350 supports integrated SimBrief flight-plan retrieval and Navigraph navigation data. The product includes bundled base navigation data, while current database updates require a Navigraph subscription.  

Navigraph authentication is handled through the integrated Navigraph system within the aircraft.  

Setup

1. Open the A350 OIS.
2. Locate the Navigraph or account-linking page.
3. Begin the authentication process.
4. Follow the code or browser instructions.
5. Authorise the A350.
6. Return to the cockpit.
7. Confirm charts and navigation services are available.
8. Compare the aircraft AIRAC cycle with SimBrief.

An AIRAC mismatch can cause:

• Missing waypoints.
• Missing SIDs.
• Missing STARs.
• Invalid airway messages.
• Different approach procedures.

12. Community Folder Management

The A350 package and its liveries may add several folders to the Community Folder.

After installation:

1. Record the main A350 package name.
2. Record installed livery folders.
3. Remove old versions.
4. Check that no duplicate manual installation exists.
5. Keep MSFS 2020 and MSFS 2024 files separate.
6. Use Add-ons Linker only if the aircraft works correctly with linked packages.
7. Do not rename core A350 package folders unless official instructions permit it.

For troubleshooting, create a dedicated profile containing:

• Core A350 package.
• One default or official livery.
• Required navigation integration.
• No unrelated airports or utilities.

13. First Installation Test

Load the aircraft using:

• A default airport.
• A large parking stand.
• Clear Skies.
• Daylight.
• Default A350 livery.
• No AI traffic.
• No GSX.
• No external sound or camera utilities.

Confirm:

• The aircraft appears in the menu.
• The cockpit loads.
• The displays initialise.
• The OIS loads.
• The aircraft responds to switches.
• No WASM or system error appears.
• No CTD occurs.

Allow the aircraft several moments to initialise before interacting with it.

STEP 2 – CONFIGURATION AND NORMAL FLIGHT

Part A – OIS and Aircraft Configuration

14. Understanding the OIS

The A350 uses an Onboard Information System, or OIS, rather than a simple tablet.

It may provide access to:

• Aircraft settings.
• SimBrief.
• Charts.
• Flight operations.
• Payload.
• Fuel.
• Performance calculations.
• Ground services.
• Checklists.
• Navigation information.
• Aircraft configuration.

The OIS also supports deeper SimBrief flight-planning functionality through its Flight Operations Plan area.  

15. Initial OIS Setup

Review:

• Units.
• SimBrief Pilot ID.
• Navigraph account.
• Brightness.
• Aircraft state.
• Performance settings.
• Cabin options.
• Ground services.
• Sound settings.
• Loading options.

Keep the same units across:

• SimBrief.
• OIS.
• MFD flight-management pages.
• Fuel loading.
• Performance calculator.

16. Performance Options

The exact options may vary by product version, but students should review any settings controlling:

• Cabin detail.
• Texture quality.
• Display quality.
• Display refresh.
• Exterior equipment.
• Interior equipment.
• Aircraft effects.
• Sound or cabin systems.

Begin with the default profile.

Change a performance option only when:

• The aircraft is GPU limited.
• VRAM usage is close to capacity.
• Displays are not updating smoothly.
• The cabin causes excessive loading.
• The airport and aircraft combination is too demanding.

Change one setting at a time.

17. Display Settings

The A350 contains several large, detailed displays.

Check:

• Display brightness.
• OIS brightness.
• Navigation-display range.
• Airport-navigation display.
• Electronic checklist pages.
• Display refresh or quality options where available.

Do not leave all displays at maximum brightness at night.

If cockpit performance is poor, compare:

1. Cold and dark.
2. Electrical power on.
3. All displays active.
4. Navigation maps active.
5. Charts open.
6. OIS open.
7. External view.

This helps identify how much workload comes from cockpit display rendering.

18. Throttle Calibration

The A350 uses Airbus-style throttle detents.

Typical positions include:

• Reverse.
• Idle.
• Climb.
• Flex/MCT.
• TOGA.

Calibration Procedure

1. Open the OIS control or throttle-calibration page.
2. Select the number of physical throttle axes.
3. Move both levers to full reverse.
4. Save the reverse position or range.
5. Move them to idle.
6. Save idle.
7. Move them to CL.
8. Save the climb detent.
9. Move them to FLEX/MCT.
10. Save the detent.
11. Move them to TOGA.
12. Save the final detent.
13. Apply the configuration.
14. Move through every position slowly.

Confirm the virtual aircraft displays the correct detent at each physical position.

Incorrect calibration may cause:

• Thrust levers failing to reach CL.
• Autothrust not operating correctly.
• FLEX or TOGA activating unexpectedly.
• Reverse thrust failing.
• Engines producing different thrust.

19. Flight Controls

Check:

• Pitch.
• Roll.
• Rudder.
• Throttle 1.
• Throttle 2.
• Brake axes.
• Parking brake.
• Spoilers.
• Flaps.
• Nose-wheel steering or tiller.

Remove duplicate bindings.

Use small dead zones only where hardware drift exists.

Because the A350 is a large aircraft, abrupt control inputs should be avoided. Use smooth, measured inputs during taxi and manual flight.

20. Payload and Fuel

After generating the SimBrief flight:

1. Open the OIS loading page.
2. Retrieve the flight.
3. Review passenger count.
4. Review cargo.
5. Review block fuel.
6. Begin loading.
7. Confirm Zero Fuel Weight.
8. Confirm centre of gravity.
9. Confirm predicted Take-off Weight.
10. Confirm predicted Landing Weight.
11. Compare all values with the SimBrief OFP.

Do not load the aircraft simultaneously using:

• OIS.
• MSFS Weight and Balance.
• GSX.
• Another payload utility.

Use the supported integration or one primary loading method.

21. SimBrief Import

Generate a completed flight in SimBrief before requesting it in the aircraft.

Then:

1. Open the OIS Flight Operations page.
2. Enter or verify the Pilot ID.
3. Retrieve the latest flight.
4. Confirm origin and destination.
5. Confirm aircraft variant.
6. Confirm flight number.
7. Review fuel and payload.
8. Send or import the route into the flight-management system.
9. Open the flight-plan page.
10. Verify the route waypoint by waypoint.

Do not assume a successful download means the route is ready for departure.

Part B – Cold and Dark Preparation

22. Establish Electrical Power

At the parking stand:

1. Set the parking brake.
2. Confirm engine masters are off.
3. Confirm thrust levers are idle.
4. Turn aircraft batteries on.
5. Connect external power through the OIS if available.
6. Select external power on.
7. Confirm cockpit displays begin powering.
8. Set cockpit lighting as required.

Allow the aircraft systems to initialise.

23. Navigation-System Alignment

Configure the aircraft navigation systems according to the normal cockpit procedure.

General process:

1. Select the inertial or navigation systems to their normal alignment mode.
2. Confirm the aircraft position.
3. Enter or verify the airport and gate position.
4. Allow alignment to complete.
5. Confirm the navigation displays show valid position data.

Do not taxi until the aircraft position and navigation systems are ready.

24. Overhead Preparation

Complete a basic scan:

• Batteries and external power checked.
• Navigation systems aligned.
• Emergency lighting armed.
• Passenger signs set.
• Fuel system reviewed.
• Hydraulic system reviewed.
• Air-conditioning system reviewed.
• Packs and bleed system checked.
• Window and probe heating set for the correct flight stage.
• Anti-collision light left off until pushback or start.
• APU prepared for pushback.

The A350 uses electronic checklists extensively. Use them to support the flow, but still understand what each action accomplishes.

Part C – Flight-Management Programming

25. Initial Flight Data

On the flight-management pages, enter or verify:

• Origin.
• Destination.
• Alternate.
• Flight number.
• Cost index.
• Cruise altitude.
• Cruise temperature where required.
• Route.
• Fuel and weight data.

Importing from SimBrief may populate several fields automatically, but every value must be checked.

26. Route Review

After import:

1. Open the flight-plan display.
2. Confirm the origin.
3. Confirm the destination.
4. Step through every waypoint.
5. Check airway connections.
6. Check altitude constraints.
7. Check speed constraints.
8. Identify discontinuities.
9. Identify vector or manual segments.
10. Compare the route with SimBrief and Navigraph.

Do not delete every discontinuity automatically. Some are created intentionally for radar vectors or manual flight segments.

27. SID and STAR Selection

At departure:

1. Select the expected runway.
2. Select the SID.
3. Select the correct transition.
4. Insert the procedure.
5. Review the route.

At arrival:

1. Select the destination runway.
2. Select the STAR.
3. Select the approach.
4. Select any transition or via.
5. Check the final route.
6. Confirm altitude and speed constraints.

The arrival may need to be changed during flight because of:

• Weather.
• VATSIM instructions.
• BeyondATC.
• Runway changes.

28. Take-off Performance

Use the OIS performance calculator or supported aircraft performance page.

Enter:

• Runway.
• Runway condition.
• Wind.
• Temperature.
• Pressure.
• Aircraft weight.
• Flap setting.
• Anti-ice status.
• Packs or bleed configuration.
• Runway intersection if applicable.

Calculate:

• V1.
• VR.
• V2.
• FLEX temperature or take-off thrust.
• Flap setting.
• Trim.
• Thrust-reduction altitude.
• Acceleration altitude.

Never reuse speeds from a previous flight.

29. FLEX Thrust

FLEX uses reduced thrust when runway length, weight and weather permit it.

Benefits include:

• Reduced engine stress.
• Lower operating temperatures.
• More realistic airline operation.

Use TOGA where:

• Runway length is limiting.
• Performance calculations require full thrust.
• Runway contamination or weather requires it.
• The take-off is rejected and reattempted under changed conditions.

Part D – Engine Start and Taxi

30. Before Pushback

Confirm:

• Fuel and payload complete.
• Doors closed.
• External equipment removed.
• Flight plan complete.
• Take-off data entered.
• Beacon on.
• APU started.
• APU available.
• APU generators or power available.
• Bleed or pneumatic system configured.
• Fuel pumps configured.
• Pushback clearance received.

31. Engine Start

A general twin-engine sequence is:

1. Set the engine-start selector or start mode.
2. Start the first engine according to the aircraft checklist.
3. Monitor rotation.
4. Confirm fuel flow.
5. Monitor EGT.
6. Monitor oil pressure.
7. Confirm the engine stabilises.
8. Start the second engine.
9. Repeat the monitoring process.
10. Confirm both generators and associated systems.

Never rush engine monitoring.

If an engine does not rotate or does not show the expected parameters, stop the sequence and investigate.

32. After-Start Flow

After both engines stabilise:

• APU bleed or air off as appropriate.
• APU shut down when no longer required.
• Engine anti-ice set as required.
• Flaps set.
• Spoilers armed.
• Autobrake configured.
• Trim checked.
• Flight controls checked.
• Ground services confirmed clear.
• Taxi lights on.

33. Taxi

Release the parking brake and use minimal thrust.

Remember:

• The A350 is long and heavy.
• The cockpit sits well ahead of the nose gear.
• Turns require careful positioning.
• The main gear may cut inside the cockpit path.
• Braking should be smooth.
• Taxi speed should be reduced before tight turns.

Use the airport-navigation display, charts and external awareness carefully.

Part E – Take-off, Climb and Cruise

34. Before Take-off

Confirm:

• Flaps set.
• Spoilers armed.
• Autobrake configured.
• Take-off speeds displayed.
• Thrust setting confirmed.
• Flight directors on.
• Initial altitude set.
• Runway verified.
• SID verified.
• Landing lights on.
• Strobes on.
• Electronic checklist complete.

35. Take-off

1. Align with the runway centreline.
2. Stabilise engine thrust.
3. Move the thrust levers to FLEX/MCT or TOGA.
4. Confirm the correct thrust mode.
5. Maintain centreline.
6. Monitor engine indications.
7. At V1, continue unless a serious failure requires rejection.
8. Rotate smoothly at VR.
9. Follow the flight director.
10. Select gear up after positive climb.

Avoid excessive rotation. The A350’s length increases tail-strike risk if rotation is too aggressive.

36. Managed and Selected Modes

The A350 follows Airbus automation principles.

Managed Guidance

The aircraft follows targets calculated by the flight-management system.

Examples:

• Managed speed.
• NAV.
• Managed climb.
• Managed descent.

Selected Guidance

The pilot manually selects a target.

Examples:

• Heading.
• Selected speed.
• Open climb.
• Open descent.
• Vertical speed.

Always confirm the active modes on the Flight Mode Annunciator.

37. Climb

During climb:

1. Retract flaps according to the speed schedule.
2. Move thrust levers to CL when prompted.
3. Confirm autothrust becomes active.
4. Monitor engine indications.
5. Follow ATC altitude clearances.
6. Confirm constraints.
7. Monitor pressurisation.
8. Compare fuel remaining with SimBrief.

Do not allow managed climb to pass an altitude that ATC has not cleared.

38. Cruise

At cruise:

• Confirm level-off.
• Monitor fuel against the OFP.
• Check aircraft weight.
• Review optimum altitude.
• Consider planned step climbs.
• Review destination weather.
• Review the alternate.
• Prepare the arrival.
• Monitor aircraft systems.
• Check memory and performance during long flights.

Long-Haul Fuel Management

39. Compare Planned and Actual Fuel

At selected waypoints, compare:

• Planned fuel remaining.
• Actual fuel remaining.
• Planned time.
• Actual time.

A difference may result from:

• Stronger winds.
• Route changes.
• Extended taxi.
• Holding.
• Different cruise altitude.
• Incorrect SimBrief profile.
• Aircraft weight differences.

40. Step Climbs

As fuel burns, the aircraft becomes lighter and may be capable of a more efficient cruise altitude.

Review:

• Optimum flight level.
• Maximum flight level.
• SimBrief step-climb plan.
• ATC clearance.
• Weather and turbulence.

Never climb solely because the planned OFP contains a step climb. Confirm the aircraft can safely and efficiently reach the new altitude.

41. Landing-Fuel Monitoring

Before descent, calculate whether the expected landing fuel remains above:

• Planned reserve.
• Alternate fuel.
• Final reserve.
• Operational minimums.

If fuel is lower than expected, identify the reason before continuing without review.

Part F – Descent and Approach

42. Descent Preparation

Before top of descent:

1. Confirm destination weather.
2. Confirm arrival runway.
3. Insert or verify the STAR.
4. Insert or verify the approach.
5. Review altitude constraints.
6. Enter approach minima.
7. Calculate landing performance.
8. Check landing weight.
9. Review the missed approach.
10. Complete the arrival briefing.

43. Managed Descent

To begin managed descent:

1. Set the cleared lower altitude.
2. Confirm the route and constraints.
3. Select managed descent according to the aircraft interface.
4. Monitor the FMA.
5. Monitor speed.
6. Monitor vertical path.
7. Use selected modes when ATC instructions differ from the planned profile.

Use speedbrakes only when required and retract them when no longer needed.

44. ILS Approach

For a normal ILS:

1. Confirm the runway.
2. Confirm the ILS frequency.
3. Confirm the identifier.
4. Confirm the final approach course.
5. Intercept from an appropriate altitude and heading.
6. Arm approach mode.
7. Monitor localiser capture.
8. Monitor glideslope capture.
9. Extend flaps progressively.
10. Lower the landing gear.
11. Select landing flaps.
12. Complete the landing checklist.

45. RNAV Approach

For an RNAV approach:

• Confirm the procedure is in the flight-management system.
• Check the correct minima.
• Confirm navigation accuracy.
• Monitor lateral and vertical guidance.
• Check the FMA.
• Review the missed approach.
• Do not treat every RNAV approach as equivalent to an ILS.

Part G – Landing and Shutdown

46. Manual Landing

1. Disconnect the autopilot at a comfortable height.
2. Maintain stable speed.
3. Use small sidestick movements.
4. Keep the aircraft aligned.
5. Begin the flare at the appropriate height.
6. Reduce thrust to idle.
7. Touch down on the main landing gear.
8. Lower the nose smoothly.
9. Apply reverse thrust.
10. Monitor autobrake or apply manual braking.
11. Reduce reverse thrust as speed decreases.

Remember the A350’s large size and inertia.

47. After Landing

After leaving the runway:

• Flaps retract.
• Spoilers disarm.
• Landing lights off.
• Strobes off.
• Taxi lights on.
• Weather radar off.
• Transponder configured.
• APU started where required.
• Electronic checklist completed.

Do not stop on the runway to complete the full after-landing flow.

48. Shutdown

At the parking stand:

1. Set the parking brake.
2. Connect external power or establish APU power.
3. Confirm electrical supply.
4. Move both engine masters off.
5. Turn the beacon off after engine shutdown.
6. Turn fuel pumps off.
7. Configure hydraulic and pneumatic systems.
8. Set passenger signs appropriately.
9. Open doors when engines have stopped.
10. Complete the parking checklist.

For full securing:

• Navigation systems off.
• Emergency lighting off where appropriate.
• External power disconnected.
• Batteries off.

STEP 3 – PERFORMANCE AND COMPATIBILITY TESTING

Testing the iniBuilds A350

49. Establish a Benchmark

Use the same:

• Airport.
• Stand.
• Weather.
• Time.
• Graphics settings.
• Traffic settings.
• Camera view.

Compare the A350 with:

• A simple default aircraft.
• Another complex airliner where useful.

Record:

• Flight loading time.
• Average FPS.
• 1% lows.
• Frame times.
• MainThread status.
• GPU utilisation.
• RAM.
• VRAM.
• CPU temperature.
• GPU temperature.

50. Large-Display CPU Impact

The A350 has several large interactive displays.

Test:

1. Cold and dark.
2. Electrical power established.
3. All cockpit displays active.
4. Navigation display at long range.
5. Airport-navigation display active.
6. OIS open.
7. Charts open.
8. Exterior view.
9. Cockpit view restored.

Record:

• MainThread status.
• FPS.
• 1% lows.
• Display responsiveness.
• GPU utilisation.

If performance drops primarily after displays power up, avionics and display workload are significant contributors.

51. VRAM Usage

Monitor VRAM with:

• Default livery.
• Third-party livery.
• Cabin enabled.
• Premium airport.
• High texture settings.
• OIS charts open.

Warning signs include:

• VRAM reaching capacity.
• Texture pop-in.
• Heavy panning stutters.
• Delayed scenery loading.
• Large frame-time spikes.

Potential adjustments include:

• Texture Resolution.
• Cabin detail.
• Livery texture resolution.
• Airport texture options.
• Render resolution.

52. Long-Haul Memory Test

Record RAM and VRAM:

• At the departure gate.
• After take-off.
• At initial cruise.
• After two hours.
• Before descent.
• On approach.
• After landing.

Some memory increase is normal as the simulator loads:

• Airports.
• Terrain.
• Weather.
• Aircraft assets.

Investigate when memory:

• Continues rising without stabilising.
• Reaches system limits.
• Causes severe stutters.
• Produces a WASM failure.
• Causes a CTD.

Recent A350 updates have specifically included memory-handling and WASM stability improvements, making version tracking important during long-flight testing.  

53. Premium-Airport Test

Compare:

1. A default airport.
2. A premium international airport.

Use identical:

• Weather.
• Stand.
• Traffic.
• Camera.
• Aircraft state.