richboy2307

Radio Altitude (RA) callouts are automated aural announcements that alert the flight crew to the aircraft's height above ground during approach and landing. They provide critical situational awareness in the final phase of flight, helping pilots monitor descent rate, verify height against the expected profile, and prepare for landing or go-around decisions. You can toggle which RA callouts you wish to hear via the EFB Callout Settings page. (Click to enlarge image) Changing RA CalloutsOpen the EFB and navigate to Settings > Callouts Toggle the switch next to the desired callout to enable or disable it. Your selections are automatically saved and will persist across sessions and aircraft variants.

The Audio settings page on the Electronic Flight Bag (EFB) allows you to fine-tune individual sound category volumes, enable specific sounds, control noise-cancelling and select your preferred cabin announcement language. This page is accessed via EFB Settings > Audio. (Click to enlarge image) Volume SlidersEach category below can be independently adjusted from 0% to 100% using its respective slider: Category Description Master Volume Global volume control affecting all aircraft sounds. External Engine Engine sounds heard from an external camera view. Internal Engine Engine sounds heard from inside the cockpit and cabin. Systems Aircraft systems sounds (hydraulics, avionics fans, relays, etc.). Manipulations Switch clicks, knob turns, and other cockpit interaction sounds. Announcements Cabin crew and PA announcements. Ground Services Sounds related to ground handling (GPU, air conditioning carts, jet bridge, etc.). Environment Ambient and environmental sounds (wind, rain, airframe noise). Tip: Lowering Internal Engine relative to Systems or Announcements can help improve callout and PA clarity during critical phases of flight. Adjust the sliders for what works best on your Audio/EQ setup. Audio TogglesNoise Cancelling Headset Simulates the effect of a noise-cancelling headset, reducing ambient cockpit noise for clearer radio and callout audio. Note: For this feature to function correctly, ensure Loudness Limiter and Headphone Simulation are disabled in your simulator's Settings > General > Sound menu. For more information refer to How to - Disable Loudness Limiter & Headphone Simulation. Thrust Detent Enables audible click/detent sounds when moving the throttle levers through IDLE, CLB, FLX, and TOGA positions. Flaps Audible in the Cockpit Enables the sound of flap surface movement to be heard from inside the cockpit. Cabin Announcements - Language SelectionChoose the language used for cabin crew announcements (e.g., safety demonstrations, boarding, and arrival PAs): English (US) English (UK) German Japanese Russian Spanish Portuguese (BR) French Portuguese Arabic Custom - Allows use of a custom/user-provided announcement audio set. Simply click on your preferred language button to apply it. The currently selected language will be highlighted. Custom Cabin Announcements - COMING SOONCOMING SOON

Showing / Hiding the EFBClick on the pen holder located above the OIT, on either the Captain (CPT) or First Officer (FO) side, to show or hide the respective EFB. (Click to enlarge image) Adjusting EFB Position (Tilt & Rotation)Open EFB > Settings > EFB > EFB Position Adjustment. A pop-up window will appear with an adjustment area. Click and drag with your mouse within the white box to adjust the EFB's mounting pivot: Inner (center) area — Adjusts Rotation Outer area (within the white box) — Adjusts Tilt Once satisfied with the position, click Done to confirm. Click Reset at any time to restore the default position. (Click to enlarge image)

The onboard printer is used to create hard copies of key flight data like Take-Off (T.O) Data, Flight Plan (F-PLN), METAR, Mailbox messages, and more. While this data is already accessible via the Electronic Flight Bag (EFB), Onboard Information Terminal (OIT) and Flight Management System (FMS), printing allows you to cross-check and reference information physically on the cockpit tray table. (Click to enlarge image) How It WorksThe printer simulates a realistic print process using a combination of: 3D model animations - representing the physical printing mechanism Show/hide attachments - simulating the printed page being fed out and placed onto the tray table in the cockpit Once data is sent to print, it is automatically formatted using a template corresponding to the type of printout requested (e.g., F-PLN INIT, METAR, T.O Data) and rendered onto the printed page texture. Note: Page sizes may vary Paper length is dynamic and scales based on the content being printed. For example, a METAR printout will use significantly less paper than a full F-PLN printout. (Click to enlarge image) How to Print1. Configure Auto-Print Options (Optional)Open the EFB, navigate to Settings > EFB, and enable any desired auto-print options (e.g., Auto Print Initial FPL, Auto Print TakeOff Data, Auto Print Winds) if you want certain items to print automatically without manual input. (Click to enlarge image) 2. Print Flight Plan, Take-Off or Wind DataNavigate to the Printer page on the FMS (DATA > PRINTER) using the MFD and cursor controls. Select the on-screen PRINT prompt where available to send that data to the printer. The options will remain gray until the relevant data is uplinked into the FMS first. (Click to enlarge image) 3. Print Loadsheet, METAR or Mailbox MessagesGo to the Mailbox or MFD ATC Communications (ATC COM) page on the FMS, select the specific METAR or message you wish to print, and press the on-screen PRINT button. OR 4. Collect Your PrintoutOnce printing completes, click on the simulated printout located on the pedestal to retrieve it. It will then be placed on the cockpit tray table for reference. Note: Only 1 printout can be displayed at a time. The printed page remains on the tray table until manually removed or replaced by a new printout. The printed page will show/hide alongside the tray table when closed. Since paper length varies by content, larger printouts (e.g., full F-PLN with multiple waypoints) will take slightly longer to complete than smaller ones (e.g., METAR). Use the printer as a quick physical reference during busy phases of flight, reducing the need to repeatedly navigate FMS/OIS pages. Note: The printout is strictly simulated inside the virtual cockpit only. The virtual printout cannot be sent to a real-world physical desktop printer or exported directly as a PDF at this time.

To steer the A220 effectively, first ensure NOSE STEER is turned ON using the button directly under the gear lever. Use your rudder pedals for gentle corrections and straight taxiing, and switch to the tiller-only inputs for sharp turns. When rudder pedals and steering tiller are moved simultaneously, the max deflection is limited to the 9° left / right only. For tiller-only inputs, press the PEDAL DISCONNECT button on the tiller to boost your turning gain for maximum steering angle. The steering tiller commands the nosewheel up to 80° left / right.

Use the link below to see an index of all simulator variables (L-Vars and H-Events) and input events that the A220 reads and writes, organized by system. These can be used to read and modify the aircraft state's using external applications. Simulator Variables (L-Vars and H-Events) https://docs.synapticsim.com/pilots/simvars Input Events https://docs.synapticsim.com/pilots/inputs

There is an Electronic Flight Bag (EFB) located on both the left and right-side consoles on the A220. EFB Controls MenuPower Off EFB: Click anywhere on the screen to turn back on Lock EFB: Return to Lockscreen Screen Brightness Slider: Adjust brightness of EFB screens Display Mode: Set a DARK or LIGHT theme on the EFB UI Panel States: Select any state to set aircraft systems accordingly Note: Click anywhere on the screen to exit the menu. SettingsSetting menu selector and Version Indicator Settings menu display. Aircraft Settings Weight Units: choose between Metric (KG) and Imperial (LBS) units for Aircraft Systems and EFB. IRS Align Time: choose between Realistic, Fast (60s) and Instant IRS alignment on first power up. Auto GPU Disconnect: automatically disconnects the GPU and Chocks whenever beacon lights are turned on. External VFX: hide any external condensation visual effects for extra performance. Pause at Top of Descent: automatically pauses the sim at the set distance prior to the FMS computed Top of Descent (TOD). SATCOM: toggles the option Satellite Communications equipment on the exterior of the aircraft Cabin Lighting: Allows you to set manual or automatic control of cabin lighting based on time of day. AP/AT Discon Protection: inhibits the automatic disconnection of Autopilot and Autothrust based on excessive turbulence or control inputs. Time Compression: selects the desired simulation rate (upto 4x) OVHD Light Switches Config: chooses whether the switches on the overhead panel should be moved upwards (UP ON) or downwards (DOWN ON) to illuminate the selected exterior light. Weathering: Set desired exterior visual weathering level. EFB Settings On-Screen Keyboard: enables a virtual keyboard when clicking on any data entry fields. Entry Mode Keybind: Set the keybind to toggle Entry Mode Entry Mode allows you to your physical keyboard for data entry into the FMS. Press the same key again to exit Entry Mode Note: While in “Entry Mode” all other control inputs to the sim are disabled. Exit entry mode to resume functionality. Audio Settings Noise Cancellation: to simulate usage of headphones that filter out certain engine and environment sounds, Sliders: To control volume levels of Engine, Environment and Rattle sounds. Callout Settings Select which altitude callouts you want to hear during approach and landing. 3rd Party Settings Streamer Mode: hides your Simbrief ID on the EFB Navdata Source: choose the navigation database used by the FMS Sim Default uses the simulator-provided data updated regularly. Navigraph uses the last installed data that requires an active Navigraph subscription to update. Note: Updates are done via the FMS Maintenance Data Load Menu, which is explained further in the next section. Use Navigraph Charts: toggle between LIDO and Navigraph Charts (MSFS24 Only)

The Synaptic A220 Navigation Display (ND) supports a highly detailed terrain map overlay that accurately simulates the various rendering behaviours of the real unit. This relies on data injection from a separate map-server app running alongside the sim. App InstallationFollow the instructions at https://docs.synapticsim.com/pilots/map-server to install the map server. Enabling Terrain Overlay on NDVia Dropdown Select the OVLY dropdown on the ND Tick the TERRAIN checkbox Via TERR Button Ensure MAP is displayed on atleast one INBD Display. Press the TERR button on the glareshield on either side of the cockpit.

Download the A220 Paintkit using the link below: Synaptic A220 Paintkit_1.0.1.zip V1.0.1 Changelog: Blender file is sectioned per texture material now Added wing reg decals Added Comp textures to all PSDs Added readme file

Download the attached Synaptic x iniBuilds A220 Manual A220_MSFS_Manual_v1.0.0.pdf For more systems information, check out the Synaptic Documentation https://docs.synapticsim.com/

The Synaptic A220 comes with a custom GSX Profile bundled in the Marketplace streamed/downloaded package already. However, if you encounter issues with GSX recognizing the aircraft type, you can install the linked GSX profile manually as a backup. Installation Extract the synaptic_a220 folder to %AppData%\Virtuali\Airplanes Uninstallation Delete the synaptic_a220 folder from %AppData%\Virtuali\Airplanes Synaptic A220 GSX Profile.zip

A220-300Click the image to add the airframe to your SimBrief!

@willwest43 If you have one, that also shows your control inputs simultaneously on screen would be ideal. Also mention the hardware you're using for control. You could use something like the input viewer from your toolbar to show inputs in real time. Enable the "Simple" layout with numbers as well for reference. Thanks!

Thanks will pass it on to the team for further evaluation.

Yes your submitted reports are under investigation, and any changes are subject to data validation. Changes to engine parameters or cruise pitch angles has effects across all phases of flight. Just to manage expectations don't expect a quick turnaround on this. Things you mentioned falling back on your legacy FSX knowledge are not directly applicable to how things work in MSFS24. (e.g. Table 1506 etc.) Thanks for your patience meanwhile!

Thanks will pass it on to the team.

Try again in 1.0.8 update and let us know please. Usage of Greater Circle distances is one of the updated items.

As mentioned above, we have been trying but don't have any viable workaround at the moment for what appears to be a platform-level bug with how its rendering the clickspots. Should we find one that works, it will be pushed via an update but barring that it remains an issue that needs addressing sim-side. Thanks!

A known issue since SU5 Beta, please see:

Now you can. Try on v1.0.9. If you do happen to get a crash, please follow this guide to report the CRASH variables as well.

What is WASM?The WebAssembly Module (WASM) is a container for running programmes written in other langauges (eg C/C++) that is then converted to native code ahead of time (as DLLs) during first launch (WASM Compilation). This helps improve performance for subsequent uses but causes longer load times on first launch. his also improves security of the sim and portability of projects across PC / Consoles. In case of issues, only the WASM crashes instead of the rest of the sim along side with it. This is why the sim and some functions may continue to work, however other systems and displays that use WASM on the aircraft become unresponsive or "freeze" in place with a red warning screen. So what to do in case of WASM crash?Do not close the sim/restart flight immediately Verify the WASM error message & crash LVARs Report the WASM error message & crash LVARs with reproduction steps using the guide below. Verify WASM Crash in SimStep 1. Enable Developer Mode FS24 Settings > General > Advanced Options FS20 Options > General Options > Developers Step 2. Enable the Console by pressing "~" key on your keyboard or using the Dev Toolbar at the top of the screen Step 3. Filter the Console by ❌Error messages only by clicking on ⚠️Warning and ℹ️Messages to disable them (remove blue box border around them). Step 4. Type 'WASM' in the search box. Find the WASM Error and Copy the message. Also take a screenshot of this console window for making a report. Step 5. Check the new CRASH LVARs via the Behaviours Menu. Also take a screenshot of this for making a report. Accessing Behaviours Menu FS24 Via the DevMode toolbar at the top, select Tools > Behaviours and navigate to the Variables tab. Uncheck "Only Show Variables get/set....". Type 'CRASH' in the search box and expand their name to display the values. Report WASM Crash on ForumStep 6. Paste the WASM Error message, screenshot of the Console and INI_CRASH LVARs obtained in Step 4 and Step 5 above into a forum post/discord message/ support ticket WASM Crash Report. Step 7. Take note of what you pressed or things you did, just before you noticed this crash happen. Step 8. Verify if you are able to repeat the crash by following those same steps. Step 9. Please provide the following information Aircraft: A300 PW Freighter Simulator: FS2024 Navdata Method: SIM DEFAULT or NAVIGRAPH BASE OFP: Include a PDF of your Operational Flightplan (OFP) if related to FMS/Route Procedures crashes WASM Error: The error you copied in Step 4 above Crash Variables: The variables you screenshotted in Step 5 above Specs: CPU, GPU and RAM of your system. Step 10. Include on your report a Screenshot / Video showing what you pressed/did just before the crash happened to give us more clues. Screenshot of the Crash Variables Steps on how to reproduce the crash so that we can try ourselves with debugging tools to identify the cause of crash. These types of WASM crashes are heavily dependent on the actions taken just before the issue occurs. Detailed reports of the exact steps leading up to the crash are extremely helpful, as if we’re able to reproduce the issue internally using the same sequence, our team can investigate, debug, and resolve it much more effectively.

This would be useful yes, along with exactly the airport at which you tried and with what approach. Normally if you're in ALT mode already, arming LOC then ILS should properly set the aircraft up for a GS intercept from below.

Try these: L:OVH_CPT_WIPER and L:OVH_FO_WIPER 0 = OFF, 1 = SLOW, 2 = FAST I dont have Axis and Ohs but checked via SPAD and both seem to be working. Yes they do work. The DEACT sticker is referring to the rain repellent switches, not the wipers themselves. Their clickspot however is currently affected by a platform level bug since SU5 beta that incorrectly scales the clickspots of certain types of XML interactions. The same was reported on A310 and taken by Asobo as a sim bug - basically the click spot boundaries have become too small / scale incorrectly with zoom levels, resolutions etc. In these instances the clickspot will always be exactly at the center of the switch. Move closer or zoom in if you're having troubles for the time being. You can confirm this by enabling Developer Mode > Tools > Behaviours > Debug > Interactions. You'll note that the interaction shows, and works as intended but the hitbox seemingly de-scales wrongly when the debug is disabled.

The display map will show at position 0,0 until Alignment is completed , AND MSU Mode Select knob is set to NAV, AND Execution of TK CHG in AUTO or MNL mode from 00 to 01. All of these are necessary to initialize the system. You can then re-center the map to your actual position by clicking the aircraft icon. Because when you spawn on the runway, it automatically aligns the INS to your present position. The map in the center is an INS DISPLAY MAP, its driven by coordinates from INS1, 2 or 3 respectively. Its not a GPS map that is always aware of your position. So when you spawn at a gate, cold and dark, it places the purple dot at 0,0 as it has no known position until the alignment and initialization process is completed as per above.

Once we get more clarity on the PS5 Marketplace and it's process we'll be able to say more but yes, we intend to support the platform with our addons. There is no ETA but I'm sure we'll make an announcement once that happens. Stay tuned to our socials or newsletter which you can sign up for at the bottom of our store page: https://inibuilds.com/