richboy2307

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.

Thanks, those features were deemed beyond the scope of this product line and the price is reflective of that. However we note the suggestion for future development.
As for the A380, expect features on par with the A350 at the very least, if not more :)
Thanks!

Hi,

No even at IDLE when stationary, a running engine can't give an EPR below 1.0 - which indicates that the total exhaust pressure precisely matches the ambient intake pressure. A flight idle of ~1.100 is pretty typical.

Noted.
For now, you can use independent axis for modulation of rev thrust within IDLE REV and MAX REV ranges after reverser engagement - they all toggle together from IDLE to IDLE REV and back.
In normal A-B flying, there are rarely situations that require engaging individual thrust reversers. Additionally, failure or abnormal situation simulations are not the primary focus of this product line hence why it was not a high priority during development.
You can actuate them in unison using the listed HOLD or TOGGLE commands below as of 1.0.6:


Depending on what you're doing you may need to adjust the trigger between BUTTON PRESSED, RELEASED or HELD accordingly. I use the Bravo myself and have it set to TOGGLE reverse thrust on one of the bottom detent buttons (26) on the throttle levers. This allows me to control the reverse thrust amount for each engine using independent throttle axes after having toggled it once. While they will toggle together, you can still apply asymmetric reverse thrust within IDLE REV to MAX REV range once you have independent axes assigned. The reversers are toggled back to forward IDLE thrust using the same button.

I could also set it to HOLD reverse thrust when held (bottom option), that way once I push it down into the detent, it engages max rev as long as the button remains active/held.

Hey @zbrainlezz
That is odd, I do have both and I'll check as well. I've been using mine bound via FSUIPC7 at the moment so I do know it can be controlled externally, but will see if can reproduce the above issue via SPAD specifically.

Based on video alone seems like while Bravo is active, its sending commands but once it stops giving commands, another device thats still at idle is then taking over perhaps?
Can you confirm there isn't another connected device that is being read by the sim (or SPAD) also sending thrust commands, thereby creating a conflict with each other?
Thanks!

The community identified a potential conflict with Twotter Revived mod that was preventing ENG 2 startup. If you use the mod, ensure you updated it to the latest version.

This one is kind of by design as a sim-ism for both stability and performance reasons.
The entire INS computations/detection logic is inhibited unless user does a TK CHG 0 (P.POS) to another waypoint to initiate it.

Thanks we'll investigate

@here
Mod Conflict
Can you please try with an empty community folder? Its possible there is some other mod installed that is now causing a conflict.
There was already one identified by the community (Twotter Revived) that was preventing ENG 2 startup. That mod itself has received an update which will prevent the conflict with Tristar (or any other addon), but its possible there are other mods influencing core sim functions even when their respective add-on is not loaded. So a conflict needs to be ruled out.
You need not uninstall any addons, simply rename your existing Community folder (e.g. _Community) and the sim will create a new empty one in its place on next start. Once you're done testing, delete the empty one and rename the old one to restore your addons.
Assistance Settings
Verify that all assistances are disabled. They have a tendency to reset after sim-updates even if you had previously disabled them.
These ones are known to conflict with logic
Automixture
AI Auto-Trim
Auto-Rudder
Disable Crash Damage (ticked = disabled)
Disable Aircraft Stress Damage (ticked = disabled)
Disable Engine Stress Damage (ticked = disabled)
Unlimited Fuel
No Repro
On our end we're not able to reproduce these issues starting the APU from C&D. Neither using the auto-flight engineer nor manually. See video attached on a streamed copy of 1.0.6.

1.0.6 - Starting from C&D manually - Standard
2026-05-18 23-42-12.mp4
1.0.6 - Starting from C&D via PFB FE Autocomplete - Cabin w/ Lounge
2026-05-18 23-49-46.mp4

Thanks will pass it on to the team for further investigation. Appreciate the references.

Hi Acceleration is planned for update 1.0.7.

@Joshua Green If you can, at the end of the flight look up these variables in dev mode - Tools > Behaviours > Variables tab > uncheck "Only show variables..." > search for "drift" :

Include your OFP as well, for devs to investigate further.

Thanks!

Hi
As Bunkie mentioned above, the HSI DIS/TIME Readouts are only driven by the INS Computers. They cannot display data from any other sources such as your GPS or NAV1/2 DME.
To use GPS Navigation, you have to
Import or manually enter your route into the GPS
Ensure CDI is set to GPS instead of VLOC

Set the RADIO/INS switch to RADIO

Set FD to ON and use VOR mode for guidance

On your HSI it will also read "GPS" to show you the source driving the HSI needle


I've done a number of flights already swapping between VOR, INS and GPS modes frequently across the same flight from C&D and haven't yet come across your issue.

Maybe a video from Cold & Dark till when you notice the issue can help assess if there is some bug or any kind of missed step during setup? You can upload to Youtube/GDrive and share link here in case file size is too large.

Hi @JaredGPW
Please try v1.0.6 and see if the issue persists?
We have reworked how HOLD THROTTLE REVERSE THRUST and TOGGLE REVERSE THRUST keybinds function and hopefully that resolves your issue?
Thanks!

Thanks we'll investigate. Its more likely SU5 as it changed emissive properties of materials again.

Now you can via RMT Entry Function.
For more info see this: https://forum.inibuilds.com/topic/36719-how-to-ins-remote-entry-function/

That would make sense, thanks will pass it on to the team.

Yoke AP Disconnect
The Autopilot Disengage button on the yoke is actuated via the AUTOPILOT OFF keybind. You need to press it a second time to cancel any AP DISC warnings.
Please verify the button you are using is mapped only to that keybind.
AP 1 Master Switch on Glareshield
The TOGGLE AUTOPILOT keybind is used to toggle the AP 1 Master Switch between the CMD and OFF positions. Note turning AP 1 Master to OFF via this keybind will trigger AP DISC warnings that must be further cancelled via the AUTOPILOT OFF keybind which actuates the Yoke AP Disconnect.
See for reference this post: https://forum.inibuilds.com/topic/36540-tm-mode-goes-to-000-epr-if-ap-is-off/#findComment-89422

As of 1.0.5 - no, only manual remote entry is supported across units.
In v1.0.6 - yes SB import remote entry to INS 1 / 2 / 3 is coming. That update is estimated to go live this week.
We appreciate the feedback and are working to add these to the manual as well as FAQ.
Remote Entry Function (RMT)
Due to the complexity of the original autofill procedure and common user difficulties when operating the INS, this feature has been simplified to provide a more intuitive user experience while preserving the intent of the real system.

The process generally works as follows:
Set the desired units to RMT mode (at least 2 required for this operation).
Enter waypoints manually in the transmitting (TX) unit using the standard procedure.
Each time a latitude or longitude is inserted (by pressing INSERT), the TX unit will automatically transfer that entry to all receiving (RX) units.

Remote Manual Entry Procedure (v1.0.5+)
Set INS 1, 2 and 3 MSU to STBY , ALIGN or NAV on the overhead panel
Set INS 1, 2 or 3 Mode to RMT (at least 2 units required for this function)
Set the Display Selector Switch to WPT on the Transmitting (TX) unit
Set WPT Selector Switch to any number from 1-9 on the TX unit
Enter Waypoint Coordinates on the TX unit
The entered waypoint LAT and LON will update automatically on your TX unit and any other Receiving (RX) unit set to RMT as you press INSERT.
Note: The waypoint will be entered into the same WPT number as selected on the main unit (i.e. if you populate WPT 3 on TX Unit, any other RX Unit will also populate its WPT 3 position)
Set INS 1, 2 and 3 Mode to AUTO or MAN for navigation.
In the example video I have remotely entered N3701.0 W00758.0 into WPT 3 from INS 2 (TX) to INS 1+3 (RX) at the same time via RMT function.
2026-05-12 04-52-20.mp4

Remote SB Import Procedure (v1.0.6+)
Set INS 1, 2 and 3 MSU to STBY , ALIGN or NAV on the overhead panel
Set INS 1, 2 or 3 Mode to RMT (at least 2 units required for this function)
Use Captain's PFB to import to INS 1 (or First Officer's PFB to import to INS 2)
The waypoints will be imported to INS 1 (or INS 2) and the other INS units set to RMT.
The auto-batch logic (if more than 9 waypoints on SB import), will apply to the main and any other RMT unit as well.
Set INS 1, 2 and 3 Mode to AUTO or MAN for navigation.
In the example video below I have remotely imported from the FO PFB to INS 2 (TX) and INS 1+3 (RX) at the same time via RMT function.
2026-05-12 04-13-23.mp4

Thanks passed on to the team.

Hi thanks we'll have a look. I can reproduce the same on my flights.

Thanks passed on to the team for further investigation.

Hi, can you please elaborate on the issue and provide any screenshot/video reference for what you're observing?

Also note you have to depress one of the 4 gear buttons (Left-Front, Left-Rear, Right-Front or Right-Rear) in order to see the temperature of the selected section. The sensor can only display temperature for one selection at a time.
The same is required for when conducting the TEST to see a rise by 100c for selected sensor.